Junior Platform Engineer – Growth Tracker

[ Name ] Junior Platform Engineer – Growth Tracker

JPE  ·  SFIA 2-3  ·  raganmcgill.co.uk

1Novice
No evidence of this yet · Lacks experience in this competency · Requires significant training and guidance
2Developing
Evidence of trying but lacking consistency · Demonstrates effort and initial attempts · Progressing, consistency is needed
3Proficient
Evidence of doing this with areas for improvement · Competent with some areas for enhancement · Meets most expectations
4Accomplished
Evidence of consistently meeting expectations · Highly reliable in delivering results · Maintains performance standards
5Expert
Evidence of exceeding expectations · Demonstrates exceptional mastery · Autonomous · Leads and mentors others
Learning & Growth
Delivery
Quality & Craft
Communication
Collaboration
Ownership
Technical Foundation
Learning & Growth
Actively seeks to deepen understanding of cloud infrastructure, Kubernetes operations, and CI/CD patterns.
Reflects on feedback from code reviews and applies lessons to subsequent work without being reminded.
Reads platform engineering literature, follows community discussions (e.g. CNCF), and brings relevant ideas back to the team.
Develops awareness of their own knowledge gaps and proactively raises them with their TTL or mentor.
Takes on moderately stretching tasks and uses them as development opportunities rather than defaulting to familiar approaches.
Builds understanding of the software engineering teams they serve - what they are building, what their delivery pressures are, what they need from the platform.
Delivery
Delivers well-defined platform tasks independently within agreed timeframes.
Manages their own task queue effectively - breaking down work, estimating effort, and flagging when estimates change.
Raises blockers promptly with enough context for a senior to help efficiently.
Keeps PRs reviewable - appropriately scoped, with clear descriptions, terraform plan output where relevant, and evidence of testing.
Responds to review feedback promptly and addresses it thoroughly before requesting re-review.
Tracks task status accurately so the team always has a clear picture of progress.
Maintains change safety discipline - planning before applying, reviewing diffs carefully, and never bypassing the review process.
Quality & Craft
Writes IaC and pipeline configuration that is clean, readable, and follows team conventions without needing to be reminded.
Applies appropriate security and operational standards to all infrastructure work - encryption, least-privilege IAM, appropriate tagging.
Reviews own work critically before submitting - checking for missing dependencies, security concerns, and unintended side effects.
Writes clear documentation and runbook entries for platform components they build or modify.
Identifies and flags technical debt encountered during delivery work, even when not expected to resolve it immediately.
Develops growing instinct for blast radius - understanding the scope of impact of any given infrastructure change.
Communication
Provides clear, specific stand-up updates that give teammates a genuine picture of progress and blockers.
Writes PR descriptions that explain what infrastructure is changing, why, and how reviewers can verify correctness.
Communicates platform concerns clearly to senior engineers - with evidence from logs, metrics, or plan output.
Asks focused, well-formed questions that show prior investigation rather than asking before attempting.
Documents decisions and assumptions in IaC and runbooks so future engineers understand the reasoning.
Gives constructive, specific feedback in code reviews on peers' work.
Collaboration
Builds effective working relationships with software engineering teams - understanding their workflow and acting on developer experience feedback.
Contributes constructively to team ceremonies - retrospectives, planning, and technical discussions.
Offers meaningful code review feedback to graduate engineers, balancing rigour with encouragement.
Shares knowledge with teammates - useful debugging patterns, operational tips, lessons from incidents - without being asked.
Works openly rather than siloing work in progress - makes it easy for others to see and assist.
Engages with incident response constructively - contributing to investigation and learning from post-incident reviews.
Ownership
Takes full responsibility for completing tasks they have committed to, including follow-through on review actions.
Flags uncertainty about infrastructure requirements or constraints early rather than making assumptions.
Monitors platform components they have built or modified after deployment - not just during development.
Proactively investigates alerts in their area of responsibility rather than waiting to be assigned.
Owns their own learning progression and actively manages it, seeking feedback and opportunities.
Acknowledges mistakes clearly, investigates root causes, and shares learnings with the team.
Technical Foundation
Demonstrates working Terraform and CI/CD proficiency in all delivered work.
Applies security best practices consistently to infrastructure work - IAM, encryption, network controls.
Operates Kubernetes confidently at a day-to-day level - deploying workloads, diagnosing failures, managing resources.
Uses the team's observability stack effectively - writing alert rules, reading dashboards, and using logs and metrics to diagnose issues.
Understands cloud networking well enough to reason about connectivity, security group rules, and routing.
Maintains working knowledge of the team's deployment and release patterns, including rollback procedures.
Understands the developer experience the platform provides and actively uses that understanding to prioritise improvements.
Evidence & examples
Evidence & examples
Evidence & examples
Evidence & examples
Evidence & examples
Evidence & examples
Evidence & examples

Strengths to recognise

Development focus areas

Overall assessment & agreed actions

raganmcgill.co.uk  ·  Junior Platform Engineer Growth Tracker