A complete guide to a software engineer resume

Before anyone evaluates your engineering ability, they evaluate your resume. For most roles at top tech companies, it's the first and most filtered layer of the software engineer interview process, and the one that decides whether everything you've built over your career gets a second look.

The structure of a great software engineer resume hasn't changed dramatically in the last few years. What's changed is what recruiters and hiring panels are watching for, how AI is reshaping screening, and what signals separate engineers who get interviews from engineers who don't.

Why your resume still decides everything

The reality for most candidates applying cold is that a human recruiter (or an AI-assisted screening system) will look at your resume for a few seconds and make a preliminary judgment. If your resume doesn't surface the right signals quickly, you won't get a recruiter phone screen, no matter how strong an engineer you are.

As AI tools have flooded the market, application volume has climbed, and hiring teams have leaned on automation to filter. At the same time, the bar for what counts as a strong senior signal has risen. Hiring panels are looking for clearer evidence of ownership, architectural thinking, and impact than they were even three years ago. 

What recruiters and hiring panels actually scan for

The reality of the initial scan

The "six-second scan" line gets repeated often, and while the exact number varies, the underlying truth holds. A recruiter or automated system spends very little time on the first pass.

What they're doing in that pass is looking for a handful of signals:

• Where you've worked and at what level
• How long you've been in the industry
• What kinds of systems you've built or worked on
• Whether you've operated at the scope the role calls for
• Clear evidence you know how to communicate impact

If those signals surface cleanly in the top third of the page, you move forward. If they don't, the file closes. For a perspective from inside the process, an ex-Meta recruiter wrote up what it actually takes to stand out as a software engineer candidate.

How AI screening tools filter applications

A growing share of companies now use AI-assisted screening at the application review stage. 

The tools vary, but the underlying behavior is consistent. They score resumes against job description requirements, surface matches for keywords and experience patterns, and rank candidates for recruiter review.

This has two implications for how you write.

First, keyword alignment matters more than it did five years ago. If the job description lists Kubernetes, distributed systems, and Go, and your resume uses slightly different terms (K8s, scaling infrastructure, Golang), an AI screen may under-score you even when you're a strong match. Using the terms from the job description, where they're accurate, is now table stakes.

Second, keyword stuffing gets penalized. Modern screening tools are trained to spot it, and recruiters who review the top-ranked resumes see through padded skills sections quickly. A resume that lists every technology you've ever touched in a skills soup signals a lack of focus.

What’s signal vs stuffing

The useful mental model is signal density. Every bullet, every line, every skill listed should give a recruiter or hiring manager a clear piece of evidence about what you've built, owned, or decided. Resumes that perform well read like a curated highlight reel of engineering work. Resumes that underperform read like a job history list.

How senior resumes get read differently

At the mid-level, recruiters are looking for baseline technical competency, reliable delivery, and some evidence of autonomy. At the senior level, the bar shifts toward scope, ownership, and the ability to make sound technical decisions under ambiguity. As you get more senior, it shifts again toward architectural thinking, cross-functional impact, and the ability to raise the performance of the engineers around you.

Your resume should make clear which of these levels you're operating at. Many strong engineers quietly mislevel themselves on paper.

The structure of a strong software engineer resume

The standard structure still holds. What's changed is what each section should emphasize.

Header and contact essentials

