Текст заказа
About Us
There are 55 million Americans over 65 living at home, and their families are anxious in ways that go far beyond "I hope mom's alright." We built a phone that works out of the box, AI check-in calls that surface how she's really doing, and a family app that replaces daily dread with peace of mind. Families tell us they used to wake up with a knot in their stomach. They don't anymore.
It is working, with tens of thousands of active customers, a strong financial position, and investors including the YC Continuity Fund behind us.
We are looking for a hands-on owner of finance and operations: a do-er who makes finance a real partner to every leader in the company and runs the operations that keep it moving. You will put the numbers at the center of how we make decisions including telling us when we should be investing more, not just less. This is not a role for someone who wants to hire a team and manage from above. You will build the model, sit in the budget reviews and negotiate the contracts yourself. If building the financial and operational backbone of the company that brings peace of mind to millions of seniors and their families is how you want to spend the next few years, we'd love to talk.
What you will own
Own and evolve our data foundation. Today, our data stack and analytics infrastructure are maintained by backend engineers who have taken on data work alongside their primary responsibilities. You will become the first person dedicated to this area: owning the reliability, structure, and evolution of the systems that bring together data from our product, billing, CRM, marketing, and other platforms.
Turn raw data into a trustworthy, usable data layer. Build and maintain pipelines, models, views, and shared definitions that make important business concepts easy to understand and analyze. Reduce duplicated logic across dashboards and queries, establish clear definitions for core metrics, and make it easier for others to answer questions without rebuilding the same logic every time.
Enable self-service analytics across the company. Make it possible for non-data specialists to answer recurring questions through dashboards, well-designed data abstractions, documentation, and AI-assisted tools.
Own recurring reporting and business visibility. Maintain and improve the dashboards and reporting used to understand growth, revenue, retention, churn, customer behavior, product adoption, and operational performance.
Investigate questions, not just fulfill data requests. When someone asks why churn increased, which customers adopt a feature, where a funnel is breaking, why a marketing channel is performing differently, or whether an experiment worked, you should be able to take an ambiguous question, find the relevant data, explore it, and come back with a clear answer---or explain what the data can and cannot tell us.
Partner closely with product, engineering, growth, marketing, and leadership. Data here is not a separate reporting function. You will work directly with people making product and business decisions, helping them define what should be measured, challenge assumptions, design useful analyses, and interpret results.
Build the foundations of our data function. You will have significant influence over how we structure analytics as the company grows: what belongs in the data layer, how metrics are defined and documented, how we monitor data quality, what should be automated, and eventually where additional data specialization or headcount would create leverage.
What we are looking for
Strong SQL and relational data skills. You should be extremely comfortable exploring complex production datasets, joining information across systems, understanding imperfect schemas, and turning messy business logic into clear, maintainable queries and models.
Production data engineering depth. You understand data pipelines, ETL/ELT, APIs, databases, data modeling, scheduling, monitoring, and failure modes. You do not need a backend engineer to diagnose every pipeline issue or build every new integration for you.
Cloud warehouse experience. Hands-on experience with BigQuery or a comparable analytical warehouse, including performance, cost, and maintainability tradeoffs.
Strong analytical judgment. You understand funnels, cohorts, retention, conversion, segmentation, experimentation, and the difference between an interesting correlation and something we should actually make a decision around. You know when a dataset is too small or biased to support the conclusion someone wants to draw.
Business curiosity. You want to understand why a metric changed, not just calculate it. You ask follow-up questions, inspect unexpected results, notice when two numbers that should reconcile do not, and keep digging until you understand what is happening.
The ability to communicate analysis clearly. You can turn a complicated investigation into a concise explanation of what happened, why we think it happened, how confident we are, and what we should look at next. Your audience will often include people who do not want or need to understand the SQL behind it.
Pragmatism about data infrastructure. We are not looking to build a sophisticated data platform for its own sake. You should know when a simple solution is enough, when something needs a more durable approach, and how to improve the architecture incrementally as our needs grow.
Comfort operating independently. There will not be a larger data team handing you tickets, reviewing every analysis, or deciding what to work on. You will need to prioritize against company goals, clarify ambiguous requests, and identify important data problems before someone explicitly asks you to solve them.
You are probably a fit if
You have 4+ years of experience in data engineering, analytics engineering, product analytics, or a similarly hands-on data role.
SQL is one of your strongest tools and you are comfortable working directly with PostgreSQL or similar relational databases.
You have worked with BigQuery or a similar warehouse.
You have built or maintained production data pipelines and worked with data coming from multiple operational systems.
You have experience building dashboards and recurring business reporting, but you do not think of dashboards as the end product of analytics.
You can independently investigate product or business questions and communicate the conclusions to non-data stakeholders.
You have worked closely with marketing, growth, sales, or revenue teams and understand the kinds of questions they need data to answer. Experience with CRM, marketing automation, attribution, or revenue operations is a strong plus.
You care deeply about data correctness and notice when definitions, edge cases, or assumptions do not quite line up.
You are comfortable inheriting an imperfect but functioning data environment and improving it incrementally rather than rebuilding everything from scratch.
You enjoy being both an engineer and an analyst and do not see infrastructure work and analytical work as separate worlds.
You are comfortable with ambiguity and biased toward finding answers.
What does your journey look like?
First 30 days: Learn the business and the data
Your first job is to understand how the company works through its data.
You will learn our core systems, data sources, schemas, dashboards, and recurring reports. You will work through how we currently measure revenue, churn, retention, acquisition, product adoption, and growth, and understand where those definitions come from.
At the same time, you will start taking ownership of existing analytics and data work. Fix a broken report. Investigate a real business question. Trace a metric back to its source. Identify places where duplicated or fragile logic is creating risk.
By the end of the first month, you should understand both the shape of our data environment and the major areas where improving it would create leverage.
Days 31 to 60: Take owners