Software Engineer - Systems and Reliablity

Define success before building. Establish measurable service-level objectives for customer-facing latency, availability and correctness.

Write maintainable code. Build systems another engineer can understand, debug and operate without depending on you being available.

Test beyond the happy path. Use unit, integration, load and fault-injection testing to validate behaviour under realistic conditions. Explain your coverage and its limitations…

Ship safely. Own CI, deployments, rollbacks, schema migrations and infrastructure changes. When your work requires a Terraform change, you own that too.

Strong engineering fundamentals and the ability to apply them to unfamiliar problems.

We assess these directly through technical discussion and practical reasoning.

Process creation, signals, file descriptors, namespaces, cgroups, PID 1 behaviour and CPU throttling.

Virtual memory, page cache, available memory, swap, cgroup memory limits, out-of-memory behaviour and stalls that occur despite low CPU utilisation.