Last updated: June 30, 2026

Frontend Developer Job Description Template 2026

A frontend developer builds the user-facing layer of web applications with HTML, CSS, and JavaScript, usually through a framework like React, earning $75,000 to $190,000 in the U.S. depending on seniority, framework depth, and scope. The template below comes from frontend job descriptions that actually closed, not the recycled postings that pull 400 applicants and zero hires.

Open ten frontend developer postings right now and eight of them will ask for the same thing. “Proficiency in HTML, CSS, and JavaScript.” “Experience with modern frameworks.” “Strong eye for detail and pixel-perfect implementation.” Those lines describe a bootcamp grad three months out and they describe a staff engineer who owns a 200-component design system. Same words. Wildly different people. The posting does no filtering at all.

That is the core problem with frontend hiring in 2026. “Frontend developer” is not one job. It is at least three, stacked under a single title, and most hiring managers don’t notice the gap until the resumes start landing and none of them match what the team actually needs.

Mike Carter here. I run engineering and technical searches at KORE1 inside our IT staffing practice, and frontend roles are where I see the widest spread between what a JD asks for and what the work requires. We earn a placement fee when you hire through us, so factor that in. The template, the salary data, and the framework guidance below hold up whether you bring in a partner or run the search yourself.

One Title, Three Completely Different Jobs

Frontend work splits into three hiring profiles in 2026: UI developers who turn designs into responsive markup, frontend engineers who build application logic in React or Vue, and frontend platform engineers who own design systems, build tooling, and performance at scale.

This is not pedantry. It is a $90,000 salary gap. Write for the wrong profile and you will burn six weeks interviewing people who cannot do, or are wildly overqualified for, the actual job.

UI Developer / Front-End Developer

Lives in HTML, CSS, and the design handoff. Takes a Figma file and ships a responsive, cross-browser interface that matches it. Strong on layout, accessibility basics, Tailwind or vanilla CSS, maybe some jQuery in older codebases, and just enough JavaScript to wire up interactions. This person is not architecting a single-page app. They make things look right on every screen and load fast. That is the job. Entry-level UI roles run $65,000 to $85,000, and mid-level sits around $85,000 to $110,000 depending on how much JavaScript the role actually demands and whether the company treats the position as design-adjacent or engineering-adjacent. Plenty of teams need exactly this person and accidentally post a “Senior Frontend Engineer” title because it sounds heavier, then wonder why the candidates want $60K more than budgeted.

Frontend Engineer

Writes application code daily. React, Vue, or Angular. State management with Redux, Zustand, or TanStack Query. Talks to REST and GraphQL APIs, handles auth flows, writes component tests in Jest or Vitest, and debugs why a re-render is tanking the page. TypeScript is assumed at this level in most 2026 shops, not a bonus. Mid-level frontend engineers run $115,000 to $150,000, and seniors land $150,000 to $185,000 in most metros, clearing $200,000 in San Francisco, Seattle, and New York where comp and the density of product engineering orgs both push upward. The pool here looks deep on paper. The quality variance is brutal. A lot of resumes list “React” on the strength of one tutorial app and a to-do list. Tells you nothing.

Frontend Platform / Staff UI Engineer

A different scope entirely. These engineers build the systems other frontend developers use. Design systems and component libraries. Build pipelines in Vite or Webpack. Server-side rendering with Next.js, Core Web Vitals budgets, bundle-size enforcement, accessibility architecture that holds across dozens of teams. They sit closer to platform engineering than to design. Compensation tracks that. Senior and staff platform engineers command $185,000 to $230,000 and higher at well-funded companies. The premium over a senior product-frontend engineer exists because this person’s decisions ripple across every other engineer’s daily work, and a bad call on the component API costs the org months.

So before you write a line of the description, settle which of those three you actually need. If a 15-minute conversation with the hiring manager doesn’t make it obvious, the posting will attract all three and screen none of them.

Sources: ZipRecruiter (June 2026), Glassdoor (2026). Ranges blend market data with our placement experience. Coastal metros add 15-25%. Equity and bonus can move total comp well past base at senior levels. The full breakdown lives in our frontend developer salary guide.

Frontend Developer Job Description Template

Copy this. Edit the bracketed parts. Delete whatever doesn’t match your real role. The notes in parentheses explain why each block exists and what to swap.

Job Title

[Frontend Developer / Frontend Engineer / UI Engineer / Senior Frontend Engineer]

(Pick the title that matches what the person does most days. “Frontend Developer” is the broadest search term and the widest net. Use “Frontend Engineer” if they write application logic in a framework daily. Use “UI Engineer” or “UI Developer” if the work leans toward design implementation and CSS. Mixing the signal here is where most postings lose the right people.)

