Team composition:
- Lead Architect — sets direction, mentors.
- Domain Architects — Data, Integration, Security, Sharing.
- Solution Architects — project-level.
- Senior Engineers transitioning to architect.
Hiring:
- External hire for specialised expertise.
- Internal promotion for cultural fit and platform knowledge.
- Mix is typical.
Roles to define:
- Who reviews code at architect level?
- Who chairs ARB?
- Who owns standards documentation?
- Who runs architect community of practice?
Skill development:
- Trailhead Architect Trail.
- Domain certifications progressing toward CTA.
- Mentorship from senior architects.
- Conference attendance.
- Stretch projects.
Architect community of practice:
- Monthly internal meetups.
- Tech talks and demos.
- Code reviews.
- Knowledge sharing.
Career progression paths:
- Solution Architect -> Senior SA -> Principal.
- Technical Architect -> Senior TA -> CTA.
- Hybrid roles — Solution + Technical at smaller orgs.
Common pitfalls:
- No architecture team — architects scattered, no consistency.
- Ivory tower — architects detached from actual delivery.
- Senior-only team — no juniors learning.
- No mentorship — knowledge stays with individuals.
Senior insight: architecture is a craft. Master-apprentice models work. Hire smart juniors; mentor them deeply.