On this path · Writing 9. Resume, Cover Letter, and LinkedIn
  1. The Principles of Clear Prose
  2. Sentence Rhythm in Writing
  3. Professional Email
  4. Slack and Chat
  5. Technical Documentation
  6. Writing RFCs and Design Docs
  7. Performance Reviews and Written Feedback
  8. Persuasive Writing
  9. Resume, Cover Letter, and LinkedIn

Resume, Cover Letter, and LinkedIn

Write impact bullets and a career narrative that read as senior.

Learning outcomes

A recruiter opens your resume and reads one line: “Responsible for the deployment pipeline.” They have given that line about two seconds, and in those two seconds they learned that you were near a pipeline. They do not know whether you built it, whether it worked, whether anyone was better off. A different candidate wrote, for the same job, “Cut deployment time from 40 minutes to 6 by parallelizing the test suite.” That line says what changed, by how much, and how. Same role, same person even, but only the second line makes a case. Career writing is the skill of turning the first line into the second, over and over, until your whole story argues for you.

After studying this page, you can:

  • Rewrite a duty-style resume line into an impact bullet built from a strong action verb, what you did, and a quantified or concrete result.
  • Apply the X-Y-Z formula (accomplished X, as measured by Y, by doing Z) and tell achievements apart from responsibilities.
  • Replace weak verbs (worked on, helped with, responsible for) with strong ones (built, led, cut, shipped, scaled, drove) and quantify impact, or name a concrete outcome when no number exists.
  • Tailor a resume to a role with the right keywords so it survives an applicant tracking system and reads as written for that job.
  • Write a cover letter that argues why you and why them, and a LinkedIn headline and About section that sound like a specific human rather than a buzzword generator.

Before we dive in

Every job application is a competition you cannot see. For one open role, a recruiter may hold a stack of fifty resumes, and they are not reading them, they are scanning them, looking for a reason to put yours in the short pile or the long one. You have a few seconds per page and one job in those seconds: to make the reader believe you will do this work well, because you have already done work like it well. That is a persuasion problem, not a record-keeping one.

This is where most people go wrong before they write a single line. They treat the resume as an honest list of what they were assigned: the systems they touched, the meetings they attended, the tools that were in the room. All true, all forgettable. The reader does not want to know what you were responsible for; they want to know what happened because you were there. The whole craft on this page is the difference between those two, and it runs through every document you write about yourself: the resume, the cover letter, and the LinkedIn profile.

Three words will recur, so fix them now. A responsibility is a duty you were given, what you were supposed to do. An achievement is a result you produced, what actually changed because of you. Impact is the size and shape of that change, ideally in numbers. Hold those apart and the rest follows. Everything here is the same persuasion you would use for any reader, the kind taught in persuasive writing, turned on the one subject you find hardest to sell honestly, which is yourself.

Mental Model: you are writing a sales argument, not a job diary

Here is the reframe that changes everything you write afterward. The wrong model, the one almost everyone starts with, is that a resume is a diary of your jobs: a faithful record of where you worked, for how long, and what you were tasked with. Under that model the goal is completeness, so you list every duty, and the document reads like a contract clause. It is accurate and nobody is moved by it.

The better model is that every line you write about yourself is one sentence of a sales argument, and the product is you. A sales argument does not list features in a neutral tone; it shows the buyer what they get. So the unit of your resume is not the duty, it is the claim of value: a thing you made better, with evidence. The reader is the buyer, their problem is the open role, and each bullet is one small proof that you solve problems of that shape. Once you see the document as an argument with a reader and a goal, the rules below stop being style tips and become moves in a case you are building.

The currency is impact, not duties

A duty tells the reader what you were near; an impact tells them what changed. The reader is buying outcomes, so price every line in outcomes. Before you keep any line, ask: “So what? What was different because I did this?” If the line has no answer, it is a duty, and a duty is worth almost nothing on the page. Rewrite it until it names the result, or cut it.

This single shift, from diary to argument, is the parent of every technique that follows. The impact bullet is how you make one claim of value. Strong verbs are how you make it land. Quantifying is the evidence. Tailoring is aiming the argument at this particular buyer. The cover letter is the argument in paragraph form, and LinkedIn is the argument left standing in public for buyers you have not met yet. Keep the model in view and the parts cohere.

