Architect

Technical Thinking

• Thinks at multiple levels of abstraction simultaneously - from system principles to implementation detail.
• Makes complex trade-offs explicit and communicates them in language that both engineers and business stakeholders can understand.
• Designs for longevity - building systems and standards that age well rather than solving only immediate problems.
• Challenges poor technical decisions constructively, regardless of seniority.
• Applies first-principles reasoning to novel problems rather than defaulting to familiar patterns.
• Maintains a coherent mental model of the organisation's systems, their boundaries, and their interdependencies.
• Distinguishes between essential complexity and accidental complexity, and drives reduction of the latter.
• Evaluates technology options with structured rigour - considering fit, risk, cost of ownership, and exit paths.

Architecture & Design

• Produces architecture proposals that are well-reasoned, clearly documented, and actionable by engineering teams.
• Designs systems with explicit consideration of failure modes, operational characteristics, and long-term evolution.
• Balances theoretical correctness with pragmatic delivery constraints, knowing when good enough is the right call.
• Ensures cross-cutting concerns - security, observability, reliability, performance - are addressed in design, not added as afterthoughts.
• Uses architecture decision records (ADRs) to create durable institutional memory around significant choices.
• Recognises when existing architecture is the wrong foundation and makes the case for change with evidence and clarity.
• Designs governance processes that are lightweight and enabling, not bureaucratic and blocking.

Standards & Governance

• Defines engineering standards that are specific enough to be useful and flexible enough to survive contact with reality.
• Establishes conformance review processes that identify drift early, before it compounds into systemic risk.
• Ensures standards are maintained as living documents, revised as technology and context evolve.
• Works with teams to understand where standards create friction and distinguishes legitimate tension from poor fit.
• Builds shared ownership of standards across Lead Engineers and TTLs rather than holding them as personal authority.
• Makes governance decisions transparently, documenting rationale so teams can understand and challenge them.
• Tracks architectural risk and technical debt at organisation level and ensures it has a managed remediation path.
• Contributes to the C4E model by translating architectural principles into usable standards and practices.

Influence & Communication

• Influences technical direction through the quality of thinking, not positional authority.
• Writes clearly - architecture documents, proposals, and ADRs that are accessible to a broad technical audience.
• Engages non-technical stakeholders with confidence, translating technical concepts into business terms.
• Makes the case for technical investment in language that resonates with business decision-makers.
• Listens carefully to engineering teams - understanding their constraints before proposing architectural changes.
• Gives feedback on technical proposals in ways that build capability, not just correct decisions.
• Presents complex trade-offs clearly - helping stakeholders make informed choices rather than making decisions for them.
• Builds a reputation for technical rigour and intellectual honesty that makes people seek out their perspective.

Collaboration

• Partners effectively with Engineering Managers - recognising that technical systems and human systems must be co-designed.
• Creates architecture guidance that empowers teams rather than constraining them unnecessarily.
• Builds consensus across engineering leaders on significant technical direction.
• Engages Lead Engineers and TTLs as co-owners of architecture, not recipients of architectural decrees.
• Collaborates with the Head of Engineering and VP on capability planning and technology investment decisions.
• Works with Product and Design to ensure technical constraints are understood early in the discovery process.
• Creates spaces for engineering-wide technical debate - architecture forums, design reviews, communities of practice.

Strategic Thinking

• Connects technical architecture decisions to business strategy, commercial outcomes, and competitive positioning.
• Anticipates the technical consequences of business growth, scale changes, and market shifts.
• Builds technology roadmaps that balance current delivery needs with long-term architectural health.
• Identifies capability investments the organisation needs to make now to retain strategic optionality later.
• Understands the total cost of architectural decisions - not just build cost, but operational and opportunity cost.
• Evaluates build vs buy decisions with commercial rigour, not just technical preference.
• Maintains a view of the external technology landscape - tracking how industry patterns are evolving and what that means for the organisation.
• Contributes to engineering strategy conversations at senior leadership level with clarity and commercial awareness.

Continuous Learning

• Stays at the forefront of technology trends, patterns, and industry practice.
• Contributes to the external engineering community through writing, speaking, or open-source contribution.
• Brings new thinking into the organisation in ways that land practically, not just theoretically.
• Seeks disconfirming evidence for their own architectural positions - holding views with appropriate confidence, not dogma.
• Learns from post-incident reviews, architectural failures, and decisions that did not age well.
• Actively develops the technical thinking capability of Lead Engineers and senior engineers around them.
• Maintains depth in their core domains while developing sufficient breadth to reason across the full system landscape.