Re: Resume Beef

in reply to Resume Beef

I would hold off on adding code to a resume. Typically a hr-type person will screen a resume for keywords/skills. Since they are not technical they will not understand the code you are writing or even be able to tell what language it is in. You may- want to have some available for a second round interview or demonstartions of projects that you have done. If you are lacking "beef" try joining an open source/non-profit project and using that for beef. Working with others definitely helps and may give you additional skills that you didn't even know you had.

"The social dynamics of the net are a direct consequence of the fact that nobody has yet developed a Remote Strangulation Protocol." -- Larry Wall

Comment on Re: Resume Beef

Replies are listed 'Best First'.
Re: Re: Resume Beef by buckaduck (Chaplain) on Feb 27, 2002 at 16:38 UTC
Typically a hr-type person will screen a resume for keywords/skills And in fact if they have an automated process of scanning and OCR, they may be surprised at the "keywords" retrieved from your code: "kill", "warn", "die", ... P.S. How would a HR person interpret the phrase `use strict` ? buckaduck	[reply] [d/l]
Re: Re: Resume Beef by perlmoth (Hermit) on Feb 27, 2002 at 16:37 UTC
Let me second this. Your resume is the wrong place to put code. It looks like noise to the hiring people and will be filtered out (and not just by HR, but engineering managers who have to go through dozens or hundreds of resumes too). Your resume should state your accomplishments as well as your skill-set. You should also keep it to one page, two at most.	[reply]

In Section Meditations