How to Write a Resume That Gets Interviews

What a recruiter actually does with your resume

Most resumes are scanned, not read. A recruiter spends roughly six to ten seconds on the first pass — long enough to register your name, your current title, where you've worked, and whether the words on the page broadly match the job. If those signals look right, the resume moves to a longer read. If they don't, it's filed and forgotten. That short first scan is the only audience that matters for the top third of your page; everything below assumes you've already passed it.

This single fact reshapes everything about writing a resume. The top of the page is prime real estate, and you spend it on the things a recruiter is checking in the first six seconds: your name, your current title, a one-line summary that signals seniority and specialism, and clean contact details. Everything else — even your career-defining project — comes after, because no one will read it if the top doesn't pass.

The header — get the basics right

Your name in a large, bold, easy-to-read typeface. Your current title directly underneath. Then a single line of contact details: email, phone, city (not full address), and one professional link — LinkedIn, GitHub, or your portfolio. Skip Twitter, Instagram, and personal blogs unless they are directly relevant to the role. Use a real email address — first-last@gmail.com is fine; an address from your university or your old workplace is not.

Don't include your date of birth, marital status, or a photo (unless you are applying in a country where photos are expected). These add legal risk for the employer and bias risk for you, and they take up space that should be earning you an interview.

The summary — your elevator pitch

Two or three sentences that explain who you are, what you do, and what you're known for. This is the single hardest section to write because it forces you to commit to a positioning. Generic summaries ("results-driven professional with a passion for excellence") are worse than no summary at all — they signal that you couldn't think of anything specific to say.

A good summary names a specific expertise, a specific kind of impact, and the kind of role you want. Example: "Frontend engineer with seven years of experience leading design-system work at consumer-scale companies. Specialist in accessibility, performance, and the React/TypeScript stack. Looking for a senior IC role on a product where the UI is the product." That tells a recruiter, in three sentences, exactly what kind of role to put you in front of.

Experience — bullets that prove impact

Experience is the most important section of your resume and the one most candidates write badly. The standard mistake is to describe what you were responsible for ("responsible for maintaining the customer database"). Recruiters know what your title is responsible for; they want to know what you actually did. The fix is to rewrite every bullet around an action verb and, where possible, a number.

A useful template: action verb + what you did + how much / by how much / for whom. Examples: "Led migration of the checkout flow from REST to GraphQL, cutting page weight 28% and improving conversion 6%." "Mentored two junior engineers through promotion to mid-level." "Reduced flaky tests in the CI pipeline from 11% to under 1% over four months." Each of those bullets tells a story: you, doing a specific thing, with a measurable outcome.

Three to five bullets per role is the right amount. Lead with the most impressive. If you can't quantify an achievement, name the audience or scope instead: "Authored the team's onboarding documentation, used by every new hire since." It still proves impact even without a percentage.

Skills — keywords that get you past the ATS

Most applications pass through an Applicant Tracking System before a human ever sees them. The ATS scans the resume for specific keywords that match the job description, then ranks candidates by how many keywords they hit. The skills section is the cheapest place to load relevant keywords without affecting readability.

Build the list by copying the job description into a notes file and circling every concrete skill or tool mentioned. If you have real experience with it, it goes on your skills list. If you don't, leave it off — both because lying gets caught at interview and because a mismatch with your bullets makes the ATS score lower, not higher. Group skills by category (Languages, Frameworks, Tools) so the list scans well to a human, and keep the total under about 20 items. A skill list with 60 entries looks like a junior who can't prioritize.

Education — short, accurate, and in the right place

For recent graduates, education goes near the top, immediately after the summary, and includes degree, school, dates, and relevant coursework or honors. For everyone else, education moves to the bottom and shrinks to a single line per degree — degree, school, year. GPA disappears after about three years in the workforce; no one is asking. Continuing education (bootcamps, certifications, online courses) goes here too if relevant; skip it if it isn't.

Projects — the lever for newer candidates

For students, career-switchers, and anyone with thin work history, the projects section is the single biggest difference between an interview pile and the reject pile. A real project — even a side project — proves you can ship. List two or three, each with a one-line description and either a link or a metric. "Built a Chrome extension that translates Twitch chat in real-time, 800 weekly active users." "Open-source TypeScript library for date math, 2.3k GitHub stars." Those bullets do more for an entry-level resume than a year of unrelated experience.

For senior candidates, the projects section is optional. Use it if you have a public portfolio or notable open-source work, but don't pad it with toy projects — at senior level, weak projects look like a step backwards.

Formatting rules that pass the ATS

ATS software has improved a lot in the last five years, but it still mishandles three things: images, tables, and unusual section headings. Use real text everywhere — no skill graphics, no rating bars, no name in a header logo. Use standard section headings the parser recognizes: "Experience," "Education," "Skills," "Projects." Don't put anything in a header or footer (some parsers ignore them entirely). Save as PDF generated from clean HTML or Word — the free resume builder on sourcecodestack does this automatically, with three template choices that all pass standard ATS parsers cleanly.

One page or two?

