CHAPTERS
- 0:00 – 1:00
AI PM interviews have shifted from product sense to AI system design (and the payoffs are huge)
Aman and Aakash set the premise: traditional product design prompts are giving way to AI system design interviews that test technical depth alongside product thinking. They tie this shift to the outsized compensation available for top-tier AI PM roles at frontier and big-tech companies.
- •Claim: “product design is dead” as a standalone interview focus; system design is now central
- •Compensation context: large stock grants and $1M+ total packages for elite AI PM roles
- •What interviewers test now: product judgment + technical/system design fluency
- •Preview of what the episode will demonstrate: a full mock system design response
- 1:00 – 1:18
Mock prompt setup: design a churn-reduction agent (scope + constraints)
The mock interview begins with the prompt to build a churn reduction agent. Aman immediately frames the need for clarifying questions to define churn, platforms, constraints, and success scope—reflecting real interview ambiguity.
- •Prompt: “Build the system design for a churn reduction agent”
- •Define churn broadly: engagement drop-off as leading indicator; payment stop as lagging indicator
- •Scope across platforms (mobile + desktop) with emphasis on revenue impact
- •Assume best-case resources; focus on ideal design rather than hard constraints
- 1:18 – 4:57
Clarifying questions that shape the problem (definition, platforms, goals)
Aman probes what churn means in this interview setting, what product context to assume, and whether there are any time/budget constraints. Aakash steers the conversation toward building a solid technical system and generating early warning signals for churn interventions.
- •Clarify churn definition and signals: engagement vs subscription/payment churn
- •Confirm platform breadth and relevance of platform-specific signals
- •Assume minimal constraints for interview purposes; optimize for ideal architecture
- •Primary objective: create proactive churn signals that enable intervention
- 4:57 – 6:14
Product vision choice: telecom mobile app + agentic customer support
Aman selects a concrete domain—telecommunications—to add realism and user texture. He frames the churn agent around an agentic AI customer-care experience embedded in a mobile app, setting up a structured approach from users to pain points to system design.
- •Pick a specific scenario to anchor decisions (telecom)
- •Target experience: mobile app with agentic AI pipeline to reduce churn
- •Proposed structure for the response: users → pain points/journey → solutions → system diagram → metrics
- •Interviewer alignment: specificity makes the system design discussion more grounded
- 6:14 – 7:40
User segmentation and choosing a primary target: power users
Aman outlines several segmentation approaches (new users, power users, B2B) and decides to prioritize power users as the primary segment. The reasoning: power users deliver disproportionate value and are strategically important to retain.
- •Segment options: tenure-based (new vs established), engagement-based (power), and B2B
- •Prioritization rationale: protect high-value, highly engaged users
- •Churn lens: losing power users is especially costly
- •Check-in with interviewer to validate segment focus before proceeding
- 7:40 – 9:12
User journey mapping: where churn risk emerges in customer-care experiences
Aman walks through a typical power-user journey involving customer support interactions and in-app engagement. He uses the journey to surface friction points that contribute to frustration and eventual churn.
- •Journey steps: call customer care → ticketing → follow-ups via email/chat → resolution → app usage
- •Telecom app context: service management plus benefits/upsells (e.g., Wi‑Fi add-ons)
- •Journey used as a systematic method to derive pain points
- •Customer-care moments are highlighted as key churn inflection points
- 9:12 – 13:35
Pain points and prioritization: focus on time/effort in customer care
Aman identifies major pain points—time-consuming customer-care interactions, fragmented cross-channel tracking, and irrelevant benefits. He prioritizes the customer-care time/effort pain point using alignment, frequency, and impact to decide what the agent should solve first.
- •Pain points: long/annoying customer-care interactions causing frustration and anxiety
- •Channel inconsistency: poor tracking of requests across call vs app creates confusion
- •Irrelevant benefits/offers reduce engagement and upsell potential
- •Prioritization framework: alignment to vision + frequency + impact → customer-care efficiency wins
- 13:35 – 14:22
From reactive support to proactive churn prevention: early warning signals + interventions
Aakash pushes for proactive detection—signals that indicate churn risk before users cancel. Aman connects this to a system that predicts churn risk and triggers interventions such as offers or faster issue resolution.
- •Goal shift: detect churn risk early rather than respond after repeated complaints
- •Predictive approach: bucket users by churn risk (e.g., red/green)
- •Interventions: targeted retention offers, prioritized handling, faster resolution
- •Bridge to solutioning: agent should combine prediction + action
- 14:22 – 16:52
Solution brainstorming: bot vs voice agent vs non-AI engagement levers
Aman explores multiple solution routes and chooses an end-to-end voice-based agentic assistant. The chosen direction emphasizes richer interaction (voice + screen/context) and proactive use of historical data to resolve issues and prevent churn.
- •Options considered: text bot from transcripts, voice bot, and non-AI gamification/benefits
- •Chosen approach: voice bot agent that can guide end-to-end resolution
- •Proactive features: use past data to anticipate churn and trigger offers
- •Acknowledged scope: MVP in ~6 months; fuller agent may take longer
- 16:52 – 21:25
Core AI system pillars: model, data, and memory (and what to store)
Aman introduces a foundational AI architecture frame—model, data, memory—and applies it to the churn agent. He emphasizes that data and contextual memory often matter more than the specific frontier model choice, especially for customer-care continuity.
- •Three pillars: model selection, data availability/quality, and memory strategy
- •Model: benchmark providers/models for voice experience; avoid over-fixating early
- •Data: call transcripts, app usage, network/service signals, competitor context, retention-offer catalog
- •Memory: prioritize episodic memory (past support conversations) vs storing everything
- 21:25 – 22:33
Latency and performance tradeoffs: user experience and safety valves
Aakash flags latency as a key pressure test for an interactive bot. Aman agrees and links performance to user satisfaction and operational safeguards, setting up later discussion on metrics and failure handling.
- •Latency is critical for voice/interactive experiences
- •Balance speed with accuracy; avoid annoying or unhelpful responses
- •Account for prompt injection and poor outputs as practical risks
- •Tie to measurement: response time + satisfaction indicators
- 22:33 – 26:08
System design walkthrough: orchestration layer + specialized agents + RAG/data layer
Aman sketches a high-level architecture: a client interaction layer (mobile/web) connected to an orchestration layer coordinating multiple agents. He proposes a data analyst agent, a customer-facing voice agent, and an executor agent that triggers actions like offers or human escalation, backed by RAG/vector retrieval and model APIs.
- •Interaction layer: mobile app (or web) as the user entry point
- •Orchestration layer: coordinates agent workflow and returns responses
- •Agent roles: data analyst (signals), customer voice agent (conversation), executor (actions/offers/escalation)
- •Data access: RAG/vector database + internal data stores; model APIs used as needed
- 26:08 – 27:22
Churn signals and model choice: LLM vs traditional ML (what interviewers want)
Aakash asks for deeper technical specificity on churn prediction and model selection. The conversation surfaces the expectation that candidates compare LLMs vs ML models for cost, interpretability, and adaptability—rather than staying purely conceptual.
- •Need: explicit churn-risk modeling approach (signals → score/bucket → interventions)
- •Interviewer expectation: explain LLM vs ML tradeoffs and choose intentionally
- •Example direction offered: use cheaper/interpretable ML (e.g., XGBoost) for churn scoring
- •Connect churn score to agent behavior (prioritize offers/escalation based on risk)
- 27:22 – 35:40
Metrics, evaluation, failure modes, and scaling to 10× traffic
Aman proposes evaluation across model quality, UX, and business impact, then outlines failure scenarios and scaling considerations. Topics include response-time thresholds, human handoff, robustness when models are down, and infrastructure/data bottlenecks at higher volume.
- •Metrics: model quality (hallucination/accuracy proxies), latency/response time, NPS/CSAT, resolution rate without escalation, retention/revenue
- •Failure modes: model downtime → immediate human handoff; slow responses → fallback; repetitive loops → escalate
- •Scaling: higher model throughput (possibly on-prem), vector DB for faster retrieval, memory optimization to reduce load
- •Operational readiness: testing/pressure checks as traffic grows from MVP to production
- 35:40 – 38:28
Post-mock feedback: time management, technical fluency, and delivery improvements
They step out of the mock interview to review what worked and what didn’t. Aakash emphasizes that strong performance requires crisp technical reasoning (especially around LLM vs ML decisions) and clean delivery, while maintaining structure and interviewer engagement.
- •Strengths: clarifying questions, structured approach, diagramming as a PM, handling ambiguity
- •Main improvement: technical fluency—state assumptions, compare options, articulate pros/cons
- •Example expectation: justify ML vs LLM for churn prediction with cost/black-box tradeoffs
- •Delivery coaching: reduce filler words, use pauses, keep interviewer engaged while presenting
- 38:28 – 40:40
Viewer takeaways and closing: engage the interviewer and practice under pressure
Aman and Aakash close with practical guidance: keep the interaction conversational, narrate your thinking, and be ready for tougher interviewers who challenge time management. The episode ends with calls to explore related mock interviews and follow/subscribe resources.
- •Engagement tip: avoid monologue—ask questions and narrate your thinking live
- •Execution tip: talk while diagramming/screen-sharing so reasoning is visible
- •Realism: some interviewers will be more pushy; manage time accordingly
- •Pointers to other mocks (AI product design/metrics/execution) and closing announcements
