A software engineer resume should show what you built, how you checked it, and what happened when it reached production. This example follows a backend engineer whose work spans booking APIs, integration tests, incident investigation, and documentation.
Avery Chen and the resume below are fictional. The companies, project, and outcomes are illustrative. Use the structure to choose evidence from your own work, and replace every claim with something you can explain in an interview.
Avery Chen
Software Engineer, Backend Systems
(512) 555-0137avery.chen@example.comAustin, TX
Summary
Software engineer building appointment scheduling services with TypeScript, Node.js, and PostgreSQL. Designs API changes with product and support teams, adds tests for booking edge cases, and documents operational hand-offs after release.
Experience
- Built TypeScript API endpoints for rescheduling and cancellation, with PostgreSQL transactions that keep appointment and availability records consistent. (note 1)
- Added integration tests for overlapping appointments, time-zone changes, and repeat requests before releasing a revised booking flow. (note 2)
- Investigated duplicate booking reports with support, traced the retry path, and documented the fix and rollback steps for the on-call team. (note 3)
- Reviewed API changes in Git pull requests with engineers and product partners, recording contract decisions and migration notes for the client applications.
- Implemented a background export job in Node.js that prepares customer activity reports and reports failed runs to the operations queue.
- Reproduced customer-reported CSV formatting errors, added regression cases, and clarified the expected file format in release notes.
Education
Skills
TypeScript, Node.js, PostgreSQL, REST APIs, Integration testing, Git, Incident investigation
Selected project
Availability rule checker (personal project, 2024–present) — Built a small TypeScript tool that checks imported scheduling rules for overlapping windows and invalid time zones. Wrote setup instructions and sample inputs so another engineer could review the checks. (note 4)
- Note 1:
The bullet names the feature, the implementation choice, and the data problem it addresses.
- Note 2:
The tests cover actual booking edge cases, rather than a vague claim of “quality.”
- Note 3:
Production work is shown through investigation and documentation, without an invented reliability metric.
- Note 4:
The project follows the work history because Avery's jobs are the stronger evidence. It adds independent work on a related problem.
Show the system and your contribution
Avery's headline says backend systems, and the first role names an appointment scheduling product. The experience bullets then identify concrete work: rescheduling endpoints, transactional updates, booking edge cases, and a duplicate-booking investigation. That helps a reader understand what Avery changed in the system. A technology list alone could not show ownership or judgment.
The first bullet is specific without a performance number. It connects the API change to keeping appointment and availability records consistent. If you have a measured result from your own work, include the metric and what it measured. If you do not, explain the design constraint, test case, or operational problem you addressed. The bullet-point guide offers a way to make that evidence clear.
Experience
- Built TypeScript API endpoints for rescheduling and cancellation, with PostgreSQL transactions that keep appointment and availability records consistent.
- Added integration tests for overlapping appointments, time-zone changes, and repeat requests before releasing a revised booking flow. (note 1)
- Investigated duplicate booking reports with support, traced the retry path, and documented the fix and rollback steps for the on-call team.
- Note 1:
The named edge cases show what the tests protected. Add only cases you actually handled.
Keep tools tied to work
TypeScript, Node.js, and PostgreSQL appear in Avery's work history as well as the skills line. Integration testing is supported by the booking-flow bullet, and incident investigation by the duplicate-booking report. The listed tools are therefore useful clues, not substitutes for evidence.
Skills
TypeScript, Node.js, PostgreSQL, REST APIs, Integration testing, Git, Incident investigation
When tailoring your resume, start with the posting's actual work: APIs, data modeling, testing, on-call support, or something else. Use the employer's term when it accurately describes your work. Do not add a cloud platform or language merely because the posting names it. If you used a tool only in a class or side project, show it in that context instead of letting the skills section imply production experience.
Include a project when it adds different evidence
Avery includes a small availability-rule checker because it shows independent work on a related problem. The project has dates, a purpose, implementation detail, and setup instructions that another engineer could review. It does not claim that the project had users or business results. The personal-projects guide explains when a project earns space and how to describe unfinished or private work honestly.
Selected project
Availability rule checker (personal project, 2024–present) — Built a small TypeScript tool that checks imported scheduling rules for overlapping windows and invalid time zones. Wrote setup instructions and sample inputs so another engineer could review the checks.
If your recent employment already proves the same skills, cut a redundant project. If the project is your best evidence for a particular technology, keep it and explain what you personally built.
Adapt the example to a posting
For a backend API role, Avery could lead with the booking endpoints and database consistency. For a reliability-focused role, the incident and regression-test bullets may matter more. Both versions should preserve the real job titles and dates. The order of evidence can change without inventing an outcome or overstating ownership.
This example is for an engineer with professional experience. A new graduate can use a different balance of internships, coursework, and projects. Keep each item labeled for what it was. For a contrasting example of evidence in a licensed profession, see the registered nurse resume example.