One page for almost everyone with fewer than 10 years of experience. The discipline of fitting onto one page forces you to cut weak bullets and keep only the strongest ones, which is exactly what a recruiter wants to read. Two pages are fine for very senior candidates with substantial relevant history, or for academic/research roles where a longer CV is the convention. Three pages is essentially never appropriate outside academia.

If you're at the borderline, shrink the margins from one inch to three-quarters of an inch, switch to an 11pt font from 12pt, and tighten line spacing slightly. Most one-page-to-two-page problems are solvable with formatting before they need cuts.

Common mistakes that get resumes rejected

Typos still kill resumes — read it aloud, then have a friend read it. Inconsistent date formats ("Jan 2022 – present" mixed with "2020 to 2022") signal sloppiness. A buzzword-stuffed summary signals that you have nothing specific to say. Vague responsibilities ("led various initiatives across the team") signal that you can't name any specific outcome. Outdated skills (HTML 4, jQuery, Subversion) signal that your knowledge has stagnated. Cut every one of those before submitting.

The single most underused fix is the tailored resume. Send a slightly different version to each role you really want — the summary tweaked to match the title, the skills reordered to lead with what they listed, the strongest matching bullets promoted higher. It takes 15 minutes per application and roughly doubles your interview rate.

Cover letter — short, specific, sent

A good cover letter is three short paragraphs. First: why this company specifically. Second: a single concrete story from your experience that maps directly to what the role needs. Third: why you're a fit and a single sentence on availability. No "Dear Hiring Manager." No "I am writing to apply for the role of." Just open with the hook — what excites you about them — and earn the read. Most cover letters are skipped; the ones that aren't are short, specific, and clearly written by a human.

After you send

Save a copy of the exact resume you sent, with the date and the company in the filename. When you get the interview, you need to know which version they read. Set a polite follow-up reminder for two weeks out if you don't hear back. And keep iterating — the resume that lands an interview gets revised after the interview, because what you learned in the conversation tells you which bullets resonated and which fell flat. The resume you ship today is not the one you ship next month, and that's the right way to do it.

When you're ready to start, open the free resume builder — six templates, live preview, autosave, free PDF export, no signup, no upload. Build it, iterate, export, and ship.

Chronological, functional, or hybrid?

There are three resume formats, and choosing the right one matters. The reverse-chronological format lists your jobs newest-first and is the default for good reason: recruiters expect it, ATS software parses it cleanly, and it shows career progression at a glance. Use it unless you have a specific reason not to. The functional format leads with skills and downplays dates; it's sometimes used to mask employment gaps, but recruiters know that, so it can raise suspicion. The hybrid format opens with a strong skills summary and then lists chronological experience underneath — a good fit for career-changers who want to foreground transferable skills while still showing a clear history. For the vast majority of people, reverse-chronological is the safe, effective choice.

Action verbs that carry weight

Weak bullets start with "responsible for" or "helped with." Strong bullets start with a verb that implies ownership and result. Reach for verbs like led, built, shipped, launched, designed, architected, automated, reduced, increased, migrated, mentored, negotiated, scaled, and owned. Match the verb to the achievement: "automated" for a process you scripted, "reduced" for a cost or time you cut, "led" for people or projects you drove. Vary them — a column of identical "Developed… Developed… Developed…" bullets reads as monotonous and lazy. The verb is the first word a recruiter's eye lands on in each bullet, so it does disproportionate work in shaping their impression of you.

Quantifying achievements when you have no numbers

"Quantify everything" is good advice that stalls people who don't think their work had metrics. The trick is that almost everything can be quantified with a little thought. No revenue figure? Use scope: "supported 12 enterprise clients," "owned 4 microservices," "mentored 3 juniors." No percentage? Use frequency or volume: "published weekly," "processed 500+ tickets a month," "reviewed every release." No hard data at all? Use before-and-after framing: "replaced a manual process that took half a day with a script that runs in minutes." The goal isn't false precision — it's giving the reader a concrete sense of magnitude. A bullet with any anchor of scale beats a vague one every time.

Tailoring each application (the highest-ROI habit)

The single change that most improves interview rates is tailoring. Keep one master resume with everything, then for each role you really want, spend fifteen minutes making a focused copy: rewrite the summary to echo the job title, reorder the skills list to lead with what the posting emphasizes, and promote the two or three bullets that map most directly to the role's responsibilities. This does two things at once — it raises your ATS keyword match, and it makes the human reader feel the resume was written for their job, not blasted to a hundred companies. Use the JSON export in the builder to save a master copy, then import and tweak it per application so you never lose your base version.

Proofreading and the final pass

Before you export, do three passes. First, read it aloud — your ear catches clumsy phrasing your eye skims over. Second, check every date, company name, and title for consistency in format and accuracy; mismatched date styles are a classic tell of a rushed resume. Third, hand it to one other person, because you cannot proofread your own writing reliably after staring at it for an hour. Confirm the file name is professional (FirstName_LastName_Resume.pdf, not "resume_final_v3.pdf"), open the exported PDF to make sure nothing reflowed oddly, and only then attach it. The few minutes this takes are the cheapest insurance you'll ever buy against a silly mistake costing you an interview.