Engineering, not development — take real work to production-grade.
01
Who it is for
For builders with real technical agency who want to cross from writing code to engineering systems. Engineering, not development: a system that scales rests on understanding the business, then design, modelling, and architecture — then code. Quality is the bar, on real Arc work rather than coursework or a prototype.
02
What it trains
- Engineering a system from the business up — design, modelling, architecture, then code
- Refactoring a built or MVP system toward production-grade
- Engineering a post-prototype project into something trustworthy
- Building the reliability and evaluation that make a system trusted
03
Example missions
- Refactor an MVP toward production-grade
- Engineer a post-PoC project into a deployable system
- Build reliability and evaluation into a working system
- Take a demo the distance to something Arc can ship
04
What you leave with
- A production-grade system or module
- A refactor that holds at scale
- A technical report on what it took
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 prototype-only work, ticket-work, or supervised task execution
07
Selection
- Recognised through real work, by invitation — not an application
- Real coding ability, and the will to cross into unfamiliar tech and domain