About the Role

(Two or three sentences. What does this person own? What product do they build? Who do they report to? Skip the company mission paragraph. Candidates scroll past it.)

[Company Name] is hiring a [title] to build and own the user-facing experience of [product/platform]. You will [primary responsibility: build new features in React / maintain and improve our component library / turn Figma designs into production UI] for [what the product does in one phrase], working closely with [design, backend, product] and reporting to [Engineering Manager / Frontend Lead]. This role is [remote / hybrid in {city} / onsite in {city}].

What You Will Do

(Six to eight specific responsibilities. Skip the empty ones like “ensure high-quality user experiences.” Every line should name something the person could start on day one, including the tools and systems they will actually touch.)

• Build and ship features in [React / Vue / Angular] with [TypeScript / JavaScript], from design handoff to production deploy
• Translate [Figma / Sketch] designs into responsive, accessible interfaces that hold up across browsers and screen sizes
• Integrate with [REST / GraphQL] APIs, manage client state with [Redux / Zustand / TanStack Query], and handle loading, error, and empty states properly
• Write and maintain component and integration tests in [Jest / Vitest / Playwright / Testing Library], and keep the suite green in CI
• Own [Core Web Vitals / bundle size / accessibility] for your surface area, including [WCAG 2.2 AA conformance / keyboard navigation / screen reader support]
• Contribute to our [design system / component library] in [Storybook], proposing new patterns instead of one-off styling
• Review pull requests for accessibility, performance, and component reuse, not just whether the feature works
• Partner with backend and product during planning to flag frontend complexity before the ticket is committed

What You Bring

(Split required from preferred, and be honest about the line. Every “required” item you inflate shrinks your pool for no reason. The CS-degree line below is the one that quietly costs you the most candidates.)

Required:

• [2-4 / 4-7 / 7+] years building production frontends, with real depth in [React / Vue / Angular]
• Strong [JavaScript / TypeScript] fundamentals, not just framework familiarity
• Fluency with modern CSS: [Flexbox, Grid, responsive design, Tailwind / CSS Modules / styled-components]
• Experience consuming [REST / GraphQL] APIs and managing asynchronous data and state
• A working understanding of web performance and accessibility, and the ability to explain why a page is slow or unusable
• Comfort with [Git, code review, CI/CD] and shipping in a collaborative codebase

Preferred:

• Experience with [Next.js / Remix / Nuxt] and server-side or static rendering
• Familiarity with [a design system, component-driven development, Storybook]
• Testing depth beyond unit tests: [Playwright / Cypress] for end-to-end coverage
• Exposure to [build tooling: Vite / Webpack / Turbopack] and bundle optimization
• Background in [your domain: fintech / healthcare / e-commerce / SaaS]

Compensation and Benefits

(Put a range in. Candidates skip postings without one, and twelve states now require it anyway. A $30K band is fine. It signals the seniority tier and kills mismatches before anyone wastes an interview.)

• Base salary: $[X] – $[Y] depending on experience and location
• [Three or four benefits that actually matter: equity, healthcare, 401k match, remote flexibility, learning budget]

About [Company Name]

(Two or three sentences. Product, stage, team size, the stack. Frontend candidates want to know what they will build and who they will build it with.)

What Most Frontend Job Descriptions Get Wrong

I pulled about 50 frontend postings off LinkedIn and a few job boards last month, mixed across startups and enterprise. Five mistakes showed up in well over half of them.

The framework alphabet soup. “Experience with React, Angular, Vue, Svelte, Ember, Backbone, jQuery, and a strong willingness to learn new frameworks.” Nobody is deep in all of those, and the people who are genuinely strong in one will read that list as a team that doesn’t know what it runs. Name the framework your codebase actually uses. Add one acceptable alternative if cross-training is realistic. That is the whole tools section.

The second one does real damage. Requiring a computer science degree. Frontend is the single most bootcamp-and-self-taught-heavy corner of engineering, and some of the strongest people I have placed never sat in a CS lecture. One of my best placements last year came out of a graphic design background, taught herself React and TypeScript across about two years, and had a feel for layout, motion, and accessibility that most CS grads pick up years later, if ever. The degree filter cut people like her before a human ever opened the resume. CS programs barely teach the browser anyway.

Three: conflating design and engineering. “Must have a strong design sense and create pixel-perfect, beautiful interfaces” sitting in the same posting as “architect scalable state management for a complex SPA.” Those are two different hires most of the time. Some unicorns do both. They are rare. They cost accordingly. If you genuinely need a design-engineer hybrid, say so plainly and pay for it. If you need an engineer who can implement a designer’s work faithfully, say that instead. Asking for a world-class designer and a senior architect in one body, at one salary, is how the search stalls for three months.

