At Donut we are on a mission to create more trusting, collaborative, & successful work relationships. We believe genuine relationships are the key to being engaged, happy, & successful at work.
Donut came together over a shared passion to help people connect, & the insight that strong relationships at work are the bedrock of a successful team. Employees who feel socially connected to their coworkers express greater individual purpose & fulfillment, less workplace loneliness & isolation, & improved performance & productivity. We are building a company that embodies those ideals while instilling them in others.
How we work:
Our small, fully remote product, design, & engineering team is filled with empathetic & caring individuals dedicated to unlocking the power of human connection. We're organized as smaller (three to six person) pods that evolve a few times a year based on our objectives & the addition of new talent. We build new features together in two-week sprints & this cadence aligns with other company rituals. Our core connection hours are 11 a.m. - 5 p.m. ET / 8 a.m. - 2 p.m. PT.
About the role:
We are looking for our first Data Scientist to join our team. To-date, basic data analysis activities have been conducted in Periscope Data dashboards & in Mixpanel by a mix of engineers & people in operations & product/design. As Donut deepens its product capabilities, we are eager to add more & better data-derived insights to our approach for user-centric product development.
This role is all about high impact. If you're eager to guide big choices, pick low-hanging fruit, & see user & business outcomes quickly, we'll be a great match. If you're primarily interested in theoretical ML or deep learning, then Donut is probably not at the right stage for you. This is a chance to apply your analytical craft with a team that respects your work.
Like many startups, we have a near-endless backlog so optimizing prioritization is essential. You'll have the chance to build things right from the ground up: to make crucial foundational decisions to better incorporate discrete signals in our product development process.
You will report to the VP of product but your scope will follow opportunities wherever they are. This may include analysis, for example, higher in the marketing funnel or overlapping with our customer support organizations' scopes. We're a collaborative company so doing the right things for our users is more important than rigid boundaries of roles. (Just for clarity: this is not a euphemism for being immature, disorganized, or chaotic. :)