Stage 7 · Master
Advanced Topics & Future of Platform Engineering
Career Growth: Platform Engineer
IC track vs management. Staff/Principal platform engineer skills. Speaking, writing, open source. PlatformCon, community.
IC vs Management Track
Platform engineering offers both tracks. IC track: deep technical expertise, architecture, coding, standards. Management track: people, strategy, budget, hiring. Both are equally valued. Many switch between tracks.
| Aspect | IC Track (Staff/Principal) | Management Track (EM/Director/VP) |
|---|---|---|
| Focus | Technical excellence, architecture, coding | People, strategy, budget, hiring |
| Scope | Technical: platform architecture, standards | Organizational: team health, delivery |
| Deliverables | RFCs, code, tools, platforms | Roadmaps, budgets, hiring plans, careers |
| Influence | Technical authority, persuasion | Organizational authority, resources |
| Time Split | 70% technical, 30% communication | 20% technical, 80% people/process |
| Career Milestone | Staff → Principal → Distinguished | EM → Director → VP → CTO |
Many platform engineers try management for 1-2 years, return to IC. The skills transfer: technical credibility helps management; people skills help IC influence. Try both if unsure.
Platform Engineer Levels
| Level | Title | Scope | Key Behaviors | Typical Experience |
|---|---|---|---|---|
| L3 | Platform Engineer | Task/Feature | Implements features, fixes bugs, writes tests, follows standards | 1-3 years |
| L4 | Senior Platform Engineer | Component/Service | Designs components, mentors L3, drives features, improves reliability | 3-5 years |
| L5 | Staff Platform Engineer | System/Platform | Architects platform capabilities, sets standards, cross-team influence | 5-8 years |
| L6 | Principal Platform Engineer | Organization/Industry | Sets technical strategy, industry influence, org-wide architecture | 8-12+ years |
| L7 | Distinguished Engineer | Industry | Defines industry direction, keynotes, standards bodies, rare | 12+ years |
Staff/Principal Skills
| Skill Category | Staff Engineer | Principal Engineer |
|---|---|---|
| Technical Depth | Deep in 2-3 domains (K8s, Go, Cloud) | Broad across 5+ domains, connects dots |
| Architecture | Designs platform capabilities | Sets org-wide technical strategy |
| Influence | Persuades teams, drives adoption | Shapes org strategy, influences execs |
| Communication | Clear RFCs, design docs, talks | Keynotes, strategy memos, board updates |
| Mentorship | Mentors 5-10 engineers | Mentors staff engineers, grows leaders |
| Standards | Writes platform standards | Defines industry standards (CNCF, etc.) |
| Coding | Writes production code daily | Writes strategic code, prototypes, tools |
| Incidents | Leads platform incidents | Defines incident culture, postmortem process |
| Hiring | Interviews, onboards | Defines hiring bar, grows org |
The jump from Senior → Staff is the hardest: from 'how do I implement this?' to 'what should we build and why?' Requires shifting from output to outcome, from local to global optimization.
Building Visibility
- Write: RFCs, design docs, postmortems, blog posts (internal + external)
- Speak: Team demos, org all-hands, meetups, conferences (PlatformCon, KubeCon, SREcon)
- Demo: Monthly platform demo, record and share
- Teach: Office hours, workshops, onboarding sessions, mentoring
- Document: Standards, runbooks, architecture decisions, API docs
- Open Source: Contribute to CNCF projects, publish platform tools
- Metrics: Make your impact visible — dashboards showing adoption, savings, reliability
Community & Open Source
Platform engineering community is tight-knit. Engage: PlatformCon, KubeCon, SREcon, local meetups. Contribute: CNCF projects (Backstage, ArgoCD, Crossplane, Kyverno, Cluster API). Publish: blog, newsletter, talks. Network: Slack communities (#platform-engineering, #backstage, #argoproj).
| Activity | Effort | Impact | Frequency |
|---|---|---|---|
| Write blog post | Medium | High (lasting) | Monthly |
| Give talk | High | High (networking) | Quarterly |
| Contribute OSS | Variable | High (credibility) | Monthly |
| Answer Slack questions | Low | Medium (reputation) | Weekly |
| Mentor | Medium | High (multiplier) | Weekly |
| Write RFC | Medium | High (influence) | As needed |
| Run workshop | High | High (enablement) | Quarterly |
Continuous Learning
Platform engineering moves fast: Kubernetes, CNCF landscape, cloud providers, AI. Learning strategy: T-shaped (deep in platform, broad in adjacent), just-in-time learning, learning by teaching.
| Area | Depth | Resources |
|---|---|---|
| Kubernetes | Deep | Kubernetes the Hard Way, CKS cert, KubeCon talks |
| Cloud (AWS/GCP/Azure) | Broad + 1 deep | Provider certs, Well-Architected, re:Invent talks |
| Go/Rust | Deep | Effective Go, Rust Book, platform codebases |
| Distributed Systems | Deep | DDIA, MIT 6.824, papers (Raft, Paxos, CRDTs) |
| Observability | Deep | Grafana docs, Prometheus book, OpenTelemetry spec |
| Security | Broad | CKS, OWASP, SLSA, Sigstore, Kyverno/OPA |
| Platform Engineering | Broad | PlatformCon, Team Topologies, Platform Engineering book |
| AI/ML Platform | Emerging | Kubeflow, MLflow, Ray, KServe, CNCF AI WG |
Best way to learn: teach. Write a blog post, give a talk, run a workshop, mentor. You'll find gaps in your understanding. Teaching forces clarity. Platform engineering is a teaching profession — you're constantly teaching developers how to use the platform.
Example Career Paths
Year 1-2: Platform Engineer (L3)
- Implement golden path templates
- Fix bugs in platform API
- Write tests, improve CI
- Learn: Go, K8s, ArgoCD, Crossplane
Year 3-4: Senior Platform Engineer (L4)
- Design new golden path (ML platform)
- Mentor 2 L3 engineers
- Drive platform reliability (SLIs, runbooks)
- Speak at internal demo day
Year 5-6: Staff Platform Engineer (L5)
- Architect platform federation model
- Lead platform reliability (error budgets, game days)
- Write platform standards (RFCs)
- Speak at PlatformCon
- Mentor 5+ engineers across teams
Year 7-8: Principal Platform Engineer (L6)
- Define platform strategy for 5000+ dev org
- Influence cloud provider roadmaps
- Keynote at KubeCon
- Define industry standards (CNCF TAG)
- Grow next generation of staff engineers
Year 1-3: Senior Platform Engineer (L4)
- Technical lead for platform API team
- Mentor, code review, architecture
Year 4: Engineering Manager (Platform API)
- 6 engineers, delivery + people
- 1:1s, career growth, hiring
- Still technical: code review, architecture
Year 5-6: Director of Platform Engineering
- 3 EMs, 30 engineers
- Strategy, budget, org design
- Cross-org influence
- Less coding, more strategy
Year 7+: VP Engineering / CTO
- Org-wide technical strategy
- Board reporting
- Culture, hiring, business alignment
Treat your career like a platform: invest in capabilities (skills), expose APIs (visibility), measure SLIs (impact), have runbooks (resilience), enable self-service (mentoring). The best platform engineers build platforms for their own career growth.
Mark this lesson complete to store local progress and unlock a cleaner resume path the next time you visit.