Breaking it down

1. The impact bullet: verb, what, result

Start with the smallest unit, because every resume is built from it: the bullet. A weak bullet describes a duty. A strong bullet, the impact bullet, has three parts in order: a strong action verb, what you actually did, and the result that followed, with a number wherever one exists. Verb, what, result. Miss the third part and you have described effort; include it and you have described value.

Watch the transformation on the line from the top of the page. “Responsible for the deployment pipeline” has no verb of your own (just the limp “responsible for”), a vague what (a pipeline existed), and no result at all. Now add the three parts: the verb is “cut,” the what is “deployment time, by parallelizing the test suite,” and the result is “from 40 minutes to 6.” Assembled: “Cut deployment time from 40 minutes to 6 by parallelizing the test suite.” The reader now sees an action, a method, and a measured win in one line.

There is a formula that forces all three parts into place, popularized in hiring advice as the X-Y-Z formula: accomplished X, as measured by Y, by doing Z. X is the achievement, Y is the metric that proves it, and Z is the method you used. Map our line onto it and every slot is filled: you accomplished a faster pipeline (X), as measured by 40 minutes dropping to 6 (Y), by parallelizing the test suite (Z). The formula is not a rigid template you must obey word for word; it is a checklist that catches the missing piece, and the piece people forget is almost always Y, the measurement.

The anatomy of an impact bullet. The top path builds it as verb plus what plus measured result; the bottom path is the same line read as the X-Y-Z formula, accomplished X as measured by Y by doing Z. Both converge on one strong line.

Read the diagram as two routes to the same destination. The top row is the plain-language recipe (a strong verb, the work, the measured result), and the bottom row is the X-Y-Z formula that names each slot more formally. They are the same bullet seen two ways, which is the point: whichever scaffold you find easier to hold in your head, both push you to attach a measured result to a strong verb. If your draft bullet reaches the end without a result, you have written a duty, and the next section shows how to spot and fix that at scale.

2. Strong verbs and the duties trap

A bullet can have the right shape and still go limp at the first word, because the verb sets the tone of the whole line. Compare how a sentence opens. “Worked on the search service” and “Helped with the migration” and “Responsible for monitoring” all start by shrinking you: “worked on” could mean you led it or you watched it, “helped with” puts you in the supporting cast, and “responsible for” describes a job title, not an act. Strong verbs do the opposite. “Built the search service,” “Led the migration,” “Drove monitoring adoption” each name a specific thing you did and put you in charge of it.

The deeper problem behind weak verbs is the duties trap: listing what you were responsible for instead of what you achieved. Duties read as forgettable for a structural reason, not a stylistic one. A duty is true of anyone who held your title, so it tells the reader nothing that distinguishes you; “responsible for the deployment pipeline” is true of every engineer who was ever assigned that pipeline, including the ones who let it rot. An achievement is true only of you, because you are the one who produced that particular result. The reader is scanning for what sets you apart, and duties, by definition, never do.

The table below puts weak bullets beside their strong rewrites and names the exact fix in each, so you can see that the repair is mechanical, not magical: pick a stronger verb, surface the real action, and attach a number.

Weak resume bullets, their impact rewrites, and the specific fix each rewrite applies. Read the right column to see whether the repair was the verb, the missing impact, or the missing quantification.

Weak bullet (duty)Impact rewrite (achievement)Fix applied
Responsible for the deployment pipeline.Cut deployment time from 40 minutes to 6 by parallelizing the test suite.Strong verb plus quantified result
Worked on improving site performance.Reduced page load time by 35 percent by lazy-loading images and caching API calls.Strong verb plus quantification
Helped with onboarding new engineers.Wrote the onboarding guide that took new engineers from setup to first commit in one day.Strong verb plus concrete outcome
Was part of the team that migrated the database.Led the migration of 12 services to the new database with zero downtime.Strong verb plus quantification, claims your role
Involved in code reviews and quality.Drove a code-review standard that cut production incidents by half over two quarters.Strong verb plus measured impact
Responsible for handling customer support tickets.Resolved 200-plus support tickets a month while keeping satisfaction above 95 percent.Strong verb plus two quantities
16 of 6

