Honestly, and I say this as someone who has been doing hiring lately and looking at a ton of resumes, I have *never *once looked at the “Objective” field on a resume and had my opinion swayed in a positive fashion - but there are plenty of times that I’ve thought someone’s objective was stupid, and it has hurt their chances at a position.
Really, I would leave it off. I don’t know if all hiring managers feel the way I do, but I dislike the field in general and the best thing you could do for a resume you gave to me would be to keep that off the resume. :-/
That’s the fun thing about it, you never know what the personal preferences of the people considering will be. In my opinion, ‘safe’ is getting rid of an antiquated and useless field - you want a good job and you want to learn new things and be the best you can be and… yeah, I assume that, I don’t care.
(And your biggest fault is that you are too committed to your work, right? :sure:)
[whisper]I think that’s a terrible question anyway, but you get the idea.[/whisper]
Wow so I finally disagree with you, curious to see how our relationship will progress after this :lol:
No seriously though, I used to do the interviews for people at my last job and even now I am interviewing people here and I can honestly say that stuff is important to me. Even though I know the objective is really bull****, I mean we all just want cool jobs and to make a lot of money right? Yeah, but humor me. Make me believe you actually do have an objective goal, and some do. My objective is real, it’s something like “to improve my existing Flash knowledge and take it to another level yada yada yada.”
I think leaving that out at for an entry level position may be fatal to some employers. If you have 5+ years experience and a strong portfolio/work experience you probably don’t need one.
Anyway that’s just my 2 cents ya heard!
[quote=Anogar;2341018]Honestly, and I say this as someone who has been doing hiring lately and looking at a ton of resumes, I have *never *once looked at the “Objective” field on a resume and had my opinion swayed in a positive fashion - but there are plenty of times that I’ve thought someone’s objective was stupid, and it has hurt their chances at a position.
Really, I would leave it off. I don’t know if all hiring managers feel the way I do, but I dislike the field in general and the best thing you could do for a resume you gave to me would be to keep that off the resume. :-/[/quote]
Haha, between our combined 12,000ish posts we had to eventually express different opinions. I still :love: you. :lol:
[quote=Digitalosophy;2341050]No seriously though, I used to do the interviews for people at my last job and even now I am interviewing people here and I can honestly say that stuff is important to me. Even though I know the objective is really bull****, I mean we all just want cool jobs and to make a lot of money right? Yeah, but humor me. Make me believe you actually do have an objective goal, and some do. My objective is real, it’s something like “to improve my existing Flash knowledge and take it to another level yada yada yada.”
I think leaving that out at for an entry level position may be fatal to some employers. If you have 5+ years experience and a strong portfolio/work experience you probably don’t need one.
Anyway that’s just my 2 cents ya heard![/quote]
I like the idea of an objective field - but to me it just feels disingenuous. The problem with them is that of all the resumes I’ve seen, I’ve never seen an objective that I couldn’t have written ***for ***the applicant based on their job title.
Oh, you’re applying for a Senior Web Developer position? Okay, I assume your objective is something like *“to further my skillset by expanding into new and emerging web technologies, work on new and exciting projects that push the limits of… etc, etc.”
*Ya know what I mean? Sure, you want to further yourself, your skills, you want to make more money, work on cooler projects, I think everyone does. So, okay, my point is that the objective field should tell the person reading it something they don’t know - and I’ve never really seen that. Tell me something new, and I’m sold on the objective field - I sure as heck don’t want to read that you want a good job and to learn cool things though.
I applied for a summer job, and a lot of the applications asked for an objective, and I just said that I wanted to make money for college. In this case the objective line tells the employer a lot.
[quote=Al6200;2341089]I applied for a summer job, and a lot of the applications asked for an objective, and I just said that I wanted to make money for college. In this case the objective line tells the employer a lot.
I now work at Arby’s.[/quote]
[ot]Alright, I say this with nothing but your best interests at heart: You are an idiot for working at Arby’s.
A quick glance through your post history shows that you aced your AP math exams, you have a decent grasp of Flash, you foolishly trust the FDA and its paid scientists (wait, that’s not related! Muahahah.)… Anyhow, you could be making twice what you’re currently making - as a production Flash developer or doing entry level HTML stuff for a small company. Use your skills, even if just for a summer before going off to college and becoming a real programmer / mathmetician / whatever.
Geez. Arby’s? Really? You make bad sandwiches for minimum wage instead of sitting at a comfy desk doing boring entry-level web development stuff? Dumb dumb dumb. Seriously.[/ot]
Back on topic, Arbys will hire anyone willing to stand around all day making bad sandwiches, I promise the ‘objective’ field didn’t influence their decision.
Yea listen to anogar, he is the reason I started looking for web design/development jobs. I am starting to get interviews and may be employed soon.
I plan to keep the nerdy abbreviations, because how do you unabbreviate php?? I read at like monster.com that using buzz words is important.
Also alot of sites say include lots of info, and lots of sites say keep it short and simple. I always liked the short and simple approach but am I hurting my self by doing this?
I think more job entries is always a good thing, if they’re even remotely related. I once saw a resume that included experience fixing the cranes on those machines where you put in the quarters and try to grab the stuffed animal thing… yeah, that’s not the sort of thing to put on your resume, but if it’s even slightly related toss it on there.
…Sorry I just hate when people spell it as one word… back on topic: Your resume looks good, I agree with the time period bit in months, etc… I also agree with the lack of personal skills not mentioned on your resume…
[quote=ajcates;2341110]Yea listen to anogar, he is the reason I started looking for web design/development jobs. I am starting to get interviews and may be employed soon.
I plan to keep the nerdy abbreviations, because how do you unabbreviate php?? I read at like monster.com that using buzz words is important.
Also alot of sites say include lots of info, and lots of sites say keep it short and simple. I always liked the short and simple approach but am I hurting my self by doing this?[/quote]
Short and simple is awesome, as long as you don’t leave anything out…
keep PHP, but OO is so unnecessary, and like someone else said, most of the time its HR sifting through piles of resumes, not the tech department… who eventually do get the resume (obviously) but anyways
[QUOTE=Anogar;2341098][ot]A quick glance through your post history shows that you aced your AP math exams, you have a decent grasp of Flash, you foolishly trust the FDA and its paid scientists (wait, that’s not related! Muahahah.)…[/ot][/QUOTE]:lol:
