Frontend Career Path
See reference/career-levels.md for
the shared 8-level ladder, the progression diagram, and the three
track-agnostic advancement dimensions (Autonomy, Impact/scope,
Mentorship). This file adds only what’s specific to Frontend.
Levels
Section titled “Levels”| Level | Scope in Frontend |
|---|---|
| Trainee | Implements small, well-defined UI changes (styling tweaks, static markup) under close guidance. |
| Junior | Builds individual UI components from a spec, with review before and after implementation. |
| Junior Advanced | Builds and tests UI components independently; asks for help only on ambiguous requirements. |
| Semi Senior | Owns a full page/view end-to-end: components, API integration and tests. |
| Semi Senior Advanced | Owns multiple related views, or a feature with shared state/components across them. |
| Senior Level 1 | Owns a project’s frontend architecture decisions (state management, component structure, performance budget). |
| Senior Level 2 | Defines frontend patterns and standards reused across projects on the account. |
| Senior Level 3 | Leads the project’s technical delivery end-to-end, managing the Developers on the team — see roles/leader.md. |
Criteria to advance
Section titled “Criteria to advance”Each transition lists only the track-specific bar (Technical
complexity). Autonomy, Impact/scope and Mentorship are the same for
every track — see
reference/career-levels.md.
Trainee → Junior
Section titled “Trainee → Junior”- Technical complexity: Ships a small UI change (styling, static markup) that passes review without rework on fundamentals.
Junior → Junior Advanced
Section titled “Junior → Junior Advanced”- Technical complexity: Builds a component from a spec using the project’s framework (React or equivalent) and integrates it with a documented API without help.
Junior Advanced → Semi Senior
Section titled “Junior Advanced → Semi Senior”- Technical complexity: Handles cross-browser/responsive/accessibility edge cases independently and writes its own component/E2E tests.
Semi Senior → Semi Senior Advanced
Section titled “Semi Senior → Semi Senior Advanced”- Technical complexity: Owns a page/view’s state management and API integration end-to-end, including error and loading states.
Semi Senior Advanced → Senior Level 1
Section titled “Semi Senior Advanced → Senior Level 1”- Technical complexity: Makes performance and accessibility trade-off calls for a feature (bundle size, WCAG conformance) without escalating them.
Senior Level 1 → Senior Level 2
Section titled “Senior Level 1 → Senior Level 2”- Technical complexity: Defines the project’s frontend architecture (state management approach, component structure, testing strategy).
Senior Level 2 → Senior Level 3
Section titled “Senior Level 2 → Senior Level 3”- Technical complexity: Sets frontend standards adopted across multiple projects on the account, in addition to taking on project delivery ownership.