[NAME] — Backend Engineer ([Primary stack])
[City, RO] (optional) · [Email] · [Phone] (optional) · [LinkedIn] · [GitHub] · [Portfolio]

SUMMARY
2–4 lines: what backend systems you built, your main stack, your strongest outcomes, and what you’re looking for next.

BACKEND HIGHLIGHTS
- [impact: performance / cost / reliability] using [stack] in [context]
- [ownership: API/DB/async/observability] with a verifiable outcome
- [quality: testing / security / auditability] with a verifiable outcome

EXPERIENCE
[Company] — [Role] · [Period] · [City/Remote]
- Impact + context + stack + outcome (p95, cost, incidents, delivery speed)
- Ownership (API design, DB, queues, observability)
- Quality (tests, security basics, audit logs, conventions)

[Company] — [Role] · [Period]
- 2–4 bullets

SELECTED PROJECTS (optional; recommended for juniors)
[Project] — [Link]
1–2 lines about what it does and for whom.
- What you built (stack)
- What problem it solves / what you learned

SKILLS
Languages: …
Frameworks: …
Data/DB: …
Cloud/DevOps: …
Observability: …
Testing: …

EDUCATION & CERTIFICATIONS
[University / Course] — [Period]
[Certification] — [Year]