Frontend developer job description template
By Sergio Gualda · 3 min read · Updated
A clear frontend developer job description names the stack, the product and how much say the person has over what gets built. That last part is usually missing, and it decides who applies. Some developers want a well-specified ticket and others want to argue with the design, so tell them which job this is.
The template
About the role: We're hiring a frontend developer to work on [product area], using [React, TypeScript and whatever else you run]. You'll join [team] and work closely with [designers and PMs]. You'll report to [title].
- You'll build interfaces from design through to production, and own how they behave once they ship.
- You'll raise the cases a design missed, such as empty states, errors and slow connections, before they reach users.
- You'll push back when a request costs more than it's worth, and offer a cheaper way to get most of it.
- You'll keep performance and accessibility in view as part of normal work.
- You'll review code and help keep the codebase easy to change.
- You have [three or more] years building production web applications with [your framework].
- You can talk through a time you changed what was being built, as well as how.
- Nice to have: experience with [design systems, or your domain].
Being clear about product input
Add one sentence that sets the expectation. For more autonomy: “Engineers here shape what we build and often write the first version of a spec.” For less: “Design and product set the direction, and your job is to make it excellent and tell us early when it won't work.” Either is fine, and each attracts different people.
Assessing what the listing asks for
If the job asks for product judgment, a coding test won't show it. Use one for whether they can build, then something separate for how they decide. Our guide to evaluating a frontend engineer goes through the difference.
Frequently asked
- Is a frontend developer the same as a frontend engineer?
- In practice, yes. Some companies use “engineer” for more senior or systems-heavy roles, but candidates search for both, so use whichever your other engineering titles use.
- How many years of experience should I ask for?
- Ask for fewer than you think, and describe the scope instead. A hard number screens out strong people who've moved fast, and it says little about what they can own.