Clover Health - Head of Engineering, Data Platform
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT
Requirements
• An engineering background with deep, hands-on experience in Snowflake and DBT • Proven experience navigating genuinely complex data environments and deeply heterogeneous source systems, messy integrations, inconsistent data models, and real business logic embedded in pipelines. The complexity of what you’ve worked with matters far more than the volume or scale • Cross-domain background is a plus; if you’ve built complex data platforms across different business contexts, that breadth is an asset. Experience in regulated domains (healthcare, financial services, etc.) is helpful but not required • A strong, well-reasoned point of view on data access philosophy; you believe raw data should be broadly available to business users and can defend why • You have shipped AI-backed data systems and pipelines serving LLM applications, agentic workflows in data operations, or AI tooling that fundamentally changed what your team could do. Using Copilot for autocomplete is not the bar. You have opinions about where AI is reliable, where it isn’t, and how it changes what a data platform needs to be • Action-oriented on governance; you document what matters, automate what you can, and don’t let process become a bottleneck • Experience building and developing teams; you think about composition intentionally, hire for gaps, and invest in people’s growth • Exceptional communicator; you are clear, direct, and concise with both technical and non-technical audiences.
Responsibilities
• Own Platform Strategy & Execution • Own the data platform end-to-end — architecture, tooling decisions, and roadmap — with a bias toward enabling broad, self-serve access to data across the business • Be hands-on with Snowflake and DBT, contributing directly alongside the team on builds, migrations, and optimizations • Integrate and rationalize a complex ecosystem of source systems and vendors into a cohesive, reliable data warehouse • Define and evolve our approach to data modeling, including well-reasoned opinions on mart/gold layer design — when to enforce structure and when to get out of the way • Make strategic build vs. buy decisions on tooling and vendor relationships, framing those decisions in terms of business and operational outcomes — not just technical elegance • Drive AI-Native Data Platform • Design and evolve a data platform that is built for an AI-native organization — pipelines that serve LLM applications, infrastructure that supports agentic workflows, and tooling that compresses what used to take weeks into hours • Use AI actively in your own workflow and bring strong opinions about where AI changes what a data platform needs to do and where it doesn’t • Stay ahead of how AI is reshaping the role of data teams and translate that into concrete platform and staffing decisions • Ensure material Business Impact • Frame every platform decision in terms of business outcomes — operational efficiency, financial impact, clinical results. The data platform is a strategic enabler, not an isolated technical domain • Partner with business stakeholders to translate data needs into platform capabilities without creating unnecessary friction or access barriers • Make progress and tradeoffs visible to leadership as a natural byproduct of how you work • Lead and Develop People • Lead and develop a small high-impact team; setting a high bar for craft, communication, and ownership • Think deliberately about team composition: what skills exist today, what gaps need to be filled, and how to sequence hiring to match the platform roadmap • Invest in the growth of your team members, give clear feedback, create opportunities for ownership, and develop people who can grow with the platform • First 90 Days: Develop a clear point of view on the platform's current state. Identify the highest-leverage opportunities. Ship a first step-function improvement or solve a fundamental limitation. • 6 Months: Team transformation completed. New smaller team operates in a new operating model with substantially higher impact. • Long Term: Data platform is recognized as a strategic business asset. Team is growing their skills, increasing capacity and insights, and operating with autonomy
Benefits
• Employee Stock Purchase Plan (ESPP) offering discounted equity opportunities • Reimbursement for office setup expenses • Monthly cell phone & internet stipend • Remote-first culture, enabling collaboration with global teams • Paid parental leave for all new parents • We always put our members first, and our success as a team is measured by the quality of life of the people we serve. Those who work at Clover are passionate and mission-driven individuals with diverse areas of expertise, working together to solve the most complicated problem in the world: healthcare.
No credit card. Takes 10 seconds.