this post was submitted on 20 Jul 2023
393 points (95.6% liked)
Programming
17484 readers
104 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What they're asking for is a public portfolio.
Obviously, you can't give them code that legally belongs to a past employer and they're not allowed to look to avoid accusations of copyright infringement.
Especially if they do any reverse-engineering for interoperability, there must be zero suspicion that they were inspired by code they're not allowed to use.
This is where open source contributions under permissive licenses come in.
Something shown to work in a real project is also viewed better than out of context code snippets.
When you're essentially saying you have nothing to show them, you're indistinguishable from someone who actually has nothing and is lying about their skills, so the onus is on the interviewers to vet you, which for various reasons may not be possible, so they'd rather just move on to someone with a clearly proven track record.
Ok but the original point still stands. Coding outside of work and at work is poor work life balance. Even my own projects I do are to learn not solve an actual problem in the world with code.
And a public portfolio is the CV that states "I worked for this company making thier products". They might ask for the specific products, but there's a chance some people never made public ones.
Github is for college and thesis projects. That's what most people have on there.
The correct answer to these recruiters is still not stated yet. When they say
People should answer
Indeed. A clearly proven track record is a given, in that I worked at software company x y & z for a number of years each as a developer in these technologies and with these good references. You don’t need to see my individual contributions to understand that holding several multi-year dev positions at enterprise software houses tells you a lot.
Tbh, if my track record is in question I don’t expect to be at an interview, I expect my CV to be on a no pile.
I think the real issue is that recruiters learn how to interview graduate junior dev candidates and apply it across the board. When you interview mid/senior devs with years of experience for senior roles which require years of experience, maybe “do fizzbuzz” and “show us your open source work” is a little patronising, no?
Might just be me tho, maybe I’m just a prick. Could be.