Keep this tight. Full name, email, phone number, city (or time zone if you're remote), and links to your LinkedIn and GitHub. That's it.

Skip the objective line, the inspirational quote, and the headshot. None of those help at top-tier companies and some actively hurt.

Your LinkedIn profile should cleanly match your resume. If the two tell different stories, recruiters notice.

The professional summary (and when to skip it)

A short summary at the top is optional and often skipped. When done well, it frames how you want to be evaluated in a sentence or two.

A strong summary names your seniority, your technical core, and the kinds of systems you've worked on. 

Write a summary that makes you stand out, reads cleanly, and positions you for a recruiter to place you in the right role family. If you can't write a summary that adds signal beyond what your work experience already shows, skip it. A bad summary is worse than no summary.

Work experience

This is the core of your resume and where most of the evaluation happens. Each role should include:sZX

• Company name and a one-line descriptor if the company isn't well-known
• Your title
• Dates (month and year)
• Three to six bullets describing your work

Projects

Projects are most valuable when they're filling a gap. If you're transitioning into software engineering from another field, projects demonstrate technical ability. If you're a mid-level engineer at a less well-known company, projects can show scope and ambition that your job hasn't let you demonstrate.

For senior candidates at strong companies, projects are usually not the highest-value use of space. Your work experience is doing the work. If you do include a projects section, pick two or three that demonstrate real engineering decisions, scope, or technical depth. A list of tutorial-completed side projects hurts more than it helps.

Skills section

The skills section is lower-value real estate than most engineers treat it as. It exists primarily to surface keyword matches for AI screening and recruiter scans.

Organize it by category (languages, frameworks, infrastructure, databases) and list only what you've actually worked with substantively. If a recruiter asks you about React in an interview, you should be able to talk about it with depth.

Resist the urge to pad this section. A concise skills block of ten relevant technologies reads stronger than a sprawling list of forty.

Education

Keep education brief unless you're a recent graduate or targeting companies that weight education heavily. University, degree, and graduation year are usually enough. Drop GPAs after your first few years in the industry unless they're exceptional.

Engineers making a career transition without a CS degree face a different set of choices.

What to cut

What you leave off matters as much as what you include. Cut:

• Interests and hobbies, unless a specific hobby is directly relevant (like a technical side project or open source contribution)
• "References available on request"
• Objective statements
• Every tutorial project you ever completed
• Acronyms and company-specific jargon that only make sense inside your last company
• Full paragraphs of prose where bullets would be cleaner

Writing impact-driven bullet points

This is where the resume is won or lost. Hiring managers read bullets quickly, and the quality of your bullets determines whether they want to spend an hour of an engineer's time interviewing you.

Scope, ownership, and measurable outcomes

Every strong bullet answers three questions implicitly:

1. What did you do?
2. At what scope or for what system?
3. What was the outcome?

Outcomes don't always need to be numeric, but numbers carry weight when they're accurate. Latency reductions, throughput increases, reliability improvements, dollars saved, team size led, systems owned. Real numbers that you can defend in an interview are some of the strongest signal you can put on paper.

Applying the STARR framework to resume bullets

The STARR framework (Situation, Task, Action, Result, Reflection) is most often associated with behavioral interview answers, but a compressed version works well for resume bullets too. A tight bullet collapses situation, action, and result into a single line.

How AI is reshaping resume screening and writing

AI has changed the dynamics on both sides of the resume. Companies are using it to screen applications, and candidates are using it to write them. Understanding both sides is useful.

How companies are using AI to screen applications

Most mid-size and large companies now run applications through some form of automated screening before a human recruiter looks at them. These tools score resumes against the job description, surface matches, and rank candidates for recruiter review.

The practical implications:

• Structured formatting matters. Clean text, standard section headings, and no multi-column layouts. Tables and graphics often confuse parsers and can drop your resume entirely.
• Language should align with the job description, where accurate. Use the same terms the company uses.
• PDFs and Word documents both work, but keep the file simple.

The broader shift toward AI in hiring is also changing what companies look for on the engineering side. 

How candidates are using AI to write

Many candidates now draft resumes with AI assistance. This works when the candidate stays in the driver's seat, using AI to sharpen their own language and catch weak phrasing. It fails when the output reads generic, overclaims on scope the candidate can't defend in an interview, or uses language the candidate wouldn't use in conversation.

A resume generated from a prompt without careful editing is easy to spot. It uses the same kinds of phrases across candidates, tends toward vague impact claims, and doesn't survive follow-up questions in an interview.

Treat AI as an editor. It's useful for pressure-testing your bullets, helping you find sharper language, and catching places where you've undersold a contribution. It's less useful for generating scope or impact you don't actually have.

Common resume mistakes experienced engineers make

A handful of mistakes often appear in resumes from experienced engineers. Most are fixable in an afternoon.

• Listing every technology you've ever touched. Skills sections should be curated. A shorter, stronger list reads better than a sprawling one.
• Vague ownership claims. "Contributed to" and "part of the team that" signal that the engineer wasn't driving the work. If you led something, say so. If you didn't, find a way to describe your actual contribution in specific terms.
• Missing quantitative impact. Numbers are not mandatory on every bullet, but the absence of any numbers on a senior-level resume is a signal in itself. Find the metrics you can defend and use them.
• Over-tailoring for every application. Tailoring is valuable at the top of the resume (summary, top bullets, skills). Deep tailoring for every application usually isn't worth the time. A strong base resume with light customization per role performs almost as well with a fraction of the effort.

Frequently asked questions

How long should my resume be? One page for most engineers, including senior candidates. Two pages is acceptable if you have more than ten years of experience and the second page is pulling weight. More than two pages almost never works.

Should I include a summary or objective? Skip the objective. A short summary is optional. Use it if it adds signal beyond what your work experience already shows. If it doesn't, leave it off.

How do I handle employment gaps or layoffs? Be direct and brief. Layoffs are common, and hiring panels read them as external events, not candidate signals. A short note on the resume or a line in the cover letter is often enough. For longer gaps, brief, honest framing works better than trying to hide them.

Should I tailor my resume for every application? Light tailoring (skills emphasis, top-bullet ordering, summary adjustment) is worth it for roles you care about. Deep tailoring for every application usually isn't. Build a strong base resume and adjust the top third per application.

Do personal projects still count? Yes, when they demonstrate real engineering decisions or fill a gap your work history doesn't. No, if they're tutorial projects or half-finished experiments. Quality beats quantity in this section.

Should I use AI to write my resume? Use AI as an editor. It's useful for pressure-testing bullets, finding sharper language, and catching weak phrasing. It's less useful for generating scope or impact you don't have. Authenticity is catching up as a screening signal.

What about ATS-friendly formatting? Stick with clean, single-column formatting, standard section headings, and simple fonts. 

Get personalized feedback on your resume

Formation Fellows get structured, mentor-led preparation for every stage of the software engineer interview process, including resume reviews with mentors who've worked as hiring managers at top tech companies, unlimited mock interviews, personalized skill development, and career and negotiation support.

If you're preparing for stronger roles and want personalized feedback on your resume and a mentor-led path through the rest of the interview process, apply to Formation.

Formation also runs free Studio Workshops, live, mentor-led sessions built around how interviews actually run at top tech companies. These aren't passive webinars. Engineers think out loud, make decisions, and debate tradeoffs in real time alongside experienced mentors. If you want to see what interview-ready actually looks like before committing to a longer program, a Studio Workshop is a good place to start.