Tech & product example
Software engineering resume example
A software engineering resume example for senior engineers applying across Amsterdam and European tech hubs. Six years of production ownership, systems metrics and open-source contribution — the impact-led format engineering managers screen for before technical interviews.
Por qué este CV está estructurado así
Ravi is a senior SWE with six years — experience leads with scope, latency and uptime metrics, not a skills dump. Stack appears in bullets (TypeScript, Python, PostgreSQL) tied to outcomes. Open-source contribution is one line in experience, not a separate vanity section. TU Delft BSc sits below experience — recruiters hire on shipped systems, not GPA. Minimal template maximises ATS parsing for EU tech portals. No photo. One page is standard unless staff-level scope genuinely needs two.
Professional Summary
Senior software engineer with six years building distributed services in TypeScript and Python. Owned auth, billing and payments platforms serving 120k+ MAU with measurable reliability and latency improvements.
Experience
- Shipped auth and billing services handling 120k MAU with 99.95% uptime over 12 months
- Cut p95 API latency 35% by introducing query caching and connection pooling in PostgreSQL
- Owned on-call for payments; reduced incident MTTR from 90 to 35 minutes
- Led migration from monolith checkout to event-driven microservices; zero-downtime cutover
- Built React and Node.js features for B2B workflow product used by 2,400 accounts
- Introduced CI/CD pipeline cutting deploy time from 45 to 12 minutes
- Maintained open-source CLI tool (1.2k GitHub stars) for API schema validation
Education
Cum Laude · Distributed Systems, Algorithms, Software Architecture
Skills
Languages
Minimal template · see layout
Qué buscan los recruiters
- Scope and ownership — systems, teams, on-call named explicitly
- Metrics: latency, uptime, MAU, MTTR with mechanism in the bullet
- Stack tied to outcomes, not a keyword laundry list
- Production experience over tutorial or coursework projects
- Seniority-appropriate bullets — no intern language at six years
- One-page default; two pages only at staff scope with justification
- Open-source only when maintained and relevant to role
Errores comunes
- Skills section with 30 technologies and no shipped outcomes
- Listing every project from university at senior level
- Vague “improved performance” without p95 or uptime numbers
- Hiding on-call or incident ownership when applying to platform roles
- Two-column layouts that break EU tech ATS parsers
Keywords ATS
| Keyword | Why it matters |
|---|---|
| TypeScript | Core stack |
| PostgreSQL | Data layer |
| Microservices | Architecture signal |
| CI/CD | Delivery practice |
| On-call | Operational ownership |
| Latency | Performance metric |
| AWS | Cloud platform |
| Open source | Community signal |
Preguntas frecuentes
One page is standard in Europe for up to ~8 years if bullets are impact-dense. Two pages only when staff-level scope cannot fit.