Full Stack Developer CV Example & Template
A complete two-page CV for a full stack developer with four years of experience building web products with React, Next.js, Node.js and PostgreSQL, followed by what engineering leads and recruiters look at first. Copy the layout, then replace the products, stack and numbers with your own, and show which side of the stack is your stronger one.
Last reviewed October 2026
Example Full Stack Developer CV
Tom Hargreaves
Full Stack Developer, React, Next.js, Node.js and PostgreSQL
Manchester, UK
Profile
Full stack developer with four years of experience building customer-facing web apps and the APIs behind them for UK SaaS companies. I am strongest on the frontend with React and Next.js, and I design and ship backend services in Node.js with PostgreSQL. I take features from database schema to production, including payments, tests and monitoring. Looking for a mid-level full stack role on a product team.
Experience
Full Stack Developer
Feb 2023 – Present
Tallyhub (subscription billing SaaS, 45 staff) · Manchester
- Build and maintain a Next.js and TypeScript customer portal on top of a Node.js and PostgreSQL API, used by around 6,500 active accounts.
- Integrated Stripe Billing and webhooks for plan changes and failed payment recovery, which recovered about 11% of failed renewals and removed manual invoicing for 300 accounts.
- Reduced portal load time from 3.8s to 1.6s on mid-range mobiles by moving data fetching to the server, splitting bundles and adding indexes on the three slowest queries.
- Designed the database schema and migrations for a team permissions feature, shipped in six weeks with no downtime using Prisma migrations.
- Added Playwright end-to-end tests for checkout and sign-up, raising release confidence enough to move from fortnightly to twice-weekly deploys.
Junior then Mid-level Web Developer
Jul 2021 – Jan 2023
Northlight Digital (product studio) · Manchester
- Delivered six client web apps in React and Node.js, from sprint planning to deployment on AWS, working in teams of three to five.
- Built a booking platform with a REST API and PostgreSQL that handled 2,400 bookings a month for a leisure client.
- Introduced GitHub Actions for tests and preview deployments, cutting the time to review a pull request from a day to a few hours.
- Improved accessibility on a client site to WCAG 2.1 AA after an audit, fixing 47 issues in keyboard navigation and colour contrast.
Web Developer (placement year)
Jul 2019 – Jun 2020
Kestrel Logistics · Salford
- Built internal dashboards in React and Express for the operations team, replacing three spreadsheets used by 25 people.
- Wrote SQL queries and a small reporting API against a PostgreSQL database holding two million shipment records.
- Paired with senior developers on code reviews and learned to write unit tests with Jest.
Education
BSc (Hons) Computer Science with Industrial Placement, 2:1
2016 – 2021
University of Salford
Skills
React and Next.js · TypeScript · Node.js and Express · PostgreSQL and Prisma · REST API design · Stripe integration · AWS: S3, Lambda, ECS · Docker · GitHub Actions · Playwright and Jest · Tailwind CSS · Web accessibility
Side project
- Built and run a small invoicing tool for freelancers in Next.js and PostgreSQL, with 140 active users and Stripe subscriptions
Why this Full Stack Developer CV works: what shortlisters check first
A clear strong side
Almost every full stack developer is stronger on one end. Say which one in the headline or profile, then show real work on the other. Hiring managers distrust a CV that claims equal depth everywhere. A line such as 'strongest on the frontend, comfortable owning APIs and schemas' sets honest expectations and gets you matched to the right team.
Features shipped from schema to screen
The value of a full stack developer is end-to-end delivery. Pick two or three bullets where you took a feature from database design through API to interface, and name each layer. Billing, permissions, bookings and dashboards are good examples because they touch data, logic and user experience, and they have visible results.
Numbers from both ends
Show a frontend result, such as load time, Core Web Vitals, conversion or accessibility fixes, and a backend result, such as query time, throughput, error rate or cost. Include the number of users or accounts. Without numbers a reader cannot tell whether you worked on a toy or a real product.
A stack that matches the advert
Most UK adverts name a stack, such as React with Node.js and PostgreSQL, or Next.js with a cloud provider. Mirror the exact names you really know, in the order the advert uses. Note the version or flavour where it matters, for example Next.js App Router. Mention working knowledge honestly, so interview questions stay fair.
Testing, deployment and ownership
Employers hiring one developer to cover several layers want proof you can ship safely. Mention automated tests, CI/CD, preview environments, monitoring and who was on call. A short line about how you reduced release risk, for instance by adding end-to-end tests on checkout, often matters more than another framework on the list.
Key skills recruiters look for
How to write each section of a Full Stack Developer CV
Profile
State years of experience, the type of product, your main stack and which side you lead on. Add one outcome with a number. Close with the kind of team you want to join. Skip phrases like 'passionate coder'.
Experience
Start each role with the product, company size and team. Use three to five bullets, each with a technology and a result. Spread them across frontend, backend and delivery, so a reader sees the full range without a separate list.
Skills
Group into frontend, backend, data and delivery tools if you have many. Put the strongest first. Use official names, such as Next.js and PostgreSQL, because applicant tracking systems search for exact terms.
Projects
A real side project with users counts as experience, particularly if you handled payments, auth or deployment. Say what it does, the stack, the number of users and a link on the page only if it works and the code is tidy.
Education
Graduates keep education near the top; after two or three years move it beneath experience. A placement year is worth its own entry. Bootcamp graduates should name the programme, the year and the final project.
More example bullet points
Strong Full Stack Developer CVs lead with measurable impact. Here are examples of the kind of bullets that make recruiters stop scrolling:
Built end-to-end SaaS dashboard from schema design to deployment, onboarding 500+ paying customers in first quarter
Owned full feature lifecycle for billing system integration: Stripe API, webhook handling, and customer-facing portal
Reduced page load time by 60% through SSR implementation, image optimization, and CDN configuration
Common Full Stack Developer CV mistakes
- Claiming equal expertise in every framework, which makes interviewers test the weakest one.
- Listing duties such as 'built features using React' with no users, scale or measured result.
- Showing only frontend or only backend bullets under a full stack title.
- Linking a portfolio with broken demos or tutorial clones, which hurts more than having none.
- Leaving out testing and deployment, so a reader assumes you hand work over to someone else to release.
Full guide
Full Stack Developer CV guide: what recruiters actually look for →
Free, no signup
Check your Full Stack Developer CV for ATS problems →
How to tailor your Full Stack Developer CV for each application
Every Full Stack Developer job posting is different. The skills they prioritize, the seniority they expect, the setting — all of it shapes what your CV should emphasize. A CV that gets an interview at one employer can miss at another, even for the same job title.
The fastest way to tailor your CV is to paste the job description into NextCV. The AI reads the posting, maps it to your experience, and rewrites your bullets to match what the employer is scanning for. 1 free preview, no signup required — you only pay when you want a clean PDF download. Sign up free for 3 more.
Full Stack Developer CV FAQ
What should a full stack developer CV include?
A profile stating your stack and stronger side, experience bullets that show frontend, backend and delivery work with numbers, a skills section matching the advert, and education. Add a project link if the code is tidy. Two pages is plenty.
Should I say I am frontend-leaning or backend-leaning?
Yes, if it is true. Most full stack developers have a stronger side, and hiring managers prefer honesty to a claim of equal depth. Say which side you lead on and show real work on the other, so you are placed on the right team.
How many technologies should I list?
Around 10 to 14, in groups, and only ones you could discuss in an interview. A shorter list that mirrors the advert is more convincing than a long one. Put the stack you used most in the last two years first.
Is a portfolio or GitHub link necessary?
Not necessary, but helpful for developers with fewer than three years of experience or a non-traditional route. Link two or three projects with readable code and a short README. If your best work is private, describe it with numbers instead.
How do I show full stack experience as a junior?
Use projects, placements and internships to show work across layers: a database schema, an API and a user interface in the same product. Mention deployment and tests. Keep claims modest, and say what you built yourself and what you pair-programmed.