Frontend Developer

The journey

1. Practised under observation

   1. 01The web platform and structured contentWhat the web actually is, and HTML as the language of structure and meaning.Practised under observation

      MilestoneStructured for everyone

      Meaning lives in the markup, so assistive technology and search both read the page the way a person does.

   2. 02Styling, layout and responsive designFrom structure to a visual system, using CSS as a layout discipline that holds as a product grows.Practised under observation

      MilestoneHolds on every screen

      A design becomes a working interface that keeps its shape on a phone, a tablet, and a desktop, and stays readable throughout.

2. From here, milestones are verified rather than practised.

   Verified against a real task

   1. 03Programming the browserJavaScript from zero to a working, data-driven application, with no framework involved.Verified against a real task

      MilestoneAlive and honest

      Real data arrives, people interact, and the interface stays usable when the data is slow, missing, or broken.

   2. 04Professional tooling and engineered codeFrom code that works to code that ships, through version control, review, dependencies, and types.Verified against a real task

      MilestoneEngineered, not improvised

      Nothing you ship has only your eyes on it: changes go through review, and the dependencies and types behind them are choices you can defend.

   3. 05Component-based application engineeringThe modern frontend discipline: components, state, and routing composed into a real application.Verified against a real task

      MilestoneComposed to scale

      A stranger can find their way around your application, and you can defend where each piece of state lives and where you kept things simple.

   4. 06Quality: testing, verified accessibility and frontend securityTrust manufactured at the interface, with tests that catch, accessibility proven rather than claimed, and a posture for code running in hostile territory.Verified against a real task

      MilestoneProven, not promised

      People who cannot use a mouse or a screen can still use what you built, untrusted input gets nowhere, and credentials put nobody at risk.

   5. 07Performance and production deliveryFast for real people on real networks, with a measured budget and a pipeline that ships it.Verified against a real task

      MilestoneFast where it counts, shipped for real

      Speed is a number you measured and improved for reasons you can explain, and nothing ships without a way back.

   6. 08The Frontend Developer in the organizationThe seam worker, holding the lines to design, to the services behind the interface, and to the people deciding what gets built.Verified against a real task

      MilestoneThe seam worker

      A vague request and a design become something shippable, with the states nobody designed and the questions nobody asked surfaced along the way.

3. 1. Capstone

      An interface the organization ships

      A complete production frontend for a real product domain, built under observation from structure through to a deployed, measured, accessible application with its own known limitations written down.

      Defence

      You walk an instructor through your own interface: why it is built this way, who it works for and who it does not, what happens when the network is slow or a service fails, and what you would fix first. The credential is not awarded if you cannot account for your own work.

   2. Credential

      High-assurance credential

      Evidence that you can ship interfaces organisations put in front of every user, on every device. It does not claim seniority, and it does not oblige any employer to accept it.

      See how proof works