The idea: every candidate must pass three critical barriers before an offer is made, after Stage 0 sets the role up correctly. These barriers test role fit, product thinking, functional strength, and team contribution. Each barrier ends with a clear pass/fail decision.
Stage 0 — Role Definition
Leader/Participant: Head of Product
Before opening any Product role:
- Write a job description clearly defining core responsibilities, scope of ownership, expected seniority and decision-making level, and key cross-functional partners.
- Define a role FAQ, including team context and reporting line, compensation range, contract type, and work schedule / timezone expectations.
- Align the interview process to real scenarios the candidate will face in the role.
- Clarify whether the role is primarily product management, product design, or another product function, so the technical review can be tailored appropriately.
Barrier 1 — Fit Screen
Leader/Participant: HR
Purpose: validate baseline fit for Plei, communication quality, professionalism, and alignment with the pace and expectations of the company. Duration: 30–40 minutes (video call).
Focus areas: motivation for joining Plei; communication clarity and professionalism; career goals and level fit; comfort working in a fast-moving, cross-functional environment; English fluency.
What we're evaluating: energy and motivation; clear communication; professional maturity; general culture fit.
Decision: Pass / Fail
Facilitator Guide for Barrier 1 – The Fit Screen (Culture & Ownership) Full guide
1. Purpose
Quickly assess cultural alignment, communication clarity, and ownership mindset. The goal is to filter early. Only candidates who clearly resonate with Plei’s mission, demonstrate ownership, and show a growth mindset should advance.
This barrier is intentionally similar across product management and product design because it is not evaluating craft depth yet. It is evaluating whether the candidate is likely to thrive at Plei.
2. Format
Length: 30–40 minutes (video call)
Facilitator: HR
Style: Conversational, structured, and warm. This is often the candidate’s first meaningful impression of Plei, so balance rigor with friendliness.
3. Focus Areas & Example Questions
3.1 Mission Resonance – “Why Plei?”
We want to know if they connect to our purpose: Building Connection Through the Beautiful Game.
- Tell me what excites you most about Plei and why you want to join us.
- How do you see soccer, or sports more broadly, shaping communities?
- What part of our mission resonates with you personally?
What to look for: Authentic excitement, some understanding of our mission, and motivation that goes beyond simply looking for a new role.
3.2 Ownership Mindset
We want people who take end-to-end responsibility, not people who stop at “I did my part.”
- Tell me about a time when you owned a project or initiative from start to finish. What did you learn?
- Have you ever spotted a problem that was not technically your responsibility but decided to fix or escalate it?
- Describe a time you failed or made a mistake. How did you handle it and what did you do next?
What to look for: Clear examples of ownership, accountability, initiative, and closing the loop.
3.3 Growth Mindset
We want people who learn fast, adapt, and take feedback well.
- What is a skill you have had to learn quickly to succeed in your role?
- Tell me about a time you received tough feedback. How did you respond?
- How do you stay up to date with new tools, practices, or changes in your field?
What to look for: Curiosity, humility, continuous improvement, and low defensiveness.
3.4 Communication
We want clear communication in English and the ability to work effectively in a cross-functional environment.
- Explain a complex project you worked on as if I were not familiar with the domain.
- Tell me about a time you had to work with cross-functional, distributed, or multicultural teammates. How did you make sure communication stayed clear?
What to look for: Clear, structured responses. Strong listening. The ability to explain ideas simply and adapt to the audience.
3.5 Product Environment Fit
We want candidates who are comfortable operating in a fast-moving, cross-functional product environment.
- What kind of team environment helps you do your best work?
- How do you operate when priorities are changing or information is incomplete?
- What kind of collaboration do you expect from engineering, design, product, data, or marketing partners?
What to look for: Comfort with ambiguity, collaboration, pace, and healthy pragmatism.
4. Evaluation Framework
Pass/Fail Decision – No “maybe.”
Scoring Dimensions (1–5):
- Mission Resonance – Do they connect to Plei’s purpose?
- Ownership – Do they take responsibility beyond their role?
- Growth Mindset – Do they learn fast and adapt?
- Communication – Can they express ideas clearly in English?
- Product Environment Fit – Are they likely to thrive in a fast-moving, cross-functional environment?
Candidate must score at least 3/5 in all dimensions to move forward. Any 1/5 is an automatic fail.
5. Facilitator Flow (Suggested Timeline)
- Welcome & Set Context (3 min) — quick intro of yourself and Plei. Explain the purpose: “This call is about getting to know you better and understanding how you align with our mission and culture.”
- Candidate Introduction (5 min) — “Tell me about yourself and your journey so far.”
- Mission Resonance (5–7 min)
- Ownership (8–10 min)
- Growth Mindset (5–7 min)
- Communication & Product Environment Fit (throughout the call)
- Candidate Questions (3–5 min)
- Wrap Up (2 min) — explain next steps and thank them for their time.
6. Notes for Interviewer
- Write detailed notes in ClickUp immediately after the call.
- Avoid vague comments like “seems nice” or “smart.” Be specific about evidence.
- Remember that this screen is about raising the bar, not just moving candidates forward.
- Do not over-index on polish alone. Look for substance, self-awareness, and evidence of ownership.
Barrier 2 — Product Fundamentals
Leader/Participant: Head of Product
Purpose: understand the candidate's product mindset, functional background, motivations, and potential fit within the Product team. Duration: 45–60 minutes (video call). Format: structured interview.
Evaluation focus:
- Mindset & motivations: why they want this role, what kinds of problems energize them, how they think about impact, users, and business outcomes.
- Background & functional strength: relevant experience and pattern recognition, strengths built over time, unique skills or perspectives.
- Team fit: collaboration style, self-awareness, ability to work across design, engineering, and growth teams.
- Judgment: how they prioritize, handle ambiguity, and balance speed, quality, and learning.
What we're evaluating: product judgment, relevant background experience, history of impact, agency, collaboration.
Decision: Pass / Fail
Facilitator Guide for Barrier 2 – Product Team Fit & Mindset Full guide
1. Purpose
Understand whether the candidate is a strong fit for the Product team specifically. This interview should help answer whether they bring the relevant experience, mindset, judgment, and communication style to succeed at Plei.
This is not a technical interview and it is not a portfolio review. The goal is to learn how they think, how they work, what kinds of problems they are best suited for, and whether they are likely to be an effective teammate in our environment.
2. Format
Length: 45–60 minutes (video call)
Facilitator: Head of Product
Style: Conversational but structured. The interview should feel thoughtful and probing, while still creating space for the candidate to reflect and be themselves.
3. Focus Areas & Example Questions
3.1 Motivation & Role Fit
We want to understand why they want this role, why now, and whether their interests match the opportunity.
- What interested you in this role specifically?
- Why does this role feel like the right next step for you?
- What kinds of product or design problems energize you the most?
- What kind of environment helps you do your best work?
What to look for: Thoughtful motivation, self-awareness, and a clear connection between their strengths and the role.
3.2 Relevant Experience
We want to understand whether they have worked on problems that are meaningfully relevant to what we need.
- Tell me about the work you have done that feels most relevant to this role.
- What types of users, products, or business problems have you spent the most time on?
- What have you learned from the environments you have worked in before?
- What is a product or initiative you are especially proud of, and why?
What to look for: Relevant patterns, good judgment about what matters, and evidence that their background could transfer well to Plei.
3.3 Product Mindset & Judgment
We want to understand how they think about users, outcomes, tradeoffs, and decision-making.
- When you are approaching a new problem, where do you usually start?
- How do you decide what matters most when there are many competing inputs?
- Tell me about a time you had to make a decision with incomplete information.
- How do you think about balancing speed, quality, and learning?
What to look for: Structured thinking, pragmatism, comfort with ambiguity, and signs of good product judgment.
3.4 Collaboration & Team Fit
We want to know what kind of teammate they are and how they work with partners across functions.
- What does great collaboration with engineering, design, product, data, or growth look like to you?
- Tell me about a time you disagreed with a cross-functional partner. How did you handle it?
- What kind of manager or team setup helps you thrive?
- How do you build trust with teammates?
What to look for: Maturity, low ego, strong collaboration instincts, and the ability to work well across functions.
3.5 Communication
We want clear communication, strong listening, and the ability to explain ideas in a simple and convincing way.
- Explain a product decision you were involved in and walk me through the reasoning behind it.
- Tell me about a time you had to align others around a point of view.
- How do you adapt your communication when speaking with different audiences?
What to look for: Clarity, structure, strong listening, and an ability to communicate nuance without becoming vague.
3.6 Self-Awareness & Growth
We want candidates who understand their strengths, are honest about their gaps, and show evidence of learning.
- What are you best at today?
- What are you still developing?
- Tell me about a piece of feedback that changed how you work.
- What have you changed your mind about in product or design over the last few years?
What to look for: Reflection, humility, coachability, and evidence of growth over time.
4. Evaluation Framework
Pass/Fail Decision – No “maybe.”
Scoring Dimensions (1–5):
- Role Fit – Do their motivations and strengths match the role?
- Relevant Experience – Have they built experience that transfers well to our needs?
- Product Mindset & Judgment – Do they show strong thinking about users, outcomes, and tradeoffs?
- Collaboration & Team Fit – Are they likely to be a strong cross-functional teammate?
- Communication – Can they express ideas clearly and thoughtfully?
- Self-Awareness & Growth – Do they show maturity, reflection, and coachability?
Candidate must score at least 3/5 in all dimensions to move forward. Any 1/5 is an automatic fail.
5. Facilitator Flow (Suggested Timeline)
- Welcome & Set Context (3–5 min) — brief intro and framing. Explain that this conversation is about learning more about their background, mindset, and fit with the Product team.
- Candidate Introduction (5 min) — “Tell me about yourself and your path so far.”
- Motivation & Role Fit (8–10 min)
- Relevant Experience (10 min)
- Product Mindset & Judgment (10–12 min)
- Collaboration, Communication, and Growth (10–12 min)
- Candidate Questions (5 min)
- Wrap Up (2 min) — explain next steps and thank them for their time.
6. Notes for Interviewer
- Write detailed notes immediately after the interview.
- Focus on specific evidence, not general impressions.
- Avoid drifting into technical craft assessment. Save portfolio review, case discussion, and deep functional evaluation for Barrier 3.
- This round should answer: Would I want this person on the Product team? Do they seem like someone with the right mindset, communication style, and transferable experience to succeed here?
7. Role-Specific Note
This guide should work for both product management and product design candidates. The questions can be tailored slightly depending on the role:
- For product management candidates, lean a bit more into prioritization, decision-making, and stakeholder judgment.
- For product design candidates, lean a bit more into collaboration, user empathy, and how they approach ambiguous problems.
Still, this should remain a fit and judgment interview, not a technical or craft deep dive.
Barrier 3 — Technical Review / Case Study
Leader/Participant: Product manager for PM roles, designer for design roles, plus Head of Product for the final presentation
Purpose: assess day-to-day functional capability, problem solving, communication, and execution under time pressure. Duration: approximately 2 hours total (video + async). Format: two-part interview conducted as one barrier.
Part 1 — Functional technical interview (first 30 minutes): assesses technical and functional depth in the candidate's craft — for PM roles: product sense, prioritization, roadmap thinking, stakeholder management, analytical reasoning; for design roles: portfolio walkthrough, design process, UX judgment, visual and interaction thinking, collaboration with product and engineering.
Part 2 — Live case study: 60 minutes of asynchronous working time on a project brief, followed by a presentation and discussion with the interviewer and Head of Product. Evaluates problem framing, structure and clarity of thinking, speed under limited time, decision-making under pressure, communication of trade-offs, and quality of the final output.
Decision for the full barrier: Pass / Fail
Facilitator Guide for Barrier 3 – Product Management Technical Interview & Case Presentation Full guide
1. Purpose
Assess whether the candidate can perform the day-to-day work of a strong product manager at Plei. This barrier is split into two parts: a short technical interview focused on product management craft, and a case exercise that tests how the candidate approaches a realistic product problem under time constraints. Together, these two parts should answer whether the candidate has the functional skills, product judgment, communication ability, and execution style needed for the role.
2. Format
Total Duration: Approximately 2 hours
Part 1: 30-minute live technical interview
Part 2: 60-minute asynchronous case working session followed by a 30-minute live presentation and Q&A
Facilitators: Part 1 — Product Manager. Part 2 — Product Manager + Head of Product.
3. What This Barrier Is Evaluating
- Product judgment
- Prioritization and tradeoff thinking
- Problem framing
- Decision-making under ambiguity
- Communication and stakeholder reasoning
- Ability to think through and shape strong AI-powered product experiences
- Ability to produce a clear and useful deliverable under time pressure
This barrier is not intended to test perfect polish. The goal is to understand how the candidate thinks, what they focus on, and how effectively they can make progress with limited time.
4. Part 1 – Technical Interview
Purpose: Use this section to go deeper on the candidate’s product management craft. This is where the facilitator should probe how they make decisions, prioritize work, work with partners, and think about outcomes.
Duration: 30 minutes
4.1 Product Sense
- Tell me about a product decision you are proud of. Why was it the right decision?
- How do you identify whether a problem is worth solving?
- How do you think about user value versus business value?
What to look for: Sound judgment, clarity of thinking, and a strong understanding of how to create value.
4.2 Prioritization & Tradeoffs
- Tell me about a time when you had to choose between several worthwhile opportunities. How did you decide?
- How do you handle pressure from multiple stakeholders who all want different things?
- How do you decide when something is good enough to ship?
What to look for: Structured prioritization, pragmatism, and thoughtful tradeoff reasoning.
4.3 Execution & Collaboration
- How do you work with engineering and design when there is disagreement on scope or approach?
- Tell me about a time execution went off track. What did you do?
- What does strong product management look like during implementation, not just planning?
What to look for: Ownership, cross-functional maturity, and practical execution instincts.
4.4 Metrics & Learning
- How do you know whether a product decision worked?
- Tell me about a time data changed your perspective.
- How do you make progress when the data is incomplete or noisy?
What to look for: Comfort with evidence, learning orientation, and balanced use of qualitative and quantitative inputs.
4.5 AI Product Thinking
- If you were asked to build an AI-powered product experience, how would you decide whether AI should be part of the solution at all?
- What do you think makes an AI feature genuinely useful to users versus just a gimmick?
- How would you think about reliability, trust, and failure modes when shipping an AI product experience?
- What should a product manager understand about prompts, models, context, evaluation, or feedback loops when working on AI products?
What to look for: Product judgment about when AI is useful, awareness of limitations and failure modes, and enough fluency to help shape AI products thoughtfully with design and engineering.
5. Part 2 – Case Exercise + Presentation
Purpose: See how the candidate approaches a realistic product problem in a limited amount of time, and how effectively they communicate their thinking back to others.
Format:
- The candidate receives a case brief.
- The candidate works independently for 60 minutes.
- The candidate returns for a 30-minute presentation and Q&A with the Product Manager and Head of Product.
What the Candidate Should Deliver — a lightweight deliverable that helps explain:
- how they framed the problem
- what assumptions they made
- what solution or recommendation they arrived at
- what tradeoffs they considered
- whether and how AI should be part of the product experience, and what tradeoffs or risks that introduces
- what they would do next
The deliverable format can vary. We are not evaluating slide design. We are evaluating clarity and substance.
What to Look For During the Presentation
5.1 Problem Framing — Did they correctly identify the core problem? Did they make sensible assumptions? Did they focus on what matters most?
5.2 Structure of Thinking — Is their approach organized and easy to follow? Did they break the problem into useful parts? Did they avoid jumping to solutions too quickly?
5.3 Judgment & Tradeoffs — Did they make good decisions with limited time? Did they acknowledge tradeoffs and constraints? Did they show pragmatism rather than perfectionism? If they incorporated AI into their thinking, did they do so in a way that felt useful, realistic, and grounded in user value?
5.4 Communication — Can they explain their reasoning clearly? Can they respond thoughtfully to questions? Can they defend their point of view without becoming rigid?
5.5 Quality of Output — Is the final deliverable clear and useful? Is it appropriately scoped for the time available? Does it reflect the level of the role?
6. Evaluation Framework
Pass/Fail Decision – No “maybe.”
Scoring Dimensions (1–5):
- Product Judgment – Do they make strong decisions and reason well about users, business, and tradeoffs?
- Prioritization – Can they identify what matters most?
- Execution Thinking – Do they show practical instincts about shipping and implementation?
- Analytical Reasoning – Can they use evidence and logic effectively?
- AI Product Judgment – Can they reason clearly about where AI creates real user value, what it takes to ship responsibly, and what risks or limitations must be managed?
- Communication – Can they explain ideas clearly and handle Q&A well?
- Case Output Quality – Did they produce a strong deliverable for the time available?
Candidate must score at least 3/5 in all dimensions to move forward. Any 1/5 is an automatic fail.
7. Facilitator Flow
Part 1 – Technical Interview
- Intro & context setting (2–3 min)
- Product sense and prioritization questions (10–12 min)
- Execution and collaboration questions (8–10 min)
- Metrics, learning, and AI product thinking questions (5–7 min)
- Transition to case exercise (1–2 min)
Part 2 – Case Exercise & Presentation
- Share case brief and instructions
- Candidate works independently for 60 minutes
- Candidate presents for 20–25 minutes
- Q&A and probing discussion for 5–10 minutes
8. Notes for Interviewers
- Evaluate the quality of the candidate’s thinking, not whether it matches your exact preferred answer.
- Do not over-reward polished presentation if the substance is weak.
- Do not over-penalize rough formatting if the thinking is strong.
- Keep in mind the time constraint. Strong candidates should show prioritization and judgment, not completeness.
- Written feedback should be specific and submitted before the final debrief.
9. Case Options
Use one of the following case briefs for Part 2 of this barrier. Both cases are intentionally generic and are designed to test how candidates turn messy inputs into a prioritization decision, project framing, and a clear recommendation.
PM Case Option 1 – Growth Opportunity Prioritization Case brief
1. Purpose
This case is designed to evaluate how a product manager turns messy inputs into a clear prioritization decision. The candidate should show how they synthesize stakeholder perspectives, product data, and business context into a well-reasoned recommendation.
This is intentionally a generic product problem. The goal is not to do free work for Plei. The goal is to assess judgment, prioritization, communication, and the ability to define a strong project brief.
2. Candidate Prompt
You are a product manager at Stayzy, a two-sided marketplace for booking short-term stays and weekend getaways. The company has strong brand awareness in a few major cities and is trying to improve how effectively new users become active bookers.
Over the last quarter, growth has slowed. The team has surfaced several possible opportunities, but there is no alignment yet on what should be prioritized next.
You have one hour to review the context below and prepare a short project brief recommending one priority opportunity that the team should work on now. You do not need to design the full solution. Focus on identifying the most important opportunity, explaining why it should be prioritized, and outlining a high-level solution approach.
3. Company Context
About the Company: Stayzy helps travelers discover and book short-term stays for weekend trips, work travel, and local getaways. Supply is healthy in the company’s top markets, but leadership believes demand-side activation is now the biggest bottleneck.
Business Context: The company makes money when users complete a booking. Users who book once are far more likely to return and become repeat customers over time. Because of that, helping new users reach their first successful booking experience is a major company priority.
4. Context
Stakeholder Inputs
- The Head of Growth believes the biggest opportunity is improving new user activation because too many users drop off in their first few sessions.
- The Head of Operations believes support volume is increasing because users are confused during key journeys, and that reducing friction in the experience should be the top priority.
- A senior executive is pushing for a visible new feature because they believe the product needs more differentiation in the market.
- Engineering says the team has limited bandwidth over the next 6–8 weeks, so the next project should be relatively focused.
User Signals
- New users often complete account setup but do not reach their first meaningful success moment.
- Returning users who do succeed early tend to come back repeatedly over the following month.
- Qualitative feedback suggests some users find the early experience confusing and are not always sure what to do next.
Product Data
- case1_growth_user_signups.csv (1.1 MiB)
- Support tickets related to onboarding confusion have increased 25% over the last two months.
- A recently launched premium feature has very low adoption among new users.
Constraints
- The team can only take on one medium-sized project this cycle.
- The team wants a project that can show measurable impact within 6–10 weeks.
- You do not need to assume any additional research beyond what is listed here, but you may state reasonable assumptions.
5. Deliverable
Prepare a short project brief that covers:
- What is the problem, and why is it worth solving now?
- What is the desired impact of working on this project?
- How will we tangibly measure success?
- What is the experimentation plan?
- What high-level solution approach might your consider?
6. What We Are Looking For
- How clearly you identify the most important opportunity
- How well you synthesize conflicting stakeholder input
- Whether you prioritize based on likely user and business impact rather than title or opinion alone
- How effectively you use the available data
- How clearly you define success and an experimentation plan
- How practical and focused your proposed approach is
7. Notes for Facilitators
Strong candidates will usually:
- identify activation as the most leveraged problem to solve
- connect early user behavior to retention and business impact
- avoid getting distracted by louder stakeholder opinions without evidence
- define a focused and testable first step rather than a broad transformation
- show that they can make a decision even with incomplete information
What Strong Exploration of the CSV Might Surface
The attached CSV is user-level, not pre-aggregated, so candidates need to group and calculate rather than read a number off a slide. Roughly what’s in there:
- The topline funnel rolls up to account creation ~72%, activation ~37%, second key action ~17%, matching the original case narrative, but only if they aggregate correctly.
- Activation rate varies a lot by acquisition channel: Referral sits highest at ~53%, while Influencer is lowest at ~25%, with Paid Social and App Store Organic in between. A candidate who cuts by channel can make a sharper case that not all signups are equally likely to activate, which has implications for both the activation fix and where marketing spend goes.
- Activation also varies by device (iOS ~41% vs Android ~32%), which is a smaller but real secondary cut.
- Day-30 retention is roughly 3x higher for activated users than non-activated users, reinforcing the case’s framing, and this is independently verifiable from the raw data rather than asserted.
- Premium feature adoption is very low across the board (roughly 2–3% of all signups), which supports deprioritizing the executive’s “flashy new feature” pitch.
We don’t expect candidates to find every cut above. What we’re looking for is whether they go beyond the topline percentages at all, whether they sanity-check a stakeholder claim against the data instead of taking it at face value, and whether the slicing they choose actually changes or strengthens their recommendation, rather than slicing for its own sake.
There is no single perfect answer. The point is to evaluate prioritization quality and reasoning, not whether the candidate matches a predetermined solution exactly.
PM Case Option 2 – Retention Opportunity Prioritization Case brief
1. Purpose
This case is designed to evaluate how a product manager evaluates multiple signals, identifies the most important retention problem, and turns that into a focused project recommendation.
The candidate should show how they synthesize user behavior data, stakeholder input, and product constraints into a clear prioritization decision and project brief.
This is intentionally a generic product problem. The goal is not to do free work for Plei. The goal is to assess judgment, prioritization, communication, and the ability to define a strong project brief.
2. Candidate Prompt
You are a product manager at GoLoco, a two-sided marketplace for booking local experiences, classes, and small group activities. User acquisition remains healthy, but retention has flattened and leadership wants the team to focus on improving long-term engagement.
You have one hour to review the context below and prepare a short project brief recommending one priority opportunity that the team should work on now. You do not need to design the full solution. Focus on identifying the most important opportunity, explaining why it should be prioritized, and outlining a high-level solution approach.
3. Company Context
About the Company: GoLoco helps people discover and book local activities like fitness classes, workshops, food tours, and social events. The company’s strongest users tend to come back regularly once they find a routine that fits their lifestyle.
Business Context: The company makes money when users complete bookings, and long-term retention increases significantly when users build a repeat habit early. Leadership believes the current challenge is less about top-of-funnel acquisition and more about helping users become regular customers.
4. Context
Stakeholder Inputs
- The Growth team believes the biggest opportunity is improving notifications and re-engagement messaging.
- The Research lead believes users do not experience enough value in the first two weeks and that the core product experience needs to be improved.
- Customer Support believes users are churning because billing and plan expectations are confusing.
- A senior executive wants the team to launch a community feature because competitors have one.
User Signals
- Many users complete initial setup and try the product once or twice, but never build a repeat habit.
- Users who engage with the product at least 4 times in their first 14 days are much more likely to remain active after 60 days.
- Some qualitative feedback suggests that users do not always understand what success with the product looks like.
- Other feedback suggests that users forget to come back unless something prompts them.
Product Data
- case2_retention_user_engagement.csv (691 KiB)
- Notification open rates are moderate, but downstream re-engagement is inconsistent.
- Support tickets about billing confusion represent 12% of all tickets, but most churned users never contacted support.
Constraints
- The team can only take on one medium-sized project this cycle.
- Leadership wants measurable movement within one quarter.
- You do not need to assume any additional research beyond what is listed here, but you may state reasonable assumptions.
5. Deliverable
Prepare a short project brief that covers:
- What is the problem, and why is it worth solving now?
- What is the desired impact of working on this project?
- How will we tangibly measure success?
- What is the experimentation plan?
- What high-level solution approach might your consider?
6. What We Are Looking For
- How clearly you identify the most important retention opportunity
- How well you synthesize conflicting stakeholder input
- Whether you prioritize based on user and business impact rather than seniority or opinion alone
- How effectively you use the available data
- How clearly you define success and a test plan
- How practical and focused your proposed approach is
7. Notes for Facilitators
Strong candidates will usually:
- identify early habit formation as the key problem rather than jumping to a feature request
- connect repeat engagement behavior to long-term retention
- show discernment about symptoms versus root causes
- avoid overfitting to the loudest stakeholder perspective
- define a focused intervention and measurable test instead of a large vague initiative
What Strong Exploration of the CSV Might Surface
The attached CSV is subscriber-level, not pre-aggregated, so candidates need to group and calculate rather than read a number off a slide. Roughly what’s in there:
- The topline funnel rolls up to setup ~55%, week-1 engagement ~46%, 4+ sessions in 14 days ~20%, day-60 retention ~14%, close to the original case narrative, but only if they aggregate correctly.
- Among users who completed setup, those who hit 4+ sessions in the first 14 days retain at roughly 43% by day 60, versus roughly 16% for setup-complete users who didn’t, a gap of about 2.7x. This directly supports the habit-formation framing, and a careful candidate should compute this ratio against the right denominator (setup-complete users) rather than the full population, which would overstate the gap.
- Habit formation (4+ sessions in 14 days) varies by acquisition source: Referral is highest at ~31%, Paid is lowest at ~12%, with Organic and Partnership in between. This is a useful secondary cut but a distraction from the core recommendation if a candidate over-indexes on it.
- Billing-related tickets are about 12% of all support tickets, matching the case narrative, but only about 15% of churned users contacted support at all. A candidate who checks this should conclude billing confusion can’t be the primary churn driver for the broader user base, since most churners never engaged with support in the first place.
- Notification open rates land around 34%, which is moderate, supporting the case’s framing that notifications alone aren’t the core problem.
We don’t expect candidates to find every cut above. What we’re looking for is whether they go beyond the topline percentages at all, whether they use the support ticket data correctly to rule out the billing theory rather than assume it, and whether the slicing they choose actually changes or strengthens their recommendation, rather than slicing for its own sake.
There is no single perfect answer. The point is to evaluate prioritization quality and reasoning, not whether the candidate matches a predetermined solution exactly.
Facilitator Guide for Barrier 3 – Product Design Technical Interview & Case Presentation Full guide
1. Purpose
Assess whether the candidate can perform the day-to-day work of a strong product designer at Plei. This barrier is split into two parts: a short technical interview focused on product design craft, and a case exercise that tests how the candidate approaches a realistic design problem under time constraints. Together, these two parts should answer whether the candidate has the functional skills, design judgment, communication ability, and collaboration style needed for the role.
2. Format
Total Duration: Approximately 2 hours
Part 1: 30-minute live technical interview
Part 2: 60-minute asynchronous case working session followed by a 30-minute live presentation and Q&A
Facilitators: Part 1 — Product Designer. Part 2 — Product Designer + Head of Product.
3. What This Barrier Is Evaluating
- Design judgment
- User empathy and problem framing
- Interaction and experience thinking
- Collaboration and communication
- Ability to think through and shape strong AI-powered product experiences
- Ability to produce a clear and useful deliverable under time pressure
- Reasoning behind design choices and tradeoffs
This barrier is not intended to test perfect polish. The goal is to understand how the candidate thinks, what they prioritize, and how effectively they can make progress with limited time.
4. Part 1 – Technical Interview
Purpose: Use this section to go deeper on the candidate’s product design craft. This is where the facilitator should probe how they approach problems, make design decisions, collaborate with partners, and think about user experience.
Duration: 30 minutes
4.1 Design Process
- Walk me through how you typically approach a new product problem.
- How do you move from ambiguity to a clear design direction?
- How do you know when you are ready to explore solutions?
What to look for: Structured process, comfort with ambiguity, and thoughtful problem framing.
4.2 User Experience Judgment
- Tell me about a product experience you designed that you are proud of. What made it successful?
- How do you balance user needs with business goals and technical constraints?
- How do you decide what level of fidelity or detail is needed at a given stage?
What to look for: Strong UX instincts, judgment, and practical tradeoff thinking.
4.3 Collaboration & Feedback
- How do you work with product managers and engineers when there is disagreement on direction?
- Tell me about a time feedback changed your design approach.
- What does strong collaboration look like during implementation?
What to look for: Low ego, strong collaboration habits, and openness to iteration.
4.4 Systems Thinking & Craft
- How do you think about consistency across experiences without becoming too rigid?
- When do you optimize for speed versus craft?
- How do you make sure details that matter to users are not lost during execution?
What to look for: Good design instincts, practical craft judgment, and a balanced view of quality.
4.5 AI Product Thinking
- If you were designing an AI-powered product experience, how would you decide whether AI should be part of the solution?
- What do you think makes an AI feature genuinely helpful to users versus confusing or gimmicky?
- How would you design for trust, transparency, and recovery when an AI system gets something wrong?
- What should a product designer understand about model limitations, context, and failure modes when designing AI products?
What to look for: Strong user-centered thinking about AI products, awareness of failure modes, and enough fluency to design experiences that make AI useful, trustworthy, and easy to understand.
5. Part 2 – Case Exercise + Presentation
Purpose: See how the candidate approaches a realistic design problem in a limited amount of time, and how effectively they communicate their reasoning back to others.
Format:
- The candidate receives a case brief.
- The candidate works independently for 60 minutes.
- The candidate returns for a 30-minute presentation and Q&A with the Product Designer and Head of Product.
What the Candidate Should Deliver — a lightweight deliverable that helps explain:
- how they framed the problem
- what assumptions they made
- what user needs they prioritized
- what solution direction they chose
- what tradeoffs they considered
- whether and how AI should be part of the product experience, and what tradeoffs or risks that introduces
- what they would refine or test next
The deliverable format can vary. We are not evaluating polished visuals alone. We are evaluating clarity, reasoning, and usefulness.
What to Look For During the Presentation
5.1 Problem Framing — Did they correctly identify the core user problem? Did they make sensible assumptions? Did they focus on the most important needs and constraints?
5.2 User-Centered Thinking — Did they demonstrate empathy for users? Did they think clearly about user flows, friction, and decision points? Did they balance desirability, feasibility, and business value?
5.3 Structure of Thinking — Is their approach organized and easy to follow? Did they break the problem into useful parts? Did they make clear choices rather than trying to solve everything?
5.4 Design Judgment & Tradeoffs — Did they make strong design decisions for the time available? Did they acknowledge tradeoffs and constraints? Did they show pragmatism rather than perfectionism? If they incorporated AI into their thinking, did they do so in a way that felt useful, realistic, and grounded in user value?
5.5 Communication — Can they explain their reasoning clearly? Can they respond thoughtfully to questions? Can they defend their point of view without becoming rigid?
5.6 Quality of Output — Is the final deliverable clear and useful? Is it appropriately scoped for the time available? Does it reflect the level of the role?
6. Evaluation Framework
Pass/Fail Decision – No “maybe.”
Scoring Dimensions (1–5):
- Design Judgment – Do they make strong design decisions and reason well about users, constraints, and outcomes?
- Problem Framing – Can they define the right problem before jumping to solutions?
- User Experience Thinking – Do they demonstrate empathy and strong experience design instincts?
- Collaboration – Do they show healthy instincts for working across functions?
- AI Product Judgment – Can they reason clearly about where AI creates real user value, how to design for trust and failure, and what risks or limitations must be managed?
- Communication – Can they explain ideas clearly and handle Q&A well?
- Case Output Quality – Did they produce a strong deliverable for the time available?
Candidate must score at least 3/5 in all dimensions to move forward. Any 1/5 is an automatic fail.
7. Facilitator Flow
Part 1 – Technical Interview
- Intro & context setting (2–3 min)
- Design process and UX judgment questions (10–12 min)
- Collaboration and feedback questions (8–10 min)
- Systems thinking, craft, and AI product thinking questions (5–7 min)
- Transition to case exercise (1–2 min)
Part 2 – Case Exercise & Presentation
- Share case brief and instructions
- Candidate works independently for 60 minutes
- Candidate presents for 20–25 minutes
- Q&A and probing discussion for 5–10 minutes
8. Notes for Interviewers
- Evaluate the quality of the candidate’s thinking, not whether the solution matches your exact preference.
- Do not over-reward polished visuals if the reasoning is weak.
- Do not over-penalize rough output if the design thinking is strong.
- Keep in mind the time constraint. Strong candidates should show prioritization, judgment, and clarity, not completeness.
- Written feedback should be specific and submitted before the final debrief.
9. Case Options
Use one of the following case briefs for Part 2 of this barrier. Both cases are intentionally generic but grounded in a specific company context, and are designed to test how candidates interpret a product brief, work within constraints, move quickly, and communicate a strong solution direction.
Design Exercise Option 1 Case brief
The Scenario
Imagine you’ve recently joined Stayzy, a marketplace for booking short-term stays and weekend getaways.
The company has experienced healthy user growth, but leadership has identified a problem: too many new users create an account but never complete their first booking.
Because users who successfully book once are significantly more likely to return, improving activation has become one of the company’s highest priorities this quarter. Engineering has capacity for one medium-sized initiative over the next six-week development cycle.
Your Product Manager asks you to evaluate the opportunity and recommend where the team should focus.
Business Goal
Increase the percentage of new users who successfully complete their first booking and improve early retention.
Customer Context
Stayzy primarily serves people booking short-term accommodations for leisure travel, weekend getaways, and occasional business trips.
Most new users are already familiar with digital booking experiences through products like Airbnb or Booking.com. They expect a modern, intuitive experience and generally want to complete their booking with minimal effort.
This opportunity focuses specifically on new users during their first experience with the product.
What We Know
The following information has been gathered from existing research and product data.
Research
- Interviews suggest many new users aren’t sure what to do immediately after creating an account.
- Some users say the product feels promising but they struggle to understand how to get value quickly.
- Users who complete their first booking are significantly more likely to return.
Product Signals
- Product analytics show a meaningful percentage of users leave during their first session.
- Support tickets frequently reference confusion during the initial experience.
Team Context
- Leadership believes improving activation is the highest-leverage opportunity this quarter.
- Engineering can support one medium-sized initiative (roughly 3–4 weeks).
- The team wants measurable impact within one quarter.
What We Don’t Know
The team has not yet determined:
- Whether the primary issue is lack of guidance, insufficient trust, poor discoverability, or another factor.
- Which point in the first-session experience contributes most to abandonment.
- Whether the problem affects all new users equally or only specific segments.
- Whether improving activation requires reducing friction, providing better guidance, or rethinking the overall first-time experience.
As with most product opportunities, the available information is incomplete. You’re encouraged to make reasonable assumptions where necessary, but be prepared to explain them.
Assumptions
Since there is no existing product provided, assume Stayzy already supports the core marketplace experience, including: account creation, browsing listings, property detail pages, and booking accommodations. You may make additional reasonable assumptions where necessary. If you do, explain them during your presentation.
Your Task
Prepare a recommendation for how you believe the team should approach this opportunity. Your presentation should help us understand:
1. Problem Framing — What problem do you believe is worth solving? Why is this the highest-priority opportunity? What assumptions are you making?
2. Opportunity — What initiative would you recommend? Why this direction instead of other possible solutions?
3. Experience Strategy — Describe the experience you would create. You may communicate this however you feel is most effective — diagrams, user flows, journey maps, simple sketches, storyboards, low-fidelity wireframes, slides, or written frameworks. We are not evaluating visual polish. Use whatever artifacts best communicate your thinking.
4. Tradeoffs — What would you intentionally leave out of the first version? Why?
5. Validation — How would you measure success? What would you want to learn after launch? What risks or assumptions would you continue validating?
Time Expectations
You’ll have 60 minutes to prepare. Afterward, you’ll present your recommendation and discuss your thinking with the interview team. Expect the discussion to be collaborative. Interviewers may introduce additional constraints or ask follow-up questions to better understand how you think through new information.
Design Exercise Option 2 Case brief
The Scenario
Imagine you’ve recently joined GoLoco, a marketplace for booking local experiences, classes, and small group activities.
The company has seen steady growth in traffic and first-time browsing, but leadership has identified a problem: many users explore several options but leave without booking because they feel unsure which activity is right for them.
The team believes AI might help users compare options, narrow choices, and move forward with more confidence, but it is not yet clear where AI would create the most value. Engineering has capacity for one medium-sized initiative over the next six-week development cycle.
Your Product Manager asks you to evaluate the opportunity and recommend where the team should focus.
Business Goal
Increase booking conversion among consideration-stage users by helping them choose the right activity faster and with more confidence.
Customer Context
GoLoco serves people looking for local activities such as fitness classes, food tours, workshops, outdoor experiences, and social events.
Many users come to the platform with a general goal in mind, such as finding something fun for the weekend, planning an outing with friends, or trying a new activity, but they are often unsure which option best fits their needs.
This opportunity focuses specifically on users who show intent by exploring multiple experiences but have not yet decided what to book.
What We Know
The following information has been gathered from existing research and product data.
Research
- Interviews suggest users often feel overwhelmed when several options seem similarly appealing.
- Some users say they want help understanding the differences between experiences without having to read every listing in detail.
- Users respond positively to guided recommendations when they feel relevant and trustworthy.
Product Signals
- Product analytics show many users visit multiple experience pages in a single session but do not complete a booking.
- Session replays and support conversations suggest some users hesitate because they do not feel confident choosing between similar options.
Team Context
- Leadership believes this is a promising area to explore because improving decision confidence could increase conversion without requiring more supply.
- Engineering can support one medium-sized initiative (roughly 3–4 weeks).
- The team wants measurable impact within one quarter.
What We Don’t Know
The team has not yet determined:
- Whether AI is actually the best way to solve this problem or whether a simpler product change would work better.
- Which moment in the decision-making journey is the best place to introduce AI assistance.
- Whether users would trust AI-generated guidance enough to act on it.
- What kind of support would matter most, such as comparison, summarization, recommendations, or guided questions.
- How much transparency and user control are needed for the experience to feel helpful instead of intrusive.
As with most product opportunities, the available information is incomplete. You’re encouraged to make reasonable assumptions where necessary, but be prepared to explain them.
Assumptions
Since there is no existing product provided, assume GoLoco already supports the core marketplace experience, including: account creation, browsing activities, activity detail pages, and booking experiences. You may make additional reasonable assumptions where necessary. If you do, explain them during your presentation.
Your Task
Prepare a recommendation for how you believe the team should approach this opportunity. Your presentation should help us understand:
1. Problem Framing — What problem do you believe is worth solving? Why is this the highest-priority opportunity? What assumptions are you making?
2. Opportunity — What initiative would you recommend? Why this direction instead of other possible solutions?
3. Experience Strategy — Describe the experience you would create. You may communicate this however you feel is most effective — diagrams, user flows, journey maps, simple sketches, storyboards, low-fidelity wireframes, slides, or written frameworks. We are not evaluating visual polish. Use whatever artifacts best communicate your thinking.
4. Tradeoffs — What would you intentionally leave out of the first version? Why?
5. Validation — How would you measure success? What would you want to learn after launch? What risks or assumptions would you continue validating?
Time Expectations
You’ll have 60 minutes to prepare. Afterward, you’ll present your recommendation and discuss your thinking with the interview team. Expect the discussion to be collaborative. Interviewers may introduce additional constraints or ask follow-up questions to better understand how you think through new information.
Final Decision & Debrief
Leaders/Participants: HR + Head of Product + functional interviewer(s)
- Debrief within 24 hours of the final interview.
- Written feedback submitted before the live debrief.
- Each interviewer makes a clear recommendation.
- The final decision reflects both role-specific strength and overall team fit.
- If approved, move quickly to close the candidate.