I've seen lots of resume which has it's first section called "Objective" which (usually) states your career plan as to what you want to be, and what kind of position you're looking for.
I find this section pretty much useless (most often), as it doesn't add anything interesting for a potential employer. It usually starts with:
- Seeking a software developer position ...
- I aspire to obtain a position ...
- I would like to take the post of ...
- My objective is to utilize my skills and knowledge ....
Irrespective of how sophisticated and honest they may be, they end up focusing on the need of the job seeker rather than the need of a potential employer. When you apply for a software developer position, the very act of sending-your-resume-to-the-hiring-team says that you're looking for a software developer position, then why write it in the resume also? Moreover, the so-called objective can reliably be inferred from the other sections, such as skill set, work experience, education etc.
I've never seen any section which highlights the most important keywords which might interest a potential employer. So I think it is a good idea to put a "Summary" instead of "Objective" (i.e as first Section of your resume). This section should summarize your all other sections and especially your experience in years in few words.
Software Developer with 5 years of industry experience with C++, C#, WPF, WCF, and other Microsoft technologies.
Anybody who likes this summary, will surely read the rest of your resume, because even though the summary is one-line, it answers many questions useful to a potential employer:
- What position? Software developer.
- How much experience? 5 years experience.
- What skill set? C++, C#, WPF, WCF, and other Microsoft technologies.
Now someone might say that the same information can be put under objective section also. I would say the Objective sections are notoriously infamous that many hiring team don't read them at all. I, for one, didn't read when I was given this task to filter resumes in my office, and I'm sure many don't either. In addition to that, the statement fits more in "Summary" section, rather than in "Objective".
Summary could have bullet points, optionally can include the kind of work you're looking for (in case if it is not obvious from your resume OR you would like to take different kind of challenges from your previous job). For example,
- Software Developer with 5 years of industry experience with C++, C#, WPF, WCF, and other Microsoft technologies.
- Have interest in designing and crafting efficient modern softwares, and learning new technologies and tools if need arises.
So my question is :
Is it a good idea to put Summary in place of Objective in your resume?