Resume Summary or Objective? What to Put at the Top
The first two lines of your resume are the most valuable space you own. Here is what belongs there at each career stage — and the sentence to delete.
Most resumes open with a sentence that says nothing. "Seeking a challenging position in a reputed organisation where I can utilise my skills and grow with the company." It appears on an enormous number of Indian resumes, and it costs you the single most-read piece of space on the page.
The problem is not that it is badly written. The problem is that it is true of every applicant, so it distinguishes nobody.
Summary versus objective
- A summary describes what you have done and are good at. It looks backward at evidence. Use it when you have relevant experience.
- An objective describes what you want. It looks forward at intent. Use it only when your intent is not obvious from your history — a career change, a return after a break, or a relocation.
If you have relevant experience and you write an objective, you are spending your best space telling the reader something they can infer from the fact that you applied.
What a good summary contains
Three things, in roughly two lines: your role and level, the domain or stack you work in, and one concrete piece of evidence. No adjectives that cannot be verified.
Hardworking and passionate software professional with excellent communication skills seeking a challenging role in a dynamic organisation.
Backend engineer with four years on Java and Spring Boot in payments. Rebuilt a settlement job that had been failing nightly, cutting reconciliation time from six hours to under one.
The second version is not better because it is longer. It is better because every clause is checkable. A reader finishes it knowing what you do, where, and what you have actually fixed.
For freshers
You have no work history, so lead with what you do have: what you studied, what you have built, and what you are aiming at. Keep it specific to the application.
Fresh graduate looking for an opportunity to start my career in a good company and learn new technologies.
Computer science graduate (2026). Built and deployed a three-service inventory app in Django and Postgres for a campus project; comfortable with SQL, Git and REST APIs. Looking for a backend or full-stack role.
For career changers
This is where an objective genuinely earns its place, because the reader is about to wonder why a mechanical engineer is applying to a data role. Answer it in the first line, before they have to guess.
Name the transition, name what transfers, and name the evidence that you have already started. A stated intention with nothing behind it is weaker than no statement at all.
Rules that apply to all three cases
- Two to three lines. Anything longer is a paragraph and will be skipped.
- No first person pronouns. "Managed a team of six", not "I managed a team of six".
- Rewrite it per application. This is the one section worth retyping each time — it is short, and it is the part a reader is guaranteed to see.
- No adjectives you cannot support. "Detail-oriented" is not evidence; a defect rate is.
If you are unsure whether yours is working, read only the first two lines aloud and ask whether they would apply equally well to the other applicants. If they would, the space is being wasted.