2 min lesson
The portfolio / past-work deep dive
Rebuild the sequence in "The portfolio / past-work deep dive" from memory, ending with the check that proves the outcome.
Step 1 of 2
For 60 minutes you walk one or two studies end to end and the interviewers probe well past the result. Expect questions about who pushed back, why you chose this method over the alternatives and how you would run the same study in half the time. They are reading judgment, not your slide design.
Use a clear arc and hold to it: Problem, Approach, Process, Artifacts, Impact, Learnings. Lead with the impact and the decision that changed, then let the methodology come out under questioning rather than as an opening lecture.
- 1Problem. The question and the stakes - what decision was blocked or at risk without an answer.
- 2Approach. The method you chose and, in one line, the alternatives you rejected and why.
- 3Process. Recruiting, the guide or instrument, moderation or fielding and how you analyzed - kept tight, not exhaustive.
- 4Artifacts. One or two real outputs: a synthesis, a clip reel, a readout deck the team actually used.
- 5Impact. The decision that changed and a number where you have one - the part you open with.
- 6Learnings. What you would do differently or faster, pre-written before you walk in.
Mixed methods - qual paired with analytics, surveys or an experiment.
A technical or expert audience, ideally developers.
A decision that visibly moved because of the work.
Speed under a real constraint, not a year-long program.
Who disagreed with the finding and how you handled it.
Why this method and not a survey, a test or analytics alone.
What you would cut to run it in half the time.
Where the study was wrong or thin in hindsight.
Pre-write the 'what I'd do differently' answer for every case - it is almost always asked and a crisp, specific one reads as a researcher who learns rather than one who defends. Name the actual cut you would make and the rigor you would trade for speed, not a humble platitude.
Learn more
Full explanation
Don't give the methodology tour
Opening with sample sizes, your screener and your coding scheme buries the value and reads as a technician. Lead with the decision that changed and the impact number, then surface method when probed. The panel is hiring someone who drives roadmap, so the outcome has to come first.
QAn interviewer asks how you would run your flagship case study in half the time. What does a strong answer look like and what does a weak one reveal?