Principal of backend

About this role

About SchemeServe SchemeServe is insurance software like no other. Hosted in the cloud for MGAs, brokers and insurers, the SchemeServe platform boasts unique flexibility, unstoppable innovation and truly Obsessive Support. Started in 2000 by our CEO, Adam, SchemeServe has grown from strength to strength, never having taken outside investment. We're proud of how far we've come and how loyal we've stayed to our Core Values.

We're fully remote (we were doing it before it was fashionable!), although we get together twice a year for Team Retreats. We prize self-development and encourage everyone to keep learning and challenging themselves. Free books? Mentoring? Professional development? You got it. We also offer flexible working, paid charity days, a fantastic, relaxed and open company culture and free biscuits through the post. We genuinely believe this is the best place you could ever work.

If you're excited, good! So are we. Come and join the Insurtech revolution! Principal Backend Engineer UK Remote We're looking for an exceptional Principal Backend Engineer to help make backend engineering across SchemeServe better. You'll be one of the most technically experienced engineers in the organisation and the CTO's primary technical partner for backend engineering, helping shape our architecture, engineering principles and technical direction.

But this isn't primarily a feature delivery role and your job isn't to personally build everything you help design. Your real job is to make our engineering organisation better at building great software. You'll work alongside engineers and teams, helping solve difficult problems, challenging their thinking and developing their technical skills and judgement. What We Mean By Principal This is a deeply technical role. You'll need the depth to understand complex backend systems, architecture, security, performance, resilience and maintainability; review designs and implementations; spot risks; and challenge experienced engineers.

But technical knowledge alone isn't enough. We want someone who understands there isn't always one "correct" way to build software. Patterns, standards and best practices are useful tools. They aren't commandments. We care about finding the most appropriate solution to the problem in front of us. That means understanding the problem, business, existing platform, risks and likely future – and making pragmatic decisions based on the trade-offs.