Full-Stack Developer

The journey

1. Practised under observation

   1. 01The interface foundationThe user-facing half from zero, with structure, style, and responsive layout at working professional depth.Practised under observation

      MilestoneA real site, structurally honest

      That you can build a site whose structure carries meaning, works for people using assistive technology, and holds its shape on a phone, a tablet, and a desktop.

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

   Verified against a real task

   1. 02Programming across the wireOne language, two seats, with programming fundamentals at depth, the browser brought alive, and the tooling both halves will share.Verified against a real task

      MilestoneAlive on the client, fluent underneath

      That you can build an interface that fetches real data and stays usable when that data fails, and work the way a team works with versioned history and review.

   2. 03The service halfThe producer seat at working depth, with HTTP mastered, an API designed as a product, and the seam between your own two halves written down.Verified against a real task

      MilestoneTwo halves, one contract

      That you can write down the contract between your own interface and your own service and honour it as if a stranger owned the other side, and refuse bad input at the border.

   3. 04Persistence and data integrityTruth that survives restarts, with relational modelling, transactional honesty, and migrations as code at the whole-product seat.Verified against a real task

      MilestonePersistence the product can trust

      That you can model data so the database protects it, change its shape safely once it holds real records, and find which layer a wrong number on the screen actually came from.

   4. 05Identity and security across the whole stackThe full-stack advantage made real, owning the entire authentication flow end to end and defending both seats at once.Verified against a real task

      MilestoneThe whole chain, defended

      That you can build and explain every link from a login click to an authorised response, keep hostile input out of both halves, and put the security check where it cannot be bypassed.

   5. 06The integrated applicationComposition at product scale, with a component-based interface over a real service, and caching, background work, and real-time added where the product needs them.Verified against a real task

      MilestoneOne product, properly composed

      That you can share one typed contract across both halves so a change on one side cannot quietly break the other, and add speed and background work without making the product wrong.

   6. 07Shipping and running the whole productDelivery and operations at the product-team level, with the stack packaged, shipped through gates, observed, and run at an honest cost.Verified against a real task

      MilestoneShipped whole, run honestly

      That you can ship both halves through automated gates, diagnose a problem that shows up in the interface but started in the service, and say what the product costs to run.

   7. 08The Full-Stack Developer in the organizationThe whole-product professional, owning scope across every seam, calling specialists at the right moment, and carrying breadth honestly.Verified against a real task

      MilestoneThe whole-product owner

      That you can break a vague feature down across layers and say what each half costs, and recognise when a problem has passed your depth and hand it over with evidence rather than guessing longer.

3. 1. Capstone

      A product, whole, from one pair of hands

      A complete production product for a real domain, built under observation from an accessible interface through a contract-described service, persistence, the whole authentication chain, and deployment, with its own known limitations and its thinnest layer written down.

      Defence

      You walk an instructor through your own product across both halves: why the layers are divided this way, the authentication chain from click to authorised response, where a hostile input is stopped on each side, which half is weakest and what a specialist would fix first, and what you would hand a new team on day one. The credential is not awarded if you cannot account for your own work.

   2. Credential

      High-assurance credential

      Evidence that you can carry a whole product from idea to running software and account for every layer of it. It certifies working professional depth on both halves rather than specialist depth on either, it does not claim seniority, and it does not oblige any employer to accept it.

      See how proof works