Fill in the fields below, then save as PDF or print at A2 landscape.
Role
Senior Platform Engineer
Level 1
Unsatisfactory
Low
Individual
Impact
Fails to lead complex platform delivery work; significant cloud architecture or reliability engineering decisions are left unmade or made poorly without documentation.
Internal developer platform direction is unclear; golden path definitions are absent or poorly adopted by engineering teams.
Mentoring of intermediate and junior engineers is absent or ineffective; the team's platform capability is not growing.
Examples
Owned the internal developer platform strategy for a quarter and produced no meaningful golden path improvements or adoption metrics.
Three intermediate engineers asked for design guidance on a multi-account Terraform strategy and received no substantive response for four weeks.
Dampeners
Was given conflicting priorities from engineering leadership that made it difficult to establish a clear platform direction.
Progression Signal
Begins making and documenting a meaningful cloud architecture decision with clear trade-off reasoning.
Resumes structured mentoring of intermediate engineers with a deliberate development focus.
Business Impact
Impact
Engineering teams lack a coherent internal developer platform, leading to inconsistent deployment patterns and reduced delivery confidence.
Platform reliability posture degrades without senior ownership of SLOs, error budgets, and incident management.
Examples
Four engineering teams built divergent deployment patterns in the absence of a platform golden path, creating a retroactive standardisation cost.
Dampeners
The divergence is recoverable; the cost of standardisation is high but not yet compounding into production incidents.
Progression Signal
A clear internal developer platform direction is established and communicated; engineering teams begin aligning to it.
Mid
Individual
Impact
Makes cloud architecture decisions without documenting trade-offs or building consensus; decisions are later reversed or bypassed by engineering teams.
Reliability engineering is reactive; does not proactively manage error budgets or lead GameDays and chaos engineering exercises.
Fails to influence engineering teams toward better deployment and reliability practices; advocacy is absent or ineffective.
Examples
Made a multi-account strategy decision without consulting engineering team leads; two teams built workarounds within six weeks.
No error budget review had occurred in three months despite the SLO framework being in place.
Dampeners
Engineering leadership may not have provided the space and air cover needed for proactive reliability investment.
Progression Signal
Begins documenting architecture decisions with trade-offs and bringing stakeholders into consensus-building conversations.
Resumes error budget reviews on a regular cadence and uses them to drive one concrete reliability prioritisation decision.
Business Impact
Impact
Reversed architectural decisions create rework cost and engineering team frustration, eroding trust in the platform team's technical authority.
Unmanaged error budgets result in reliability investment being crowded out by feature delivery, increasing incident risk.
Examples
Reversed multi-account decision created three weeks of rework across two engineering teams and damaged the platform team's credibility.
Dampeners
Rework cost is significant but bounded; credibility damage is the longer-term risk.
Progression Signal
Architecture decisions begin landing with engineering team buy-in and remaining stable over time.
High
Individual
Impact
Consistently resistant to challenge on architectural decisions; alternate approaches from the Platform Architect or engineering leadership are dismissed rather than engaged with.
Does not set a quality standard for the discipline; their own infrastructure work is not a reference implementation for the team.
Creates a culture of technical risk-aversion within the platform team - safe, familiar choices rather than sound engineering judgement.
Examples
Received well-reasoned pushback from the Platform Architect on a zero-trust networking approach and rejected it without engaging the substance of the concern.
Team noted in retrospective that cloud architecture decisions were consistently driven by familiarity rather than fitness for purpose.
Dampeners
External pressure or past architectural failures may be driving risk-aversion; the pattern needs a structured conversation to surface.
Progression Signal
Engages constructively with architectural challenge and demonstrates willingness to evolve a technical position based on evidence.
Business Impact
Impact
Technical risk-aversion results in a platform that does not evolve to meet engineering team needs, increasing delivery friction over time.
Loss of trust from the Platform Architect and engineering leadership undermines the platform team's ability to influence technical direction.
Examples
Engineering teams began routing around the platform team for architecture decisions due to lack of confidence in platform technical leadership.
Dampeners
The routing-around pattern is early; trust can be rebuilt if behaviour changes quickly.
Progression Signal
Engineering teams re-engage the platform team for architecture input as trust in technical judgement is rebuilt.
Level 2
Development Needed
Low
Individual
Impact
Leads complex platform delivery work but with gaps in cloud architecture rigour - security implications and operational overhead are not fully considered in design.
Internal developer platform golden paths are defined but adoption is low because enablement and documentation are insufficient.
Mentors intermediate engineers but does not shape their technical development trajectory with sufficient deliberateness.
Examples
Designed a Kubernetes multi-tenancy pattern without considering the RBAC operational overhead for engineering teams; adoption was low as a result.
Golden path documentation existed but no enabling sessions were run; only two of eight engineering teams had adopted it after two months.
Dampeners
Growing into the full senior scope; enablement and adoption leadership skills are developing alongside technical depth.
Progression Signal
Runs enablement sessions for golden path adoption and tracks adoption rate as a metric of success.
Begins structuring intermediate engineer development conversations around a deliberate technical growth roadmap.
Business Impact
Impact
Low golden path adoption means engineering teams continue with inconsistent deployment patterns, maintaining the delivery friction the platform was designed to reduce.
Design gaps in Kubernetes multi-tenancy create operational overhead for engineering teams that reduces the value of the platform.
Examples
Six engineering teams were still using non-standard deployment approaches due to low golden path adoption, negating the platform investment.
Dampeners
The adoption gap is recoverable with an enablement push; the platform capability itself is sound.
Progression Signal
Golden path adoption rate reaches a meaningful threshold through active enablement; engineering teams report reduced deployment friction.
Mid
Individual
Impact
Leads reliability engineering but does not drive the cultural shift needed for reliability to be treated as a shared engineering responsibility.
Communicates platform architecture decisions clearly to technical peers but struggles to translate them for engineering leadership or non-technical stakeholders.
Cloud cost awareness is present but FinOps practices are not embedded in the team's delivery decisions.
Examples
Defined SLOs for platform components but engineering teams continued treating reliability as purely a platform team concern rather than a shared responsibility.
Architecture decision record was clear to platform engineers but engineering leadership found it difficult to understand the business resilience implications.
Dampeners
Cultural change in reliability ownership requires sustained advocacy; progress is often slow at first.
Progression Signal
At least two engineering teams begin actively participating in error budget discussions and treating reliability as a shared concern.
Produces one executive-level reliability risk communication that translates technical risk into business impact language.
Business Impact
Impact
Reliability as a platform-team-only concern creates a fragile model where the platform team is always the single point of accountability for production incidents.
Inability to communicate platform risk in business terms limits the organisation's ability to make informed investment decisions about reliability.
Examples
Three platform incidents were escalated to the platform team alone because engineering teams had not accepted shared responsibility for service reliability.
Dampeners
The incident pattern reflects cultural immaturity that is addressable; no SLA breaches occurred.
Progression Signal
Engineering teams begin owning their service reliability within the platform's SLO framework, reducing the platform team's sole accountability.
High
Individual
Impact
Technically strong but does not drive the scale of platform and cultural change expected at senior level - operating closer to a strong intermediate than a full senior.
Does not represent platform engineering credibly in cross-functional forums; avoids or delegates executive and stakeholder communication.
Platform technical direction is competent but not bold; defaults to safe architectural choices rather than driving the platform forward.
Examples
Consistently delegates all engineering leadership and CTO-level platform conversations to the Platform Architect rather than engaging them directly.
Platform architecture has been stable for 18 months with no strategic evolution in cloud capabilities or developer experience.
Dampeners
May require more active sponsorship from engineering leadership to develop the confidence and space for bold platform direction.
Progression Signal
Leads one significant cross-functional platform conversation and drives it to a clear outcome.
Proposes one bold platform architectural evolution with a clear business case and drives it to adoption.
Business Impact
Impact
Platform stagnation results in engineering teams working around platform limitations rather than being enabled by the platform.
Absence from executive forums means platform investment needs and risks are not being communicated to decision-makers.
Examples
Engineering teams began procuring third-party developer tooling independently, bypassing the platform team due to slow platform evolution.
Dampeners
The third-party procurement pattern reflects engineering team frustration that is recoverable with bold platform evolution.
Progression Signal
Platform evolution programme is established and communicated to engineering leadership with a clear roadmap and investment case.
Level 3
Consistently Delivers
Low
Individual
Impact
Leads the delivery of complex platform work - multi-account cloud architecture, Kubernetes cluster upgrades, observability platform builds - with technical rigour and operational discipline.
Defines and manages SLOs and error budgets for platform services, using data to drive reliability prioritisation.
Mentors intermediate engineers effectively, shaping their technical development with deliberate coaching conversations.
Examples
Led a Kubernetes version upgrade across four production clusters, coordinating engineering team readiness and delivering zero-downtime for all workloads.
Error budget review led to reprioritising a new feature request in favour of a Kubernetes autoscaler reliability improvement.
Dampeners
Leading platform delivery well within established scope; cross-organisational platform strategy influence is developing.
Progression Signal
Begins shaping the organisation's internal developer platform strategy - not just delivering to it.
Business Impact
Impact
Complex platform deliveries land reliably and improve the engineering teams' deployment confidence and operational capability.
SLO-driven prioritisation improves the platform's reliability posture and reduces engineering team disruption from platform incidents.
Examples
Kubernetes upgrade delivered on schedule with zero engineering team disruption; deployment frequency across adopting teams increased by 20%.
Dampeners
Business impact is growing across multiple teams; not yet organisation-wide platform strategic influence.
Progression Signal
Platform improvements begin delivering measurable, organisation-wide changes in engineering team delivery metrics.
Mid
Individual
Impact
Owns the internal developer platform strategy - defining golden paths, measuring developer experience through DORA metrics, and driving adoption through enablement.
Shapes the organisation's cloud architecture - multi-account strategy, network topology, shared services - with documented trade-off reasoning and engineering leadership alignment.
Represents platform engineering credibly in cross-functional forums, translating technical concerns into business resilience and engineering productivity language.
Examples
Defined the organisation's golden path for microservice deployment; adoption reached 85% of engineering teams within the quarter.
Presented cloud architecture trade-offs to engineering leadership in terms of engineering team delivery speed and security risk; received funding for the recommended approach.
Dampeners
Operating well within the senior scope; working at full senior level consistently.
Progression Signal
Begins influencing platform architecture decisions at a level that extends beyond the organisation's current engineering teams.
Business Impact
Impact
Golden path adoption delivers measurable improvements in deployment frequency, change failure rate, and new service onboarding speed.
Cloud architecture decisions shaped with business context and stakeholder alignment land durably, avoiding costly reversals.
Examples
Golden path adoption correlated with a 35% improvement in deployment frequency and a 50% reduction in deployment-related incidents over the quarter.
Dampeners
Impact is organisation-wide and growing; approaching the boundary between senior and architect-level contribution.
Progression Signal
Platform strategy influence begins extending to organisation-wide engineering culture, not just platform tooling adoption.
High
Individual
Impact
Leads platform engineering with the highest standards of technical rigour - their infrastructure is secure, observable, cost-efficient, and maintainable by design.
Drives reliability engineering deeply into the organisation's engineering culture through GameDays, failure mode analysis, and shared SLO ownership.
Sets the technical direction for platform engineering and influences it credibly across all engineering teams.
Examples
Led the organisation's first chaos engineering programme, resulting in six production resilience improvements before any of the failure modes became incidents.
Zero-trust networking architecture they designed was adopted as the organisation's standard, endorsed by the CISO and implemented across all environments.
Dampeners
Operating at full senior level with growing scope; Platform Architect-level contribution is emerging.
Progression Signal
Begins taking on platform architecture governance responsibilities alongside senior delivery - a natural transition toward Principal or Architect scope.
Business Impact
Impact
Chaos engineering and reliability culture improvements materially reduce production incident frequency and business disruption.
Zero-trust architecture delivers a significant security posture improvement with measurable compliance benefit.
Examples
Chaos engineering programme attributable to a 70% reduction in unexpected production outages over six months.
Dampeners
Impact is significant and cross-cutting; approaching Platform Architect scope.
Progression Signal
Platform architectural governance and strategic influence grow to match the scope of their technical contribution.
Level 4
Leading
Low
Individual
Impact
Shapes platform architecture and internal developer platform strategy with organisation-wide scope and visible engineering leadership alignment.
Drives reliability engineering at scale - error budget management, GameDays, cross-team SLO ownership - as a genuine cultural shift.
Grows intermediate and junior engineers at a rate that measurably expands the team's platform capability and delivery capacity.
Examples
Designed and socialised a multi-account cloud strategy that unified three divergent approaches across the engineering organisation.
GameDay programme led to six engineering teams taking direct ownership of their service SLOs and participating in error budget reviews.
Dampeners
Operating at leading level; influence is organisation-wide and growing in strategic depth.
Progression Signal
Platform strategy influence begins extending beyond the engineering organisation to inform product and business investment decisions.
Business Impact
Impact
Cloud architecture unification reduces infrastructure cost and operational overhead while improving engineering team delivery confidence.
Shared SLO ownership reduces the platform team's sole accountability for reliability and builds engineering organisation resilience.
Examples
Multi-account unification delivered an estimated 20% reduction in cloud spend through consolidation and right-sizing.
Dampeners
Impact is significant across the engineering organisation; growing in strategic business reach.
Progression Signal
Platform strategy contributions begin informing executive-level business resilience and technology investment decisions.
Mid
Individual
Impact
Platform engineering technical authority is recognised across the organisation; engineering leaders seek their input on infrastructure and delivery strategy.
Internal developer platform outcomes - deployment frequency, change failure rate, lead time to change - are tracked and improving, driven by deliberate platform investment.
Builds a platform engineering community of practice that raises standards and capability across the organisation.
Examples
DORA metrics programme established by this engineer showed 40% improvement in deployment frequency across adopting teams over two quarters.
Platform engineering community of practice they founded attracted engineers from eight teams and produced three shared tooling improvements.
Dampeners
Operating at leading level with genuine cross-organisational impact; approaching Platform Architect scope.
Progression Signal
Formal recognition of Platform Architect scope is the appropriate next step.
Business Impact
Impact
DORA metric improvements driven by platform strategy deliver measurable business value - faster software delivery, higher quality, reduced incident cost.
Community of practice creates a sustainable, self-reinforcing improvement dynamic across the engineering organisation.
Examples
DORA improvements correlated with a 30% reduction in deployment-related business incidents and a measurable improvement in engineering team satisfaction.
Dampeners
Impact is at full organisation-wide scale; the role scope should reflect this.
Progression Signal
Transition to Platform Architect is the logical and appropriate next step.
High
Individual
Impact
Operating at full Platform Architect level - shaping enterprise platform strategy, cloud-native standards, and developer experience vision with organisation-wide authority.
Security and compliance architecture leadership matches the depth and scope expected of a principal platform practitioner.
Represents platform engineering at executive and industry level with confidence and authority.
Examples
Designed the organisation's enterprise cloud-native platform architecture, presented to the board as a strategic technology investment.
Speaking engagement at PlatformCon attributable to increased external interest in the organisation's platform engineering capability.
Dampeners
Operating above senior scope in all dimensions; Platform Architect title is the correct role level.
Progression Signal
Promotion to Platform Architect is clear and overdue.
Business Impact
Impact
Enterprise platform architecture investments deliver strategic business resilience, security compliance, and engineering organisation productivity at scale.
External reputation built through speaking and community contribution creates talent attraction value for the engineering organisation.
Examples
Platform architecture investment case they presented led to a seven-figure infrastructure modernisation programme.
Dampeners
Operating at Platform Architect level of business impact; role level should reflect this.
Progression Signal
Promotion to Platform Architect resolves the role level mismatch; strategic impact expected to continue.
Level 5
Transformative
Low
Individual
Impact
Performing well beyond senior level - operating as a fully effective Platform Architect in all but title.
Enterprise platform strategy, cloud-native standards, and developer experience architecture are shaped with the depth and scope of a principal practitioner.
Builds platform engineering capability across the organisation in a way that creates lasting, structural improvements.
Examples
Defined the organisation's full platform technology radar, adopted by engineering leadership as the standard for technology decisions.
Platform engineering capability programme they led resulted in three internal promotions within the team over the year.
Dampeners
Exceptional at senior level; promotion to Platform Architect is the appropriate and urgent response.
Progression Signal
Promotion to Platform Architect should be imminent.
Business Impact
Impact
Delivering Platform Architect-level strategic business impact at senior engineer cost.
Platform technology radar and capability programme create lasting, compounding returns across the engineering organisation.
Examples
Technology radar adoption led to decommissioning three redundant tooling stacks, saving significant annual licensing and operational cost.
Dampeners
Exceptional at this level; promotion unlocks the full scope of strategic platform leadership.
Progression Signal
Post-promotion trajectory expected to continue at this level of strategic impact.
Mid
Individual
Impact
Anomalously strong for a senior platform engineer - their platform architecture and strategy contributions are genuinely enterprise-shaping.
Developer experience and reliability outcomes they drive are recognised at board and executive level as strategic business enablers.
Sets a standard for platform engineering across the industry, not just the organisation.
Examples
Cloud-native architecture they designed became an industry reference implementation presented at KubeCon.
DORA and developer experience programme produced outcomes cited by the CTO in the organisation's annual report.
Dampeners
This rating at senior level is rare; immediate promotion to Platform Architect is warranted.
Progression Signal
Promotion is overdue; delay creates significant retention risk for a top-quartile platform practitioner.
Business Impact
Impact
Business value delivered is at enterprise strategy level - far beyond the senior platform engineer scope.
Industry recognition creates talent attraction value and positions the organisation as a platform engineering leader.
Examples
Industry recognition of the platform engineering programme contributed to five senior engineering hires in the following six months.
Dampeners
Exceptional and should not persist at senior level; promotion should be immediate.
Progression Signal
Post-promotion, impact expected to operate at full enterprise strategic scope.
High
Individual
Impact
Performing at a level that makes their senior title irrelevant - they are a Platform Architect by impact, strategic scope, and organisational authority.
Every dimension of Platform Architect responsibility - cloud-native standards, security architecture, developer experience vision, technology selection - is being performed at the highest level.
Represents an extreme outlier in the senior platform engineering cohort.
Examples
Defined the enterprise cloud security architecture, gained regulatory body endorsement, and drove full implementation across all production environments.
Their platform engineering methodology was adopted as a case study by a major cloud provider.
Dampeners
Keeping this individual at senior level is a significant retention risk and an organisational failure.
Progression Signal
Immediate promotion to Platform Architect; the performance process has fundamentally failed to keep pace with this individual's contribution.
Business Impact
Impact
Delivering transformative enterprise business value that exceeds the Platform Architect scope in some dimensions.
Industry-level recognition creates competitive advantage for the organisation in technology and talent markets.
Examples
Cloud provider case study generated significant commercial interest and was referenced in the organisation's technology partnership announcement.
Dampeners
This situation reflects a systemic failure in the performance process; immediate action is required.
Progression Signal
Promotion to Platform Architect resolves the mismatch; continued growth at strategic scope expected.