Architecture — where it leads
Several directions, never one. Each says what your training reuses, what graduates typically lack, the real entry conditions, and one thing you can test this term. A degree is not assessed here — the assessment sits on the task, so follow any direction through to its occupation page.
Where it can lead#
Practising architecture
task-level analysis →- What transfers
- All of it, and this is the only path where carrying the compliance and standing on site are part of the job rather than adjacent to it.
- What graduates typically lack
- Graduates generally arrive strong on concept and presentation and thin on what a thing costs, how long it takes to procure, and what a contractor will do with an ambiguous drawing.
- Entry reality
- The longest and most regulated route on this site: registration takes years of logged practice after the degree, and the early years are the ones where visualisation and documentation hours dominate — which is exactly where the assessment says the change is landing.
Take one of your studio schemes and price a single element of it — a façade bay, a stair — by ringing two suppliers. The gap between what you assumed and what it costs is the part of this job the studio does not grade.
Product and UX design
task-level analysis →- What transfers
- Working inside constraints you did not choose, and iterating a design against feedback from people who are not designers — the studio crit is unusually good preparation for a design review.
- What graduates typically lack
- Graduates move without the habits of the software side: working in short cycles, instrumenting whether a change worked, and treating a design as something that ships and then gets measured rather than as something that is finished and handed over.
- Entry reality
- A common and well-trodden move, and one of the few that does not waste the years already spent. Expect to be asked for software work in a portfolio, which means building a small amount of it deliberately rather than hoping the architecture work reads across.
Redesign one screen of an app you use daily, and then find three people who use it and watch them try your version without explaining it. The watching is the part that transfers.
Project delivery and coordination
task-level analysis →- What transfers
- Coordinating consultants, suppliers and a programme — the part of studio work that was never about drawing, applied where getting the thing delivered is the whole objective.
- What graduates typically lack
- Graduates are used to a programme that slips without consequence. On a delivery role the date is the deliverable, and the skill is knowing which slippage matters and which is noise.
- Entry reality
- Open to graduates and often the fastest route to seeing how buildings actually get made. Read the occupation page's scope first: it is written for fulfilment operations in services and logistics, and construction delivery shares the shape but not every detail.
Take charge of the schedule for one group project and record every date that moved, who moved it and why. Most of the answers will not be about the work itself, and that is the finding.
Leading a team on site
task-level analysis →- What transfers
- Reading drawings against what is actually built, and being the person a trade asks when the drawing and the ground disagree.
- What graduates typically lack
- Graduates have rarely had authority over people whose trade they do not practise, which is the daily condition of the role rather than an occasional difficulty.
- Entry reality
- Reached after site experience rather than from the degree. Worth knowing that the occupation page marks its own confidence low: this role is on every org chart and has thin public evidence.
Visit one live site and ask a trade what on the drawings they had to work around last week. Their answer is the gap between design and build, stated by the only people who see it.