How to write a resume summary, with examples for every stage

The summary is the two or three lines at the very top of your resume, right under your name. It is often the first thing a recruiter reads, and it decides how they read everything below it. A good summary tells them in a few seconds who you are, what you can do and why you fit this particular job.

Many Indian resumes still open with a career objective such as "Seeking a challenging position in a reputed organisation where I can utilise my skills". The problem is that an objective talks about what you want, while the recruiter is looking for what you offer. A summary flips that around, and it works for freshers as well as experienced candidates.

Do you need a summary?

Almost always, yes. It is especially useful when:

• You are a fresher and your relevant projects or internships sit lower down the page.
• You are switching careers and need to explain how your background connects to the new role.
• You have several years of experience across different roles and want to frame them around one direction.
• You are returning after a career break and want to lead with your strengths, not the gap.

Keep it short. If your summary runs past four lines, it stops being a summary and recruiters skip it.

A three-line formula

1. Who you are. Your role or target role, your level, and your main strength. For example: "Backend developer with three years of experience building payment APIs in Java."
2. Your proof. One or two specific achievements, projects or skills, with numbers where you have them.
3. What you bring to this role. A line that connects you to the job you are applying for. This is the line you change for each application.

Write it in a neutral, slightly clipped style without "I" at the start of every sentence. That is the convention on resumes, and it saves space.

Examples for different situations

Fresher, computer science

Computer science graduate (2026) with a strong base in Java, data structures and SQL. Built a library management system with Spring Boot and MySQL used by 300 students at my college, and solved more than 250 problems on coding practice platforms. Looking to start as a backend developer in a team that values clean, tested code.

Fresher from a non-computer-science degree

B.Com graduate with practical skills in Excel, SQL and Power BI. Analysed two years of sales data for a family distribution business and built a dashboard that cut monthly reporting time from two days to two hours. Seeking an entry-level data analyst role where business understanding and numbers both matter.

Developer with three years of experience

Java developer with three years of experience building and maintaining Spring Boot microservices for a fintech product with 2 million users. Reduced average API response time by 35% through query optimisation and caching with Redis. Interested in backend roles with ownership of high-traffic services.

Data analyst with two years of experience

Data analyst with two years of experience in retail analytics using SQL, Python and Tableau. Built the weekly performance reports used by regional managers across 60 stores and automated data pulls that saved the team about ten hours a week. Looking to grow into product analytics.

Manual tester moving to automation

QA engineer with two years of manual testing experience on web and Android apps, now automating regression suites with Selenium and Java. Wrote 120 automated test cases that run on every build, catching release-blocking bugs earlier. Seeking an automation testing role.

Career switcher

Mechanical engineer moving into software testing after four years in manufacturing quality control. Experienced in writing test procedures, root cause analysis and documentation; recently completed ISTQB Foundation and built a Selenium test suite for an open-source web app. Bringing a quality-first mindset to a junior QA role.

Returning after a career break

Frontend developer with four years of experience in React, returning after a two-year career break for family caregiving. Recently rebuilt my portfolio with Next.js and TypeScript and contributed fixes to two open-source UI libraries. Ready to rejoin a product team in a full-time frontend role.

Words to cut

Some phrases appear on so many resumes that recruiters no longer read them. Replace each one with evidence:

• "Hardworking and dedicated." Show it instead: a project you finished, a certification you earned while working, a deadline you met.
• "Passionate about technology." Name what you built with it.
• "Team player with good communication skills." Mention leading a team project or presenting to a client.
• "Seeking a challenging role in a reputed organisation." Say which role, and what you bring to it.

Tailoring your summary in two minutes

You do not need a new summary for every application. Keep a base version and adjust three things:

• Change the role in the first line to match the job title in the listing.
• Swap in the achievement most relevant to that job.
• Use one or two keywords from the listing that genuinely describe you. This also helps when recruiters search the company's applicant tracking system. Our guide to ATS-friendly resumes explains how that search works.

Common mistakes

• Making it too long. Five lines or more and recruiters skip straight past it.
• Promising what the rest of the resume does not show. If your summary says "expert in machine learning", the projects below need to back that up.
• Claiming things you cannot discuss. Interviewers often start with your summary. Every claim should be something you can talk about for two minutes.
• Using the same summary for very different roles. A summary written for a developer job will not convince a recruiter hiring an analyst.

Once your summary is ready, make sure the projects below it are just as specific. Read how to describe projects on your resume, and if you are a fresher, our section-by-section fresher resume guide.