Wells Fargo · Primly Community

Wells Fargo technical program manager (TPM) interview, what changed from past years

hardware_hugo · 4 replies

Did the Wells Fargo TPM interview earlier this year for a role on their enterprise cloud infrastructure program. Want to share because the TPM process has apparently evolved a lot and the advice on older forums is stale.

WF has been on a multi-year cloud migration (Azure is their primary platform, AWS in some orgs). The TPM roles in that space are actually meaty, not program admin. You're expected to be technical enough to engage with architects and make sense of delivery risk.

Process: Recruiter screen. They ask about your experience with SDLC, Agile/SAFe (WF uses SAFe at scale), and stakeholder management. If you haven't read anything about SAFe in the last two years, do that before the screen. Technical screen (45 min). Not coding. They gave me a scenario: you're managing a cloud migration program with 8 engineering teams, 3 of them dependent on a shared platform service, and one of those dependencies has slipped by 6 weeks. Walk me through how you identify risk, communicate to exec sponsors, and manage the teams. I worked through it out loud. They wanted to see: do you escalate early or late, how do you maintain team trust while applying pressure, how do you distinguish between recoverable and unrecoverable slippage. Deep-dive panel (four rounds, 45-60 min each). One technical (walk me through a past program you delivered end-to-end with architecture context), one stakeholder management, one metrics/data (how do you measure program health, what does a healthy DORA metric look like for a platform team), one behavioral.

The metrics round caught me off guard. They asked about DORA metrics specifically (deployment frequency, change failure rate, lead time, MTTR). If you can't speak to those you'll struggle. Also asked about how I track dependency health across teams and what leading vs. lagging indicators I use for delivery risk.

What the comp looks like: TPM at WF sits somewhere in the $155-180k base range depending on the program scope and whether it's a senior or principal level role. Bonus target 15-20%. Total comp below big tech but the programs are large and the breadth of stakeholder exposure is real.

One thing I genuinely didn't expect: they asked about my experience working with regulatory teams and audit. Cloud migrations at a major bank touch compliance at every layer, and they want TPMs who can operate in that environment without losing their mind.

4 replies

pivot_pat

The SAFe detail is important. Most TPM candidates coming from pure Agile shops have never operated in SAFe, and WF is deeply invested in it. The PI planning cycle, the program increment structure, ART coordination. It's not hard to learn but if you show up having never heard the vocabulary it's a bad start.

ops_omar

The DORA metrics question is showing up everywhere now. I've seen it in PM interviews, TPM interviews, even some EM loops. It's basically a filter question: do you think about engineering delivery quantitatively or just vibes. Knowing what the four metrics are and what good looks like (e.g. elite performers deploy multiple times per day, sub-1hr MTTR) takes 30 minutes to prep.

jordan_pm

Exactly. And the nuance they care about is whether you know the difference between leading and lagging. MTTR is a lagging indicator; you can't fix it fast. Change failure rate gives you earlier signal. That conversation took up half the metrics round.

hardware_hugo

Interesting that WF TPM roles have gotten this technical. I have some hardware program background and was wondering if there's a path into financial services TPM without pure software delivery experience. Sounds like you need pretty deep cloud/software delivery fluency.