Use this as a neutral starting point for a frontend developer job description — adapt every line to your own company, team and market. For the writing principles, see how to write job descriptions; for the underlying structure, the job description template.
Role overview
Frontend work spans a spectrum from markup-and-styling to complex application engineering. Stating the real stack, the type of product and the expected level prevents both over- and under-qualified applications.
What a frontend developer typically does
A frontend developer implements features, fixes bugs and improves existing interfaces, working from designs and requirements. They collaborate with designers and backend developers, write maintainable code, review others’ work, and care about accessibility, performance and how the interface behaves across devices.
Key responsibilities
- Build and maintain user interfaces from designs and requirements
- Write clean, maintainable, well-tested frontend code
- Ensure interfaces are accessible and work across devices and browsers
- Collaborate with designers and backend developers on integration
- Review code and contribute to shared standards
- Investigate and fix bugs and performance issues
- Keep up with the parts of the ecosystem relevant to your stack
Day-to-day activities
- Implementing a feature from a design and a ticket
- Pairing or syncing with designers and backend developers
- Writing and running tests, and reviewing teammates’ pull requests
- Debugging an issue reported by users or QA
- Refactoring or improving an existing component
- Discussing approach and trade-offs in technical conversations
Required and preferred skills
Required skills
- Solid HTML, CSS and JavaScript fundamentals
- Experience with the frameworks or libraries in your stack
- An understanding of accessibility and responsive design
- Good debugging and problem-solving habits
- Collaboration and clear technical communication
Preferred skills
- Experience with your specific framework, tooling or design system
- Testing experience relevant to frontend work
- Awareness of performance and web fundamentals
- Exposure to your product domain
Education and experience considerations
Frontend developers come from many paths — formal computer-science study, bootcamps and self-teaching are all common. A portfolio or real, working code usually signals more than a particular qualification.
Match requirements to the level. A junior role should focus on fundamentals and potential, while a senior role can expect depth and ownership. List specific frameworks as the stack you use, not as gatekeeping, and avoid demanding an unrealistic number of years for the tools you actually need.
Example job description template
A generic, editable structure — not tied to any company. Replace every bracketed placeholder.
Hiring a frontend developer?
Plan the role before you post it. Start from a neutral structure and a free, printable interview scorecard — no signup, no gating.
Common hiring mistakes
- Listing a huge stack of technologies as mandatory, screening out strong candidates
- Mismatching level and expectations — junior pay for senior responsibility
- Ignoring accessibility and performance, which are core to good frontend work
- Demanding an unrealistic number of years for a recent framework
- Describing the stack vaguely, so candidates cannot tell if they fit
Interview considerations
- Use a small, realistic practical exercise over a trivia quiz, and respect the candidate’s time.
- Review real code together and discuss trade-offs rather than chasing one "right" answer.
- Probe how they think about accessibility and performance, not just features.
- Rate every candidate against the same scorecard to keep technical hiring fair.
For ready-made questions and a way to compare candidates fairly, use the interview question bank and the hiring scorecard guide.