The Context Line Above Your Bullets
Most engineering bullets are carrying two jobs at once. They have to describe what you did, and they have to establish where you were doing it — the scale of the company, the size of the team, the technologies in the room. The second job eats the sentence.
The fix is structural rather than editorial. Put the environment on its own line, once per role, and every bullet underneath is freed to be about work.
What it looks like
Senior Backend Engineer, Northwind — Jan 2023 to present B2B logistics platform, roughly eighty engineers. Payments team of five; Go services on ECS, PostgreSQL, Kafka.
- Owned the settlement service end to end, including its on-call and its reconciliation against the provider’s daily file.
- Rebuilt the retry path after a provider outage produced duplicate captures — moved to idempotency keys issued at request time, with a reconciliation job that flagged mismatches for manual review.
One italic line, then bullets that never have to say “using Go and PostgreSQL” because it’s already established. Both bullets are shorter than they would otherwise be and neither one contains a technology roster.
The three things it establishes
What the company is and roughly how big. Unless your employer is a household name, the reader has no way to place its industry, its size, or the maturity of its engineering — and all three change how your bullets read. Six words fix it: B2B logistics platform, roughly eighty engineers. This is the highest-value part of the line, and it is the one most often missing.
Your team and its scope. A team of five and a platform organisation of eighty imply completely different jobs under the same title. Naming your team also quietly does the seniority work described in scope, not years — “payments team” and “developer experience team” tell the reader what your surface area was before they read a word of your bullets.
The stack, once. Four to six names, at the layer that matters. This is where all the technology density on your resume should come from, alongside the grouped skills block, and it removes the incentive to stuff names into every sentence — the argument in name the problem, not just the tool.
Why one line beats spreading the same facts around
Bullets get shorter and better. Two-line bullets become one-and-a-half-line bullets, and the space recovered goes to mechanism. Across four roles this can save a third of a page.
It prevents the wrong inference. “Owned the deploy pipeline” at a company with a platform team means something different from the same words at a company of eight. Left ambiguous, some readers overrate you and some underrate you, and you can’t control which — the problem moving from a big company to a startup, and back is about.
It makes the skills list checkable. A reviewer who has seen Kafka in two context lines reads it differently in your skills block than one who has only seen it in the list. The stack lines are what make the list credible rather than aspirational.
It reads as organised. A small thing, and real: a resume with a consistent structural pattern signals someone who thinks about structure.
The variants worth knowing
Consultancy or agency work. The context line carries the client type without breaking confidentiality: Consultancy; two engagements — a retail client's order platform (Java, Oracle) and a public-sector data migration (Python, PostgreSQL).
A role where you changed teams. One line, both teams, chronologically: Started on the mobile API team, moved to platform after a year — Go, Kubernetes, Terraform. This is more legible than splitting one employer into two entries.
A company nobody has heard of, including its outcome. If the company no longer exists, say so plainly here rather than leaving the reader to wonder: Seed-stage fintech, closed in 2024; six engineers. It answers the question in four words and removes it from the interview.
A well-known employer. Skip the descriptor, keep the team and stack. The name has done the scale work already.
How it goes wrong
It becomes a paragraph. Two lines maximum, and one is better. Once it reaches three lines it is competing with your bullets, which is the opposite of the point.
It repeats what the bullets say. The line is environment only. If a sentence in it describes something you did, it belongs in a bullet.
It inflates. Naming the whole organisation’s technology estate when you touched two of the items is the same overclaim as a padded skills list, and it is easier to catch here because the reader will ask which parts you worked on. List the stack of your team, not of the company.
It carries marketing copy. Your employer’s positioning statement is not context. “The leading cloud-native platform for enterprise supply chain transformation” tells a reviewer nothing; “warehouse management SaaS, mid-market retail” tells them everything they needed.
It appears on roles from a decade ago. Old roles should be shrinking, not gaining lines. Use it on your most recent two or three roles and let the rest be a title and a date, per the weighting in what belongs on an engineering resume.
Not the same as the summary line
Worth separating, because they get confused and doing both badly is common.
The summary is at the top, is about you, and positions the whole application: what kind of engineer you are and what you are applying as. It’s optional and frequently skippable.
The context line is per role, is about the environment, and exists to make the bullets underneath legible. It’s not optional in any resume with more than one employer, because without it the reader is guessing at scale on every line.
They can and should say different things. If your summary and your first context line contain the same words, one of them isn’t working.
The edit
Take your most recent role and move every fact about the environment out of the bullets and into one italic line above them. Company type, size, team, stack.
Then reread the bullets. Most will have lost a clause and gained clarity, and one or two will have collapsed into nothing — which is useful information, because those were bullets whose entire content was the environment.