7 days left in your free trial.

Career Explorer

Try a real day-in-the-life before you commit. 12 minutes. No experience required.

Product Manager
12 min simulation
Strategy User Research Prioritization
Marketing Strategist
~14 min simulation
Brand Strategy Content
Coming Soon
VC Analyst
~15 min simulation
Deal Sourcing Analysis
Coming Soon
Data Analyst
~13 min simulation
SQL Visualization
Coming Soon
Consultant
~14 min simulation
Problem-Solving Strategy
Coming Soon
UX Researcher
~12 min simulation
User Interviews Synthesis
Coming Soon
Product Manager
Day-in-the-Life Simulation
Setting the Scene Step 1 of 6
Junior Product Manager  ·  Meridian  ·  Day 3

Your first real problem just landed.

You're a junior PM at Meridian — a project management SaaS used by 50,000 teams. Three days in, and your manager just messaged you with a live issue.

PS
Priya Singh  Product Lead
Today at 9:14 AM · via Slack

Hey — quick heads up before standup. Our activation rate dropped 12% this quarter. New users are signing up but something's blocking them from completing setup.

I need you to own this. Stakeholder review is in 2 weeks. Figure out what's happening and come back with a recommendation.

Where do you want to start? 👀

Your Situation
📉
Activation Rate
↓ 12% this quarter
👥
Active Teams
50,000 teams
🗓
Stakeholder Review
2 weeks away
⚙️
Engineering Capacity
1 sprint free
Product Manager · Decision 1
Where do you start?
Step 2 of 6
Decision 1 of 4
Your manager needs a response. Where do you start?
Activation dropped 12% this quarter. New sign-ups aren't completing setup. You have 2 weeks until stakeholder review and 1 sprint of engineering time. What's your first move?
A
Talk to users first
Schedule 5 interviews with people who signed up recently but never completed setup.
B
Pull the analytics first
Find exactly where in the onboarding funnel users are dropping off before doing anything else.
C
Benchmark competitors
See how similar tools handle onboarding — could surface quick ideas.
D
Write a hypothesis first
Document your best guess about what's happening before touching any data.
The Problem
📉
Activation Rate
↓ 12% this quarter
🗓
Deadline
2 weeks
💡 PM Tip
Real PMs diagnose before they prescribe. The question isn't just "what's wrong" — it's "what do I need to know first to make the best next decision?"
Product Manager · Deep Dive
Synthesize the user feedback
Step 3 of 6
Mini Task — User Research Synthesis
The data shows 68% of users drop off at "Invite Your Team."
You pulled the funnel analytics. The drop-off is concentrated at one step. Now you read the latest user feedback from churned sign-ups. Read all five, then identify the most important insight.
Your analysis
Which insight best explains the 68% drop-off at "Invite Your Team"?
You're looking for the structural reason, not the surface complaint.
A
The tutorial moves too fast
Users lose confidence early and don't make it to team setup.
B
The interface is too overwhelming
Too many options on first login causes users to drop before completing setup.
C
Users don't realize they need admin access
Most new sign-ups can't complete workspace setup — they need an existing admin to invite them first.
D
Team setup is too early in the flow
The "Invite Your Team" step should come later, after users have explored the product.
What You Know
📊
Drop-off Point
"Invite Your Team" step
📉
Drop-off Rate
68% of new users
💡 PM Tip
The best insight isn't the loudest complaint — it's the one that explains why a specific step in the funnel breaks. Ask: which of these causes people to stop at exactly this point?
Product Manager · Decision 2
What do you build?
Step 4 of 6
Decision 2 of 4 — Prioritization
Hypothesis confirmed. Engineering has 1 sprint. What do you ship?
The data and user feedback align: most new sign-ups aren't workspace admins. They hit "Invite Your Team," realize they can't proceed, and leave. You have one sprint. What's your recommendation?
A
Rebuild the onboarding flow end-to-end
Design a completely separate onboarding path for non-admin users. Estimated: 6 weeks.
B
Add a callout at signup explaining admin requirements
Surface a clear message early: "Your company may already have a workspace. Check with your IT admin." Estimated: 3 days.
C
Survey 100 more users to validate first
Run a targeted survey before touching the product to confirm this is the root cause. Estimated: 1 week.
D
Build an email drip for non-admin users
Auto-detect when a sign-up is likely non-admin and send a guide email while they wait for access. Estimated: 2 weeks.
Your Constraints
⚙️
Eng Capacity
1 sprint
🗓
Time to Review
10 days left
💡 PM Tip
The best PM decision isn't always the biggest fix — it's the highest-ROI bet for the time you have. Ask: what's the minimum change that tests the hypothesis and moves the metric?
Product Manager · Decision 3
What's next?
Step 5 of 6
Decision 3 of 4 — Sequencing
It worked. Activation is up 15%. Your manager wants to know what's next.
Your fix shipped 10 days ago. Activation improved 15%. The sprint cost 3 days of engineering time. Priya is asking what you want to tackle next. You have 1 more sprint before stakeholder review.
A
Commission a full visual redesign of onboarding
The UX could be cleaner. Invest in a comprehensive redesign to improve the overall experience.
B
Build mobile onboarding
30% of sign-ups happen on mobile, but the onboarding experience isn't optimized for it.
C
Run 3 A/B test variants on the callout copy
Optimize the message that's already working. Can likely squeeze more lift out of the same fix.
D
Investigate the next biggest drop-off in the funnel
Pull the updated funnel data and find the next step with the highest drop-off rate.
What Just Happened
📈
Activation Lift
↑ 15% in 10 days
Engineering Cost
3 days
💡 PM Tip
When one thing is fixed, the next-biggest problem surfaces. Good PMs follow the data, not their gut, when sequencing what to tackle next.
Product Manager · Decision 4
Stakeholder review is tomorrow.
Step 6 of 6
Decision 4 of 4 — Communication
Stakeholder review is tomorrow. You have one opening slide. What's your lede?
You have 5 minutes to present. Leadership includes the VP of Product, Head of Engineering, and CEO. They've been watching the activation metric for 3 months. What's your first sentence?
A
"We found the root cause, shipped a fix in 3 days, and activation improved 15%. Here's what's next."
Lead with the result, the evidence, and the forward plan.
B
"We're still gathering data — the hypothesis looks right but we want to be certain before committing."
Be transparent that more evidence is needed before making a firm recommendation.
C
"The activation problem is solved. We're moving on."
Activation improved — the issue is closed and the team is focused on the next priority.
D
"We've made progress, but to do this properly we need 6 weeks of engineering time."
The 3-day fix was a patch — a real solution requires a full onboarding rebuild.
The Full Story
📉
Started With
↓ 12% activation drop
📈
Shipped
+15% lift, 3-day fix
💡 PM Tip
Great PM communication leads with impact, not effort. Stakeholders care about outcomes and what comes next — not how hard the work was.
Your Results
Product Manager Simulation
0
/100
You think like a PM.
Loading your results...
Problem Framing
Prioritization
User Thinking
What you did well
    Where to grow
      Your Resume Bullet
      Based on the work you completed in this simulation.
      Loading...
      🔍 Why this reflects real product management

      You just worked through a real PM problem: a metric dropped, and you had to diagnose it, prioritize a fix, ship under constraints, and communicate the outcome to stakeholders. Every decision you made maps to something PMs do every week — pulling funnel data before jumping to solutions, identifying structural blockers through user feedback, choosing the highest-ROI fix over the most thorough one, and leading with outcomes in stakeholder reviews. This isn't a simplified version of PM work. It's what the job actually looks like.

      Your next step on Extern
      BeReal — Product Innovation Externship
      Work on a real product challenge with one of the fastest-growing apps in the world.
      8 weeks  ·  5-10 hrs/week
      Starts March 23, 2026
      Product Management