Fullstack Developer CV — ATS-Friendly Template and Writing Guide

Write a 4–6 line summary that demonstrates you build complete features across the stack, not just UI screens. Name your core front-end and back-end technologies (for example React with TypeScript and Node.js/Express) and include at least one database technology such as PostgreSQL. Add one reliability or performance KPI—e.g., “reduced p95 latency by 38%” or “maintained 99.95% uptime”—and explicitly connect it to what you changed (caching with Redis, database indexing, load testing, or query optimisation). Show that your work ships safely by mentioning CI/CD with GitHub Actions and automated quality checks like Jest/Supertest and Playwright so recruiters can trust your engineering rigour. If you deploy on AWS using Docker, state it directly (e.g., ECS or EC2) to prove your software survives real infrastructure constraints, not just local development.

Use a Core Skills block that is ATS-friendly but recruiter-readable by grouping by Front End, Back End, Data and DevOps. For Front End, include React, TypeScript, and state management such as React Query or Redux Toolkit, plus testing tools like Playwright or Cypress to show you can prevent regressions. For Back End, list Node.js with Express or NestJS, REST API development, OpenAPI/Swagger documentation, and authentication/authorisation using OAuth 2.0/OpenID Connect or JWT with RBAC. For Data, include PostgreSQL with migrations (for example Prisma migrations, Flyway or Liquibase), plus performance techniques like indexing, query tuning and transactional integrity. Where you’ve used performance improvements, mention Redis caching and background processing using a queue system such as BullMQ (or equivalent) to reinforce production readiness. For DevOps, include Docker, CI/CD with GitHub Actions, and observability via OpenTelemetry and AWS CloudWatch (or Datadog) so it’s clear you monitor, debug and iterate in production.

Write 4–6 bullets per role using a “Problem → What you built → How you validated it → Measured outcome” pattern, and keep each bullet anchored to specific tools. Start with a strong action verb and mention concrete implementations such as implementing REST endpoints in Node.js/Express with PostgreSQL queries, or building React TypeScript components integrated with API contracts using OpenAPI. Include testing and quality gates: specify Jest and Supertest for API tests, and Playwright/Cypress for end-to-end checks, plus any coverage targets (e.g., aiming for 80%+ branch coverage). Add a clear KPI each time, such as reducing p95 API latency, lowering error rates (e.g., from 2.3% to 0.7%), improving conversion, or achieving faster deployment frequency through GitHub Actions workflows. Demonstrate stability practices with monitoring and incident response using AWS CloudWatch alarms and OpenTelemetry traces, and mention how you improved reliability through rate limiting, input validation (e.g., Zod/Joi) and safer authentication flows. Close with collaboration evidence such as Git-based pull requests, structured code reviews, and Agile delivery cadence with QA and product stakeholders so recruiters see how you operate in a real team.

Choose 2–3 projects that match how the roles are actually staffed: one should be UI-heavy, one should be API/data-heavy, and one should demonstrate deployment and operations. For each project, state the stack clearly (for example React + TypeScript, Node.js/Express, PostgreSQL, Docker, AWS) and describe the real-world use case (B2B onboarding, appointment booking, internal admin tooling, analytics dashboards or secure content management). Include at least one engineering metric per project, such as cutting p95 response times via PostgreSQL indexing, reducing N+1 query patterns, or raising test coverage with Jest and integration tests. Show operational competence by explaining your CI/CD pipeline in GitHub Actions, how the application runs in Docker containers, and what you monitored using OpenTelemetry and AWS CloudWatch dashboards/alarms. If security matters, include what you did (for example OAuth 2.0/OIDC login, JWT validation, CSRF/XSS mitigations, and RBAC enforcement) and tie it to measurable outcomes like fewer unauthorised access incidents or reduced authentication errors. The goal is to read like production delivery evidence, so recruiters can quickly infer you can ship, scale and maintain systems end-to-end.