JPMorgan Chase · Primly Community

JPMorgan Chase technical program manager (TPM) interview: six rounds and what actually matters

hardware_hugo · 5 replies

Went through JPMC's TPM interview loop for a role in their technology organization, specifically coordinating large infrastructure modernization programs. This was my third TPM interview process in the past year and JPMC's was the most structured by a significant margin.

For context: JPMC uses the "technical program manager" title for people who sit between engineering leadership and delivery, owning large cross-team programs. It's not a PM role in the product sense. It's closer to senior program management with enough technical depth to credibly engage with engineering teams.

Six rounds total. Let me be direct about each.

Recruiter screen. They had sent me the job description but I quickly learned this was an internal migration program, modernizing legacy Java monoliths to a microservices architecture. Knowing this changed how I prepared. Research what you can before this call.

Hiring manager conversation. More of a mutual fit conversation. She asked about the largest program I'd managed, how I handle dependencies across six or more teams, and my approach to executive communication when things are going wrong. She said explicitly: "In this role you will be the person delivering bad news up the chain before your engineering partners do. How do you think about that?"

Technical depth round. This was the one that surprised me. I don't write code day-to-day and they knew that. But they asked me to draw out a microservices architecture for a payment processing system and identify the failure modes. They wanted to see that I understood distributed systems failure patterns at a conceptual level. Idempotency, circuit breakers, eventual consistency. You don't need to implement them, but you need to talk about them fluently.

Program delivery round. All scenario-based. How do you manage a program that is three months behind with two months left. How do you handle a team that is consistently not hitting their commitments. How do you structure a program kickoff for a team that has never worked together.

Cross-functional stakeholder round. Interview with a VP and a senior PM together. They cared most about how I communicate technical risk to non-technical stakeholders. Practiced some answers about translating engineering complexity into business impact language.

Leadership principles. JPMC does a formal values-based interview. Behavioral questions tied to their stated principles. Know them in advance, the recruiter will share them if you ask.

Offer came in at the VP level (remember: VP at JPMC is approximately director-equivalent in tech company terms). Base was $170k, bonus target 15%, some restricted stock that vests over three years. Total comp well into $200k for a senior program in NYC.

5 replies

ops_omar

The "delivering bad news before your engineering partners do" framing is exactly the TPM job in large organizations. If you're interviewing for any TPM role at a bank or large enterprise, have a very specific story about a time you escalated a risk early, what happened, and what you'd do differently. This question or something like it will appear.

consultant_cam

The technical depth round you described is interesting because it's really a communication test dressed as a technical test. They want to see you can engage with engineers credibly, not that you can design the system yourself. The failure modes question is a great example: circuit breakers and idempotency are conceptual, not implementation. Know the vocabulary.

jordan_pm

Exactly right. My background is in program management, not engineering. I spent two days reading about microservices failure patterns before the loop. Didn't need to go deep, just needed to be able to have an intelligent conversation. Know the vocabulary, know the tradeoffs at a high level, be honest about where your knowledge ends.

hardware_hugo

Is there any embedded systems or hardware program work at JPMC or is it all software? Asking because I have a TPM background in hardware programs and wondering if it translates.

ae_andre

The comp numbers at VP/TPM level look solid for a bank. How was the negotiation process? Banks can sometimes be rigid on base but flexible on signing or have some ability to move on bonus target.