Module 2
Role of the Software Architect
What the job actually consists of day to day, how decisions get made and recorded, and what specifically changes when you move from senior developer to solution architect.
What you will be able to do
- Describe what an architect does with their time, beyond producing diagrams.
- Write an Architecture Decision Record that a future team can actually use.
- Influence a technical decision without relying on authority.
- Name the specific skill gaps between a senior developer and a solution architect.
- 8 min
01What an Architect Actually Does All Day
The job is mostly not drawing. It is defining constraints, resolving conflicts between teams, and being accountable for decisions whose consequences arrive long after you made them.
- 10 min
02Influence Without Authority
Architects rarely command anyone. Decisions stick when teams are convinced, and the techniques for that are learnable rather than innate.
- 9 min
03Architecture Decision Records in Practice
The cheapest high-value habit in the discipline: one short document per significant decision, capturing the forces and the alternatives you rejected.
- 10 min
04From Senior Developer to Solution Architect
The specific habits that make a strong senior developer and the specific ways each one has to change. This is the transition the track is built around.
Role of the Software Architect
8 questions · pass at 70%