Fast answers depend on finding the failure chain without treating a plausible diagnosis as proof.
The investigation must shorten on-call reconstruction while keeping Nova and compute API evidence under engineering judgment.
Who you’d be doing this for
“My launch review paused because the funnel spun for ten minutes, then nobody could tell me why it came back.”
Cosmin Horvat · Product Manager
Runs funnel and experiment reviews using analytics results that pass through the compute layer.
What is at stake
Funnel and experiment results stall, and on-call engineers rebuild the failure story by hand. You must weigh faster evidence assembly against a diagnosis engineers can actually trust.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster triage vs. evidence engineers can inspect
- compute API reliability vs. Nova investigation load
- ranked causes vs. confirmed root causes
- pilot speed vs. durable team ownership
Why Amplitude
Nova and the compute API sit behind the charts, insights, and experiment results that product teams rely on.
Written with these in mind
Not your kind of problem? 18 more at Amplitude, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.