Fill in the fields below, then save as PDF or print at A2 landscape.
Role
Intermediate Platform Engineer
Level 1
Unsatisfactory
Low
Individual
Impact
Fails to design and deliver platform components independently despite having clear ownership and access to senior guidance.
Produces Terraform modules and Kubernetes configurations that do not meet the team's quality, security, or observability standards and require significant rework.
Does not fulfil mentoring responsibilities to graduate and junior engineers; pairing sessions are cancelled or unstructured.
Examples
Delivered a Kubernetes workload configuration that had no resource limits, no liveness probes, and no associated runbook after three weeks of ownership.
Cancelled four scheduled pairing sessions with a junior engineer in a single month without rescheduling.
Dampeners
Was given ambiguous ownership boundaries and insufficient context about the expected quality standard for this role level.
Progression Signal
Begins delivering platform components that meet the team's quality checklist without senior correction.
Resumes structured mentoring sessions with junior engineers on a consistent schedule.
Business Impact
Impact
Senior engineer time is consumed correcting intermediate-level work rather than advancing platform architecture.
Platform components delivered below the quality standard increase operational burden and reliability risk for engineering teams.
Examples
A Kubernetes workload without resource limits caused a node memory exhaustion incident affecting three co-located services.
Dampeners
Incident was contained at non-production; learning opportunity identified and documented.
Progression Signal
Platform components begin landing with correct observability, resource management, and documentation, reducing operational risk.
Mid
Individual
Impact
Designs platform components with significant gaps in observability, security, or operational runbook coverage that require senior engineer correction.
Incident investigations are surface-level; escalates to senior engineers without attempting structured root cause analysis.
Developer experience work is reactive; does not proactively seek feedback from engineering teams or identify friction points.
Examples
Delivered an IaC module for a new cloud service with no SLO definition, no alerting configuration, and no runbook.
Escalated a Kubernetes scheduling failure to a senior engineer after a single kubectl describe without reviewing events, logs, or node conditions.
Dampeners
Working across a newly unfamiliar cloud platform area; knowledge gaps may be contributing to quality shortfall.
Progression Signal
Begins including observability and runbook coverage as a default part of platform component delivery.
Attempts more thorough incident investigation before escalating - reviewing events, logs, and metrics.
Business Impact
Impact
Platform components without SLOs and alerting leave engineering teams without visibility into service health, increasing MTTR.
Frequent escalation to senior engineers for incident investigation reduces the team's ability to handle concurrent incidents.
Examples
Three platform components delivered without alerting required a retroactive observability sprint to bring them to the expected standard.
Dampeners
The retroactive work was completed without production impact; the pattern is the concern.
Progression Signal
New platform components begin landing with SLOs, alerting, and runbooks as a default, reducing retroactive work overhead.
High
Individual
Impact
Consistently resistant to feedback on design decisions; the same architectural weaknesses - missing reliability patterns, overly broad IAM scopes - recur across multiple pieces of work.
Mentoring of junior engineers is perfunctory; feedback is generic rather than specific and educational.
Creates friction in design reviews through defensiveness or dismissal of well-reasoned alternative approaches.
Examples
Received the same feedback about missing error budget tracking in SLO design across four consecutive reviews with no change.
Junior engineer's post-pairing retrospective described the sessions as 'not useful' due to vague, non-specific guidance.
Dampeners
Structural or interpersonal issues within the team may be contributing to the resistance pattern.
Progression Signal
Engages constructively with design feedback and demonstrates genuine design improvement in one delivery cycle.
Business Impact
Impact
Repeated quality gaps in platform components compound reliability risk across the engineering estate.
Poor mentoring quality reduces the team's ability to grow junior engineers' platform capability at the expected rate.
Examples
Junior engineers' Terraform quality plateau was directly linked to the lack of specific, actionable feedback from their assigned mentor.
Dampeners
The team's overall quality has not significantly degraded; the risk is in trajectory rather than immediate impact.
Progression Signal
Mentoring quality improves to the point where junior engineers' platform skills show measurable development.
Level 2
Development Needed
Low
Individual
Impact
Delivers platform components independently but with gaps in security hardening, observability coverage, or operational documentation.
Mentors junior engineers but sessions lack structure; feedback is inconsistently specific or actionable.
Contributes to technical discussions but does not yet propose design alternatives backed by clear trade-off reasoning.
Examples
Delivered a Kubernetes namespace configuration without network policies, requiring a retroactive security review before the service could move to production.
Pairing sessions with a junior engineer were unstructured and relied on ad hoc questions rather than a deliberate teaching plan.
Dampeners
Growing into the full scope of the intermediate role; depth in security hardening and mentoring craft is still developing.
Progression Signal
Begins including network policies and security hardening as a default in Kubernetes component delivery.
Structures pairing sessions around specific learning goals and provides targeted, actionable feedback.
Business Impact
Impact
Security and observability gaps in delivered platform components require retroactive work that adds friction to engineering team delivery timelines.
Junior engineers' growth rate is slower than it should be given the mentoring investment being made.
Examples
Two platform components required security remediation before production sign-off, adding an average of five days to delivery timelines.
Dampeners
Retroactive work was completed without production incidents; pattern needs addressing before it scales.
Progression Signal
Security and observability coverage becomes consistent in delivery; junior engineer growth rate improves.
Mid
Individual
Impact
Delivers well but operates primarily within their technical comfort zone - CI/CD and basic Kubernetes - and does not drive improvements in reliability or developer experience.
SLO definitions are present but not connected to error budget management or reliability-driven prioritisation decisions.
Identifies platform technical debt but does not propose or drive structured remediation.
Examples
Defined SLOs for a platform component but never used them to make a prioritisation decision or discuss an error budget position with the team.
Flagged three instances of fragile Terraform state management across the codebase but raised no proposal to address them.
Dampeners
Reliable delivery is genuinely valuable; the gap is in converting technical depth into platform-wide improvement.
Progression Signal
Begins using SLO data to make a concrete reliability prioritisation recommendation to the team.
Proposes a structured remediation plan for identified platform technical debt.
Business Impact
Impact
Platform reliability improvements are slow despite SLO tooling being in place, because data is not being used to drive decisions.
Unaddressed technical debt in IaC state management continues to accumulate, increasing the risk of future incidents.
Examples
The team's error budget was consumed by a fragile state management issue that had been identified but not addressed three months earlier.
Dampeners
The incident was resolved without production impact; the process gap is the primary concern.
Progression Signal
SLO data begins driving reliability conversations in planning, and one technical debt item moves from flagged to resolved.
High
Individual
Impact
Delivers well but is not growing into the broader scope of the intermediate role - developer experience leadership, reliability advocacy, and platform architectural contribution.
Does not engage with engineering teams to understand their platform pain points or gather developer experience feedback.
Feedback from senior engineers on design decisions is acted on locally but not used to develop improved design instincts.
Examples
Twelve months in and still requires a senior engineer to prompt all developer experience investigation and reliability improvement work.
Has not spoken directly with a software engineering team about their platform experience despite owning the primary component they use.
Dampeners
May need a more explicit expectation-setting conversation about the full scope of the intermediate role.
Progression Signal
Initiates one developer experience feedback conversation with an engineering team and acts on what they learn.
Business Impact
Impact
Platform developer experience and reliability improvements are dependent on senior engineer direction rather than intermediate-level initiative.
Growth trajectory below expectation for tenure creates uncertainty about the return on investment at this role level.
Examples
All platform DX improvements in the past two quarters were initiated by the senior platform engineer rather than owned from the intermediate level.
Dampeners
Delivery quality remains high; the gap is in scope of initiative rather than execution capability.
Progression Signal
Begins initiating one platform improvement per quarter without senior engineer prompting.
Level 3
Consistently Delivers
Low
Individual
Impact
Designs and delivers platform components independently - CI/CD pipelines, Kubernetes configurations, IaC modules - meeting the team's quality, security, and observability standards.
Provides structured, specific, and educational code review feedback to junior and graduate engineers.
Investigates platform incidents thoroughly using metrics, logs, and traces before escalating, and contributes to post-mortem quality.
Examples
Designed and delivered a reusable Terraform module for standardised RDS configuration, complete with encryption, backups, alerting, and runbook.
Led a Kubernetes pod scheduling incident investigation, using Prometheus metrics and Kubernetes events to identify a node affinity misconfiguration independently.
Dampeners
Working well within defined domain; not yet designing platform components that span multiple infrastructure domains.
Progression Signal
Begins proposing platform improvements that span CI/CD, Kubernetes, and observability - not just working within one area.
Business Impact
Impact
Platform components delivered to production quality standard reduce operational burden and improve reliability for engineering teams.
Mentoring quality compounds the team's platform engineering capability, creating a multiplier effect on delivery capacity.
Examples
Kubernetes network policy standard eliminated four inter-service connectivity incidents over the two months following adoption.
Dampeners
Impact is growing across multiple engineering teams; not yet organisation-wide.
Progression Signal
Begins contributing to platform improvements with organisation-wide reach - affecting all teams building on the platform.
Level 4
Leading
Low
Individual
Impact
Delivers independently and is driving meaningful platform improvement initiatives that reduce developer friction across multiple engineering teams.
Mentors junior and graduate engineers at a level that accelerates their growth and builds genuine platform engineering depth.
Contributes substantively to platform architecture reviews, identifying failure modes and proposing well-reasoned alternatives.
Examples
Designed and led a CI/CD pipeline standardisation initiative adopted by six engineering teams, reducing build configuration complexity significantly.
Junior engineer mentored over two quarters grew to independently own a Kubernetes service area without support.
Dampeners
Leadership scope is still primarily within the platform team; cross-organisational platform influence is emerging.
Progression Signal
Is increasingly sought out by senior platform engineers for design review input on complex platform work.
Business Impact
Impact
CI/CD and platform standardisation improvements deliver measurable gains in deployment frequency and engineering team autonomy.
Mentoring quality compounds the platform team's capability, reducing reliance on senior engineers for Kubernetes and IaC depth.
Examples
CI/CD standardisation reduced new service onboarding time from three days to four hours across adopting teams.
Dampeners
Impact is significant within adopting teams; organisation-wide adoption is growing.
Progression Signal
Platform improvements begin achieving full organisation-wide adoption and impact.
Mid
Individual
Impact
Consistently delivers platform improvements with cross-team reach and is beginning to shape the platform engineering discipline within the organisation.
Developer experience improvements they lead are data-driven and produce measurable outcomes - DORA metrics, deployment frequency, change failure rate.
Is a credible technical voice in reliability and platform architecture discussions beyond their immediate team.
Examples
Designed and delivered an internal developer platform golden path for microservice deployment, adopted by all engineering teams within three months.
SLO and error budget framework they established is now used to prioritise reliability work across the full platform estate.
Dampeners
Beginning to operate at senior platform engineer level; a formal promotion review is appropriate.
Progression Signal
Conversation should be about promotion timeline to senior platform engineer.
Business Impact
Impact
Golden path and platform standardisation work delivers organisation-wide developer experience improvements.
SLO framework improves the organisation's ability to make evidence-based reliability investment decisions.
Examples
Golden path adoption reduced deployment-related incidents by 40% across participating teams in the quarter following launch.
Dampeners
Impact is significant and cross-cutting; scope is approaching senior platform engineer level.
Progression Signal
Promotion to senior platform engineer is the appropriate next step to match scope of contribution.
High
Individual
Impact
Operating at the ceiling of what an intermediate role can deliver - performing at senior platform engineer level in impact and technical scope.
Drives platform reliability and developer experience improvements with clear, measurable, organisation-wide outcomes.
Sets a technical quality standard for platform engineering that other engineers in the organisation reference.
Examples
Led the design of the organisation's observability platform, standardising on OpenTelemetry across all engineering teams.
Proactively identified and drove remediation of a systemic IaC security pattern that had created compliance risk across 30 cloud accounts.
Dampeners
Operating above intermediate scope; the promotion case is clear and compelling.
Progression Signal
Promotion to senior platform engineer is overdue; delay risks disengagement.
Business Impact
Impact
Organisation-wide observability and IaC security improvements deliver material reductions in incident rate and compliance risk.
Their technical leadership is recognised by engineering teams across the organisation as a driver of platform quality.
Examples
Observability standardisation reduced mean time to detect platform incidents by 60% across all production services.
Dampeners
Impact ceiling at intermediate level; promotion unlocks the organisational scope for continued growth.
Progression Signal
Immediate promotion to senior platform engineer; the role level is the constraint on this individual's impact.
Level 5
Transformative
Low
Individual
Impact
Performing well beyond intermediate level - operating as a capable senior platform engineer in all but title.
Drives platform architecture decisions and reliability improvements with organisation-wide scope and measurable outcomes.
Mentors multiple junior engineers to the point of full independence, compounding the team's platform capability.
Examples
Independently designed the organisation's multi-environment Terraform state architecture, adopted across all cloud accounts.
Two junior engineers mentored by this individual were promoted to intermediate in the same review cycle.
Dampeners
Exceptional at intermediate level but bounded by role scope; promotion unlocks further strategic platform contribution.
Progression Signal
Promotion to senior platform engineer should be imminent.
Business Impact
Impact
Delivering senior platform engineer impact at intermediate cost - a significant return on investment.
Platform architecture and reliability improvements have measurable, organisation-wide effect on engineering delivery capability.
Examples
Multi-environment state architecture eliminated a class of Terraform state conflict incidents that had been affecting the team for a year.
Dampeners
Exceptional contribution at this level; promotion is the correct response.
Progression Signal
Post-promotion trajectory expected to continue at pace.
Mid
Individual
Impact
Anomalously strong for an intermediate platform engineer - operating at full senior level in platform architecture and reliability engineering.
Drives cross-cutting platform improvements that reshape how engineering teams build and operate services on the platform.
Sets a technical leadership example that raises the bar for the entire intermediate and junior cohort.
Examples
Designed and drove adoption of a GitOps platform standard across all engineering teams, replacing an inconsistent patchwork of deployment patterns.
Led the organisation's first GameDay exercise, identifying and remediating six platform reliability risks before they caused production incidents.
Dampeners
This rating at intermediate level is rare; immediate promotion review is warranted.
Progression Signal
Promotion to senior platform engineer is overdue; further delay creates significant retention risk.
Business Impact
Impact
GitOps standardisation and reliability engineering contributions deliver transformative improvements to engineering team delivery confidence.
Business value delivered is disproportionate to the intermediate role level.
Examples
GitOps adoption reduced deployment-related production incidents by 55% in the quarter following full rollout.
Dampeners
Exceptional and should not persist at intermediate level; promotion is urgent.
Progression Signal
Post-promotion, impact trajectory expected to accelerate into strategic platform leadership.
High
Individual
Impact
Performing at a level that makes their intermediate title irrelevant - a senior platform engineer by impact, scope, and technical authority.
Shapes platform architecture across the organisation with the confidence and rigour of a senior practitioner.
Represents an extreme outlier in the intermediate cohort.
Examples
Authored the organisation's cloud security architecture standard, adopted by all engineering teams and approved by the CISO.
IaC and Kubernetes review contributions are of a quality that senior platform engineers cite as reference implementations.
Dampeners
Keeping this individual at intermediate level is a significant retention risk and a failure of the performance process.
Progression Signal
Immediate promotion to senior platform engineer; the performance process has failed to keep pace with this individual's growth.
Business Impact
Impact
Delivering senior-level business value at intermediate cost - an exceptional return on investment.
Recognised across the engineering organisation and beyond their team as a leading platform practitioner.
Examples
Cloud security architecture standard they authored resolved a SOC 2 audit finding and was cited as a model by the external auditor.
Dampeners
This situation reflects a performance process failure; promotion action must be immediate.
Progression Signal
Promotion resolves the mismatch; strategic platform leadership expected post-promotion.