How programmers should write their resumes
doesnotcompute.biz
How programmers should write their resumes
1–10 of 74 posts
Re: How programmers should write their resumes
#2I rarely agree with the author of this blog post :
- "Don't bother mentioning your G.P.A." : I know firms are only interested in your diploma's name, but it can be an advantage to mention you passed summa cum laude whereas another barely made it by coasting and offloading his share of works on others students (which is unfortunately a useful skill in the workplace).
- "Don't bother using verbs other than "made" for programming projects." : I completely disagree. Using the exact verb to describe your work show your understanding of the tasks which fell onto you, but also your writing proficiency (which will be reflected in the quality of your comments).
- "Answer this: where can I look at some stuff you built?" Github is a nice place to show-off your skill but not everyone is interested in open-source side-projects, so it's not a silver bullet.
- "Answer this: which languages and databases do you prefer?" Well, if you want to pass the résumes' automatic parser used by the HR dep., you need to stuff your application with keywords anyway.
- "Don't bring up your hobbies." : This one really raised my hair. Not everyone is tweeting every part of their life (I certainly don't) so hobbies are a great way to lighten the mood during the interview and assessing the interviewee's personality.
Re: How programmers should write their resumes
#3Not into GitHub? Register a memorable domain and throw together a to-the-point portfolio page instead.
Or use another goddamned software hosting service? I'll never understand this sense of GitHub supremacy amongst trendies.
Otherwise, the advice in general is subpar.
Re: How programmers should write their resumes
#4I rarely agree with the author of this blog post : - "Don't bother mentioning your G.P.A." : I know firms are only interested in your diploma's name, but it can be an advantage to mention you passed summa cum laude whereas another barely made it by coasting and offloading his share of works on others students (which is unfortunately a useful skill in the workplace). - "Don't bother using verbs other than "made" for p…
> Answer this: where can I look at some stuff you built?
You can't, it's closed source proprietary internal stuff. And I'm not allowed to talk too much about it because I had to sign a NDA.
Re: How programmers should write their resumes
#5Not into GitHub? Register a memorable domain and throw together a to-the-point portfolio page instead. Or use another goddamned software hosting service? I'll never understand this sense of GitHub supremacy amongst trendies. Otherwise, the advice in general is subpar.
Is having a portfolio website necessary now-a-days? What does HN think?
Re: How programmers should write their resumes
#6I rarely agree with the author of this blog post : - "Don't bother mentioning your G.P.A." : I know firms are only interested in your diploma's name, but it can be an advantage to mention you passed summa cum laude whereas another barely made it by coasting and offloading his share of works on others students (which is unfortunately a useful skill in the workplace). - "Don't bother using verbs other than "made" for p…
> Answer this: where can I look at some stuff you built? You can't, it's closed source proprietary internal stuff. And I'm not allowed to talk too much about it because I had to sign a NDA.
I don't have NDAs but I have the same kind of problem - lots of things I've done have been internal tools/systems which aren't visible or wouldn't make sense to anyone outside the relevant companies.
Re: How programmers should write their resumes
#7Earlier quoted context omitted.
> Answer this: where can I look at some stuff you built? You can't, it's closed source proprietary internal stuff. And I'm not allowed to talk too much about it because I had to sign a NDA.
I don't have NDAs but I have the same kind of problem - lots of things I've done have been internal tools/systems which aren't visible or wouldn't make sense to anyone outside the relevant companies.
I see the same but the job hunt seems to favor OSS. if you can't share code you write at work then the other option I'd to give up free/family time to do some side project you can share.
Re: How programmers should write their resumes
#8I rarely agree with the author of this blog post : - "Don't bother mentioning your G.P.A." : I know firms are only interested in your diploma's name, but it can be an advantage to mention you passed summa cum laude whereas another barely made it by coasting and offloading his share of works on others students (which is unfortunately a useful skill in the workplace). - "Don't bother using verbs other than "made" for p…
> Answer this: where can I look at some stuff you built? You can't, it's closed source proprietary internal stuff. And I'm not allowed to talk too much about it because I had to sign a NDA.
Either that, or it's code that runs machines that most people haven't even heard of. Not everyone builds web-apps for a living.
Re: How programmers should write their resumes
#9Don't call yourself a programmer.
Re: How programmers should write their resumes
#10I rarely agree with the author of this blog post : - "Don't bother mentioning your G.P.A." : I know firms are only interested in your diploma's name, but it can be an advantage to mention you passed summa cum laude whereas another barely made it by coasting and offloading his share of works on others students (which is unfortunately a useful skill in the workplace). - "Don't bother using verbs other than "made" for p…
> Answer this: where can I look at some stuff you built? You can't, it's closed source proprietary internal stuff. And I'm not allowed to talk too much about it because I had to sign a NDA.
This. And while learning is important, I really am getting tired of the bullshit line about everyone needing open-source side projects (and this is coming from a guy who enjoys side projects). How many other professionals need side projects for legitimization? My mechanical engineering friends build stuff too, but no one's expecting them to bring in a home-made contraption for their interviews.