How to Write a Good Resume

Course Content

How to Write a Good Resume

15 sections · 30 lessons

Summaries and the anatomy of an experience entry

Section 4 settled the mechanics. This section builds the content, one part of the page at a time, in the order a reader meets them: the optional summary at the top, then the experience entries, then the bullets inside them, and finally the supporting sections below.

This first lesson covers the two structures that frame everything else. A summary, when you need one, frames the whole page. A context line frames each role. Both exist to answer a question before the reader has to ask it.

Summary or objective: when to include one

A summary is two to four lines at the top of your resume describing who you are professionally. Most engineers should not have one.

When a summary earns its spaceInclude one• Switching careers into engineering• Returning after a long break• Relocating to a new market• Senior scope not obvious from titlesSkip it• Your titles already say the level• It would repeat the first bullet• It lists adjectives, not evidence• It costs a third of page one
The default is no summary, because most engineers spend four lines saying what their job titles already said.

Why the default is no

A summary occupies the most valuable space on the page — the top third that the lesson on reading speed showed carries the decision. To earn that space it has to say something your experience section does not already say.

Most summaries do not. They say things like:

Experienced software engineer with a passion for building scalable solutions and a proven track record of delivering high-quality products in fast-paced environments.

Every word there is unverifiable and applies to tens of thousands of people. It has consumed the best real estate on your resume to say nothing, and it has pushed your actual experience further down.

The four cases where a summary earns its place

1. Career change. Your history does not point at the job you want, so the reader needs a frame before they read it.

Backend engineer, three years, after six years as a mechanical engineer in automotive manufacturing. Now building the telemetry pipeline that ingests 2M sensor events a day at Kestrel Systems.

2. Relocation or an unusual location. The reader's first question is logistical, so answer it before they wonder.

3. A seniority signal that titles do not carry. If your title was "Software Engineer" but you led a team of six across three services, the title is understating you, and one line can fix that.

4. A specialisation that is not obvious from employers. If you are a distributed systems specialist whose employers are not known for that, say so.

How to write one that works

Three rules:

  • Facts, not adjectives. Years, domain, scale, specialisation. Nothing that cannot be checked.
  • Three lines maximum. Four is a paragraph, and paragraphs get skipped.
  • Answer the reader's likely objection. The summary exists to remove a question, not to introduce you.

Compare:

Passionate full-stack developer with strong problem-solving skills seeking challenging opportunities in a growth-oriented organisation.

Payments engineer, five years, currently owning the settlement service that processes ₹40 crore a day at Northwind. Looking for backend infrastructure roles in Berlin; relocating March 2027.

The second is the same length and tells a recruiter four useful things.

The anatomy of an experience entry

Below the summary, or at the top if you have none, come your roles. Every role on your resume has the same five parts. Most candidates include four of them and omit the one that does the most work.

Senior Backend EngineerKestrel Systems · logistics SaaS, 40 engineers2021 – presentOwned the order pipeline: 2M events/day, 6 services, team of 4.1Job title2Company + one-line descriptor4The context line — the part everyoneskips5Bullets: outcome first3DatesSenior Backend EngineerKestrel Systemssame role, no context line — reader cannot tellscopeFive parts.Only one of them is optional, and it is not the context line — that isthe line that tells the reader how big the job was.
Strip the context line and the same role reads as a smaller job.

The five parts

Text
Senior Backend Engineer                                    Mar 2023 – PresentKestrel Systems (B2B logistics SaaS, 200 staff, Bengaluru)Own the routing service: 12M requests/day, 4 engineers, on-call rotation of 6.• Cut p99 routing latency from 840 ms to 120 ms by replacing per-request  graph traversal with a precomputed adjacency cache, unblocking the  same-day-delivery launch.• ...

1. Job title. Use a standard one. If your official title was non-standard, you may write the standard equivalent with the official one in brackets: Senior Engineer (officially "Technical Lead II"). Never invent a title you did not hold.

2. Company, with a descriptor. If your employer is not widely recognised, five words telling the reader the domain and scale is one of the cheapest improvements available.

3. Dates. Month and year. Consistent format throughout. Do not use years only to hide a short stint — recruiters notice, and it reads worse than the gap would have.

4. The context line. One line, before the bullets, establishing scope.

5. Bullets. Three to six for your current role, fewer as you go back. The oldest roles may need none at all.

Why the context line matters so much

Bullets describe what you did. The context line describes how big the thing was. Without it, the reader has to infer scope from your achievements, and they usually infer low.

Consider the same bullet under two different context lines:

Own the routing service: 12M requests/day, 4 engineers, on-call rotation of 6.

• Cut p99 routing latency from 840 ms to 120 ms…

Contributed to the routing service alongside 3 other engineers.

• Cut p99 routing latency from 840 ms to 120 ms…

Identical achievement. Completely different read on seniority.

The context line is also where team size, ownership, and on-call responsibility go, so they do not have to be crammed into individual bullets.