Openstack Infrastructure Engineer

Requirements

• Experience operating open-source infrastructure systems. Extensive experience will be expected at senior level.
• OpenStack implementation, operations or troubleshooting experience.
• Experience with Ceph or similar distributed storage systems, including capacity, replication, failure domains, recovery, latency and performance.
• Strong Linux systems administration and troubleshooting skills.
• Practical knowledge of data-centre-grade hardware, including enterprise servers, CPUs, memory, storage media, NICs, firmware and out-of-band management.
• An understanding of how hardware design, power, cooling, rack layout and component failure affect platform reliability and performance.
• Strong networking fundamentals, with experience in OVN, OVS, BGP underlays, LACP, Juniper, IPv4, IPv6 and physical or virtual cloud networks being advantageous.
• The ability to troubleshoot across compute, storage, physical and virtual networking, databases, message queues, containers, hypervisors and guest workloads.
• Experience with virtualisation and cloud infrastructure at scale.
• A security-minded approach to architecture, automation, access control and operational workflows.
• An SRE mindset focused on reducing failure probability, recovery time, operational risk and data-loss exposure.
• Experience with Infrastructure as Code, configuration management and automation practices.
• A preference for repeatable, version-controlled automation over undocumented manual work.
• Discipline when planning and executing upgrades, migrations and high-impact infrastructure changes.
• Strong end-to-end ownership, from physical infrastructure and network fabric through OpenStack services to customer workloads.
• The ability to reason about capacity and performance across CPU, memory, storage, IOPS, latency, throughput, packet rates and control-plane scale.
• The ability to use AI-assisted tools productively while understanding their limitations. AI may accelerate research, troubleshooting, documentation and automation, but does not replace engineering judgement, experience, peer review or testing.
• Clear technical documentation skills, including architecture decisions, runbooks, change plans, incident findings and recovery procedures.
• The ability to contribute constructively to technical reviews, challenge unsafe assumptions and respond well to detailed feedback.
• The ability to work effectively in a distributed, largely asynchronous team.
• A willingness to participate in an on-call rotation managed through Rootly and respond to occasional out-of-hours incidents, maintenance or operational requests when required.
• Gets the difference between “done” and “97% done” and the potentially significant costs of the latter.