How to Write a Tech Resume That Gets Past ATS

You applied to 40 jobs and heard back from 2. Your skills are fine. The problem is usually the document.

Most tech employers run applications through an applicant tracking system (ATS) before a person reads them. The software turns your file into text, sorts it into fields and lets recruiters search for keywords. If the parser can’t read your layout, or your resume never uses the words the recruiter searches for, you drop out of the pile before anyone sees your work.

This guide walks through a tech resume section by section, with before-and-after bullets you can copy and adapt.

How an ATS reads your resume

An ATS is database software for hiring. Common examples include Greenhouse, Lever, Workday and iCIMS. When you upload a resume, the system extracts the text and tries to map it to fields such as name, job titles, dates, employers, schools and skills. Recruiters then filter and search that data.

Two things go wrong at this stage:

1. Parsing fails. Greenhouse’s own support documentation says a resume may not import correctly if it lacks enough information, uses a non-standard file type or contains characters its parser does not recognize. Text inside images, text boxes and unusual graphics is a common culprit.
2. Search misses you. A recruiter types “Kubernetes” or “React” into the search bar. If your resume says “container orchestration” or “front-end frameworks” instead, you may not show up.

The U.S. Department of Labor’s CareerOneStop resume guidance gives the same advice: reuse the exact terms from the job posting, keep the layout simple and avoid tables, text boxes, columns and graphics.

Key takeaway: An ATS rarely “rejects” you on its own. It makes you hard to find. Your job is to be easy to parse and easy to search, then convincing once a person opens the file.

Format rules that keep your resume readable

Before you write a word, set up a format that every parser can handle.

Element	Safe choice	Risky choice
Layout	One column, top to bottom	Two columns, sidebars
Headings	“Experience”, “Skills”, “Education”, “Projects”	Creative labels like “Where I’ve Made Magic”
Contact details	In the main body, near the top	Inside the page header or footer
Skills	Plain text list	Skill bars, star ratings, logos
Fonts	Standard fonts such as Arial, Calibri or Georgia	Decorative or icon fonts
File type	PDF or .docx, unless the posting asks for something else	Images, scanned PDFs, design-tool exports
Length	1 page early career, 2 pages for experienced roles	3+ pages for private-sector roles

A quick test: open your PDF, select all the text and paste it into a plain text editor. If the order looks scrambled or chunks are missing, an ATS will probably struggle too.

If you’re applying for federal tech jobs, check length rules carefully. The U.S. Office of Personnel Management announced that USAJOBS limits resumes to 2 pages starting September 27, 2025, and applicants whose only resume runs longer can be found ineligible.

Section by section: what goes where

A strong tech resume usually follows this order. Move projects higher if you’re switching careers or just graduating.

Header

Name, city and state (no street address needed), phone, a professional email and links to LinkedIn and GitHub or a portfolio. Make the links plain text so they survive parsing. If you don’t have a portfolio yet, our guide on how to build a tech portfolio covers what to include.

Summary

Two or three lines that state your target role, your years of experience and your strongest skills. This top third of the page is what recruiters scan first, so match it to the job.

• Before: “Passionate, hardworking developer seeking a challenging opportunity to grow.”
• After: “Backend engineer with 4 years building Python and Go APIs on AWS. Focused on payments reliability, observability and reducing cloud costs.”

Skills

Group skills so they’re easy to scan. Use the same spelling as the posting, and include both the acronym and the full term once (“Continuous integration (CI)”).

• Languages: Python, TypeScript, SQL, Go
• Frameworks: Django, React, Node.js
• Cloud and DevOps: AWS (EC2, Lambda, S3), Docker, Kubernetes, Terraform, GitHub Actions
• Data: PostgreSQL, Redis, Snowflake

List only what you could discuss in an interview. Interviewers often pick an item from this list and ask you to go deep.

Experience

This is where most resumes lose. Each role gets a title, employer, location (or “Remote”) and dates in a consistent format, then 3 to 6 bullets. Put the most relevant and impressive bullet first.

Projects

Essential for new grads, bootcamp grads and career changers. Treat each project like a job: a name, the stack and 2 or 3 bullets about what you built and what happened.

Education and certifications

Degree, school and graduation year (optional if it was long ago). Add certifications that match the role, such as cloud or security credentials. Bootcamps belong here too.

How to write bullets that get interviews

A good bullet answers 3 questions: what did you do, how did you do it and what changed because of it? Former Google people-operations chief Laszlo Bock popularized a version of this as the “X-Y-Z” formula: accomplished X, as measured by Y, by doing Z.

