refractal - Systems Engineer

• A systems engineer who reasons carefully about latency, failure, isolation, integrity, and cost, and uses measurements rather than assumptions. • Strong experience with backend, distributed, or infrastructure systems; Python experience is preferred. • Production observability and distributed tracing experience, ideally with OpenTelemetry or similar tooling. • Experience building responsive services under load with correct timeout, retry, and backpressure behaviour. • Experience with Postgres, Row-Level Security, migrations, and multi-tenant access-control testing. • Hands-on experience with containers, cloud infrastructure, continuous delivery, and operational security. • The ability to work independently and own technically ambiguous production problems. • Radical transparency. We believe the best work happens when everyone feels able to give and receive honest, constructive feedback. • Public service. We see AI security as a form of public service. Getting the AI transition right means putting the right infrastructure in place to manage the threats that come with it, and our work helps protect the institutions and services society depends on. • Fail fast. We test ideas early, seek feedback and learn quickly. We experiment rapidly and change course when something isn't working, without compromising on security. • Pragmatism, not dogmatism. We choose approaches based on how well they solve the problem. That means combining established cybersecurity methods with frontier AI research, questioning our assumptions, and changing our minds when the evidence changes.