Lead Backend Engineer, Spill

• You’ve got a good grasp of computer science fundamentals - either from a computer science degree or experience
• You have a track record of building and shipping software, probably in a small team in a startup environment for 7+ years
• You have successfully worn the tech lead hat within your company for multiple projects

Desirable

• Here are some examples of the types of projects this role would work on: Build a tool for Spill’s clinical team to efficiently triage messages for safeguarding concerns. Set up a lightweight datalake with data from our CRM, billing system and database to automate monthly reporting. Add traceability from sessions used to sessions paid for to speed up our billing processes
• You can think of this role having the initial “mission”: to build and run the "Internal OS" that automates every administrative task at Spill (onboarding, billing, therapist matching)
• It’s typical for startups / scale ups to put all early engineering resource into new product features in order to unlock more growth
• They then hire a bunch of ops people to handle all of the support and admin work that comes with that growth
• At Spill, our mission is to make high-quality mental health support accessible to as many people as possible and a large part of making something accessible is making it affordable
• This means that in order to achieve our mission, we have to keep our operating margins as low as possible
• You will be part of a 4-person engineering team and will be the most senior backend engineer on the team
• You will work cross-functionally on projects with design, product, clinical, sales and marketing and operations with other engineers and as the only engineer
• Calvin, Spill’s founder, or Harry, Spill’s VP Ops, is the most likely person to be the PM (ie be the person shaping the goals and scope of the work) on projects you work on
• However, for some projects, you may also be required to take on that role. 50% of your time will be spent on building and improving the tools themselves that people will use to complete their tasks with and 50% of your time will be spent on the layer above to improve efficiencies across multiple tools at once

• 40-minute intro call (20 mins initial questions from you, 20 mins initial questions from us)
• 60-minute backend task (real time programming task)
• 60-minute system design task (system whiteboarding)
• 60-minute product requirements task (another whiteboarding exercise that follows on from the system design task)