Role Overview

Wert is crypto-to-fiat payment infrastructure: our widget lets people buy crypto with a card inside someone else's product. Real money, real regulators, production volume.

We are hiring our first in-house DevOps engineer. Our infrastructure has been run by an external provider for three years, and we are bringing that function inside.

Be clear about the shape of this job. You will be the only DevOps engineer at Wert, and the work is not to write a roadmap and hand it to a team — there is no In House DevOps team (yet). It is to take a live payment platform into our own hands, with yours, while it keeps serving traffic. You get a part-time internal partner who knows the current setup, and support for the decisions you make.

If you are looking for a lead or architect seat where you set direction and others execute, this is not that role. If you are at your best inside a system rather than above it — and you like being the person who actually owns it — read on.

What you will own

Bringing infrastructure in-house

• Take over a platform you did not build: map it, absorb what is undocumented, take ownership of access, and move active infrastructure work inside the company.
• Decide what we keep from the current stack and what we replace — then execute that decision yourself rather than delegating it. We would rather you learn and optimise what exists before proposing an expensive migration away from it.
• Put infrastructure knowledge somewhere Wert can read it. Today too much of it lives in heads.

CI/CD and developer experience

• Own the delivery pipeline end to end and make it something engineers trust: fast, predictable, and strict where strictness matters.
• Build per-PR review environments that developers and QA drive themselves, wired for automated test gating — including routing external provider callbacks into ephemeral environments.
• Root-cause the failures instead of restarting the job. This is the difference we hire for.

Platform and infrastructure as code

• Architect and maintain the environment in Terraform (or Pulumi/CDK), with an internal library that lets product engineers self-serve the simple things without waiting on you.
• Own Kubernetes: workload configuration, resource behaviour, upgrades, and the boring reliability work that keeps a payment platform boring.

Running a payment platform

• Observability with thresholds you can defend. Metrics, logs, and alerts that fire on what matters and stay quiet otherwise.
• Third-party failure is our normal state. Blockchain nodes, KYC providers, and payment providers degrade without telling us. Detecting that, telling it apart from our own failures, and making it visible to whoever is on duty is core to this role, not an edge case.