TechnologyMid level

Full Stack Developer CV Example

End-to-end features across React and Node with the numbers that prove both halves are real.

"Full stack" is the most doubted phrase in tech CVs — screeners suspect it means one side done well and the other superficially. This example rebuts the doubt structurally: every project bullet names work on both halves, each with its own measurement.

Why this CV works

Both halves are proven separately: a frontend load-time win and a backend/API design win, not one blurred claim.
Business framing (AED 3M monthly, 800 buyers) shows the work matters, not just that it exists.
Delivery hygiene — flags, e2e tests, one-click rollback — reads like someone safe to give production access on day one.
The agency background explains breadth honestly instead of hiding it.

The professional summary

Full Stack Developer with 6 years shipping React/TypeScript frontends and Node.js/PostgreSQL backends. Built a B2B ordering portal end-to-end now processing AED 3M of monthly orders, cut its first-load time from 4.1s to 1.2s, and designed the API layer that mobile and web share. Equally at home in either half of the codebase.

Name your exact frontend and backend stacks in one sentence, then one end-to-end system you own. The phrase "full stack" convinces nobody; a system that spans the stack does.

Writing the work experience

Alternate the halves deliberately: a frontend bullet with a user-facing metric, a backend bullet with a systems metric. That rhythm is what makes "full stack" concrete.

Turning duties into achievements

Instead ofDeveloped frontend and backend features

WriteBuilt a B2B ordering portal end-to-end (Next.js + Node/Postgres) processing AED 3M of orders monthly

Instead ofImproved website performance

WriteCut first-load from 4.1s to 1.2s via code-splitting, an image CDN and server-side rendering

Skills on this CV

ReactTypeScriptNode.jsExpressPostgreSQLNext.jsREST & GraphQL APIsRedisDockerAWSJest / PlaywrightTailwind CSS

ATS tips for Full Stack Developers

Write "full stack", "front-end" and "back-end" (and the unhyphenated forms once) — ads are inconsistent and filters are literal.
List React and Node.js separately even though they pair — each is filtered on its own.
"TypeScript" is increasingly a hard filter; if you use it, it belongs in the summary, not just the list.

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

Pick one flagship system and let three bullets orbit it — scattered feature lists read shallow.
User-facing numbers (load time, orders) and engineering numbers (incidents, rollbacks) together prove range.
Agency work is a strength if framed as delivery under constraint; count the projects and keep it brief.

Frequently asked questions

Frontend-heavy or backend-heavy — should the CV say?

Yes, in the summary's stack sentence order. Leading with React signals frontend-lean; leading with Node signals the reverse. Order it to match the roles you want.

Do agency projects count as real experience?

Absolutely — frame them as shipped systems with deadlines and traffic, not as a client list.

GraphQL or REST on the CV?

Whichever you actually built, named. If both, one bullet each; do not blend them into "APIs".