Four, no mention of the product or the stack. Frontend candidates want to know what they are building and what they are building it with. “Our web platform” tells them nothing. Is it a data-heavy B2B dashboard with thousands of rows and real-time updates? A consumer app obsessed with animation and load time? A sprawling marketing site? Each one rewards a different kind of engineer, and the strong candidates self-select based on that detail. Leave it out and you get a flood of mismatches.

Five: ignoring accessibility and performance entirely, then acting shocked when neither gets done. If WCAG conformance matters to you, and in 2026 it increasingly carries legal weight, it belongs in the JD as an expectation, not a surprise discovered in month two. Same with Core Web Vitals. A frontend engineer who has never owned a performance budget will not magically start caring about Largest Contentful Paint because you mentioned it once in the interview. Put it in the description and you screen for people who already think that way.

The Framework Question: Does Requiring React Help or Hurt?

React runs the market. 44.7% of developers reported using it in the 2025 Stack Overflow Developer Survey of just over 49,000 respondents, with Next.js close behind at 20.8%. Angular sat at 18.2%, Vue.js at 17.6%, and Svelte at 7.2%. jQuery, the framework everyone keeps declaring dead, still showed up at 23.4%. Not dead. That number is the weight of legacy code still in production and still needing someone to maintain it.

Here is where that data should change your JD. If your stack is React, requiring React is fine. If your stack is Vue or Angular, requiring React experience screens out the exact people who can do your job and lets in people who will need a month to ramp on a framework you didn’t hire them for. Frameworks share concepts. Component models, state, lifecycle, reactivity. A strong Vue engineer becomes productive in React faster than a mediocre React engineer becomes good at anything. Hire for the fundamentals and name your framework as the context, not the gate.

TypeScript is the real 2026 baseline. It hit 43.6% usage in the same survey and at most product companies it is now the default, not a preferred bonus. If your codebase is TypeScript, say it plainly under required. If it isn’t yet, and you want it to be, say that too, because strong frontend engineers increasingly treat a JavaScript-only shop as a yellow flag.

One more thing on frameworks. Do not require a specific version or a hyper-narrow combination unless you truly need it. “5+ years of React 19 with the App Router in a Next.js monorepo using Server Components” describes maybe a few hundred people on earth, given React 19 and the App Router are recent. You will wait forever. Truly forever. Describe the shape of the work and let the candidates who can clearly do it show you they can.

Frontend Developer Salary Benchmarks 2026

Three sources. They disagree, and the disagreement is useful. It tells you where the aggregators are anchored versus where real offers land.

The BLS number lumps web developers in with digital designers and skews toward generalist web roles, which is why its median lands below what a React engineer at a funded startup actually gets. ZipRecruiter sits higher because it leans on posted ranges. Glassdoor’s wide band reflects how much the title stretches, from a $77K UI developer to a $136K senior engineer carrying the same words on their LinkedIn. If you are budgeting a frontend engineer hire for 2026, plan on $115,000 to $150,000 for a solid mid-level with real React or Vue depth, and $150,000 to $185,000 for a senior who can own a feature area end to end. Design-system and platform work adds $25,000 to $45,000 on top.

The Bureau of Labor Statistics projects 7% growth for web developers and digital designers through 2034, faster than the average for all occupations, with about 14,500 openings a year. Steady demand, not a gold rush. The advantage in this market goes to whoever writes the clearest posting, not whoever pays the most.

KORE1’s placement data across 30+ U.S. metros shows the sharpest comp jumps happen at two transitions: jQuery-and-templates to modern framework work, and senior product engineer to platform or design-system ownership. Candidates who can prove the second jump are scarce and priced like it. Our salary benchmark tool helps you calibrate a range for your market and seniority before you post. We hold a 92% twelve-month retention rate on the people we place, which is the number that actually matters once the offer is signed.

Customizing the Template by Company Stage

The template is a skeleton. What makes it work is the detail you add, and that detail changes a lot depending on where your company sits.

Early-stage startup. Your frontend hire will wear several hats and probably touch backend. Say that. Be honest that the design system is “a Figma file and some opinions” rather than a mature component library, because the engineer who thrives in that ambiguity is a different person from the one who wants a polished platform to build on. Emphasize ownership, range, and comfort with shipping fast and refactoring later. Equity matters more here than an extra $10K of base, so lead with it.

Growth-stage and enterprise. The work narrows and deepens. You probably have an established React or Angular codebase, a real design system, accessibility and performance standards, and review processes. Your JD should signal maturity: name the design system, the testing bar, the CI setup, the WCAG target. Senior candidates read those details as evidence the org takes frontend seriously, which is exactly the signal that pulls in the people who have options. Vague enterprise postings read as bureaucratic, and the strongest engineers assume the worst.

