Platform Engineer, Opus 2

• Generalist breadth. You’re not blocked by “that’s not my layer” when a problem spans a service, its pipeline, and the infrastructure underneath it
• Depth starting to form. A stronger area is developing (Kubernetes, AWS, CI/CD, infrastructure as code, observability), the one colleagues start coming to you for. By the upper end of this band, that’s noticeable
• Ownership of the work you commit to. Outcomes, not just output. You finish what you start, and ambiguity is something you push through rather than something that stalls you
• Pragmatism. You favour simple, testable solutions, and you ask for help when complexity gets ahead of you
• A user mindset about platform. Your users are engineers. You care whether they can genuinely self-serve, and you write the documentation that lets them
• Coaching the level below. You answer questions clearly. You give review feedback that grows people rather than feedback that’s just correct
• Change disposition. You treat change in tools and ways of working as part of the job. You learn fast and bring it back to the team

Desirable

• You’ve found your footing. You can deliver infrastructure and tooling work with timely guidance, you’re starting to see how the platform fits together as a system, and you’re getting a feel for which choices hold up under load
• That’s the moment we want you in. You’ll join the team that makes it possible for every squad at Opus 2 to build, ship, and operate their own services, and the AI shift in software is something you’ll be living and shaping, not just reading about
• You can grow toward Senior and beyond. Internal progression is the default at Opus 2, and we hire externally only when there is no internal alternative
• Deliver well-scoped platform work end-to-end. Small to mid-size pieces of infrastructure, tooling, or pipeline work with timely guidance. You break it down, ship in slices, and see it land for the engineers who use it
• Build tooling that makes engineers faster. Automation over manual steps, paved paths over access requests and tribal knowledge
• Work on our CI/CD pipelines. GitHub Actions and ArgoCD, kept fast, reliable, and understandable by the squads that depend on them
• Contribute to architecture and design conversations with the development squads. Ask the questions that surface tradeoffs on scalability, reliability, and security early
• Help keep the platform observable. Dashboards, alerting, and instrumentation in Grafana Cloud that give an a fighting chance
• Take part in security and cost reviews. Spot what looks off against best practice, raise it, and pick up your share of the remediation
• Pull others up while you grow. Help juniors, review their work well. The mentoring habit starts here, not at senior
• Use AI tools well across the SDLC. Daily workflow, exploration, knowledge-sharing. Bring back what you find to the team
• Improve the system. Documentation that was missing, a flaky pipeline, observability you wish you’d had. You leave things better than you found them