Infrastructure Operations Engineer

About the role

A database is only as reliable as the machinery that builds and tests it. This role owns that machinery: the build system, the release process, the test harness that runs the engine against real workloads, and the developer environments the team works in every day. It is operations in the oldest sense: keeping the workshop in order so the builders can build.

What you’ll do

• Own CI pipelines: fast, hermetic builds that developers trust instead of retry.
• Build the release process: versioned artifacts, checksums, reproducible packaging.
• Maintain long-running test harnesses: correctness suites, recovery drills, upgrade paths.
• Keep developer environments consistent: one command from clone to running server.
• Write the runbooks and operational documentation the team actually reads.

What we’re looking for

• Experience operating build and release infrastructure for compiled systems software.
• Fluency with Linux, containers and CI systems — debugging them, not just using them.
• A tester’s mindset: adversarial thinking about upgrades, partial failures and dirty state.
• Documentation written as carefully as code.

Nice to have

• Experience with database testing: determinism harnesses, fault injection, workload replay.
• Packaging experience across Linux distributions, macOS and Windows.
• Familiarity with Rust toolchains at scale.

What you’ll work on

Everything around the engine rather than in it: the pipelines behind the download page, the verification behind every release, the environments behind the developer guides. When the engine team ships with confidence, this role is why.

Why this role matters

Users meet PLOMID first as an artifact they download and verify. The distance between “it compiled once” and “it is shippable” is this entire role. Infrastructure companies are judged on exactly that distance.