Hacker News Reader

Hrm. I'm not looking, but I like reading these things. Regarding "Objective, seriously? It's not 1992 anymore", I've always put an objective on my resume. Typically something short and sweet, like "seeking a senior software engineering position solving challenging systems problems" or whatever. Is that not useful? I wouldn't want someone to read beyond the first couple lines of my resume if they're looking for a web developer or a finance manager.

View on HN

Think of it this way:

1) Your resume is sitting somewhere that it will be mixed with web devs and finance managers. Or...

2) Your resume is given to people who are hiring senior system software engineers.

Try to make sure #2 happens, which you should be doing anyways. And once that happens, the objective doesn't really matter much anyways.

Fair enough, but here's another example. Say someone is trying to move from IC to management. They might have no mgmt experience so they put "seeking engineering management position" as their objective. Is there a better way? The other traditional thing to do would be to explain this in your cover letter.

Edit: I get that you should be shopping it around and applying to various positions but it seems inevitable that a copy of your resume will get filed into countless HR databases. It seems rational to me to indicate what you're looking for on the resume.

Reply on news.ycombinator.com