We are a multi-brand non-profit, with an appetite for social good, innovation and sustainable growth. We strive for continuous improvement and believe that employers need to invest in their staff and ensure they are always learning and developing their skills.
We have a flat, transparent structure where everyone is encouraged to speak up and have their say.
We foster a positive, diverse, and inclusive company culture. We always strive to adapt our culture to make SH:24 a more welcoming place to work.
We promote self-management, offering service users a portfolio of clinically assured, discreet and easy to access services which would traditionally be delivered in NHS clinics.
Our users move seamlessly between digital and physical services, with clinical excellence ensured through partnership with NHS specialist sexual health services.
Our objective is to improve access to sexual health services through a more holistic, user centred service. The service is designed to be flexible around the needs of users, encouraging greater autonomy, both in making decisions about their care and in navigating their preferred route through services.
We operate in two pizza teams - both cross functional, each with a dedicated PO.
Designers (Service/UX/UI/Product) sit across the teams, as does a Test Engineer.
We work Kanban, and run daily stand ups and regular ceremonies. We do all we can to support learning and growth - knowledge sharing through honest comms and pairing.
Committed to TDD, we operate no-blame culture and embrace failure as a tool to learn and improve.
We build software primarily in Ruby. Much of it is done within Ruby on Rails. We have a mixture of full stack Ruby on Rails applications and REST APIs. We are committed to adopting more progressive, modern front end technologies and have introduced some React, but would like to do a lot more.
Three steps:
1. Informal chat with a senior member of our team (to ensure cultural fit)
2. Take home code test (time boxed to 2-3 hours)
3. Remote pairing with a member of our team and an informal chat with two of our other developers and members of the product team (2-2.5hrs in total)
We typically review code tests within a day of receiving them and arrange final interviews (step 3) within 2-3 days.