Agencies and product companies reward different instincts too. Agency frontend work prizes speed, breadth, and the ability to context-switch across client codebases. Product work rewards depth in one surface over time. The “About the Role” and “What You Will Do” sections have to reflect which one you are, or you will keep hiring people who leave in eight months because the job wasn’t the one they read.

Things People Ask About Frontend Developer Job Descriptions

Frontend developer versus frontend engineer, does the title difference actually matter?

It matters more than most teams think, mainly because candidates read it as a seniority and scope signal. “Developer” tends to attract people who implement designs and build features within an existing structure. “Engineer” pulls people who expect to make architecture decisions, own state management, and weigh in on tooling. Neither is better. They are different jobs at different price points. The trouble starts when the title and the bullets disagree. You post “Frontend Developer” at a developer salary but describe engineer-level work in the bullets, or the reverse, post “Senior Frontend Engineer” and then hand the person a queue of CSS tickets. The mismatch surfaces in week three, the new hire feels misled, and you are back to sourcing. Match the title to the actual scope and the salary to the title, and the whole pipeline gets cleaner.

Should I require a specific framework like React?

Require it only if your stack runs on it. If you are a React shop, asking for React is reasonable and saves ramp time. If you run Vue or Angular, requiring React experience screens out the people who can actually do your job. Frameworks share more than they differ, and a strong engineer in one becomes productive in another in weeks. We saw this play out. We ran a search last quarter where the client required “React, 5+ years” and got a thin pipeline of 14 in three weeks. We broadened it to “strong in any modern component framework, React preferred,” and the next two weeks brought 51 applicants, including the Vue engineer they ended up hiring, who was shipping production React inside her first sprint. Name your framework as context. Gate on fundamentals.

Is a CS degree necessary for frontend roles?

No, and frontend is the area where the degree requirement costs you the most. This corner of engineering is overwhelmingly bootcamp, self-taught, and career-switcher territory, and many of the best practitioners came in through design, marketing, or unrelated fields. The skills that matter, framework depth, CSS mastery, accessibility, performance instinct, are learned by building, not in a lecture hall, and most CS programs barely cover the browser at all. Require the skills. Make the degree “preferred” or drop it. You will widen your pool by a meaningful margin without lowering the bar one inch, and in a market the BLS expects to keep growing through 2034, a wider pool is the whole game.

Does this person also do design and Figma work, or just implement it?

Decide before you post, because it changes who applies. A pure implementation role wants an engineer who can take a finished Figma file and build it faithfully, no design judgment required. A design-engineer hybrid expects the person to make visual and interaction decisions themselves, which is a rarer and pricier skill set. Many JDs blur the two by asking for “a strong design sense” on what is really an engineering role, and that one phrase quietly changes who self-selects in. If design ownership is real, say it and budget for it. If the designers own the design and you just need it built well, say that, and you will stop scaring off excellent engineers who don’t consider themselves designers.

Should I post a salary range?

Always. Twelve states and a growing list of cities now legally require it, and even where it is optional, postings with a range pull far more qualified applicants. Use a band. $120K to $150K is fine. It tells candidates where the role sits and prevents a senior engineer who needs $180K from burning four interview rounds before the number comes up. The worry that a posted range invites lowballing is backwards. The range filters out the mismatches up front, which is exactly what you want, because the alternative is discovering the gap at the offer stage and losing your backup candidate while you scramble.

Contract or direct hire for frontend roles?

Depends on the work and the certainty. For a defined build, a redesign, a migration off jQuery, a launch with a real end date, contract staffing gets you a productive engineer without a permanent commitment. For ongoing ownership of a product’s frontend, direct hire at the ranges above. Contract-to-hire splits the difference when you are not sure how the role will evolve: start with a few months, see how they work, convert if it fits. KORE1 fills frontend roles across all three models, and the right structure depends on your roadmap, not on which option looks cheapest this quarter.

Next Steps

Copy the template. Fill the brackets with your real product, stack, and team. Delete the notes in parentheses. Post it with a salary range.

If you want help shaping a frontend JD for your team, calibrating a range for your market, or sourcing engineers directly, talk to a recruiter on our team. We fill IT roles in 17 days on average across 30+ U.S. metros, through contract, contract-to-hire, and direct hire, and we back it with a 92% retention rate. When you are ready to evaluate applicants, our frontend developer interview questions give you a screening loop that actually separates the tutorial resumes from the real ones. Hiring across the broader team too? The front-end developer staffing page covers how we approach these searches end to end.