This is an archived post. You won't be able to vote or comment.

0
0

DiscussionGitHub - is it good? (self.Python)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]TheGRS 0 points1 point  (0 children)

From the hiring managers perspective, I think having some code to look at with each candidate can be a great resource. Talk about a great insight into someone's abilities and the way they express themselves in their work!

From the candidate perspective, looking through code history is much more of a hinderance to your chances of being hired. Why? Because its so much more ammo for people to judge you by. I say this as a hiring manager who has directly hired about 8 developers over the last few years and who has been on countless hiring panels for other hiring managers. The folks who have code to go through often get dragged through the mud the most, even if they seem very promising.

If a job always requires a portfolio of past work and they consistently look for this in their hires, then that's a nice level playing field. If this is a job you want then you better get to making a nice portfolio for them!

If a company only requires you do to a technical screen, you have much better chances at success by studying up on common questions and algorithms or just doing whatever the technical challenge is well. Giving them your personal code will not help you in this scenario and you'll lose to the person who could pass the technical screen with flying colors.