Full Stack Developer Job Description Template (2026)

Full JD (copy-ready)

Paste this into your ATS or careers page. Edit the company name and any bracketed placeholders.

# Full Stack Developer — Job Description

## Role summary
A Full Stack Developer takes a feature from Figma to production across every layer: React or Next.js on the frontend, Node.js or Python APIs on the backend, PostgreSQL or MongoDB schema changes, CI/CD, and production debugging. They own the contract between frontend and backend, write end-to-end tests that actually reproduce real failures, and move tickets to "done" without bouncing work to other engineers. They trade depth in one layer for end-to-end shipping speed.

## Responsibilities
- Take a ticket from design spec to production across frontend, backend, database, migrations, and deploy — without handing off to other engineers.
- Design the API contract between frontend and backend before writing either side; document in OpenAPI, tRPC, or GraphQL SDL so the two sides never drift.
- Build React or Next.js components in TypeScript against Figma specs; wire them to REST/GraphQL endpoints built in the same PR when possible.
- Ship PostgreSQL or MongoDB schema changes including reversible migrations, backfills, and data integrity checks.
- Wire up authentication end-to-end: session or JWT flow, middleware on the backend, protected routes on the frontend, and the CSRF story between them.
- Configure GitHub Actions pipelines covering lint, typecheck, unit tests, E2E tests, build, and preview deploys on Vercel, Fly.io, or AWS.
- Triage production incidents end-to-end: frontend Sentry + backend Sentry + CloudWatch/Datadog logs + DB slow query log, not just the layer you are comfortable in.
- Wire up background jobs in BullMQ, Sidekiq, or Celery with retry policies and idempotent handlers when the frontend flow crosses into async work.
- Handle file uploads, webhooks, real-time updates, and third-party integrations (Stripe, Twilio, Auth0, SendGrid) end-to-end.
- Enforce type safety across the stack with shared TypeScript packages, tRPC, or generated GraphQL types so the frontend cannot call a backend that does not exist.
- Review PRs that touch both sides with a holistic eye: an API change should land with its matching client change in the same release.

## Must-have skills
- 4+ years shipping production full-stack features, with real depth on both a frontend framework (React 18+, Next.js, or Vue 3) and a backend framework (Node.js/NestJS/Express, Django, or Rails).
- TypeScript end-to-end, including patterns for sharing types between client and server.
- PostgreSQL or MongoDB at the level of writing reversible migrations and reading query plans, not just ORM calls.
- REST API design with correct status codes, idempotency, pagination, and versioning; exposure to GraphQL or tRPC.
- Docker and CI/CD in GitHub Actions, CircleCI, or GitLab CI including preview deployments.
- Practical auth implementation: session + cookies or JWT with refresh rotation, including the CSRF story on the frontend.
- Debugging across the stack: Sentry on both sides, browser DevTools, DB slow query logs, and APM traces.

## Nice-to-have skills
- Infrastructure-as-code (Terraform, Pulumi) for the databases and services their features depend on.
- Experience with a typed RPC layer (tRPC, GraphQL codegen) across frontend and backend.
- Real-time features with WebSockets, SSE, or Liveview-style patterns.
- Mobile or React Native exposure for end-to-end ownership across web and native.
- Stripe or similar payment integration including webhook security and idempotency.
- DevOps ownership in Kubernetes or a serverless platform at a production scale.

## Tools and technology
- React / Next.js
- Node.js (NestJS/Express) or Django
- TypeScript
- PostgreSQL / MongoDB
- Prisma or Drizzle
- Docker
- GitHub Actions
- Vercel / AWS / Fly.io
- Sentry + Datadog
- Playwright

## Reporting structure
Reports to the Engineering Manager or Tech Lead. Collaborates daily with designers on spec clarification, product on acceptance criteria, and other engineers when a feature crosses service boundaries. Operates as the directly responsible individual for features end-to-end.

## Success metrics (KPIs)
- Lead time from ticket accepted to production under 5 business days on median features.
- Sentry error rate on owned features trending flat or down quarter-over-quarter.
- Zero production incidents caused by frontend/backend contract drift on shipped features.
- Test coverage (behavioral) on owned features maintained or improved each sprint, both sides of the stack.
- CI pipeline green rate above 90% on owned PRs; no "retry until green" habit.
- PR review turnaround under 1 business day on peer PRs.