Kavya's resume, whole
Here is everything above on one page: one column, contact details in the body, legal-style company names, designation before working title, months on every role, the date on the same line as the role, a separate skills line, and no photo, icons or CGPA. Every name, company, number, phone number and email in it is invented.
Kavya has six years and two months (Aug 2020 to Oct 2026), which puts her in the judgement band of the length rule above, and she stays at one page for three reasons. She has two employers, not four, so nothing old needs a second page. Every bullet passes the bullet check. And she has no system she designed that other teams depend on, and no engineer she hired, so a second page would hold more of the same evidence, not new evidence of scope. When she has one of those, the second page earns its place; Meera's resume, below, shows what goes on it.
INVENTED example · a one-page resume 2 min
KAVYA RAGHUNATHAN
Senior Software Engineer | Payments backend | 6 years
Bengaluru, India | kavya.raghunathan@example.com | +91 90000 00000 | linkedin.com/in/example-kavya
SUMMARY
Backend engineer who owns refunds and settlement for 40 merchants at a payments company. Event-driven systems on Kafka, Java and Spring Boot; reliability and data correctness for money movement.
EXPERIENCE
Halcyon Payments Private Limited, Bengaluru
Senior Software Engineer (working title: Backend Lead, Settlements) | Apr 2023 - present
- Moved refund processing from a nightly batch to Kafka events; refunds that took about a day now complete in minutes for 40 merchants. Led design and rollout with two engineers.
- Cut p99 latency of the order-status API from 900 ms to 300 ms by replacing per-request database reads with a Redis cache keyed by merchant; measured over 30 days of production traffic.
- Cut pages from the payments queue consumer from about 12 a month to 3 by adding idempotency keys and a dead-letter queue; wrote the post-mortem for the two worst incidents.
- Extracted the settlement module from a Java monolith into its own service (own database, REST API plus Kafka consumer); 4 of 11 releases afterwards needed no change to the monolith. One of three engineers on the project; owned the data migration.
- Reviewed about 15 pull requests a week for a team of five; wrote the service's on-call runbook, now used by two other teams.
- Introduced a PR-description and test-scaffold workflow using an AI coding assistant; engineers kept all review rights; median PR cycle time fell from 31 to 22 hours, defect escapes flat.
Brightloom Commerce Technologies Private Limited, Pune
Software Engineer | Aug 2020 - Mar 2023
- Built the order-export service (Java, Spring Boot, PostgreSQL) used by 120 sellers; replaced a cron script and cut failed exports from about 6% to under 1% of runs.
- Reduced checkout API timeouts from 2.1% to 0.4% of requests by adding connection-pool limits and a circuit breaker on the tax-calculation call; verified with two weeks of load-test and production metrics.
- Wrote 40+ integration tests with Testcontainers for the pricing module; the module's regression bugs in production fell from 9 in the half-year before to 2 in the half-year after.
- Mentored two interns for a quarter; both received full-time offers.
SKILLS
Languages: Java, Python, SQL. Frameworks and data: Spring Boot, Kafka, PostgreSQL, Redis.
Infrastructure: AWS (EC2, SQS, RDS), Docker, Kubernetes basics, Terraform basics, GitHub Actions.
Practices: idempotency, event-driven design, observability (Prometheus, Grafana), test automation.
EDUCATION
B.E. Computer Science, Western Ghats Institute of Technology, Pune | 2016 - 2020
The contact line is fake on purpose: example.com is a domain reserved for examples, and the phone number is a placeholder. The page was print-tested for this lesson: set alone in 10.5-point Georgia with 16 mm margins on A4, it fits on one page, with the last line about 77 per cent of the way down the printable area. Note what is not there: no objective, no photo, no "declaration", no skill bars, and no tool that she could not defend for half an hour.
The same PDF through pdftotext gives its first ten lines in order: name, headline, contact, then each heading followed by its content, and the role's dates on the role's own line. Lines are cut at 62 characters to fit this page:
Code, 10 lines
KAVYA RAGHUNATHAN Senior Software Engineer | Payments backend | 6 years Bengaluru, India | kavya.raghunathan@example.com | +91 90000 0 ... SUMMARY Backend engineer who owns refunds and settlement for 40 mercha ... systems on Kafka, Java and Spring Boot; reliability and data c ... EXPERIENCE Halcyon Payments Private Limited, Bengaluru Senior Software Engineer (working title: Backend Lead, Settlem ... Moved refund processing from a nightly batch to Kafka events; ...
Next stop: A senior resume: Meera, ten years, 3 min
A senior resume: Meera, ten years
Kavya's page proves a strong six years. A senior page has to prove something different, and in the same space. The reader at 8 to 12 years is not asking whether you can build; they are asking what you decided, who you took with you, and what was still true a year later.
Meera Subramanian is invented, and so are her employers, projects and every number. Her ten years include a services firm, a 14-month stint that ended when a product line closed, and a move into a product company. At ten years the page runs to two; the author's reading, consistent with the rule given earlier in this lesson, is that cutting a decade to one page cuts the scope evidence a senior reader came for. Only the first page and the top of the second are shown.
INVENTED example · a senior resume 2 min
MEERA SUBRAMANIAN
Lead Engineer | Payments ledger and settlement | 10 years
Bengaluru, India | meera.subramanian@example.com | +91 90000 00001
SUMMARY
Designed and leads the ledger and settlement platform at a payments company: 22 million postings a day, three dependent teams. Designs the system, hires for it and owns its on-call. Java 21, Kafka, PostgreSQL, AWS.
EXPERIENCE
Larkspur Payments Private Limited, Bengaluru
Lead Engineer (working title: Tech Lead, Ledger) | Apr 2023 - present
Senior Software Engineer | Feb 2020 - Mar 2023
- Designed the ledger-posting service that replaced two batch jobs: 22 million postings a day, 1,800 postings a second at peak, 99.95% monthly availability target; wrote the design doc, reviewed by three teams, and chose an outbox over dual publishing to keep postings and events consistent.
- Led the cutover with four engineers across two teams: six weeks of dual writes, then zero unexplained differences on a reconciliation of all postings before switch-off; no customer-visible incident. Reconciliation breaks stayed under five a month for the twelve months after.
- Hired three engineers (interviewed about forty candidates); two were promoted a level within two years, one now owns the refunds consumer.
- Set the on-call rotation for the platform and cut pages from about 20 a month to 4 by adding idempotency keys and alert thresholds tied to the availability target; the runbook is used by two other teams.
- Cut cloud cost of the posting path by 28% (about 9 lakh a month) by moving a hot read from the primary database to a cache; measured against the prior quarter's invoice.
Nimbus Cart Private Limited, Pune
Software Engineer | Dec 2018 - Jan 2020 (product line closed by the company)
- Built the catalogue-search service (Java, Elasticsearch) used by 60 sellers; when the company announced the product line's closure in Aug 2019, documented the service and handed it over before the line shut, then left in Jan 2020.
Corvid Infosystems Limited, Chennai (client: a UK retail bank, name under NDA)
Software Engineer | Aug 2016 - Nov 2018
- Owned the card-dispute batch for a bank's retail platform, a module of 40,000 lines; cut its nightly run from 4.5 hours to 70 minutes by partitioning by account range.
EDUCATION
B.E. Information Technology, Cauvery Institute of Technology, Chennai | 2012 - 2016
Gave up / revisit when / signal (Meera's page). Gave up: the client bank's name (under NDA) and a skills list longer than one line. Revisit when: she applies where the NDA client is the draw, in which case she asks the recruiter on a call what may be named. Signal: each bullet carries one of scale, decision, people or durability. Cost. The cache bullet states its saving as 9 lakh a month, checkable against an invoice; a bullet without a number would not.
Next stop: Hops, stints and seniority words, reference checks, 2 min
Hops, stints and seniority words, reference checks
Hops, stints and a move from services to product
The author's reading, with no source tested: a short stint is a line, not a paragraph. Put the months on the role, add the cause in brackets only if it is a fact a letter or reference would bear out, and keep the explanation for the call (lesson 4 has Meera's answer to "why 14 months?"). A services role needs one product-style bullet that shows ownership: Meera's batch cut states a module, a size and a before-and-after, and the client is named by sector because of the NDA. Two moves inside the same company belong on the same entry with both dates, as above, so the recruiter does not read one stay as a hop.
Seniority words a recruiter searches
The earlier search section shows keywords found as plain words. At senior level the words change: "designed", "tech lead", "lead", "architecture", "on-call lead", "hired", and the domain terms. Use a title only if it is true, and put your working title next to your designation, as Meera does. A recruiter filtering on a title such as "Lead Engineer" or on a year range cannot find "Senior Software Engineer II" unless the lead word is also in the profile. This is the author's reading of how the filters in the table above work.
Reference checks: prepare them like a bullet
A reference is asked about the same things a bullet claims. The author's reading, with background-check vendor pages as the only source (listed below): choose two people who saw the decision and the result, usually a former manager and a peer or report. Ask them first. Send them the three bullets you most want checked, with dates, and tell them which parts you led and which you did not. Do not coach their words. If your best referee is your current manager and you have not resigned, say so to the recruiter and give a former manager instead; the check commonly follows the offer, not the screen.
Next stop: Tailoring one resume to one posting (worked example), 3 min
Tailoring one resume to one posting (worked example)
Keep a base version holding every bullet you might use, Kavya's resume plus the bullets that did not fit. For each application, move the three bullets closest to that team's work to the top of the current role, and use the words in the posting's qualifications where they are true of you. Amazon's recruiters say the same. Reorder your history; do not rewrite it.
One worked case shows what "reorder, do not rewrite" changes and what it leaves alone.
INVENTED example · one posting, one tailored resume 3 min
Kavya applies to an invented posting, PO-207, Senior Software Engineer, Payments, at an invented company, Tamarind Pay, in Bengaluru. Its qualifications, in the order printed:
PO-207 Senior Software Engineer, Payments (Tamarind Pay) Basic qualifications 1. 5+ years building backend services in Java or Kotlin 2. Event streaming in production (Kafka or Kinesis) 3. Idempotent APIs for money movement Preferred qualifications 4. Reconciliation or ledger systems 5. Tier-1 on-call ownership 6. PostgreSQL at scale; AWS
She marks each line true, partly true or not true of her, from her base file. Line 1: true for Java, not Kotlin. Line 2: true for Kafka, not Kinesis. Line 3: true, the idempotency-key bullet. Line 4: partly; her base file records that the settlement migration was signed off by a full reconciliation of settlement records, but she has never built a ledger. Line 5: true, the pages bullet and the runbook. Line 6: true, PostgreSQL at Brightloom and AWS in her skills. Then she changes order, and words only where they are true:
| Part of the page | Base version | For PO-207 |
|---|---|---|
| Headline | Senior Software Engineer | Payments backend | 6 years | Senior Software Engineer | Payments backend: refunds, settlement | 6 years |
| Summary, second sentence | Event-driven systems on Kafka, Java and Spring Boot; reliability and data correctness for money movement. | Idempotent, event-driven services on Kafka and Java; reconciliation and data correctness for money movement. |
| Bullet 1 | Refunds moved to Kafka events | Unchanged (answers posting line 2) |
| Bullet 2 | p99 latency, 900 to 300 ms | Pages cut from 12 to 3 with idempotency keys (was bullet 3; lines 3 and 5) |
| Bullet 3 | Pages, 12 to 3 | Settlement extraction, with "owned the data migration" made "owned the data migration and its reconciliation sign-off" from the base file (was bullet 4; line 4) |
| Bullet 4 | Settlement extraction | p99 latency (was bullet 2; no posting line asks for it) |
| Skills, first line | Java, Python, SQL; Spring Boot, Kafka, PostgreSQL, Redis | Java, SQL, Python; Kafka, PostgreSQL, Spring Boot, Redis |
Not changed: titles, employers, dates and every number. Not added: Kotlin, Kinesis and the word "ledger", because none is true of her. Posting line 1 says "Java or Kotlin", and Java meets it; if a recruiter asks, the answer is one sentence: "Java, not Kotlin yet." (Lesson 4's "Six more questions real screens ask" has a fuller script for a stack mismatch.)
The profile. On Naukri she orders her key skills as Kafka, Java, PostgreSQL, idempotency, reconciliation, Spring Boot, AWS, and her headline reads: "Senior Software Engineer, payments backend, 6 years | Kafka, Java, PostgreSQL, Spring Boot, AWS | Owns refunds and settlement for 40 merchants; moved refunds from a nightly batch to Kafka events". The profile is searched by every recruiter, not only Tamarind's, so, as the author reads it, change it only with words true of every role you are targeting: tailor the resume to a posting, and the profile to the search you want to appear in.
Gave up / revisit when / signal. Gave up: the latency bullet's place near the top, and any claim to Kotlin. Revisit when: a posting leads with latency, or she has shipped Kotlin. Signal: her top third answers three of the posting's lines in its own words, and nothing on the page is new to her base file.