Expected to openPlatform

Infrastructure Engineer

The platform underneath everything: environments, pipelines, observability, and the data residency guarantees we make to clients.

About the role

We make specific promises to clients about where their data lives and who can reach it. This role owns the machinery that makes those promises true.

This seat opens as the products move into production with real client data. We are talking to people ahead of that.

Responsibilities

  • Own infrastructure as code across environments, from local development to production.
  • Build and maintain deployment pipelines that a small team can trust on a Friday.
  • Set up observability worth having: logs, metrics, traces and alerts that mean something.
  • Implement the controls behind our data residency and retention commitments.
  • Manage cost, capacity and the security posture of the whole platform.

Requirements

If you meet most of these and the rest looks learnable, apply. We would rather read your application than have you rule yourself out.

  • Substantial experience running production infrastructure on a major cloud provider.
  • Infrastructure as code as a default way of working, not an afterthought.
  • Containers, orchestration and CI/CD in your daily vocabulary.
  • A security-first instinct, particularly around secrets, access and network boundaries.
  • Calm, methodical behaviour during incidents.

Nice to have

  • Experience with data residency or sovereignty requirements in a regulated context.
  • Compliance framework exposure such as ISO 27001 or SOC 2.
  • Platform work supporting machine learning workloads.
  • Cost engineering at small scale, where every instance is visible.

How you would work here

01

Craft is the point

Work is judged on whether it holds up, not on how it was presented in a status meeting. If you do careful work it will be visible here in a way it never is at scale.

02

Real ownership

You own a product surface rather than a slice of a backlog. That means the decisions are yours to make, and the consequences are yours to sit with.

03

New technology, clear guardrails

There is genuine freedom to try things, set inside limits drawn by people who have taken systems into production before. Experiment, but know where the edges are.

04

Hybrid in Amman

Three days in the office and two from home. The office days are for the work that goes better with everyone in a room, which is most of the hard parts.

How we hire

Five steps, about two weeks end to end. The work assessment is a real day of work and it is paid.

  1. CV review

    We read it properly. You hear back either way.

  2. Call with Essa

    Forty-five minutes with the founder. Your work, our work, and whether the fit is real.

  3. Paid work assessment

    One day on a realistic problem, paid at a fair rate. The closest either of us gets to trying the job.

  4. Team session

    Time with the people you would work beside, so the decision runs in both directions.

  5. Offer

    Made quickly once we are sure. About two weeks from first contact to here.

About Digital Composition Lab

DCL is a founder-led R&D software product development lab. We take on problems where software has to be trusted rather than merely shipped, and we build the products ourselves: Agentic Data Compliance for UK GDPR alignment, and Korva for financial crime prevention.

The lab is small and deliberately full-stack in the widest sense: research, product, design and engineering in one team. More about who we are.