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 6th engineer in a 30-person company.

You’ll be responsible, along with the frontend lead, for “everything frontend” in both our React web app and our React Native mobile app. This includes slinging CSS to implement UIs, creating hooks to talk to our backend and everything in between. You’ll be building features, fixing bugs, cleaning up tech debt, and building out new projects.

Onboarding will look like a gradual ramp-up over a month or two as you learn our systems. You’ll start by fixing small bugs and cleaning up tech debt. Then you’ll be building features and pages. Finally, you’ll end up working on whatever large-scale project the team as a whole is working on. Depending on timing, you might wind up building out a brand new teen-facing web app, building huge swaths of a bespoke EHR, or creating the frontend for a dynamic schema-driven survey system.

You will work directly with the CTO and the Frontend Lead to draft Technical Proposals and implement the frontend pieces of them. You’ll also work with the PM and designers to inform what web and mobile features we build. In this way you’ll be involved, not just in building products, but also in deciding how we build products. You’ll have to say in timelines, prioritization, and all technical details of the things you work on.

You are expected to have thoughts on things like CSS structure, API design, and React State Management. You are not expected to be a UI/UX designer, though you’ll have some opportunities to weigh in on that if you want to. You don’t need to be a full-stack developer, but you may need to make junior-level changes to the backend in the process of implementing frontend features.

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.

Although “years of experience” is a very fuzzy measure, we generally believe that this job is doable by someone with at least 3 or 4 years experience in frontend development and at least 2 years of recent React experience. No previous experience with React Native is required, but a willingness to learn and become proficient with it is.

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:

• Progress to Full Stack Engineer
• Progress to a Lead Frontend Engineer

Tech Stack

• React Native (Daybreak Mobile), React JS (Web Frontend), TypeScript, Netlify
• Ruby on Rails (Rails Backend), PostgreSQL, Redis, RSpec, Heroku

Some of the tools we use on the frontend include ReactQuery, Jest, Prettier + Eslint, Axios, Storybook, and React Router.

Compensation

• Base Salary: 80k-140k
• Equity: 0.06%-0.17%
• Vacation: 3 weeks minimum, unlimited policy.

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 the 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:15 am PST
3. Do your work
4. 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) [Link to understanding PRD]
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