Senior DevOps Engineer

About us

At Arbor, we’re on a mission to transform the way schools work for the better. We believe in a future of work in schools where being challenged doesn’t mean being burnt out and overworked. Where data guides progress without overwhelming staff. And where everyone working in a school is reminded why they got into education every day. Our MIS and school management tools are already making a difference in over 7,000 schools and trusts. Giving time and power back to staff, turning data into clear, actionable insights, and supporting happier working days. At the heart of our brand is a recognition that the challenges schools face today aren’t just about efficiency, outputs and productivity - but about creating happier working lives for the people who drive education everyday: the staff. We want to make schools more joyful places to work, as well as learn.

About the role

We are looking for an experienced and dynamic Senior DevOps Engineer to join our Engineering team and help us improve the resilience and performance of the Arbor platform, enabling the business to rapidly scale. The remit and focus of the role is to continuously fix and improve our architecture, infrastructure, and ways of working. This requires an obsessive, metrics-driven approach, a curiosity about system behaviour, and close collaboration with the solution architect and engineering teams. It’s a broad and exciting role, so we’re looking for someone up for a challenge - if you’re a collaborative and curious Engineer, this is the role for you.

Core responsibilities

• Work with Head of Platform and Head of SRE to identify improvements within the platform infrastructure and implement plans to address
• Work with the Platform teams to improve the maturity of all components within the system, including ensuring High Availability, and adequate testing and DR plans
• Contribute to improving our CI/CD pipelines and providing patterns of deployment
• Assist in incident response and resolution, and subsequent post-mortems and retrospectives
• Participate in tech-talks and team based learning to ensure knowledge is spread
• Document obsessively, relying on Playbooks/Runbooks and systems documentation to aid knowledge transfer