Fill in the fields below, then save as PDF or print at A2 landscape.
Role
Junior Platform Engineer
Level 1
Unsatisfactory
Low
Individual
Impact
Fails to complete well-defined CI/CD or Terraform tasks independently despite clear direction and available examples.
Applies infrastructure changes without reviewing the Terraform plan output or checking for unintended resource modifications.
Does not investigate pipeline failures; restarts jobs without understanding the root cause or updating the team.
Examples
Assigned a clearly scoped GitHub Actions pipeline task with a reference implementation; produced nothing reviewable after three weeks.
Applied a Terraform change that modified a shared security group rule without reviewing the plan diff or flagging the blast radius.
Dampeners
Was given insufficient context about the platform architecture and change safety expectations during onboarding.
Facing a significantly more complex toolchain than their previous experience covered.
Progression Signal
Begins reviewing Terraform plan output before applying and flags unexpected resource changes to a senior engineer.
Completes a well-defined pipeline task end-to-end with minimal guidance.
Business Impact
Impact
Unreviewed infrastructure changes introduce reliability risk and undermine the team's change safety posture.
Incomplete delivery stalls platform improvements that engineering teams are depending on.
Examples
An unreviewed security group change blocked connectivity for a dependent engineering team for four hours.
Dampeners
Impact reflects a gap in onboarding rigour around change safety as much as individual capability.
Progression Signal
Change safety discipline improves; infrastructure modifications are reviewed and flagged appropriately before applying.
Mid
Individual
Impact
Completes some tasks but IaC quality consistently falls below the team's standards - missing encryption, incorrect module structure, absent documentation.
Struggles to diagnose pipeline or Kubernetes failures without being walked through the investigation by a senior engineer.
Limited engagement in code review; provides no substantive feedback on others' IaC or pipeline work.
Examples
Submitted five Terraform PRs across two sprints, all missing the required resource tagging module and encryption configuration.
Escalated every Kubernetes pod failure to a senior engineer without attempting any kubectl-based investigation first.
Dampeners
Recently promoted from graduate; some patterns may reflect habits from a less rigorous prior environment.
Progression Signal
Begins applying the team's IaC quality checklist consistently before raising PRs.
Attempts basic Kubernetes investigation using kubectl logs and describe before escalating.
Business Impact
Impact
Rework overhead on senior engineers persists beyond what is expected for a junior platform engineer at this tenure.
Platform components delivered without encryption or correct tagging create compliance and cost allocation problems.
Examples
Two Terraform modules required complete rewrites by a senior engineer due to missing encryption and incorrect state configuration.
Dampeners
Business impact is containable at current scope; risk grows if the pattern persists.
Progression Signal
IaC quality improves measurably; PRs begin landing with correct encryption, tagging, and module structure.
High
Individual
Impact
Resistant to feedback on IaC security practices; the same IAM and encryption issues recur across multiple review cycles.
Shows no initiative to improve CI/CD pipeline reliability or developer experience beyond the minimum required.
Creates friction in the team through disengagement during pairing sessions or dismissiveness toward code review feedback.
Examples
Received the same least-privilege IAM comment across six consecutive Terraform PRs with no change in approach.
Declined all pairing sessions offered on Kubernetes administration over a four-week period.
Dampeners
External factors or personal circumstances may be contributing; this should be explored in a structured conversation.
Progression Signal
Engages constructively with one review cycle and demonstrates genuine change in IaC security approach.
Business Impact
Impact
Sustained quality issues in platform components increase reliability and security risk for engineering teams using them.
Ongoing senior engineer intervention to correct IaC diverts capacity from higher-value platform work.
Examples
Senior platform engineer spent 25% of their capacity over six weeks managing and correcting this individual's infrastructure output.
Dampeners
Impact remains at team level; no production incidents attributable at this stage.
Progression Signal
Senior engineer correction overhead drops as the individual begins to self-review and address quality issues independently.
Level 2
Development Needed
Low
Individual
Impact
Delivers well-defined CI/CD and Terraform tasks but requires close direction on each; cannot yet adapt patterns to new contexts independently.
IaC quality is uneven - security settings inconsistently applied, documentation missing, module conventions not always followed.
Investigates pipeline and Kubernetes failures reactively when prompted but does not monitor proactively.
Examples
Built a GitHub Actions pipeline following a template step-by-step but could not adapt the caching strategy for a different project without guidance.
Missed adding a Kubernetes resource limit that was documented as a team standard in the platform runbook.
Dampeners
Six months into their first platform engineering role; breadth across the stack is still developing.
Progression Signal
Begins adapting known IaC and pipeline patterns to new contexts with decreasing prompting.
Business Impact
Impact
Work delivers value but at a higher review overhead than expected for the role level and tenure.
Gaps in IaC quality standards require catch-up correction that adds friction to the team's delivery process.
Examples
Each Terraform PR averaged 2.5 review rounds before meeting the team's quality bar.
Dampeners
Typical for this tenure; trajectory of improvement is the key signal.
Progression Signal
Review round count drops as quality standards are internalised and applied consistently.
Mid
Individual
Impact
Delivers assigned platform work but struggles to understand and articulate the developer experience implications of their decisions.
Observability work is surface-level - adds alerts when asked but does not consider whether thresholds are meaningful or runbooks are actionable.
Feedback from reviews is acted on locally but not generalised to improve the standard of subsequent work.
Examples
Added a Prometheus alert with a threshold copied from an example without verifying it against actual workload baseline behaviour.
Fixed a Terraform module variable issue in the current PR but introduced the same structural issue in the next one.
Dampeners
Platform engineering depth takes time to develop; uneven quality may reflect knowledge gaps rather than disengagement.
Progression Signal
Begins asking whether alert thresholds are meaningful and whether runbooks provide genuinely actionable steps.
Business Impact
Impact
Observability gaps in platform components make it harder for engineering teams to confidently operate services built on them.
Repeated feedback cycles consume senior engineer time that could be directed at higher-value architecture work.
Examples
A miscalibrated alert added to a shared platform component triggered 40 false-positive pages over a week, disrupting on-call rotations.
Dampeners
The false-positive alert was caught before impacting production workloads; the learning opportunity has been identified.
Progression Signal
Observability work begins to reflect genuine understanding of workload behaviour and operational usability.
High
Individual
Impact
Delivers work but avoids unfamiliar areas of the platform - tends to pick tasks in known CI/CD territory and avoids Kubernetes or cloud networking work.
Does not proactively investigate the developer experience the platform provides; waits to be directed toward specific improvements.
Feedback is received passively; growth in IaC depth and Kubernetes administration is slower than expected for tenure.
Examples
Consistently picks CI/CD pipeline tasks in sprint planning and avoids Kubernetes and Terraform tasks that would build breadth.
Nine months in and still requires senior guidance for routine Kubernetes workload management tasks.
Dampeners
May be lacking confidence in Kubernetes and cloud networking rather than motivation; targeted pairing may unlock progress.
Progression Signal
Takes on one Kubernetes or Terraform task outside their comfort zone and completes it with structured support.
Business Impact
Impact
Breadth gap in Kubernetes and IaC limits the team's ability to distribute platform work across the team effectively.
Slow growth trajectory creates uncertainty about the timeline to full junior-level independence.
Examples
Team planning consistently required a senior engineer to absorb all Kubernetes and Terraform tasks due to this individual's avoidance.
Dampeners
Business impact remains manageable; risk is in sustained pattern limiting team capacity distribution.
Progression Signal
Begins picking up Kubernetes and cloud networking tasks and delivering them with decreasing support.
Level 3
Consistently Delivers
Low
Individual
Impact
Delivers well-defined CI/CD, Terraform, and basic Kubernetes tasks independently with consistent quality.
Applies the team's IaC standards - encryption, least-privilege IAM, resource tagging, module structure - without needing reminders.
Investigates pipeline failures and Kubernetes pod issues with basic kubectl operations before escalating.
Examples
Delivered four GitHub Actions pipeline improvements across the sprint, each merging after a single review round.
Diagnosed a Kubernetes CrashLoopBackOff independently using kubectl logs and describe before resolving with a senior engineer.
Dampeners
Working well within defined scope; not yet designing platform components independently or proposing improvements.
Progression Signal
Begins proposing small platform improvements based on developer experience feedback without being prompted.
Business Impact
Impact
Reliable contribution to sprint velocity within the scope of junior-level platform work.
Self-sufficient on routine CI/CD and IaC tasks reduces senior engineer load and frees capacity for architecture work.
Examples
Delivered 100% of assigned platform tickets across three consecutive sprints with no senior correction required.
Dampeners
Contribution scope is still defined by others; business impact is predictable but bounded.
Progression Signal
Begins taking on platform tasks outside their immediate comfort zone and delivering them reliably.
Mid
Individual
Impact
Reliably delivers assigned platform work and is starting to contribute developer experience observations to team discussions.
Provides helpful, specific code review feedback on graduate and fellow junior engineers' IaC and pipeline work.
Develops and updates runbook entries for platform components they build or modify as a consistent habit.
Examples
Identified a missing resource dependency in a teammate's Terraform PR that would have caused a deployment ordering failure.
Wrote a detailed runbook for a new monitoring alert they added, including investigation steps and escalation criteria.
Dampeners
Still dependent on direction for task selection; not yet proactively identifying or proposing platform improvements.
Progression Signal
Starts identifying platform friction points from developer experience feedback and proposing small targeted improvements.
Business Impact
Impact
Reliable delivery and growing review contribution improve the team's collective platform quality and delivery pace.
Runbook quality improvements reduce incident investigation time for the on-call engineer.
Examples
Runbook they wrote for a new alert was used by another engineer to resolve a platform incident independently without escalation.
Dampeners
Impact still primarily within the platform team; cross-team contribution to developer experience not yet established.
Progression Signal
Begins contributing platform improvements that directly benefit engineering teams using the platform.
High
Individual
Impact
Delivers reliably and is self-directing learning toward deeper Kubernetes administration and observability stack knowledge.
Seeks out stretch CI/CD design and Terraform module tasks and handles them with appropriate support from a senior engineer.
Applies review feedback quickly and generalises it to subsequent work, showing accelerating quality improvement.
Examples
Identified a gap in their Kubernetes RBAC knowledge, worked through the documentation independently, and applied it correctly in the next sprint.
Volunteered to own the migration of a CI/CD pipeline to a new runner architecture and delivered it with one design review.
Dampeners
Still operating within defined scope; not yet leading platform component design decisions independently.
Progression Signal
Begins contributing technical design proposals for small platform improvements in planning or design sessions.
Business Impact
Impact
Reliable delivery and growing independence reduce senior engineer overhead and increase the team's effective delivery capacity.
Self-directed growth means the platform team gains increasing value from this individual's broadening skill set.
Examples
Senior engineer noted their mentoring time for this individual had halved compared to the previous quarter, freeing 20% more capacity.
Dampeners
Business impact still primarily within the platform team; cross-team impact on developer experience growing but not yet established.
Progression Signal
Contributes platform improvements that reduce friction for engineering teams, extending impact beyond the team boundary.
Level 4
Leading
Low
Individual
Impact
Delivers reliably and begins supporting graduate engineers through IaC, pipeline, and Kubernetes challenges informally.
Contributes well-reasoned perspectives in platform design discussions, backed by evidence from prior delivery work.
Takes ownership of small platform improvement workstreams without needing the scope fully defined upfront.
Examples
Helped a graduate engineer through a Terraform state locking issue without involving a senior engineer.
Proposed and implemented a CI/CD caching improvement that reduced average build time by 15%.
Dampeners
Platform technical leadership is informal and emerging; not yet a consistent multiplier on team delivery.
Progression Signal
Is sought out by graduates and peers for IaC and pipeline guidance, signalling growing technical credibility.
Business Impact
Impact
Beginning to have a multiplier effect - delivery and behaviours lift the output of graduates around them.
Reduction in graduate dependency on senior engineers creates bandwidth for higher-complexity platform work.
Examples
Fielded graduate IaC questions for three weeks, freeing the senior platform engineer to focus on a critical Kubernetes upgrade.
Dampeners
Scope of multiplier effect is still narrow - immediate team only.
Progression Signal
Multiplier effect grows as informal platform leadership becomes consistent across IaC, CI/CD, and Kubernetes knowledge areas.
Mid
Individual
Impact
Consistently delivers and actively improves team platform practices - IaC module documentation, pipeline standards, observability runbooks.
Is a trusted resource for graduates on CI/CD and basic Kubernetes operations and handles the mentoring role with care.
Brings a platform engineering growth mindset that elevates the team's collective approach to quality and developer experience.
Examples
Rewrote the team's Terraform module documentation guide, reducing the time for new joiners to make their first contribution.
Ran an informal knowledge-sharing session on Kubernetes readiness and liveness probe configuration patterns.
Dampeners
Still at junior level - depth in advanced Kubernetes administration and cloud architecture is developing.
Progression Signal
Described by peers and graduates as someone who actively makes the platform team better.
Business Impact
Impact
Contribution goes beyond delivery - actively improving team knowledge quality and platform documentation.
Platform documentation improvements reduce onboarding time and incident investigation overhead.
Examples
IaC documentation improvements they produced reduced new joiner ramp-up time by an estimated 25%.
Dampeners
Impact is still primarily within the platform team boundary.
Progression Signal
Impact begins to extend to engineering teams using the platform, through better developer experience documentation.
High
Individual
Impact
Operating at the ceiling of what a junior platform engineer role can deliver - a clear candidate for promotion to intermediate.
Proactively identifies platform reliability or developer experience gaps and drives improvements without being directed.
A visible positive force on platform quality, IaC standards, and the team's CI/CD engineering culture.
Examples
Proposed and led an improvement to the team's Kubernetes deployment standard that reduced common misconfiguration in engineering team workloads.
Consistently volunteers for stretch platform work - observability stack improvements, Terraform module refactoring - and delivers it reliably.
Dampeners
Still operating within junior-scoped context; influence on cloud architecture and platform strategy decisions is bounded.
Progression Signal
Conversation should be about promotion timeline to intermediate platform engineer, not further development at this level.
Business Impact
Impact
Delivering at a level that clearly justifies progression to intermediate platform engineer.
Platform improvements they initiate and deliver have a measurable positive impact on engineering team delivery speed.
Examples
Deployment standard improvement reduced misconfiguration-related incidents across four engineering teams over the subsequent quarter.
Dampeners
Impact ceiling at junior level; promotion unlocks the scope needed for further significant contribution.
Progression Signal
Promotion case is clear; delay risks disengagement from an individual performing above their role level.
Level 5
Transformative
Low
Individual
Impact
Performing well beyond junior level in platform delivery, Kubernetes knowledge, and team contribution.
Has independently driven IaC module improvements or observability enhancements that are now embedded in the team's standards.
Provides substantive mentoring to graduate engineers on CI/CD and Kubernetes fundamentals, reducing senior engineer dependency.
Examples
Designed and delivered a reusable Terraform module for standardised VPC configuration that eliminated a recurring class of networking misconfiguration.
Mentored three graduates through their first Kubernetes deployment tasks with no involvement from senior engineers.
Dampeners
Impact, however exceptional, is scoped by the junior role level; promotion is the appropriate response.
Progression Signal
Promotion to intermediate platform engineer should be imminent; this level of performance should not persist at junior for long.
Business Impact
Impact
Delivering impact more typical of an intermediate platform engineer.
IaC and pipeline contributions have a measurable positive effect on platform quality and engineering team delivery reliability.
Examples
The VPC Terraform module they designed reduced networking misconfiguration incidents across five engineering teams.
Dampeners
Exceptional at junior level but bounded; promotion unlocks the scope for further impact.
Progression Signal
Post-promotion growth trajectory expected to continue and accelerate.
Mid
Individual
Impact
Anomalously strong for a junior platform engineer - operating as a capable intermediate in Kubernetes operations and IaC design.
Contributes to cross-team platform discussions on CI/CD and Kubernetes standards with credibility and good engineering instincts.
Sets a standard that raises the bar for the junior cohort as a whole.
Examples
Led the design of a shared Kubernetes namespace isolation pattern adopted by three engineering teams.
Independently delivered a complete observability stack configuration for a new platform component with no escalation.
Dampeners
This rating at junior level is rare and should prompt immediate promotion review.
Progression Signal
Promotion is overdue; further delay is a retention risk.
Business Impact
Impact
Business value delivered is disproportionate to the junior role level.
Cross-team platform contributions create engineering value beyond the platform team boundary.
Examples
Kubernetes isolation pattern they designed reduced cross-team service interference incidents to zero over the following quarter.
Dampeners
Exceptional and should not persist at this level; promotion should be the priority.
Progression Signal
Post-promotion, impact trajectory expected to accelerate significantly.
High
Individual
Impact
Performing at a level that makes their junior title effectively irrelevant - they are an intermediate platform engineer by impact and technical depth.
Technical contributions to Kubernetes administration, IaC design, and CI/CD reliability rival those of intermediate engineers on the team.
Represents an extreme outlier in the junior platform engineering cohort.
Examples
Designed and delivered an end-to-end Kubernetes multi-tenancy pattern with RBAC and network policies that was adopted across the organisation.
IaC quality and Kubernetes review contributions are indistinguishable from intermediate platform engineers on the team.
Dampeners
Keeping this individual at junior level is a significant retention risk and a failure of the performance process.
Progression Signal
Immediate promotion to intermediate platform engineer; the performance system has not kept pace with this individual's growth.
Business Impact
Impact
Delivering outsized business value for a junior-level cost - effectively a force multiplier on platform team capacity.
Recognised beyond the platform team as an exceptional contributor to platform engineering quality.
Examples
Cited by multiple engineering team leads as having materially improved their deployment reliability through platform improvements.
Dampeners
This situation reflects a performance process failure; promotion action should be immediate.
Progression Signal
Promotion resolves the mismatch; accelerating growth trajectory expected post-promotion.