Notice that every rewrite in the right column starts with a verb you did, not a state you were in, and every one ends on something the reader can weigh. The fix column shows the same two levers again and again: a stronger verb and a result. Keep a short stable of strong verbs in mind as you draft (built, led, cut, shipped, scaled, drove, designed, launched, reduced, grew) and treat any bullet that opens with “worked on,” “helped with,” or “responsible for” as a draft you have not finished yet.

3. Quantifying impact when you have a number, and when you do not

The hardest part of the impact bullet is the result, and the reason is that results often hide. People assume quantifying means having clean metrics handed to them, and when they have none they fall back to “improved performance” or “increased efficiency,” which are duties wearing a disguise. The skill is twofold: find the number that is already there, and when there genuinely is no number, name the concrete outcome instead.

Most work has a number in it once you look. You may not have measured load time, but you know the deploy went from “every Friday, by hand” to “on every merge, automatically,” and that is a frequency you can state. You supported customers, so there is a ticket count, a response time, a satisfaction score. You shipped a feature, so there is an adoption figure, a number of users, a reduction in support requests about the old way. The question that surfaces these is blunt: “How much? How many? How often? Compared to what?” Run it on every bullet and most of them will yield a figure you can defend.

When there is no number, name the concrete outcome

Not everything reduces to a percentage, and a fabricated number is worse than none, because one challenged figure poisons trust in the whole resume. When you truly cannot quantify, replace the vague claim with a concrete, checkable outcome. “Improved the onboarding experience” becomes “wrote the onboarding guide new hires now follow on day one.” “Made the codebase more maintainable” becomes “split the monolith into three services each owned by a single team.” The reader cannot measure these, but they can picture them, and a picture beats an abstraction. Honesty is non-negotiable: every number and every outcome you write must be one you could explain calmly in an interview. The skill of talking through these claims out loud is its own subject in interviews speaking about yourself.

So the rule has two branches. Where a number exists or can be reconstructed, use it, because a figure is the strongest evidence a bullet can carry. Where no honest number exists, name the specific thing that changed in the world, concretely enough that the reader can see it. What you never do is leave the result slot empty and hope the verb carries the line; an unquantified, unconcrete bullet has quietly slid back into being a duty.

4. Keywords, the tracking system, and tailoring to the role

Even a resume full of strong impact bullets can fail before a human ever reads it, because a machine often reads it first. Many companies route applications through an applicant tracking system, software that stores and filters resumes, and recruiters search it for the words in the job description. A resume that never uses the role’s own vocabulary can rank low or be filtered out, not because the candidate is weak, but because the words do not match. This is the quiet reason a strong generalist resume, sent unchanged to a hundred jobs, underperforms.

The defense is tailoring: reading the specific job description and making sure your resume speaks its language where you honestly can. If the posting says “Kubernetes” and “incident response” and “mentoring,” and you have done those things, the resume should use those exact terms, not synonyms the search will miss (“container orchestration,” “on-call,” “coaching”). Tailoring is not keyword stuffing, which means cramming in terms you cannot back up; that fails the moment a human reads it or asks about it in an interview. Tailoring is choosing, among the true things you could say, the ones this role is actually looking for, and saying them in the role’s words.

A backend engineer is applying for a role whose description stresses 'reducing latency' and 'on-call reliability'. Which resume bullet is strongest for this application?

The quiz shows the four moves of this page colliding in one decision: strong verbs, quantified results, the role’s keywords, and the refusal to lean on buzzwords all point to the same line. Tailoring is the move that aims the others. You write the strongest true bullets you can, then for each application you promote the ones this role cares about and phrase them in this role’s language, so the same underlying truth is presented as the answer to this particular job.

5. The cover letter: a short argument, not a resume in prose

