Recebe mais respostas dos empregadores
Envia um currículo específico para a oferta em poucos minutos.
LawnStarter Inc. is hiring a Product Data Analyst focused on Growth and Experimentation. You will own the experimentation program, test design, and readouts across web funnels, SMS/drip, and SEO tests built on our page-clustering tooling.
You will shape growth experiments and influence acquisition-to-conversion decisions. You are expected to automate and scale analytics with Lightdash, Python-backed tooling, and AI-powered checks, working closely with CRO and Growth PMs to turn data into
LawnStarter is the nation's leading on-demand marketplace for lawn care and outdoor services, with over $100M in annual bookings. We're expanding beyond lawn care into the one-stop shop for all home services. Getting there depends on how fast we can test, learn, and scale what works.
We're a high-leverage team of Product Data Analysts embedded across the business, owning the semantic layer and the metrics everyone trusts. The experimentation program runs on real rigor, not vibes: pre-registered analysis plans gate every test launch, anytime-valid statistics keep mid-run dashboards honest under continuous viewing, automated daily SRM and attribution health sweeps catch broken tests early, and seasonal power forecasting accounts for a business that swings hard by time of year. The test lifecycle, design through readout, is already AI-driven. Our analysts are stretched across product, so Growth support has stayed part-time and reactive, until now.
You're the first data analyst dedicated entirely to Growth and Experimentation. Your primary charter is theexperimentation program: test design, statistical rigor, and readouts across web funnels, SMS/drip, sales-driven tests, and SEO tests built on our own page-clustering tooling. It's a wider surface than most companies run. You also own theacquisition-to-conversion funnelthose tests move, across paid, organic, and partner channels. What to test and which direction to bet on is the CRO's and Growth PMs' call; you shape it, they decide it.
You're not starting from scratch. Dashboards, tooling, and rigor scaffolding are already shipped and running. Expect the early months to be hands-on and manual: scoping tests, crunching readouts, while you build toward a self-serve layer. If a test readout and a funnel refresh ever compete for your week, the test wins.
Tests that can't answer the question they were run forGrowth wants more experiments, but volume without rigor produces confident, wrong conclusions. Raising the bar without becoming the bottleneck is the job.
Getting off the manual treadmillReal tooling already exists: test-design helpers, dashboards, AI skills. Most tests are still hands-on and bespoke. How do you extend that automation so routine cases genuinely self-serve?
Making the funnel decision-gradeThe semantic layer defines the funnel, but instrumentation is uneven across brands and channels, and no one owns the single trusted view. You build it, and you keep it trusted.
Turning analysis into decisionsThe hard part isn't the SQL. It's getting a PM or marketer to change course. Can you deliver insight sharp enough that the room acts, and push back when the data favors the popular but wrong idea?
AI-native.You use AI daily for SQL, dbt, and pressure-testing your analysis, extending the skills already running our experimentation process rather than merely using them. This is unlikely to be a good fit if you're skeptical of AI or treat your workflow as fixed.
A partner, not a report-writer.You don't wait for a ticket. You sit close to Growth and bring the question before anyone asks it. Skip this one if you want a clear queue with no expectation to push back.
Statistically sharp.Wrong fit if "we hit significance" ends your analysis instead of starting it. Right fit if you have a point of view on test design (power, significance, novelty and interaction effects, when not to test) and can explain a broken experiment in plain terms.
Fluent in experiment instrumentation.You know how Segment events and Flagsmith randomization interact, and catch a tracking problem before a test ships, keeping our re-run rate down. This isn't for you if instrumentation is someone else's job.
Fluent in the funnel.You think in CAC, LTV, and channel economics, and know acquisition data's quirks: attribution messiness, seasonality, channel mix. Skip this one if your background is pure product-feature analytics.
Technically self-sufficient.Wrong fit if you need clean data handed to you. Expert SQL, enough Python to automate the stat-sig math, and comfort in dbt and Lightdash, building your own models without waiting on data engineering.
Influences without authority.PMs and marketers act on what you find because your insight is clear and honest about uncertainty. This isn't for you if you consider the job done once the analysis ships, regardless of outcome.