Software engineer resume examples

What the bullets need to show

The US Bureau of Labor Statistics describes the work as analyzing users’ needs, designing and building software, keeping it working through maintenance and testing, and documenting it (Occupational Outlook Handbook). A reviewer reading your resume looks for your part in each of those:

• Ownership. What you designed, wrote, reviewed or led, as distinct from what your team shipped.
• Testing. How you knew your change worked, and what the tests caught.
• Shipping. How the change reached production: a release, a feature flag, a migration.
• Operations. On-call, incidents, postmortems and the fixes that came out of them.
• Working with others. Code review, mentoring, design documents, explaining a change to people outside engineering.
• The stack, in context. Languages and services named inside the bullet where you used them, then collected in the Skills section.

The questions that find the bullet

Answer these out loud for each project or system you worked on. They are the questions a good interviewer will ask anyway.

1. What did you build or change, and who used it?
2. Which part was yours? Did you design it, write it, review it or lead the people writing it?
3. How did it reach production?
4. How did you know it worked: tests, monitoring, a dashboard someone else owns, a ticket that stopped coming?
5. What broke, and what did you do about it?
6. For any number: where did it come from, and what was it before?
7. Which languages, frameworks and services did you use for this specific work?

Before and after, with the question that changed it

Priya Nair is a fictional backend engineer on a checkout and payments team. Her first drafts listed duties. One question each got the facts out.

Three of the six have no measured result. The payments bullet shows it as a ticket type that stopped arriving, the mentoring bullet as work the interns shipped on their own, and the migration bullet as downtime customers never saw.

Entry-level, mid-level and senior

Entry level and new graduates. Projects, internships and teaching-assistant work are your experience. Give each one a name, your role and dates, and say which part of a team project you wrote. Link a GitHub profile only if the code there is code you would discuss in an interview.

Mid-level. The examples above: systems you own, the incidents you handled and the people you helped. Most bullets should name a system, your part and a result you can explain.

Senior and staff. Your scope widens from your own code to your team’s technical direction, and at staff level across teams, so the questions shift to decisions: which design you proposed, which tradeoff you chose and why, who adopted it, and what you stopped from going wrong. Say “led” only where you led. A result that belongs to a whole team stays the team’s, with your part named.

A complete example

Priya’s resume, put together. Every experience bullet is one of the rewrites above, word for word.

What not to claim

• Numbers nobody measured. Latency, uptime, revenue or cost figures you can’t trace to a dashboard, a benchmark or a report. If you don’t know, describe what changed instead.
• The team’s result as yours. “Migrated the database” when you wrote one part of it. Name your part; the reader will respect the precision.
• Every technology the company uses. List what you worked in, not what was in the repository.
• Titles you didn’t hold. If you acted as tech lead without the title, keep the real title and describe the work in a bullet.
• Confidential details. Customer names, security incidents that were never made public, unreleased products and internal figures your employer hasn’t published.
• Code you can’t explain. If an AI assistant wrote much of a project, you still need to walk through every part you list. Say what you designed and checked yourself.

From your answers to bullets, in Hirova

Hirova, an AI resume builder for iPhone, runs the same kind of interview: it asks what you owned and what changed, sets your answers as bullets, and shows the words behind every number so you can confirm it. Nothing reaches your draft until you do.

1. Import or start fresh. Bring in a PDF or a photo of your resume. Hirova reads it on your iPhone; the file is not uploaded.
2. Answer a few questions. Three to five short questions about what you owned and what changed. Type or dictate, and skip any you like.
3. See your words set as bullets. Hirova rewrites your answers as resume lines in a consistent voice.
4. Check every fact. Each title, date and number shows the words it came from. Nothing reaches your draft until you confirm it.
5. Export a PDF. A typeset, text-based PDF you can send from the share sheet.

Your first resume is free, including the PDF in the Minimal design. Hirova Pro adds a tailored version for each job posting, with a cover letter for each. Hirova Pro is $19.99 a month or $79.99 a year in the US. The App Store shows your local price before you buy.