Platform Engineer

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.

What You'll Be Doing

• 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
  
  

The shape we're hiring for

We're growing engineers toward a T-shape: broad across the platform, with depth starting to form in at least one area. At this level, breadth comes first and depth begins to emerge.

• 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
  
  

You'll be a strong fit if

• You've shipped real infrastructure or tooling into production and can tell the story of how it was used and how it failed
• You have a working knowledge of Python, Go, or Java: enough to build tooling rather than only configure it
• You've worked with AWS and/or Kubernetes, and you want to understand them more deeply than you do now
• You've been hands-on with CI/CD pipelines, whether building them, fixing them, or making them less painful
• You have solid problem-solving instincts, a collaborative mindset, and you communicate clearly, particularly when something is broken

You're using AI tooling in your daily workflow and curious about where it fits in the platform

You enjoy improving the work around you (tooling, docs, processes), not just adding to it

Useful rather than essential, and if you can tick off several of these we would like to talk: Terraform, Docker and Helm, Crossplane, Karpenter, Kyverno, Grafana Cloud, Bash and Linux, and familiarity with security best practice

You might be a less good fit if

• You want fully-specified tickets and nothing else
• You'd rather own infrastructure exclusively and keep developers out of it
• You're not interested in helping more junior engineers grow
• You'd rather specialise narrowly and not stretch outside your comfort zone yet
• You'd rather hold off on AI tooling until others have proven what works. At this level, adopting and shaping it is part of the day job
• You find rapid change in tools and ways of working draining rather than energising
  
  

Requirements

How we work

Opus 2 builds the platform that leading legal teams use to run their most complex work: a distributed, multi-tenant SaaS platform with API-first surfaces, where security, privacy, and compliance are first-class concerns. The stakes for our customers are real, so we care about quality. We also move fast and ship, because the alternative is irrelevance.

Infrastructure Engineering sits inside Product Engineering, based out of our friendly office in central Edinburgh, and works closely with the development squads. The focus is enabling engineers to self-serve through automation and appropriate guardrails.

• Build it, run it. Squads own their products end-to-end, from the customer outcome through to operating them in production. The platform exists to make that realistic
• Pragmatic engineering. We favour simple, testable solutions over premature abstraction. We use data where it informs a real decision

No manual intervention. Automation and guardrails over tribal knowledge and access requests

A learning and improvement culture. We're building an engineering organisation that learns and adapts at the pace AI is forcing on the work. That's the bar for hiring, growth, and how we run the team

Coaching as part of seniority. Senior engineers help juniors, mid-levels, and each other grow. We protect that time on calendars

A work in progress

Opus 2 is in real transition. AI is reshaping how our customers work and how we build software, and we're investing in the engineering organisation to keep pace. Some of that is already settled, other parts are still being shaped, and the platform is one of the places most visibly in motion.

If you want a fully-paved path, this isn't it yet. You'd be helping to pave it, alongside engineers who have done it before. If you want to be part of a team that's clear about where it's going and pragmatic about how to get there, there's real leverage here.

Tech you'll work with

We pick tools to fit the problem, and we have a clear sense of where we're heading.

• Cloud: AWS
• Orchestration: Kubernetes primary, serverless where it's the better fit
• Delivery: GitHub Actions, ArgoCD
• Infrastructure and policy: Terraform, Helm, Docker, with Crossplane, Karpenter and Kyverno in the mix
• Observability: Grafana Cloud
• Languages on the platform: Python, Go, TypeScript (where we're investing), Bash; Java and PHP in established services
• Data: Postgres, MongoDB, OpenSearch / Elasticsearch, vector stores
• AI: GenAI features already in production (LLMs, retrieval, agentic workflows), with more on the way
  
  

You don't need to know all of these on day one. You should be ready to learn what you don't.

Benefits

Working for Opus 2

Platform work at a company where AI is real, in production, and a core part of how customers get value, and where the platform you help build is what makes that shippable. A focused engineering organisation where your work is visible, your decisions matter, and the path from idea to customer is short. Investment in your growth: coaching, learning time, exposure to challenging problems, and a clear path to Senior when you're ready.

Alongside that:

• Contributory pension plan