← Learning Pathways Learning Pathway

Senior Platform Engineer to Platform Architect

🕑 24-48 months Platform Engineering

Develop organisation-wide platform architecture authority by mastering cloud-native architecture at scale, FinOps, security architecture, and the trusted voice that earns engineering leaders' confidence in your platform strategy.

🎯 Focus Areas

Cloud-Native Architecture at Scale

A platform architect is accountable for the coherence and evolution of the entire engineering platform - compute, networking, storage, deployment, observability, and security - across the organisation. Decisions at this level shape the development experience of every engineer and have multi-year consequences for cost, reliability, and capability.

Platform Strategy and Technology Choices

Platform architects evaluate, select, and retire foundational technologies - Kubernetes distributions, service mesh implementations, observability backends, secrets management solutions, developer portals. These choices must balance technical capability, operational cost, vendor ecosystem health, and the organisation's ability to sustain them over time.

FinOps and Cost Architecture

At scale, cloud cost is an engineering architecture concern. Platform architects design cost allocation models, set the governance framework for resource consumption, identify architectural patterns that drive unnecessary cost, and build the case for investment decisions that trade upfront cost for long-term efficiency.

Security Architecture

Security is not bolted on after the platform is built - it is designed in from the start. Platform architects own the security architecture of the engineering platform including network segmentation, identity and access management, secrets management, supply chain security, and the threat model that drives these decisions.

Trusted Platform Voice

Platform architectural authority is earned through a track record of sound decisions, direct engagement with engineering teams, and transparent communication of trade-offs. The best platform architects spend significant time with delivery teams understanding the real constraints from the ground up, not designing from a distance.

⚡ Skills & Behaviours to Develop

Skills to Develop

  • Design a complete cloud-native platform architecture for a complex organisation, covering compute, networking, storage, delivery, observability, and security, with documented trade-offs at every major decision point.
  • Build and communicate a multi-year platform technology roadmap that connects platform investment to engineering capability and business outcomes.
  • Design the security architecture for a cloud-native engineering platform - zero trust network model, workload identity, secrets management, supply chain security, and incident response.
  • Develop a FinOps architecture covering cost allocation, chargeback models, governance processes, and architectural patterns that drive cost efficiency at scale.
  • Evaluate a major platform technology choice with structured criteria and a formal proof-of-concept, producing a recommendation that engineering leadership trusts.
  • Design the reference architecture for multi-cloud or multi-region deployment, including trade-offs in complexity, cost, and operational capability.
  • Lead an architecture review process for significant platform changes that improves quality without creating organisational bottlenecks.
  • Produce architectural documentation at multiple levels - from executive summary to implementation detail - that is genuinely used to make decisions.

Behaviours to Demonstrate

  • Engages directly with engineering teams to understand the real constraints and pain points before proposing platform architectural direction.
  • Makes platform architectural trade-offs explicit and invites challenge rather than presenting recommendations as the obvious correct answer.
  • Builds relationships with security, finance, compliance, and engineering leadership as a core part of the job.
  • Sponsors platform architecture experiments and proof-of-concept work, understanding that theoretical reasoning alone is not sufficient for major platform decisions.
  • Updates architectural positions when evidence changes, demonstrating intellectual honesty about prior decisions.
  • Communicates complex platform trade-offs to non-technical executives clearly and without hiding genuine uncertainty.
  • Produces platform strategy and investment cases that are credible because they are grounded in real cost and capability data.
🛠 Hands-On Projects
1 Produce a current-state and target-state platform architecture for your organisation, including cost model, security architecture, and delivery capability - and present it to engineering leadership.
2 Design the security architecture for your engineering platform covering network segmentation, workload identity, supply chain security, and secrets management, and implement the highest-risk improvements.
3 Build a FinOps governance framework including cost allocation by team, anomaly detection, and architectural guidance for cost-efficient Kubernetes patterns.
4 Lead the evaluation and selection of a major platform technology - a new Kubernetes distribution, service mesh, or observability backend - running a structured proof of concept and producing a documented recommendation.
5 Develop a platform technology radar for your organisation, categorising tools and platforms by adoption recommendation, and facilitate the team discussion behind the choices.
6 Design the reference architecture for a multi-region deployment model, documenting the trade-offs in complexity, cost, and recovery capabilities, and present it to engineering and business leadership.
⚡ AI Literacy for This Transition
AI workload architecture and platform AI governance
1

Develop an architectural position on how AI and ML workloads are supported by your platform - GPU node pools, inference serving, model artefact storage, experiment tracking - and document it as a platform capability roadmap item.

2

Design the security architecture for AI tool usage in your engineering organisation - data residency, network egress controls, supply chain risk for AI model dependencies, and audit logging for AI interactions.

3

Evaluate the platform cost implications of AI coding tool adoption across engineering teams - API egress costs, local inference versus cloud API trade-offs, and how to include AI tooling in FinOps governance.

4

Build an architectural position on AI integration patterns - RAG pipelines, embedding infrastructure, vector databases, prompt management - and how these capabilities should be provided as platform services.

5

Develop the organisational position on AI in CI/CD pipelines - AI-assisted code review, AI-generated test cases, AI in security scanning - and the governance framework for evaluating these tools before adoption.

6

Stay current on the regulatory and security landscape for AI in platform engineering - software supply chain concerns around AI-generated code, data residency for AI training, and emerging compliance requirements.

📚 Recommended Reading

Production Kubernetes

Josh Rosso, Rich Lander, Alex Brand, and John Harris

The deepest treatment of Kubernetes in production environments - the reference for an architect making foundational platform decisions about cluster design and operations.

Cloud FinOps

J.R. Storment and Mike Fuller

The definitive treatment of FinOps practice - cost allocation, governance, and the engineering patterns that drive cloud cost efficiency at scale.

Zero Trust Networks

Evan Gilman and Doug Barth

Security architecture for cloud-native platforms starts with zero trust principles - this is the clearest treatment of the model and its implementation.

Fundamentals of Software Architecture

Neal Ford and Mark Richards

Platform architects benefit from understanding software architecture principles and the soft skills of operating as an architect - this book covers the fundamentals in a way that applies across disciplines.

Team Topologies

Matthew Skelton and Manuel Pais

Platform architecture cannot be separated from team structure - this book provides the framework that connects platform design to how teams interact with and depend on the platform.

The Phoenix Project

Gene Kim, Kevin Behr, and George Spafford

A narrative illustration of how platform and operational architecture choices affect delivery performance - helps architects develop empathy for the organisational consequences of their decisions.

🎓 Courses & Resources

AWS Solutions Architect Professional or Google Professional Cloud Architect

A Cloud Guru

Professional cloud architect certifications validate the breadth and depth of cloud platform knowledge required for credible platform architecture decisions.

Certified Kubernetes Security Specialist (CKS)

Linux Foundation / CNCF

Security is a first-class architectural concern and the CKS validates the depth of Kubernetes security knowledge required at the architect level.

FinOps Certified Practitioner

FinOps Foundation

Cost architecture is a platform architect responsibility - the certification provides the framework and vocabulary for FinOps governance at an organisational level.

Platform Engineering and Internal Developer Platforms

Humanitec / Various

Builds the architecture thinking for designing internal developer platforms - the golden path, self-service capabilities, and the platform-as-a-product model at scale.

📋 Role Archetypes

Review the full expectations for both roles to understand exactly what good looks like at each level.

→ Senior Platform Engineer Archetype → Platform Architect Archetype