About Daybreak

Daybreak Health (www.daybreakhealth.com) is building the leading digital mental health system for youth. Our mission is to create a world where every young person benefits from mental health support.

Our mental health system removes all barriers to effective care for young people: we create easy access through our school and pediatrician partners, deliver effective care through evidence-based online therapy that is integrated with technology, and bring consumer cost to zero through our funding partnerships with government agencies and health insurance. Over the next 5 years we plan to serve more than 25 million youth who need mental health support.

The Team

As a team, we are all aligned with our North Star mission. We collaborate and execute incredibly well by doing more with less (we value efficiency and output over hours worked!) and we communicate clearly using writing (vs. unnecessary meetings). We are fully remote with team members across the country, and will stay that way. We value mental health: the willingness to be vulnerable is a requirement to join Daybreak (for example by communicating when we make mistakes). We have regular mental health days (at least once per quarter!). Last but not least, we value fun and hold regular virtual and in-person activities.

The Business

We’re a YC-backed company that raised its Seed from Maven Ventures and just raised our Series A from a Top 10 VC (announcement coming soon). We’re a rocketship, with our revenue more than tripling between July and November of 2021, and more acceleration in sight. We’re hiring for critical roles now to expand nationally and have an even bigger 2022.

The Job

You'll be the first Data Engineer on a twelve person team and will work directly with the CTO.

Today Daybreak’s data infrastructure consists of ChartIO, a small PostgreSQL DB system owned by our Rails app and Salesforce.

We’re in the progress of replacing ChartIO and want you to lay down a strong foundation upon which to build the following functionality:

  • Internal reporting and analytics to help guide the business itself.
  • External reporting to support the schools that have trusted us to help their students.
  • Reduce the burden on our Care Team
  • Improve the efficacy of our therapeutic interventions
  • Create effective new therapeutic and non-therapeutic interventions

Your first tasks will be the following:

  1. Learn our existing data infrastructure (couple of weeks)
  2. Figure out the correct data warehouse (or whatever you believe is the correct storage solution) for Daybreak
  3. Draw up a plan to integrate our existing data sources into the chosen data storage system. This integration must be robust, easy to make updates to (both the data pipelines and the resulting data), easy to add new data sources and transformations to and capable of notifying whomever is responsible for (and capable of) fixing it when there is a problem.
  4. Execute the first phases of the plan.

The CTO has some opinions about how this system should be built (AirByte + DBT + PostgreSQL) but is explicitly hiring you for your expertise and will accord you the space and trust required to be successful in your role.

Once the core infrastructure is in place you will support them and add new data pipelines as necessary. You will be included in our SDLC (detailed below) and will be expected to collaborate on (and sometimes directly lead) Technical Proposals and implement the data pipeline components defined within them. This process will allow you to define not only the details of the solutions we implement but the timelines on which we implement them. You will be looked to almost immediately as the Subject Matter Expert (SME) on our entire data infrastructure by both the CTO and Product.

In order to be capable of this work we expect that you will be extremely skilled at data schema design, data pipeline design, data integrity validation, data integrity remediation & documentation writing.

You are expected to have opinions on workflow engines, feature toggles and asynchronous processing. You are not expected to be a microservices wiz, a DevOps Ninja or a full time DBA.

Lastly, you will help Engineering as a whole to deliver on our Technical Vision, which, if lived up to, we believe will provide the opportunity for the business to succeed.

We generally believe this job is doable by someone with three to five years of industry experience composed of at least two recent years architecting, implementing and maintaining data pipelines.

Compensation

  • Base Salary: 120-170k
  • Equity: 60,000 to 30,000 shares, 5 year vesting, 1 year cliff for 20%
  • Vacation: 3 weeks minimum, unlimited policy.

Growth Opportunities

While we're a small company, we're on a growth path and can help you grow your skills. Depending on your interests and the growth of the company we can help you pursue one of the following growth paths:

  • Data Scientist (~2024, under an as-yet hired Data Scientist)
  • Lead Data Engineer (~2023, technical leadership of an as-yet budgeted data engineering team)
  • Data Engineering Manager (~2024-2025 assuming business goes as planned)

Tech Stack

  • Ruby on Rails v6.0.3 (Rails Backend), PostgreSQL, Redis, RSpec
  • React Native v0.64.1 (Daybreak Mobile), React JS v17.0.2 (Web Frontend), TypeScript, Jest
  • Salesforce
  • Segment

The Engineering Org

Daybreak Engineering is kinda nuts. We allocate time for tech debt. We run a Software Development Lifecycle (SDLC) that allows us to set our own deadlines for projects. We measure our productivity in both tickets punched and business value delivered. We're constantly looking for ways to buy solutions to our problems rather than build them. We understand that Software Engineering isn't just programming, it's programming plus time. We believe that it is worse to build the wrong thing than to build nothing at all. We are proactive instead of reactive.

We know where we're going, and we believe that through good faith debate we can get there. Check out our Technical Vision here for more: Technical Vision 2021-09-02

As a member of the Engineering Team you can expect:

  • To spend less than five hours in meetings most weeks.
  • To be given projects fit for your level of experience in addition to normal plumbing.
  • To engage in good faith debate centered on how to build the tech required to achieve our mission.
  • To be invited into the business side of things and help identify and solve problem(s) across the org through both systems thinking AND software.

A Typical Day @ Daybreak Engineering

  1. Start your day at whatever hour works best for you
  2. Submit your Geekbot standup update by 10:15am PST
  3. Attend standup at 10:15am PST via zoom
  4. Do your work
  5. End your day whenever you feel is appropriate (guidance available if that helps you)

The Software Development Lifecycle (SDLC) @ Daybreak

  1. Product draws up a Product Requirements Doc (PRD) by working with Clinical, CS/Ops or Growth to identify areas of improvement for the business.
  2. Eng weighs in on the PRD giving it a T-Shirt Size (Eg. Minutes to Hours, Hours to Days, Days to Weeks, Weeks to Months, I don't know) A primer on Engineering Estimations
  3. Product decides whether the PRD is worth further evaluation based on Eng's T-Shirt Size
  4. Eng dives into the PRD and draws up a Technical Proposal that explains, at key:value and class name granularity, how this thing will be built.
  5. Eng reviews the technical proposal internally to ensure it's something we'd be proud to build and not a steaming pile of tech debt.
  6. Eng creates actionable tickets with tripartite estimates for all proposed work. Tickets are then collected into groups that each form a distinct, standalone, piece of business value.
  7. Eng presents the groups & estimates to Product for final scoping.
  8. Product descopes groups of work to meet timelines then green lights a specific body of work
  9. Eng signs off on the build as described and gets coding

Hiring Process

Daybreak's hiring process aims to be doable in about six hours end to end spread across a calendar week.

  1. 30 minute screener call with CTO
  2. Code Challenge - 1.5 hours
    1. The Code Challenge is done in a single sitting in your web browser via Qualified.io. It is timed, but you won't be working in front of people. We're trying to see how you program, not how you deal with social pressure.
  3. Technical Proposal Drafting Challenge - 1 hour
    1. We're a document heavy company. You will be writing a lot and so we need to understand how you approach writing about technical topics.
  4. Video Interview (Final) - 3 hours
    1. At this point we trust that you could do the work, we just need to get to know you a bit better and see if you can bring something unique to the team. The interview itself is broken into three parts, one with CEO, one with COO and one with CTO + Lead Frontend Eng.