3 ms·
Great question. I'm okay with someone who doesn't have public code, although they will have to work a little harder to verify their skills match their story.
by stevepotter 1y ago
Great question. I'm okay with someone who doesn't have public code, although they will have to work a little harder to verify their skills match their story.
You have some public repos. That's plenty. Even some gists will work
I tell people all the time, if you want to make it easier to get hired, put some work online. This is especially helpful for those without great credentials or history. Take advantage of this, as it's not possible in many other professions.
- kinow 1y agoAgreed. Another thing that helps is writing. If you have a blog, it helps tremendously as it's possible to learn a lot from an engineer when the posts contain some thoughts about what that person learned or worked on, some opinions, techniques and tools used, etc. Even these Linkedin posts are fine, as long as it's not an ad to some tool, or just full of buzzwords. The kind of "behind the trenches" posts are great too, to explain something that happened in a project, a challenge you had, how you debugged a problem. This saves a lot of time in the interview as I would read it all and use that to discuss with the candidate.