Job Search
How to Write a Resume That Gets Read
A practical guide to writing a resume hiring managers actually read, with real before-and-after lines, formatting rules, and what to cut first.
Job Search
A practical guide to writing a resume hiring managers actually read, with real before-and-after lines, formatting rules, and what to cut first.
I have read thousands of resumes, and I can tell you the uncomfortable truth: most get six to eight seconds before someone decides yes, no, or maybe. That is not because hiring managers are lazy. It is because a single opening can pull two hundred applications, and the brain protects itself by skimming. Your job is to make the skim work in your favor.
The good news is that this is a solvable problem. A resume that gets read is not about clever wording or a fancy template. It is about putting the right things where the eye lands first, and cutting the noise that buries them.
The single biggest fix I see is turning duty statements into result statements. A duty tells me what you were assigned. A result tells me what happened because you were there. Those are very different signals.
Compare these two lines for the same job:
The second line is not bragging. It is specific. It tells me the scope, the method, and the outcome. Even if your numbers are modest, name them. "Reduced monthly reporting time from two days to four hours by building a template" beats "handled reporting" every single time.
If you genuinely do not have numbers, use scope and stakes instead. "Onboarded every new hire across three offices" or "owned the vendor relationship for our largest client" still tells me you carried weight. The pattern is always: what you did, how, and what changed.
Readers do not start at the bottom. They start at the top, and many never reach the bottom at all. So your strongest, most relevant material has to live in the top third of the page.
That means your most recent or most relevant role comes first, and within that role, your best bullet leads. Do not save the impressive thing for last like a movie twist. If you increased revenue, fixed a broken process, or shipped something people use, that is bullet number one.
It also means your summary, if you keep one, should be three lines of substance, not a personality essay. "Product marketer with six years in B2B SaaS, focused on launch strategy and pricing. Took two products from beta to first million in revenue." That tells me who you are in the time it takes to blink. Skip "passionate, results-driven team player." Those words are invisible because everyone uses them.
A resume is not your autobiography. It is an argument that you can do a specific job, made to someone who is tired and busy. Win the argument fast.
When people ask me how long a resume should be, my answer is: as long as it needs to be and not one line longer. For most people with under ten years of experience, that is one page. For senior folks with a deep track record, two pages is defensible. Three pages had better be a federal or academic CV, because in the private sector it reads as someone who cannot prioritize.
Here is what to cut first. Cut the job from twelve years ago that has nothing to do with your target role. Cut "references available upon request," which everyone assumes. Cut the skills section line that lists Microsoft Word, because in most fields that is like listing "can use a phone." Cut adjectives that you cannot prove. If you call yourself a strong communicator, the resume itself is the evidence, so let it speak.
On formatting, stay plain on purpose. A clean single-column layout with standard headings reads well for a human and parses cleanly for the applicant tracking software many companies use to sort resumes. Skip the photo, the rating bars for skills, the two-column designs that scramble when a system reads them, and the dense blocks of color. Use a normal font, real bullet points, and consistent dates. Save the PDF with a sensible filename like "Jordan-Lee-Resume.pdf," not "resume-final-v7-REAL.pdf."
Every strong resume is, to some degree, tailored. The posting tells you what the company values most, often in the first few bullets of the requirements. Mirror that honest language where it genuinely applies to your experience. If they ask for "cross-functional project leadership" and you have done exactly that, use that phrase rather than your internal nickname for it. This is not keyword stuffing; it is speaking the reader's language so they recognize the fit. If you want a deeper walkthrough of this, our guide on tailoring your resume to a job covers it step by step.
The line you must not cross is inventing experience. Hiring managers and references catch this, and even when they do not, you end up in a role you cannot do, which is its own kind of misery. Tailor the framing, not the facts.
I want to be honest about effort and luck, because plenty of resume advice pretends this is a formula. A strong resume does not guarantee a job. Timing, internal candidates, budget freezes, and plain randomness all play a part you cannot control. What a strong resume does is reliably move you from the discard pile to the conversation, and over dozens of applications, that shift compounds into real interviews.
So treat your resume as a living document, not a monument. Keep a master version with everything you have ever done, then trim and reorder it for each serious application. Read it out loud once before you send it, because your ear catches clumsy phrasing your eye skips. Then send it and move on to the next one. The candidates who get hired are rarely the ones with the perfect resume. They are the ones with a good resume who kept showing up, kept refining, and gave themselves enough chances for the timing to finally land. Build that habit, and the reading takes care of itself.
Keep reading
A smart follow-up can move your application off the pile, but a clumsy one can hurt. Learn when to follow up, who to contact, and exactly what to say.
How to tailor your resume to a job posting in twenty minutes: read the role, mirror its language honestly, reorder for relevance, and avoid keyword stuffing.