Infrastructure & Release Engineer

Role overview An Infrastructure & Release Engineer is needed to build the verification, deployment, and operational foundations under a fast-moving, multi-service codebase. The position is deliberately separated from product engineering: the focus is on making continuous deployment safe as the team grows, so that shipping speed no longer depends on a single person's memory. It is a greenfield mandate inside an established system, with broad latitude to set priorities.

Responsibilities - Design and operate test and typecheck gates in continuous integration, with particular care that latency and noise do not drive engineers to bypass them. - Own release and deployment across multiple independently-deployed services in a monorepo, plus a signed and notarized desktop client, so that merged code reliably matches what runs in production. - Build migration tooling and review-time checks that catch unsafe schema changes against a high-volume, live production database before they reach apply time. - Implement and remediate row-level security policies, privilege grants, and database audit posture. - Establish production observability that surfaces errors to a person without someone having to go looking. - Manage internal IT foundations (device, account, access, support) and maintain dependency and supply-chain hygiene.

Requirements - Prior experience building infrastructure and CI systems from close to zero at a small company, under real delivery pressure, without a dedicated platform team. - Strong Postgres operations background, including migration mechanics, lock behaviour, and row-level authorization models. - A design instinct that slow or noisy gates are bypassed, and that this is a design failure rather than a discipline failure. - Practical security reasoning across auth boundaries, secret handling, and least-privilege access. - Ability to hold the line on safety while remaining a collaborator engineers do not route around. - Track record of getting adoption, not just compliance, when introducing testing or CI into codebases that had none.

Nice to have - Hands-on experience with a managed Postgres platform and its authorization model in production. - Ownership of code-signing and release pipelines for a desktop application. - Incident leadership with postmortems treated as the important deliverable.

Benefits and work setup - Small, distributed, engineering-led team that ships continuously, with no standups-for-the-sake-of-it and no committee between the engineer and production. - Competitive salary and meaningful equity, with the compensation band shared in the first conversation. - Short, grounded interview process: founder conversation, technical deep-dive on adoption of past infrastructure, a paid one-day scoped design exercise against real constraints, and a final conversation on working style and compensation. No unpaid take-homes and no surprise algorithm rounds.