Front page / By role / Engineering / Software engineer / Frontend engineer
Engineering
Frontend engineer
Builds the part of an app people use directly: web pages, interfaces and how fast they feel.
Under Software engineer. Also under it: Backend engineer, Full stack engineer, Mobile engineer, Machine learning engineer, Data engineer, Solutions architect, Game developer
Workflows for this work
The job in 4 areas. Each part is a workflow: open it for its steps and the tools that do each one. Built from occupational data and the field's own body of knowledge; sources at the end.
Frontend engineer459 skill packs · 75 MCP servers · 23 pluginsEach part is a workflow. The number beside it is how many tools help with it
1Plan the interface
Turn designs and user needs into a plan for screens and components.
2Build the interface
Write the components, pages and data handling users see.
3Make it work for everyone
Check accessibility, speed and support across browsers and devices.
4Test and ship
Test the interface, release it and watch for errors.
Sources for this tree, 6
- PractitionerThe Practical Test PyramidHam Vocke, martinfowler.com
- PractitionerWhat to look for in a code review (Google Engineering Practices)Google
- Occupational dataWeb Developers (15-1254.00)O*NET OnLine, U.S. Department of Labor
- Body of knowledgeSoftware Engineering Body of Knowledge (SWEBOK), Guide V4.0IEEE Computer Society
- StandardWeb Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation 12 December 2024W3C
- VendorWeb Vitalsweb.dev (Google)
O*NET occupations consulted: 15-1254.00, 15-1252.00. Read on 2026-10-04.
Everything suggested for this role
Each pick says which of the role's tools or work it matched. Auto-listed means automated checks only.
Skill packs531
MCP servers91
Plugins and agents14
Sign in to see which tools these are. It is free.