TechnologyMid level

Software Engineer CV Example

Shipped features, measured performance wins and a clean stack list — engineering impact without buzzwords.

Engineering CVs fail in two opposite ways: a wall of every technology ever touched, or vague "worked on the backend" bullets. This example does neither — a focused stack, and bullets that name the system, the change and the measured effect.

Why this CV works

Latency, throughput and uptime numbers make the engineering claims falsifiable — exactly what technical screeners look for.
The stack list is short and honest: twelve technologies the candidate could be interviewed on, not forty they once installed.
Operational maturity (on-call, ack times, test coverage) signals someone who runs software, not just writes it.
One process contribution (the design-doc template) shows influence beyond assigned tickets.

The professional summary

Software Engineer with 5 years building payment and logistics systems in Python and Go. Cut checkout p95 latency from 1.8s to 420ms, designed an idempotent webhook pipeline handling 2M events/day, and maintains services with 99.95% uptime. Comfortable owning features from design doc to production dashboard.

Name your two main languages, the domain you build in, and your single best measured win. Avoid "passionate" — a p95 number carries the enthusiasm for you.

Writing the work experience

Bullet formula: what you changed, in which system, measured how. If you cannot measure it, name the failure mode you removed ("a class of silent overnight failures").

Turning duties into achievements

Instead ofWorked on improving API performance

WriteCut checkout API p95 latency from 1.8s to 420ms by removing N+1 queries and adding a Redis read-through cache

Instead ofWrote unit tests for the codebase

WriteRaised payments-module test coverage from 41% to 86%, halving regression bugs found in QA

Skills on this CV

PythonGoPostgreSQLRedisREST APIsDockerKubernetesAWSCI/CDUnit testingSystem designMessage queues (Kafka)

ATS tips for Software Engineers

List languages and tools as individual skills — "Python", "Go", "Kubernetes" — because filters match tokens, not sentences.
Mirror the ad's framework names exactly (e.g. "Flask", "Django"); a generic "Python web frameworks" matches nothing.
Include "CI/CD" as written — it is one of the most-filtered tokens in engineering ads.

ATS checks help identify potential compatibility issues, but employers and ATS platforms use different criteria — no template or score can guarantee an outcome.

Writing tips

Every performance claim needs a before and after; a lone "improved performance" is noise.
Uptime and on-call details differentiate you at mid-level more than another framework does.
Keep personal projects off once you have 3+ years of production bullets — unless they have real users.