← JP Morgan Chase Interview Insights

JP Morgan Chase·Product Manager·Hiring Manager Screen·Intermediate

Intermediate
May 2026

Summary

Interviewed for a PM role at JP Morgan Chase. Just the one question I can remember clearly, product need justification, which sounds straightforward but tripped me up more than I expected.

Questions Asked (1)

Q1

How do you determine whether there is a real need for a product?

Product Sense & IdeationProduct Strategy
Author's notes

I fumbled around talking about user research and market gaps but it felt pretty surface level.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by defining the problem space and the target user segment, then outline a structured process to validate the need using both qualitative and quantitative methods. Emphasize that need validation is continuous and should be tied to measurable business outcomes, especially in a regulated financial services context like JPMorgan Chase.

Pro tip: In fintech, regulatory constraints and risk appetite often shape what's feasible, so always validate need within the boundaries of compliance and existing customer trust. Show that you balance user desirability with business viability and technical feasibility from the start.

1. Define the problem and target user

Clearly articulate the problem you're solving and identify the specific user segment (e.g., retail banking customers, institutional clients). Ensure the problem aligns with the firm's strategic priorities.

2. Conduct qualitative research

Use interviews, focus groups, and observational studies to understand user pain points, current workarounds, and unmet needs. Listen for strong signals of frustration or inefficiency.

3. Quantify the opportunity

Analyze data such as market size, customer usage patterns, support tickets, and competitor gaps to estimate the potential impact. Use surveys to measure the prevalence and intensity of the need.

4. Validate with experiments

Run low-cost experiments like landing pages, prototypes, or concierge tests to gauge interest and willingness to adopt or pay. Define clear success metrics upfront.

5. Assess business viability and strategic fit

Evaluate whether solving the need aligns with business goals, regulatory requirements, and resource constraints. Consider build vs. buy vs. partner options.

Key Points to Mention

  • Jobs-to-be-done framework to uncover underlying user needs
  • Customer discovery interviews and the importance of asking 'why'
  • Quantitative validation through surveys, A/B testing, and usage analytics
  • Minimum viable product (MVP) and experiment design to test demand
  • Regulatory and compliance considerations in financial services
  • Alignment with business KPIs such as revenue, retention, and customer acquisition cost

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.