Carry an engineered system across the line into a product.
01
Who it is for
A deliberately broad pathway: it asks product sense, enough R&D and coding to talk to engineers, and a commercial / strategic eye. You sit between the engineers and the solution architect / strategist and carry a post-MVP, well-engineered system into a product — the emphasis on productisation, not marketisation.
02
What it trains
- Turning a post-MVP, engineered system into a coherent product
- Reading users and workflows from a raw capability
- Holding the middle between engineers and strategy
- Moving a system from alpha toward shipped
03
Example missions
- Define the user flow for a real Arc capability
- Write the product brief for a post-MVP system
- Translate a technical system into a product narrative
- Shape the alpha → shipped path and scope
04
What you leave with
- A product brief or flow
- A shipped or shipping surface
- A productisation plan
05
How a mission works
Arc shows you a few real projects it judges you ready for, and you choose the one that draws you. Then it is mission-based and asynchronous — a clear brief in, a concrete artifact out; you investigate, decide, and return with evidence, and Arc evaluates the outcome, not the motion. Expect the start to be hard — unfamiliar tools, an unfamiliar problem space; that crossing is the point.
06
What it is not
- Not a course or a bootcamp — the work is real, and harder
- Not employment, salary, a title, or a guaranteed role — a cultivation path, not a job
- Not feature-list product management
07
Selection
- Recognised through real work, by invitation — not an application
- Product judgement, and the depth to earn engineers' trust