How to Write a Resume That Gets Past the First Round

Quick disclaimer upfront: I'm not a recruiter. I'm not in HR. I'm a 28-year-old product marketing manager who came up through the COVID job market, spent 8 months working at a coffee shop before landing his first real role, made one career pivot, and is currently angling for a senior position. I've also been on the other side recently — helping screen candidates for a contract position we were filling at work. So I know both sides of this table, even if I'm still way closer to the candidate side.

The resume advice I got when I was starting out was bad. Not factually wrong — just generic in a way that didn't actually help me make decisions. "Use action verbs." "Quantify your achievements." "Keep it to one page." Okay, but what does that actually look like? What do I do when I'm staring at a blank Google Doc with a job posting open in another tab?

Here's what I've figured out, broken down as specifically as I can.

The 20-Second Rule {#20-second-rule}

Recruiters are not reading your resume. Not at first. They're scanning it.

There's a frequently cited (and admittedly aging) study from TheLadders that put initial resume reviews at around 7 seconds. That figure has been challenged over the years and the methodology has real limitations — but the underlying point still holds: the initial review is fast. My personal experience on the hiring side, even briefly, is that 15-20 seconds feels closer to reality when applications are high volume. Either way, you have a short window to communicate that you're worth a closer look.

What are they actually looking for in those first few seconds?

• Can I figure out what this person does quickly?
• Does their experience level match what we need?
• Are there any obvious red flags?

That's it. They're not reading your bullet points yet. They're pattern-matching against a mental model of the role.

What this means for structure: The top third of your resume is prime real estate. That's where the eye lands first. If your job title, most recent employer, and a clear sense of your professional identity aren't visible immediately, you've already lost the scan.

This is why I'm a strong advocate for a short professional summary right under your name and contact info. Not a "career objective" (those died in 2010 and should stay there), but a 2-3 sentence description of who you are professionally, what you specialize in, and one tangible result or distinguishing credential. Think of it as a human-readable headline that ATS won't kill and a recruiter will actually process.

Recruiter insight: When I was helping screen candidates for a role last quarter, our hiring manager told me she reads summaries specifically to see if candidates "get it" — whether they can clearly describe what they do and why it matters. It was the first signal that someone had self-awareness about their professional identity. The candidates who skipped the summary made her work harder to figure them out. She didn't like that.

The Essential Sections {#essential-sections}

Here's the section order I'd use for most early-to-mid career folks:

1. Contact Info — Name, email, phone, LinkedIn URL, city/state (not your full address — this isn't 1998). Personal site or portfolio if you have one.
2. Professional Summary — 2-3 sentences. What you do, your specialty, one result or credential.
3. Experience — Most recent first. This is the main event. Everything else serves it.
4. Skills — Technical tools, software, platforms, languages. Keep it scannable.
5. Education — Degree, school, graduation year. That's usually enough.
6. Certifications — If relevant to the role (Google Analytics, PMP, AWS certs, etc.), include them.

What to cut if you're fighting for space:

• Objective statements — never include these
• "References available upon request" — everyone knows this, you're wasting a line
• High school information — unless you graduated last year
• Interests and hobbies — only if they're genuinely relevant (fluent in Japanese applying to a Japan-market role: include it; enjoy hiking: no one cares)
• GPA — after 2+ years of work experience, it's not adding signal

Formatting tip: Don't put your photo on a US-market resume. In some countries it's standard. In the US, many hiring managers are specifically trained not to factor it in, and some companies have policies against photos to reduce bias exposure. Just leave it off.

The Bullet Point Formula {#bullet-point-formula}

This is where most resumes fall apart. People describe their job instead of their impact. There's a real difference.

The job description version:

"Responsible for managing social media accounts and creating content."

The achievement version:

"Grew LinkedIn following from 4K to 22K in 12 months by launching a weekly video series, driving 3x higher engagement than company benchmark."

Same person. Same job. Completely different impression.

The framework I use is: Action + Metric + Business Impact.

• Action — What you did. Lead with a strong verb: grew, launched, reduced, built, negotiated, led, redesigned, automated, closed.
• Metric — How you can quantify it. Numbers, percentages, dollar amounts, time saved, accounts managed, team size.
• Business Impact — Why it mattered. What did the company actually get out of it?

Not every bullet will have all three. Sometimes you don't have a clean metric. That's fine — but push yourself before you give up. Even "managed a portfolio of 12 enterprise accounts" tells me scope. "Managed enterprise accounts" tells me nothing.

For early-career folks especially: your numbers don't have to be enormous to be worth including. "Reduced weekly reporting errors by 40% by building a QA checklist" is a great bullet for someone one year into their career. It signals that you're paying attention, measuring things, and making incremental improvements. That's what entry-level hiring managers are actually looking for.

Common mistake: Using the same bullets for every job you apply to. The accomplishments that land for a project manager role are different from the ones that resonate for a marketing role — even when the underlying experience is identical. You need to prioritize different things depending on who's reading. More on this below.

ATS Formatting Without Killing Your Design {#ats-formatting}

ATS stands for Applicant Tracking System — the software many companies use to collect and manage job applications. Your resume often goes through ATS parsing before a human ever sees it.

The horror stories are largely overblown. Many modern ATS platforms (Greenhouse, Lever, Workday, SmartRecruiters) have gotten significantly better at parsing resumes. But there are still specific things that trip up parsers on some systems — and when they do, parts of your resume can quietly disappear.

What tends to break ATS parsers:

• Text in headers or footers — many ATS can't read them; contact info placed there may not be captured
• Tables and multi-column layouts — some parsers read across columns instead of down, creating nonsense
• Graphics, icons, logos, and charts embedded in the document
• Non-standard file formats — export as a proper PDF or whatever format the application specifies; avoid "Print to PDF from Pages" if you can help it
• Unusual bullet characters (• is safe; ◆ and ★ sometimes aren't)

What works:

• Clean single-column layout, or a careful two-column if you know what you're doing
• Standard section headers (Experience, Education, Skills — not "Where I've Been" and "What I Know")
• Submitted as a properly exported PDF unless the application specifically asks for Word
• Standard bullet points, consistent font sizing, no embedded objects

Here's the thing nobody tells you: the formatting choices that tend to parse cleanly also look better to humans. There's not much of a trade-off if you do it right. A clean, well-organized resume consistently outperforms an over-designed one. I've seen people lose their minds building Canva resumes that look beautiful and get parsed into complete gibberish on the back end. Don't do it.

Formatting tip: Run your resume through a tool like Jobscan before submitting to roles you really want. It shows you how your resume compares against a specific job description's keyword requirements — a useful proxy for how many ATS platforms rank or filter applications — and flags terms you might be missing. It's not a perfect simulation, but it's a good sanity check.

The Experience Section Deep Dive {#experience-section}

Here's the format I'd use for each experience entry:

Company Name | Job Title | [City, State or Remote] | Month Year – Month Year (or Present)
[Optional: 1-line company context]

• Achievement bullet 1
• Achievement bullet 2
• Achievement bullet 3
• Achievement bullet 4 (optional — quality over quantity)

The company context line is underused. If you worked somewhere called "Ascend Digital Partners," I have no idea if that's a 4-person agency or a 400-person company. One line — "B2B SaaS startup, Series A, ~60 employees" — gives the reader the frame they need to understand the scale of your bullets. Use it.

On job titles: Use what's on your employment record. I know title inflation exists and happens constantly. I'm not going to pretend otherwise. But it's a verifiable lie, and it can get you fired after you're hired. It's just not worth the risk.

What you can do: if your title was "Marketing Coordinator" but you were running campaigns that a Senior Manager would normally own, show that through your bullets. The evidence in the bullets matters more than the title anyway. A well-written set of achievement bullets can completely reframe how a recruiter perceives your seniority level.

How to make the same experience sound different for different roles: This is the insight that took me the longest to internalize. You don't have one fixed set of experiences. You have a set of experiences you're choosing to frame. The same two years at a company can be told as:

• A product story (for PM or product marketing roles)
• A marketing story (for brand or growth roles)
• A data story (for analytics or operations roles)

This isn't dishonesty. It's choosing which bullets to lead with, which metrics to emphasize, and which skills to call out. You probably did six different things in your last job. Which ones you surface first — and which you bury — is an active decision. Make it deliberately.

Keywords, Customization, and the One-Resume Myth {#tailoring-for-role}

Here's something that took me embarrassingly long to learn: submitting the same resume to 50 jobs is, in my experience, almost always worse than submitting a tailored resume to 10.

Many ATS systems factor keyword matching into how they rank or filter applications. If the job description uses "product positioning" seven times and your resume never uses that phrase — even though you've done that work — you may rank lower than someone whose resume happens to use the term. How much this matters varies by platform and company. But it's real enough that it should shape your approach.

My system:

Step 1 — Build a master resume. This is a complete document with every role, every bullet, every project, every skill. It's probably 2+ pages and you'll never send it to anyone. It's your source file.

Step 2 — Create a base template. One page (or up to 1.5 pages if you have 5+ years of experience), your strongest experience, your best bullets. This is the 80% resume you start from.

Step 3 — Customize per job. Before applying, spend 15-20 minutes with the specific job description. Extract the key terms: tools they mentioned, competencies they care about, outcomes they listed. Make sure those terms appear in your resume — naturally, in context, not keyword-stuffed at the bottom in white text (yes, people still try this; yes, it tends to get flagged).

Step 4 — Update your summary. Adjust the 2-3 line summary to reflect the framing of the specific role. This is often a 3-minute edit that significantly changes how the resume reads.

Step 5 — Submit. Don't overthink it. Good and submitted beats perfect sitting in your drafts folder.

This takes more time per application. But 15-20 minutes of customization is worth more than sending 40 generic applications. The one-resume approach will have you submitting a hundred applications and wondering why you're not getting callbacks. Targeted applications get callbacks.

Your Resume Checklist {#resume-checklist}

Before you hit submit, run through this:

Content:

• Professional summary clearly states what you do and one specific thing you're known for
• Every bullet follows Action + Metric + Impact (or at minimum has a metric or scope number)
• Resume is tailored to this specific job description — key terms from the posting appear naturally
• No career objectives, no "references available upon request," no high school

Formatting:

• Clean layout — single column, or two columns without tables
• Standard section headers
• Consistent font, sizing, and spacing throughout
• Exported as proper PDF (or Word if specified), contact info in the body — not the header/footer

Final check:

• Can a stranger understand what you do within 5 seconds of looking at this?
• Have you spell-checked it — not just browser autocorrect, but actually run it through Grammarly?
• Has someone else read it? Fresh eyes catch things you can't see after your tenth revision.

Early Q1 tends to be an active hiring window in tech and business — many companies that finalized headcount budgets in January are filling roles through March. That said, timing varies a lot by company, industry, and the broader economy, so I'm not going to tell you "March is the best time to job search" as if it's a law. What I will say: if you've been sitting on a job search, the worst move is continuing to sit.

The honest truth about the market right now: application volume has gone up noticeably with AI-assisted applying, and that seems to have sped up the initial screening filter at a lot of companies. That's my read, not a controlled study. What it means practically is that your resume has to work harder to clear the first round than it did a few years ago.

The good news is that most resumes are still genuinely bad. They describe jobs instead of impact. They use one version for every application. They have formatting that quietly breaks on the other end. If you actually do the work here — write achievement bullets, customize per role, format it right — you're already ahead of a meaningful chunk of the applicant pool.

That's the unglamorous reality of the job search. The fundamentals work. They're just tedious to execute.

Update me on how it goes.

—Theo