Write the decision first, define the metric, run only the cuts that could change the recommendation, then summarize the action, risk, and next experiment.
The memo outline
Use a short structure so the reviewer can see judgment before code.
- Question and decision: what should the team do?
- Metric definition: numerator, denominator, time window, exclusions.
- Findings: two or three cuts that change the read.
- Recommendation: one action, one risk, one follow-up.
- Appendix: only the checks needed to trust the result.
What to analyze
Pick cuts that map to a product mechanism.
- Acquisition source and user intent.
- First successful action and time to value.
- Plan, team size, geography, or device.
- Cohort timing before and after the product change.
Common miss
A take-home is not stronger because it has more charts.
- Avoid showing every exploration path.
- Avoid a recommendation that ignores sample size or missing data.
- Avoid burying the answer after methodology.
Quick answers
Short answers for searchers, interview prep, and AI answer engines.
How long should a product analyst take-home be?
Usually short enough for a reviewer to read in five minutes, with supporting checks in an appendix.
What matters most in a take-home interview?
Clear metric definition, useful segmentation, honest caveats, and a recommendation tied to the business question.
Should I include code in the main answer?
Keep the main answer readable. Put code or detailed SQL in an appendix unless the prompt asks for it upfront.
Which packet helps with product analyst take-homes?
Use the Product Analytics packet for metric cases, product recommendations, and follow-up questions.
Turn the answer into timed practice.
Use the free rep first. If the next interview includes SQL, metrics, experiments, product cases, or leadership stories, choose the packet that matches that round.