A customer on a mid-range Android phone taps Pay, the button does nothing for three seconds, and they tap it again. What happens next depends heavily on the frontend: a clear loading state, a disabled button and a sensible error message, or a confused customer and a support ticket. A frontend developer builds everything that runs in the browser, from screens and forms to the state behind them and the calls to backend APIs, and keeps it all quick on devices far weaker than the laptop on their own desk.
This page gives you a frontend developer job description to copy and edit. After the template you will find how the role shifts with seniority, what to test during screening, the ad mistakes that put off good applicants, and which engagement type fits which kind of frontend work.
Frontend developer job description template
Replace each bracket with your real framework and product details, and delete the frameworks you do not use. A React shop should not leave Angular in the ad out of politeness.
About the role
[Company] is hiring a Frontend Developer to build the web interface of [product]. You will turn designs from our [design team / product designers] into fast, accessible screens in [React / Angular / Vue] with TypeScript, and work with backend developers on the APIs those screens depend on. You will be based in [city / remote] and report to [engineering manager or frontend lead].
Responsibilities
- Build and maintain user interfaces in [React / Angular / Vue] and TypeScript, from Figma designs to production.
- Create reusable components and contribute to our [design system / component library].
- Manage client state and server data with [Redux Toolkit / NgRx / Pinia / TanStack Query], keeping loading, empty and error states explicit.
- Build responsive layouts with [Tailwind CSS / CSS Modules] that hold up from small phones to wide monitors.
- Monitor and improve Core Web Vitals (LCP, INP and CLS) on the pages that matter most to [users / revenue / search traffic].
- Meet accessibility standards based on WCAG, including keyboard use, focus handling and screen reader support.
- Write unit and component tests with [Jest / Vitest], and end-to-end tests with [Playwright / Cypress] for critical journeys.
- Agree API contracts with backend developers and integrate [REST / GraphQL] endpoints, including authentication and session expiry.
- Review pull requests and raise the standard of frontend code across the team.
Requirements
- [X] years of professional frontend development, with production work you can show or describe in detail.
- Strong JavaScript and TypeScript, including asynchronous code and how the browser event loop behaves.
- Deep experience in [React / Angular / Vue] and its current patterns for components and state.
- Solid semantic HTML and CSS, including flexbox, grid and responsive design without leaning on a framework for everything.
- Practical understanding of web performance: bundle size, code splitting, image handling and rendering costs.
- Working knowledge of accessibility and how to test for it.
- Comfort with Git, code review and automated tests as part of everyday work.
Nice to have
- Experience with [Next.js / Nuxt / Angular SSR], including server rendering and caching decisions.
- Experience building or maintaining a design system with Storybook.
- Exposure to product analytics, A/B testing or error monitoring in the browser.
- Experience migrating a legacy codebase, such as moving JavaScript to TypeScript.
What we offer
- [Salary range] and [benefits].
- [Work mode: on-site / hybrid / remote] and [working hours or team time zones].
- [Learning budget or conference allowance].
How the frontend developer role changes by level
Junior frontend developer
Juniors build well-defined components and fix bugs inside patterns a senior has already chosen. The ad should ask for sound HTML, CSS and JavaScript fundamentals plus one framework, and a project they can talk through. Avoid demanding production performance work at this level, since they have rarely had the chance to do it.
Mid-level frontend developer
This developer owns a feature or a product area from design review to release. They question designs that will not work on mobile, choose how state is handled, write the tests and watch the feature after launch. Requirements should mention performance fixes they have made themselves and experience working directly with backend developers and designers.
Senior frontend developer or frontend lead
A senior shapes how the whole frontend is built: rendering strategy, folder and module boundaries, the shared component library and the performance budget. They mentor others and plan upgrades such as a major framework version. If the person will also manage people or sit across several product teams, spell that out, because a frontend architect or engineering manager is a different job from a strong senior individual contributor.
Frontend developer skills that matter most, and how to check them
- JavaScript beneath the framework. Ask the candidate to explain why a search box shows stale results when responses arrive out of order, then fix it. Developers who only know framework recipes struggle here.
- State management judgement. Show a screen with filters, pagination and a detail panel, and ask what belongs in the URL, in local state and in a server cache. Good answers explain the tradeoff instead of naming a library.
- CSS and responsive work. Give them a design and ask them to build one tricky component live, including how it wraps on a narrow screen. Many CVs list CSS; far fewer people can debug a layout without guessing.
- Performance. Open a slow page in Chrome DevTools or Lighthouse together and ask what they would look at first. Listen for specifics on LCP, INP, CLS, bundle weight and render-blocking work.
- Accessibility. Ask them to use a modal or dropdown they built with only the keyboard, or describe how they would test it with a screen reader. Focus management is the quickest way to separate real experience from familiarity with the word.
- Code review. Hand over a short pull request with a race condition and a prop-drilling problem. Reading how they comment tells you what working with them would be like.
Common frontend developer job description mistakes
- Listing React, Angular and Vue as equal requirements. Few people are deep in all three, so the ad draws generalists or padded CVs. Fix: require the one you run and treat the others as a bonus.
- Using the title for a full stack job. If the person will also write Node.js services and database migrations, frontend is the wrong word. Fix: either advertise it as full stack or state exactly how much backend work is expected.
- Expecting a designer as well. Asking one hire to produce the designs in Figma and then build them usually gets you weak results on one side. Fix: say who owns design, and if the developer must fill gaps, describe that as adapting screens from existing patterns.
- Leaving out the size and age of the codebase. A new Next.js app and a large AngularJS migration attract different people. Fix: describe the current stack, its age and the next major piece of work.
- Treating accessibility and performance as buzzwords. Vague phrases like “pixel perfect” and “high performance” tell applicants nothing. Fix: name the standard you work to and the metrics the team watches.
Contract, contract-to-hire or permanent: which suits a frontend developer
Contract work fits frontend jobs with a visible end, such as a redesign, a move from JavaScript to TypeScript, an accessibility clean-up before an enterprise deal, or extra hands before a launch. It works best when your design system and review standards already exist, because a contractor can then match them rather than invent new ones.
Contract-to-hire helps when your code is the real test. A few sprints inside your repository show how someone handles your conventions and your designers, which a take-home project cannot, and you can decide on an offer with evidence in hand.
Permanent hiring suits developers who will own the frontend long term, because decisions on architecture and shared components play out over years. Zilo AI can hire frontend developers in India on contract, contract-to-hire or permanent terms, with screening on real code, testing habits and how candidates handle code review. If you need backend or QA people for the same product, our IT hiring page lists every specialisation.
Frequently asked questions
What should a frontend developer job description include?
Name the framework, the language and the styling approach, describe the product and who uses it, and state who owns design. Add the testing tools, any performance or accessibility standard you work to, the reporting line and the work mode.
What is the difference between a frontend developer and a full stack developer?
A frontend developer goes deep on what runs in the browser, including rendering, accessibility and interface state. A full stack developer also builds APIs and database work, and usually trades some of that browser depth for range.
What is the difference between a frontend developer and a UI/UX designer?
The designer decides how a product should work and look, using research, flows and Figma prototypes. The developer turns those decisions into working code. Good teams keep them in close contact, but one job title rarely covers both well.
Should frontend developers be tested with algorithm questions?
Only lightly, if at all. Building a small interface, debugging a slow page or reviewing a pull request predicts the daily work far better than a puzzle on a whiteboard.
If you would rather see frontend candidates who have already been through a code screen, Zilo AI can run that search for you. Talk to our team and tell us about your framework, your product and what the next release involves.