The summary is the most-read and worst-written part of a resume. Most are four lines of adjectives that would fit any candidate in any industry — which means they carry no information at all. These do not.
It has one job: make the reader want to read the next section. It is not a mission statement, it is not a list of your qualities, and it is not the place to say you are a hardworking team player with excellent communication skills — because the person reading it has seen that sentence four hundred times and it has never once been false.
A working summary usually contains three things: what you do and for how long, the specific domain or context, and one thing that is true of you and not of the next candidate.
The test: if you could paste your summary onto a stranger's resume in the same job title and nobody would notice, it is not a summary. Rewrite until it fails that test.
Backend engineer with four years on payment systems in Java and Postgres. Spent the last two on a settlement service handling about ₹40 crore a month, and rewrote its retry logic after an outage showed me why the old one was wrong.
Why it works — Names the domain, the stack and one specific thing you own. The admission of a failure that taught you something is unusual and reads as senior.
Final-year computer science student looking for a first backend role. Comfortable with Java and SQL, and happiest when a problem has a clear input and output. Built two projects that other students actually used, not two that existed for a grade.
Why it works — Freshers have no experience to summarise, so summarise disposition instead. The last clause quietly separates you from most of the pile.
Analyst sitting between marketing and finance at a D2C brand, working mostly in SQL and Power BI. Most of my job is answering why a number moved, which as often as not means discovering the tracking was broken.
Why it works — Describes the actual job rather than the job title. Hiring managers recognise their own team in this and read on.
Business analyst across retail and fintech, translating between operations people who know the problem and engineers who will build the fix. Led requirements for an order management rebuild now used daily by 400 store staff.
Why it works — 'Translating between' is the whole role in two words, and the number at the end proves the scale without a paragraph.
Project manager with eight years delivering software for regulated clients — banking and insurance — where the hard part is rarely the build and usually the sign-off. Ran a 14-person programme to a fixed regulatory deadline with no scope carried over.
Why it works — Naming the hard part correctly is a credibility signal. Anyone who has done this work agrees with the second clause immediately.
Performance marketer running paid search and social on about ₹12 lakh a month for an ed-tech brand. Used to being measured on cost per enrolment rather than impressions, and comfortable killing campaigns that only look good in a dashboard.
Why it works — Budget size gives scale, the metric gives seriousness, and the last clause says you will not defend vanity numbers.
Writer producing long-form and product copy for B2B SaaS, around 12 pieces a month. Two years of it taught me that the research call with a customer is worth more than any amount of rewriting.
Why it works — A specific, slightly opinionated lesson beats 'excellent written and verbal communication skills' every time.
HR generalist closing 30–40 roles a year for a 180-person services firm, plus onboarding. Best at the coordination nobody enjoys — panels, offers, first-day logistics — and at spotting where the process is losing candidates.
Why it works — Volume plus headcount frames the role instantly. Claiming the unglamorous part is disarming and true to the job.
Accountant handling books, GST and TDS for a manufacturer turning over about ₹28 crore. Brought month-end close from day 12 to day 6 by moving vendor reconciliation weekly instead of leaving it to a month-end scramble.
Why it works — A summary can carry one result if it is the right one. Close timing is the number every finance lead cares about.
B2B SaaS sales into logistics, deals around ₹4 lakh ARR on two to four month cycles, mostly outbound. Closed ₹1.9 crore across 21 accounts last year at 112% of quota.
Why it works — Deal size, cycle length, motion and attainment. A sales leader can price your experience against their market from this alone.
Operations manager for a 60-person warehouse and last-mile team doing 4,000+ grocery orders a day. Took on-time delivery from 87% to 96% while bringing cost per order down ₹9 — and rider attrition down with it.
Why it works — The clause after the dash is the one that matters. It answers the objection a good hiring manager was already forming.
Support specialist on a consumer fintech app, around 60 tickets a day across chat and email, and the escalation point for payment failures. Held CSAT at 4.7 while handle time came down from 9 minutes to 6.
Why it works — Two metrics that usually move in opposite directions, held together. That tension is what makes the claim interesting.
Designer working across packaging and social for an FMCG brand — as much the 60-SKU grid work as the campaign work. Built the template system that took new artwork from three days to four hours.
Why it works — Acknowledging the boring half of design signals someone who ships, not just someone with a nice portfolio.
Secondary science teacher, nine years, currently head of the Class 9 science team. Built the digital lesson library the school now runs on and trained 22 colleagues onto it.
Why it works — Teaching resumes are often duties-only. The second sentence turns it into evidence of initiative and reach.
Mechanical design engineer in automotive components, five years on sheet metal and plastic parts from concept to tooling release. Owned 14 parts through PPAP with no launch delays attributed to design.
Why it works — Domain-specific language proves membership. 'No launch delays attributed to design' is precise and defensible.
Site engineer on residential builds, three years, mostly RCC structure work and coordinating between contractors and the consultant. Ran the pour schedule on a 14-floor tower that finished structure two weeks ahead.
Why it works — Site experience is best evidenced by a schedule fact. Everything else on a civil resume is easy to claim.
Staff nurse with six years in a 40-bed medical ICU, comfortable with ventilated patients and as the person the new joiners come to on a night shift.
Why it works — Unit type and bed count are the specifics clinical recruiters read for. The last clause is quiet, credible seniority.
Nine years teaching secondary science, now moving into instructional design. The last two of those were spent building the digital lesson library my school still runs on, which is what made me want to do this full time.
Why it works — It states the switch openly rather than hoping nobody notices, and gives a reason that is a fact rather than a feeling.
Product manager with five years in consumer apps, returning after a two-year caregiving break. Spent the last six months of it back in the tools — shipped a small side product and completed a data analytics certificate — and I am ready for a full-time role.
Why it works — A gap explained in one clause stops being a question. Refusing to explain it is what turns it into one.
Commerce graduate looking for a first role in finance operations. Interned two months at a CA firm doing GST return prep, and I am the person my classmates sent their Excel to when it broke.
Why it works — The second half is specific, human and true for a lot of people — and it says more about aptitude than any adjective would.
Freelance web developer for three years, 20-odd client projects in React and WordPress, now looking for a team. Freelancing taught me to scope carefully and say no; I would like to work somewhere I can go deeper than a two-month engagement.
Why it works — Names the strength freelancing builds and the reason for leaving in the same breath, which pre-empts the obvious interview question.
QA engineer with two years on a consumer app, mostly manual with growing automation in Cypress. Wrote the regression suite that cut pre-release testing from two days to half a day.
Why it works — Shows direction of travel — manual moving to automation — which is what QA hiring managers are assessing.
Supply chain planner for an apparel brand, handling demand planning across 900 SKUs and four warehouses. Brought forecast accuracy from 61% to 78% by weighting recent sell-through more heavily than last year's curve.
Why it works — SKU and warehouse counts set the scale; the method clause shows you understand the model, not just the tool.
EA to a CEO for six years at a 300-person company — calendar, board pack coordination, travel, and being the filter for a hundred requests a week. Trusted with the things that cannot be dropped.
Why it works — The final short sentence does more than a list of tools. For this role, trust is the qualification.
Once the summary is written, check the whole document with the resume checker, and if the rest of the page needs the same treatment, the full worked examples show the bullet points in the same style.
Short, practical guides — pick the one that matches where you are stuck.
Browse all 20 templates