The only exception would be if you are applying to very corporate places. They may request the resume to have specific information and be in a specific format, including the traditional "objective."
I disagree- I find the objective critical for younger applicants to have on their resume. It proves they can concisely define their what, why and where in a short statement. Thats demonstrAting clarity of thought, and understanding of job roles.
I think it depends on what context you're giving out resumes in. My school had job fairs every year, and I always had an objective (and no cover letter) for those things, but axed the objective and put in a cover letter for any firm I'm contacting in a more one-on-one way.
as a younger applicant (which i am) I find it harder to really have an objective except to learn the basics of design and the professional side of architecture.
Thats exactly what you put their while an intern. Maybe add to it briefly finish IDP req.
Cover letters get looked at once - then principles and managers pass the resume around - thats why the objective is eessentially your cover letter razor sharp short and focused.
as an employer, i can take "objectives" or not, depending on what's written. often, they're just so much self-serving BS and they come across as such. but, from time-to-time the candidate will craft a written objective that is both sincere and informative -- those are easy to spot and very helpful to me in deciding whether to go forward with the candidate or not. i like knowing what a candidate hopes to achieve over the next few years -- if that fits in with what we can offer, that's really useful information. if it doesn't fit in with what we can offer, it saves a lot of time, both for the candidate and for me.
my advice -- use an objective [u]only if you're willing to be honest -- don't just try to tell the hiring manager what you think (s)he wants to hear. but, if you're honest, you're also likely to have firms drop you from consideration fairly quickly if your objective doesn't sync with their needs.
Go with a 'summary' to get around the stigma of bad 'objective' statements. That way you can highlight where you've been (recent grad, # of years of experience, completed IDP, 1/2 done with ARE, etc..) and provide clues to where you want to go in the coming years (take over the world, etc.)
Need an "Objective" section in our resumes?
Simple question....Is it important for architects to put an "objective" in their resume. Is it too extraneous and could be covered in a cover letter?
Personal Objective? In the cover letter.
axe it and put that in the cover letter. it's too extraneous
Agreed.
I've always found "the objective" in the resume downright cheesy...and had a hard time keeping those people serious
thanks for the help guys, appreciate the time
Agreed, I've always hated the objective.
The only exception would be if you are applying to very corporate places. They may request the resume to have specific information and be in a specific format, including the traditional "objective."
I disagree- I find the objective critical for younger applicants to have on their resume. It proves they can concisely define their what, why and where in a short statement. Thats demonstrAting clarity of thought, and understanding of job roles.
I think it depends on what context you're giving out resumes in. My school had job fairs every year, and I always had an objective (and no cover letter) for those things, but axed the objective and put in a cover letter for any firm I'm contacting in a more one-on-one way.
as a younger applicant (which i am) I find it harder to really have an objective except to learn the basics of design and the professional side of architecture.
Thats exactly what you put their while an intern. Maybe add to it briefly finish IDP req.
Cover letters get looked at once - then principles and managers pass the resume around - thats why the objective is eessentially your cover letter razor sharp short and focused.
your resume pretty much gets looked at once too. it then gets looked at again as the interviewer reminds him/herself who you are.
as an employer, i can take "objectives" or not, depending on what's written. often, they're just so much self-serving BS and they come across as such. but, from time-to-time the candidate will craft a written objective that is both sincere and informative -- those are easy to spot and very helpful to me in deciding whether to go forward with the candidate or not. i like knowing what a candidate hopes to achieve over the next few years -- if that fits in with what we can offer, that's really useful information. if it doesn't fit in with what we can offer, it saves a lot of time, both for the candidate and for me.
my advice -- use an objective [u]only if you're willing to be honest -- don't just try to tell the hiring manager what you think (s)he wants to hear. but, if you're honest, you're also likely to have firms drop you from consideration fairly quickly if your objective doesn't sync with their needs.
Go with a 'summary' to get around the stigma of bad 'objective' statements. That way you can highlight where you've been (recent grad, # of years of experience, completed IDP, 1/2 done with ARE, etc..) and provide clues to where you want to go in the coming years (take over the world, etc.)
i figured "taking over the world" would be a good way to honestly tell them my desires.
Block this user
Are you sure you want to block this user and hide all related comments throughout the site?
Archinect
This is your first comment on Archinect. Your comment will be visible once approved.