The cover letter fails most often by trying to be the resume again, in paragraphs. A reader who has your resume does not want it narrated back to them; they want the one thing the resume cannot say, which is the argument that connects you to this specific company and role. A good cover letter is short and answers two questions: why you (what you bring that fits this need) and why them (why this company, not a generic one, and why now).

The shape is tighter than people expect. Open with a real reason you are writing to this company, something true about them that you actually care about, not “I am excited to apply for the position.” Then make one or two specific claims that tie your strongest achievements to their stated needs, drawing on the resume but going beyond it, explaining the thinking or the fit a bullet cannot hold. Close by saying what you want (a conversation) without groveling. Three short paragraphs beat one long one. The whole letter is the persuasion of persuasive writing at small scale: a claim, evidence, and a reason the reader should care, aimed at one named audience.

The generic cover letter, and the resume-in-prose

Two failures kill most cover letters. The first is the generic letter, the one where you could swap in any company name and nothing else would change; it tells the reader you did not look closely at them, which predicts you will not look closely at the work. The second is the resume in prose, where each paragraph rephrases a bullet the reader already has, adding length and no new information. The test for both: could you send this exact letter to a different company, or does it argue for this one? If the company name is the only thing that would change, you have not written a cover letter, you have written a template.

So treat the cover letter as the place to do what the resume cannot: connect the dots between your record and their need, in your own voice, for this one employer. It is the difference between handing someone your facts and telling them what your facts mean for them.

6. LinkedIn: the headline and the human About section

LinkedIn is the version of your argument that stands in public, found by people you have not met, so two parts carry most of the weight: the headline and the About section. The headline is the line under your name, and its job is to say what you do and for whom, in plain words a stranger can act on. “Software Engineer” is a job title, not a headline; “Backend engineer building payment systems for high-traffic fintech” tells a reader what you do, the domain, and the kind of problem you solve. The headline is the most-seen line on your whole profile, and the only one that shows in search results, so it should carry meaning, not just a title.

The About section is where most profiles collapse into buzzwords, and where a human voice wins easily. The common failure is the third-person, adjective-stuffed paragraph: “A passionate, results-driven professional with a proven track record of leveraging cutting-edge technologies to deliver value.” It is written in the third person about yourself, which is oddly formal, and it is built from words (“passionate,” “results-driven,” “proven track record”) that everyone uses and nobody can verify. Write the About section in the first person, in your own voice, and replace every cliche with a specific. Not “passionate about scalable systems” but “I like the puzzle of making a slow system fast, and I have taken a checkout flow from 3 seconds to under one.” Specifics are believable because they could be checked; cliches are ignored because they could be said by anyone.

Buzzword-driven LinkedIn lines beside their specific, human rewrites. The left column could describe anyone; the right column describes one person doing one thing.

Buzzword versionSpecific, human versionWhy it works
Software EngineerBackend engineer building payment systems for high-traffic fintechHeadline says what and for whom, not just a title
Passionate, results-driven professional.I like making slow systems fast; I took our checkout from 3 seconds to under one.First person, concrete result instead of adjectives
Proven track record of delivering value through synergy.I have shipped three products from zero to launch, two of them as tech lead.Checkable specifics replace empty cliches
Leveraging cutting-edge technologies to drive innovation.I rebuilt our search on a vector database and cut irrelevant results by half.Names the actual work and its measured effect

The right column wins for one reason that ties this whole page together: a specific can be true of you and only you, while a cliche is true of no one in particular. Read each buzzword line and notice that you cannot picture a single thing the person did; read each rewrite and you can. The same instinct that drives the impact bullet, the duty-versus-achievement split, drives the LinkedIn profile, because it is the same act of persuasion, just left standing where strangers can find it.

Resume in American English, CV in British English

The word for this document depends on where you are. In American English the document is a resume, a short, tailored, usually one-to-two-page summary aimed at a specific job. In British English (and much of Europe), the everyday word for that same short document is the CV, short for the Latin curriculum vitae. The catch is that in American academic and medical hiring, a CV means something different: a long, complete, year-by-year record of publications, talks, and positions, often many pages. So “send me your CV” means a short summary in London and could mean a full academic record at a US university. When in doubt, match the word the employer used and ask what length they expect.

