JPMorgan Chase Program / Project Manager Interview Questions

1.Tell me about a project where the internal timeline or process you were handed wasn't working for the client. What did you do?

2.Tell me about a teammate who was visibly struggling — on deliverables or personally — and what you did about it. What changed?

3.Walk me through the most serious project breakdown or outage you've owned — what went wrong, what you did in the first 24 hours, and how you closed it out.

4.Describe a time you gave someone feedback that was uncomfortable to deliver. How did you frame it, and what actually happened afterward?

5.Tell me about a time a client or end-user need changed significantly mid-project. How did you handle the replan, and what did you have to give up to make it work?

6.Tell me about a project where a control or process failure put a deliverable — or the broader program — at serious risk. Walk me through exactly how you contained it and what the organization looks like differently now because of it.

7.You're managing a Chase Mobile feature rollout to 80 million customers. How would you estimate the number of support tickets you'd expect in the first 72 hours post-launch?

8.The weekly active user count for Chase Online Banking dropped 4% week-over-week. Nothing was released that week. Walk me through how you'd diagnose it.

9.Estimate how many corporate treasury clients JPMorgan Payments would need to onboard annually to grow that business's revenue by 15%. Walk me through your math.

10.You're the PM for a cross-functional initiative to reduce Chase Mobile app crash rate by 30% in one quarter. You have access to engineering, QA, and product analytics, but you own none of them. How do you structure the program and measure progress?

11.JPMorgan Chase is considering whether to build an internal tool versus buy a vendor solution for managing treasury client onboarding workflows. You're the PM asked to recommend a path. How do you frame the decision?

12.You're six weeks into a program to migrate JPMorgan Payments clients from a legacy wire transfer platform to a new one. You learn that the legacy platform's decommission date is fixed and immovable — but your current migration pace puts you 40% short of completed clients by that date. What do you do?

13.How do you build and maintain a project schedule for a multi-team initiative — what tools do you use, and how do you know when the plan is actually reliable?

14.You're managing a project with four workstreams and you need to give leadership a weekly status update. What goes in it, and how do you decide what to escalate versus handle yourself?

15.You're three weeks from go-live on a JPMorgan Payments feature and compliance drops a new control requirement that will take six weeks to implement. How do you work through that?

16.You're managing a program with six dependencies on other teams — none of them report to you. Two are consistently missing their commitments. What's your approach?

17.You're asked to run a program to roll out JPMorgan Chase's internal LLM Suite to a new business unit of 5,000 employees. What's your planning framework, and where do you expect the hardest execution challenges?

18.You're inheriting a program that's already six months in and two months behind. How do you assess where it actually stands, and what do you do in your first two weeks?

19.You're running a project and a key vendor misses a deliverable that puts your milestone at risk. You have a workaround, but it costs 20% more and needs sign-off you don't have authority to give. What do you do?

20.Your program sponsor changes mid-project and the new sponsor wants to revisit scope decisions that were already locked. Half your team has been executing against the old scope for two months. How do you handle the conversation?

21.You're managing a Chase Mobile feature rollout and during UAT, the QA team finds a defect that isn't a blocker by strict definition, but your gut says it could cause friction for a significant subset of customers. The business owner wants to ship on schedule. How do you proceed?

22.You discover mid-program that one of your workstreams has been reporting green status for six weeks, but when you dig in, it's actually amber at best. The workstream lead is a senior peer you don't manage. How do you address it?

23.You're managing the PM workstream for a JPMorgan Payments client onboarding that's been promised in 90 days. At day 45, the client's technical team starts missing integration milestones and blaming your internal API team. Your API team says the client's spec is the problem. Go.

24.Two weeks before a major go-live, your steering committee asks you to add a new high-visibility deliverable to the program scope — directly from a senior executive. It's politically untouchable, but adding it will almost certainly break the launch date. What's your next move?

25.Tell me about a time you had to get a skeptical business partner to adopt a new process or tool your team was rolling out. How did you get them on board?

26.Describe a situation where two senior stakeholders you were coordinating had genuinely conflicting priorities — not just a miscommunication. How did you drive to a decision?

27.Tell me about a time you had to represent your program's status to a senior executive and the news wasn't good. How did you prepare, and how did it land?

28.You've aligned three teams on a delivery plan — dates, owners, dependencies all locked. Then one team quietly changes their internal approach in a way that invalidates an assumption your plan was built on. You find out two weeks later. What do you do?

29.Tell me about a time you had to push back on a request from a client or executive that you believed would genuinely harm the program or the end user — not just slow you down. How did you make the case, and what happened?

30.You're managing a high-visibility program and one of your key stakeholders — a business line director — starts going around you, pulling your team members directly for status and making side commitments to the client. Your team is starting to get mixed signals. How do you handle it?