Technology · Mid-career
Software Engineer Resume Example
This example suits a software engineer with four to eight years of experience who works across more than one language and layer. It shows how to present breadth without a shapeless list of technologies: every tool appears inside a result, and each result has a before and an after.
The example resume
Laid out in the Blueprint template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.
Naledi Mokoena
Software Engineer
- naledi.mokoena@example.com
- +1 555 0114
- Cape Town, South Africa
- github.example.com/nmokoena
- linkedin.example.com/in/naledi-mokoena
Professional summary
Software engineer with six years of experience building and running services for parcel tracking and delivery routing. Comfortable across the stack, from Kotlin and Python services to TypeScript interfaces, and in the habit of measuring before and after every change. Recently led the redesign of a tracking pipeline that handles 1.2 million scan events a day.
Work experience
Software Engineer
Karoo Line Freight Systems, Cape Town
Apr 2022 – Present
- Led the redesign of the parcel tracking pipeline, replacing nightly batch imports with event streaming so customers see scans within 30 seconds instead of the next morning
- Cut p95 response time of the tracking API from 900 ms to 240 ms by adding a read model in PostgreSQL and caching depot lookups in Redis
- Built the driver manifest service in Kotlin, used by 340 drivers across 9 depots, with offline sync for areas with poor mobile coverage
- Introduced contract tests between 6 services, reducing integration defects found after release from about 5 a month to 1
- Mentored 2 junior engineers through weekly pairing and reviewed their first design documents
Junior Software Engineer
Harbour Mile Couriers, Cape Town
Feb 2020 – Mar 2022
- Developed a route planning tool in Python that grouped deliveries by suburb and time window, saving dispatchers roughly 6 hours of manual planning a week
- Rebuilt the customer booking form in TypeScript and React, raising completed bookings on mobile from 61% to 74%
- Wrote the first automated test suite for the billing module, taking coverage of rate calculations from nothing to 85% of branches
- Shared the on-call rota and wrote runbooks for the most frequent alerts, which new engineers now read in their first week
Projects
gtfs-lint
Open-source side project
2023 – Present
- Wrote a command-line tool in Go that checks public transport timetable files for 14 common errors, now used by 3 community transit projects
Education
BSc Computer Science
Table Valley University, Cape Town
2016 – 2019
Skills
Languages: Kotlin, Python, TypeScript, Go, SQL
Backend: REST and gRPC APIs, PostgreSQL, Redis, Kafka
Frontend: React, HTML, CSS
Practices: code review, automated testing, design documents, on-call
Tools: Git, Docker, GitHub Actions, AWS (ECS, S3, RDS)
Open this example in the resume builder Start empty with this template
Why this resume works
- The summary describes the kind of systems Naledi builds (parcel tracking and delivery routing) before any language, which suits a generalist applying to teams with different stacks.
- Each bullet pairs a technical decision with a result the business would recognise: scans visible within 30 seconds, dispatchers saving six hours a week, more completed bookings on mobile.
- Latency is given as a before and after figure at a named percentile (p95 from 900 ms to 240 ms), which an engineer reading the resume can judge far more easily than "improved performance".
- Kotlin, Python, TypeScript and Go each appear inside a bullet that shows them in use, so the skills list is backed by evidence instead of standing alone.
- Mentoring, contract tests, runbooks and the on-call rota show the engineering habits expected at mid level without a separate "soft skills" section.
What employers look for in this role
- Design, build and maintain services and user-facing features, from a written requirement to production
- Write automated tests and review other engineers' code
- Investigate production incidents, fix the cause and record what was learned
- Break large pieces of work into deliverable steps and estimate them with the team
- Improve the performance, reliability and maintainability of existing code
- Clarify with product managers and designers what is being built and why
Skills to consider
List only the skills you can back up with an example. These are the ones that come up most for this kind of role.
- Languages and data
- One or two languages in depth (for example Kotlin, Python, TypeScript, Go or C#), SQL and relational database design, REST or gRPC API design, Data structures and algorithms, Caching and message queues
- Engineering practice
- Unit, integration and contract testing, Code review, Version control with Git, CI/CD pipelines, Monitoring, logging and alerting, Writing design documents
- Working with others
- Estimating and breaking down work, Mentoring junior engineers, Explaining trade-offs to non-engineers, Incident communication
More bullet points to adapt
Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.
- Migrated a 40,000-line module out of a monolith into 3 independently deployed services over 8 months with no customer-facing downtime
- Reduced the CI pipeline from 22 minutes to 9 by running test suites in parallel and caching dependencies
- Found and fixed a memory leak in the label printing service that had forced a restart every 3 days
- Wrote the design document for address validation, compared 3 approaches and got agreement from 2 teams before any code was written
- Removed 12 stale feature flags and 6,000 lines of dead code, shortening the reading list for new engineers
- Added structured logging and trace identifiers across 5 services, cutting the typical time to find the cause of an incident from hours to under 20 minutes
Words that recur in adverts
These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.
Which sections to include
For a mid-level software engineer the experience section carries the application, so give it most of the page and put it directly under a short summary. Follow it with skills, grouped so a reader can find languages, data stores and tooling at a glance. Add a projects section only if it shows something your jobs do not, such as another language or open-source work. Education needs only the degree, institution and years once you have a few years of work behind you, and can sit at the bottom. Certifications matter less for general software roles than for cloud or security posts.
Mistakes to avoid
- Listing every language and framework you have ever touched, which hides the three or four you could be questioned on in depth; keep the list to what you would be comfortable using in an interview.
- Describing the team's project instead of your part in it, so the reader cannot tell whether you designed the service, fixed two bugs in it or only attended the stand-ups.
- Quoting performance gains with no baseline ("made the API 4x faster"); give the measure, the before and the after, for example p95 latency from 900 ms to 240 ms.
- Leaving out testing, code review, on-call and documentation because they feel routine, when these are what separate a mid-level engineer from a junior one.
- Linking to a code profile whose pinned repositories are tutorial clones or empty forks; add the link only if the work there supports the application.
Questions and answers
Should a software engineer resume be built around one programming language?
Only if the advert is. For a general software engineering role, lead with the kinds of systems you have built and show two or three languages in use. If the advert names a specific stack, move your experience with it into the summary and the first bullets, provided that is truthful.
How should I describe work covered by a confidentiality agreement?
Describe the problem and the result in general terms, without client names, internal system names or figures your employer treats as confidential. A relative figure such as "about a third faster" is often safe where exact volumes are not. If in doubt, check your contract or ask your employer.
Do I need to include a link to my code?
No. Many good engineers have no public code because their work belongs to an employer. A link helps when the repositories show real, readable work that is relevant to the role; an empty or abandoned profile is better left off.
How much should I say about algorithms and data structures?
Very little on the resume itself. Mention them where they explain a result, such as replacing a nested loop with an index to cut a job from 40 minutes to 3. That knowledge is tested at interview, and the guide to preparing for a technical interview covers how.