Common mistakes

The first mistake is the one this whole page fights: listing duties instead of achievements. The resume reads as a job description, every line beginning “Responsible for,” and the reader learns what you were assigned but nothing that happened. The fix is the “so what?” test on every line: if a bullet has no result, it is a duty, and a duty is nearly worthless. Rewrite it to name what changed or cut it.

The second mistake is no numbers. The bullets describe real work but never say how much, so “improved performance” and “increased reliability” float without evidence. Hunt the number that is already there (a frequency, a count, a percentage, a before-and-after), and where none honestly exists, name the concrete outcome instead. Never invent a figure; one number you cannot defend in an interview discredits all the others.

The third mistake is weak verbs. Lines open with “worked on,” “helped with,” and “responsible for,” which shrink your role and hide what you actually did. Lead with a strong verb you can stand behind: built, led, cut, shipped, scaled, drove. The verb is the first word the reader sees, and it sets whether you sound like the person who did the thing or the person who was nearby.

The fourth mistake is the generic cover letter, the one that would fit any company because it argues for none. If swapping the company name is the only edit needed to reuse the letter, it is not a cover letter; it is a form. Anchor it to one real thing about this employer and tie your record to their stated need.

The fifth mistake is the buzzword-stuffed, third-person LinkedIn profile: “a passionate, results-driven professional with a proven track record.” It is written about you instead of by you, and built from words anyone could use. Switch to the first person, cut every cliche, and replace each one with a specific you could be asked to back up. The reliable signal of a strong profile is that almost nothing in it could be copied onto a stranger’s page without becoming false.

Mastery Questions

Question

A resume line reads 'Responsible for the deployment pipeline.' Diagnose why it is weak and rewrite it as an impact bullet, naming the three parts you added.

Answer

It is weak because it has no action verb of your own ('responsible for' is a state, not a deed), a vague 'what' (a pipeline merely existed), and no result at all, so it describes a duty anyone with the title could claim. An impact bullet needs three parts in order: a strong action verb, what you did, and the measured result. Rewritten: 'Cut deployment time from 40 minutes to 6 by parallelizing the test suite.' The verb is 'cut', the what is 'deployment time, by parallelizing the test suite', and the result is the measured drop 'from 40 minutes to 6'. The same line maps onto the X-Y-Z formula: you accomplished a faster pipeline (X), as measured by 40 minutes falling to 6 (Y), by parallelizing the test suite (Z).

1 / 5

Recommended next

Sources & evidence7 claims · 2 cited

Covers impact bullets (verb plus what plus quantified result and the X-Y-Z formula), responsibilities versus achievements, strong versus weak verbs, quantifying or naming concrete outcomes, ATS keywords and tailoring, the cover letter as a focused argument, and the LinkedIn headline and About section, plus an AmE resume versus BrE CV note. Resume and cover-letter guidance cites Purdue OWL; the X-Y-Z formula and impact-bullet advice are stable common knowledge; example numbers are illustrative.

  • An effective resume bullet states an achievement built from a strong action verb, what was done, and a result, rather than describing an assigned responsibility.verified
  • The X-Y-Z formula frames a bullet as accomplished X, as measured by Y, by doing Z, forcing the achievement, its metric, and its method into one line.stable common knowledge
  • Duties read as forgettable because a duty is true of anyone holding the title, whereas an achievement is true only of the candidate who produced that result, so only achievements distinguish a candidate.internal reasoning
  • Many employers filter applications through an applicant tracking system that searches resumes for job-description keywords, so tailoring a resume with the role's own terms improves its chances of reaching a human reader.stable common knowledge
  • A cover letter should be a short, specific argument answering why-you and why-them rather than restating the resume in prose, and a generic letter reusable for any company signals a lack of fit.verified
  • A strong LinkedIn profile uses a headline naming what you do and for whom and a first-person About section with concrete specifics, replacing third-person buzzwords such as passionate and results-driven.internal reasoning
  • In American English the short, tailored job-application document is a resume, while British English calls it a CV; in American academic and medical hiring a CV instead denotes a long, complete record of publications and positions.stable common knowledge

Cited sources