yeungjai
Senior Member
- Joined
- Dec 13, 2010
- Messages
- 121
- Reaction score
- 0
I do technical recruiting, so I disagree with the 1 page resume statement (at least in certain contexts). For highly technical staff, there's just too much to put down. The nature of technical roles also lends itself to be easily searchable for key words and phrases. E.g.:
If you're a developer, I don't want to read "I developed web-based applications for XYZ". That's useless to me. I need to know whether you used J2EE, Java, .Net, or what-have-you because you either have it, or you don't and you can't BS it so don't have me waste my time trying to figure it out.
I know many recruiters who would likely disagree with me, but so long as content is relevant and concise, I'd rather see a longer resume than a shorter one. It's much easier for me to read through a thorough (and RELEVANT) account of what you've done than to have a whole bunch of gaps that would force me to find the time to get you on the phone to fill in those gaps. I'm not going to spend that time unless there is NOBODY else to consider. This includes your accomplishments, the hard skills, and environmental context (e.g. a Director-level role in a company of 100 is different from a Director-level role in a company of 10,000).
I also don't mind seeing 'objective' statements, so long as they're purposeful. Reading "I want to work with X company because they're a great place to work" is useless. "I want to obtain a position as a Financial Analyst" also doesn't say anything. Tell me in your objective not the role or the company you want, but the nature of the work you're looking for and what your value-prop is with respect to such work.
So, in brief, show:
Titles, dates of employment, company
Hard skills and niche but important tools used (everybody has Word, PP and Excel on their resume. If you want to put down Excel, show me you know more than how to write a sum function)
Key accomplishments, including leadership, turn-around situations, yada yada yada
Environmental context: e.g. Consulting function of a top 4 specializing in X offerings to Y industries
Description of core duties of the role, and preferably none of that operational crap like:
"Typed in code in a speedy and accurate manner".
Comments?
If you're a developer, I don't want to read "I developed web-based applications for XYZ". That's useless to me. I need to know whether you used J2EE, Java, .Net, or what-have-you because you either have it, or you don't and you can't BS it so don't have me waste my time trying to figure it out.
I know many recruiters who would likely disagree with me, but so long as content is relevant and concise, I'd rather see a longer resume than a shorter one. It's much easier for me to read through a thorough (and RELEVANT) account of what you've done than to have a whole bunch of gaps that would force me to find the time to get you on the phone to fill in those gaps. I'm not going to spend that time unless there is NOBODY else to consider. This includes your accomplishments, the hard skills, and environmental context (e.g. a Director-level role in a company of 100 is different from a Director-level role in a company of 10,000).
I also don't mind seeing 'objective' statements, so long as they're purposeful. Reading "I want to work with X company because they're a great place to work" is useless. "I want to obtain a position as a Financial Analyst" also doesn't say anything. Tell me in your objective not the role or the company you want, but the nature of the work you're looking for and what your value-prop is with respect to such work.
So, in brief, show:
Titles, dates of employment, company
Hard skills and niche but important tools used (everybody has Word, PP and Excel on their resume. If you want to put down Excel, show me you know more than how to write a sum function)
Key accomplishments, including leadership, turn-around situations, yada yada yada
Environmental context: e.g. Consulting function of a top 4 specializing in X offerings to Y industries
Description of core duties of the role, and preferably none of that operational crap like:
"Typed in code in a speedy and accurate manner".
Comments?