Job description template
React Developer Job Description Template (2026)
A free, copy-ready React Developer job description covering responsibilities, must-have skills, tools, seniority variants, and KPIs. Written for hiring managers, not for SEO filler.
Key facts
- Role
- React Developer
- Reports to
- Reports to the Engineering Manager or Frontend Lead
- Must-have skills
- 7 items
- Seniority tiers
- Junior / Mid / Senior
- KPIs defined
- 6 metrics
- Starting price (offshore)
- $2800/month
Role summary
A React Developer owns the frontend user interface for our product: building and maintaining the React and Next.js application, shipping accessible and performant components, wiring up server and client state, and collaborating with designers and backend engineers to turn Figma and API contracts into production UI that meets Core Web Vitals budgets and WCAG 2.1 AA.
Responsibilities
- • Build new React components and full page flows in TypeScript against Figma specs, with Storybook stories and visual regression coverage for every component.
- • Own the Next.js App Router migration and server component boundaries, deciding which components render on the server and which hydrate on the client.
- • Wire up server state with TanStack Query or RTK Query, and client state with Redux Toolkit, Zustand, or Jotai as appropriate for the feature.
- • Hit Core Web Vitals targets on every release — LCP under 2.5s, INP under 200ms, CLS under 0.1 — tracked in Lighthouse CI and Vercel Speed Insights.
- • Write Jest and React Testing Library tests for components and hooks, plus Playwright end-to-end tests for auth, checkout, and other critical flows.
- • Meet WCAG 2.1 AA on every shipped component, verified with axe DevTools, keyboard-only walkthroughs, and screen reader passes on complex widgets.
- • Review pull requests from peers with specific feedback on component API design, accessibility, performance, and test coverage.
- • Tune bundle size via dynamic imports, route-level code splitting, and tree shaking, and monitor bundle budgets per route.
- • Partner with backend engineers to shape REST or GraphQL contracts before implementation so the frontend is never blocked on API shape changes.
- • Maintain the design token pipeline, dark mode theming, and responsive breakpoint strategy across the component library.
Must-have skills
- • 3+ years shipping production React in TypeScript, including hooks, context, and Suspense.
- • Hands-on Next.js experience on App Router, including server components, server actions, and streaming.
- • Fluency in at least one server-state library (TanStack Query, SWR, or RTK Query) and one client-state library (Redux Toolkit, Zustand, or Jotai).
- • Comfortable writing tests with Jest and React Testing Library and reading Playwright or Cypress output.
- • Working knowledge of WCAG 2.1 AA, ARIA patterns, and keyboard interaction models for complex components.
- • Performance profiling with React DevTools, Chrome DevTools, and Lighthouse — able to diagnose slow renders and wasted re-renders without hand-holding.
- • Strong written English for async code review, Slack threads, and spec docs.
Nice-to-have skills
- • Experience migrating a production Pages Router app to App Router.
- • React Native or Expo experience for cross-platform work.
- • Contributions to a published component library, design system, or open-source React project.
- • Familiarity with Chromatic, Percy, or another visual regression tool.
- • Backend competence in Node.js or tRPC for full-stack ownership of a feature.
Tools and technology
- React 18/19
- Next.js (App Router)
- TypeScript
- TanStack Query
- Redux Toolkit / Zustand
- Storybook
- Jest & React Testing Library
- Playwright
- Tailwind CSS
- Vercel / Lighthouse CI
Reporting structure
Reports to the Engineering Manager or Frontend Lead. Collaborates daily with product designers (Figma handoff), backend engineers (API contracts), QA, and the product manager for the feature area.
Seniority variants
How responsibilities shift across junior, mid, and senior levels.
junior
1-2 years
- • Implement scoped components against Figma specs under review from a senior.
- • Write Storybook stories and unit tests for every component merged.
- • Fix accessibility and responsive bugs surfaced by QA and automated checks.
- • Learn the codebase conventions: state patterns, folder structure, and PR etiquette.
mid
3-5 years
- • Own end-to-end delivery of a feature area from Figma to production.
- • Make state management and data fetching decisions for new features.
- • Review pull requests from junior engineers and enforce the component API bar.
- • Co-design API contracts with backend engineers before any UI is written.
senior
6+ years
- • Set frontend architecture: App Router boundaries, state patterns, bundling strategy, and performance budgets.
- • Drive the migration roadmap (React 19, App Router, or framework upgrades) and delegate the work.
- • Mentor mid-level engineers and run the frontend hiring loop.
- • Own the design system and component library governance across multiple product teams.
Success metrics (KPIs)
- • Weekly PR throughput and review turnaround on own and peer PRs.
- • Core Web Vitals (LCP, INP, CLS) tracked per route with a hard budget that blocks releases if breached.
- • Accessibility: zero WCAG 2.1 AA critical issues reported by axe or users in shipped flows.
- • Test coverage on behavioral paths — not line count — maintained or improved each sprint.
- • Storybook coverage: every new component has a story plus controls and docs.
- • Production error rate on frontend (Sentry) trending flat or down quarter-over-quarter.
Full JD (copy-ready)
Paste this into your ATS or careers page. Edit the company name and any bracketed placeholders.
# React Developer — Job Description ## Role summary A React Developer owns the frontend user interface for our product: building and maintaining the React and Next.js application, shipping accessible and performant components, wiring up server and client state, and collaborating with designers and backend engineers to turn Figma and API contracts into production UI that meets Core Web Vitals budgets and WCAG 2.1 AA. ## Responsibilities - Build new React components and full page flows in TypeScript against Figma specs, with Storybook stories and visual regression coverage for every component. - Own the Next.js App Router migration and server component boundaries, deciding which components render on the server and which hydrate on the client. - Wire up server state with TanStack Query or RTK Query, and client state with Redux Toolkit, Zustand, or Jotai as appropriate for the feature. - Hit Core Web Vitals targets on every release — LCP under 2.5s, INP under 200ms, CLS under 0.1 — tracked in Lighthouse CI and Vercel Speed Insights. - Write Jest and React Testing Library tests for components and hooks, plus Playwright end-to-end tests for auth, checkout, and other critical flows. - Meet WCAG 2.1 AA on every shipped component, verified with axe DevTools, keyboard-only walkthroughs, and screen reader passes on complex widgets. - Review pull requests from peers with specific feedback on component API design, accessibility, performance, and test coverage. - Tune bundle size via dynamic imports, route-level code splitting, and tree shaking, and monitor bundle budgets per route. - Partner with backend engineers to shape REST or GraphQL contracts before implementation so the frontend is never blocked on API shape changes. - Maintain the design token pipeline, dark mode theming, and responsive breakpoint strategy across the component library. ## Must-have skills - 3+ years shipping production React in TypeScript, including hooks, context, and Suspense. - Hands-on Next.js experience on App Router, including server components, server actions, and streaming. - Fluency in at least one server-state library (TanStack Query, SWR, or RTK Query) and one client-state library (Redux Toolkit, Zustand, or Jotai). - Comfortable writing tests with Jest and React Testing Library and reading Playwright or Cypress output. - Working knowledge of WCAG 2.1 AA, ARIA patterns, and keyboard interaction models for complex components. - Performance profiling with React DevTools, Chrome DevTools, and Lighthouse — able to diagnose slow renders and wasted re-renders without hand-holding. - Strong written English for async code review, Slack threads, and spec docs. ## Nice-to-have skills - Experience migrating a production Pages Router app to App Router. - React Native or Expo experience for cross-platform work. - Contributions to a published component library, design system, or open-source React project. - Familiarity with Chromatic, Percy, or another visual regression tool. - Backend competence in Node.js or tRPC for full-stack ownership of a feature. ## Tools and technology - React 18/19 - Next.js (App Router) - TypeScript - TanStack Query - Redux Toolkit / Zustand - Storybook - Jest & React Testing Library - Playwright - Tailwind CSS - Vercel / Lighthouse CI ## Reporting structure Reports to the Engineering Manager or Frontend Lead. Collaborates daily with product designers (Figma handoff), backend engineers (API contracts), QA, and the product manager for the feature area. ## Success metrics (KPIs) - Weekly PR throughput and review turnaround on own and peer PRs. - Core Web Vitals (LCP, INP, CLS) tracked per route with a hard budget that blocks releases if breached. - Accessibility: zero WCAG 2.1 AA critical issues reported by axe or users in shipped flows. - Test coverage on behavioral paths — not line count — maintained or improved each sprint. - Storybook coverage: every new component has a story plus controls and docs. - Production error rate on frontend (Sentry) trending flat or down quarter-over-quarter.
Frequently asked questions
What does a React Developer do day-to-day?
A React Developer owns the frontend user interface for our product: building and maintaining the React and Next.js application, shipping accessible and performant components, wiring up server and client state, and collaborating with designers and backend engineers to turn Figma and API contracts into production UI that meets Core Web Vitals budgets and WCAG 2.1 AA.
How many years of experience should a mid-level React Developer have?
A mid-level React Developer typically has 3-5 years of experience. At that level they should own end-to-end delivery of a feature area from figma to production.
Which KPIs should I hold a React Developer accountable to?
The most important KPIs for a React Developer are: Weekly PR throughput and review turnaround on own and peer PRs.; Core Web Vitals (LCP, INP, CLS) tracked per route with a hard budget that blocks releases if breached.; Accessibility: zero WCAG 2.1 AA critical issues reported by axe or users in shipped flows.; Test coverage on behavioral paths — not line count — maintained or improved each sprint..
Which React versions do your developers work with?
Every developer in our network is current on React 18 and has shipped hooks-based code in production. Most have already migrated a legacy class-component codebase to functional components and hooks, so if you are sitting on a React 16 or 17 app that needs upgrading we can match a developer who has done that migration before. We also have developers who have worked through React 19 release candidates and the server components model for clients running bleeding-edge Next.js.
Do your developers know Next.js App Router or only Pages Router?
Both. When you kick off we ask which router your project is on and only shortlist developers whose recent production work matches. For clients mid-migration from Pages to App Router we match developers who have completed that specific migration before, because the learning curve on server components, streaming, and nested layouts is not something you want to pay for while they read the docs. Tell us in the kickoff call which side of the migration you are on.
Related
Written by Syed Ali
Founder, Remoteria
Syed Ali founded Remoteria after a decade building distributed teams across 4 continents. He has helped 500+ companies source, vet, onboard, and scale pre-vetted offshore talent in engineering, design, marketing, and operations.
- • 10+ years building distributed remote teams
- • 500+ successful offshore placements across US, UK, EU, and APAC
- • Specialist in offshore vetting and cross-timezone team integration
Last updated: April 12, 2026