Describe your most recent work to a recruiter, then identify one additional experience you would want the recruiter to share with the hiring team. Make the business or product decision, your contribution, and the outcome understandable without relying on technical jargon. ### Constraints & Assumptions - The recruiter may forward a short summary of your answer to the team. - Choose examples you can discuss without exposing confidential information. - Distinguish your work from the broader team's work. ### Clarifying Questions to Ask - Would the hiring team value more detail on experimentation, product analytics, SQL, or modeling? - How technical should the summary be for the people reviewing my profile? ### What a Strong Answer Covers - The decision or user problem, the unit of analysis, and why it mattered. - Your ownership from problem framing through analysis and communication. - The method at an appropriate level, including one important validation check. - A result stated accurately and the reason the second experience adds a distinct signal. ### Follow-up Questions 1. What trade-off did you have to make in that project? 2. How did a stakeholder use your work? 3. What would you change if you repeated the analysis?