<aside>
Salary: £135k to £150k Equity: 0.35% to 0.4% Location: Shoreditch, London In person/remote: 4x/week in-person; hours flexible but typically 09:30-18:30 Benefits: free therapy, 30 days holiday + bank holidays + day off for birthday + 3 day company shutdown over Xmas, company paid lunch twice a week The job: making high quality mental health support more accessible
</aside>
Spill’s mission is to reduce unnecessary emotional pain by making high quality mental health support easily accessible.
Our product is bought by businesses and their employees can book free therapy sessions (we recently delivered our 100,000th free session). We are bought by companies in industries ranging from tech and media to hospitality and construction. On the company itself, we operate with an intentionally small HQ team of 6 full-time employees (2 software engineers).
Despite the small headcount, our goals for the coming years are punchy - hopefully we aren’t waiting too long for our millionth free session - and we are really serious about achieving them. You can read our company handbook here to get a fuller sense of how we plan to go about it.
Before explaining the specific responsibilities of this role, it’s worth stating that this role is going to have real responsibility at Spill. Spill is in the process of going from a company that’s searching for product market fit to a company that’s in the scaling phase. You’ll be joining as the most senior engineer in the team and have the remit to improve the processes and systems that we use to build software for our clients, users and counsellors.
What this role will actually do
When you join, you will be part of a 3-4 person engineering team. You will work cross functionally on projects with design, product, clinical, sales, marketing and operations. Calvin, Spill’s founder, or Harry, Spill’s VP Ops, is the most likely person to be the PM (i.e. the person shaping the goals and scope of the work) on projects you work on. However, for some projects, you may also take on that role.
50% of your time will be spent on building our product and internal tools and 50% of your time will be spent on the layer above - to improve efficiencies across multiple products and tools at once.
Here are some examples of the types of projects this role would work on:
What this role likely won’t do
As we scale our service over the next few years, we won’t need to solve any big load or scaling challenges on our backend engineering systems. Most of the gnarly problems we’ll be facing will be business and product problems that will require us to be inventive with the software solutions we build, it won’t be working out how to handle millions of requests per minute.
Additionally, because we generally hire senior+ people for our roles, there isn’t the typical team dynamic problems you get in startups. This role won’t need to have any management responsibility in the short-medium term to have a big impact and we have the option of hiring an external engineering manager further down the line if you aren’t interested in the manager path for your career.
Our tech stack