Here are before-and-after examples for common tech roles.

Software engineer - Before: “Responsible for improving API performance.” - After: “Cut p95 latency on the orders API from 900 ms to 250 ms by adding Redis caching and rewriting 3 slow PostgreSQL queries.”

DevOps or cloud engineer - Before: “Worked on CI/CD pipelines.” - After: “Rebuilt CI/CD in GitHub Actions for 12 services, reducing average deploy time from 40 to 9 minutes and enabling daily releases.”

Data analyst - Before: “Made dashboards for the sales team.” - After: “Built a Power BI sales dashboard used by 30 reps, replacing a weekly manual Excel report and saving the team about 6 hours a week.”

IT support - Before: “Helped employees with tech issues.” - After: “Resolved an average of 25 tickets a day across Windows, macOS and Microsoft 365, and wrote 15 knowledge-base articles that reduced repeat password tickets.”

QA engineer - Before: “Did testing for the mobile app.” - After: “Automated 180 regression tests with Playwright, shrinking release testing from 2 days to 3 hours.”

Only use numbers you can explain. If you don’t have exact figures, use honest approximations (“about”, “roughly”) or describe scale: number of users, services, team size or frequency. Never invent a metric. A hiring manager will ask how you measured it.

Strong verbs to start bullets

Built, shipped, migrated, automated, reduced, designed, debugged, launched, refactored, scaled, secured, documented, mentored. Avoid “responsible for”, “helped with” and “worked on”, which describe a job description rather than an outcome.

Tailoring your resume for each job

You don’t need a brand-new resume for every application. Keep a “master resume” with every bullet you’ve ever written, then build a targeted version in 15 to 20 minutes.

1. Copy the job posting into a document. Highlight hard skills, tools, certifications and the job title.
2. Mark repeated terms. Words that show up 2 or 3 times are almost certainly searched.
3. Match your title line and summary to the role, as long as it’s truthful. If you’re a “Software Developer II” applying for “Backend Engineer”, your summary can say “backend engineer”.
4. Reorder bullets so the most relevant ones lead each role.
5. Swap in exact terms. If the posting says “CI/CD” and you wrote “deployment automation”, use the posting’s phrase.
6. Cut what doesn’t fit. An unrelated bullet costs space that a relevant one could use.

Don’t paste the job description in white text or stuff keywords into a hidden block. Recruiters see the parsed text, and stuffing looks dishonest.

For a sense of which skills employers keep asking for, see our roundup of tech careers and skills in demand.

Common tech resume mistakes

• Listing duties instead of results. “Maintained the website” says nothing about impact.
• A wall of buzzwords in the skills section that nothing in your experience backs up.
• Inconsistent dates and formatting, which CareerOneStop flags as a sign of weak attention to detail.
• Photos, age or marital status. U.S. employers don’t expect them, and they waste space.
• Old, irrelevant roles. Summarize jobs from 10+ years ago in a line, or drop them.
• Unexplained acronyms from a former employer’s internal tools. Translate “OPS-Tracker” into “internal incident-tracking system”.
• Typos in tool names. “Javascript” vs “JavaScript” won’t usually sink you, but “Kubernates” signals carelessness.

Where to start this week

If your resume needs work, here’s a 5-step plan:

1. Day 1: Strip your current resume into a plain, one-column template with standard headings.
2. Day 2: Rewrite your top 3 bullets per role using action, method and result.
3. Day 3: Build a grouped skills section and check every item against your experience.
4. Day 4: Pick 3 target postings, highlight their keywords and create a tailored version.
5. Day 5: Run the copy-paste text test, then ask someone in the field to read it for 60 seconds and tell you what role they think you’re targeting.

If you’re breaking into the field, pair this with our guides on how to get an entry-level IT job and how to switch careers into tech. Once interviews start coming, move on to coding interview prep.

Conclusion

A tech resume has 2 audiences: software that needs clean, searchable text and a person who needs proof you can do the job. Keep the format plain, use the posting’s language and turn every bullet into a small result. That combination gets you past the filter and into the conversation.

Sources

• CareerOneStop: Resumes (U.S. Department of Labor) — ATS keyword matching, simple formatting, avoiding tables and graphics, proofreading
• Greenhouse Support: Why didn’t the candidate’s resume import correctly? — reasons resumes fail to parse in an ATS
• OPM: Agency guidance on the two-page limit on resume length — USAJOBS 2-page resume limit and effective date