Workday · Primly Community

Workday technical program manager (TPM) interview: what they actually ask

infra_ines · 6 replies

Wrapped my Workday TPM loop two months ago. Got the offer, negotiated, signed. Here's the breakdown.

For context: I'm a senior PM, been treating every role as a sprint, this one looked interesting because Workday's TPM function is legitimately technical and not just glorified project coordination.

The rounds Recruiter screen. 20 min. Timeline and logistics. They ask if you're okay with hybrid in Pleasanton or one of their other offices. Remote-only seems hard for this role. Hiring manager screen (45 min): They want to understand how technical you actually are. Be specific. Vague answers about "working with engineers" don't land. I talked through a specific API redesign I drove cross-team and the tradeoffs we navigated. That opened things up. Technical discussion (60 min with a staff SWE): This surprised me. They did walk through a real architectural scenario: you're building an integration between Workday and a third-party payroll system, what does the dependency and data flow look like? Not a coding test. More about whether you can reason about distributed systems, latency, idempotency, failure modes. Know enough to have a real conversation here. Execution/delivery panel (3 people, 45 min each): "Tell me about the largest multi-team project you've owned. How did you handle slippage?" "How do you manage dependencies across teams with different priorities?" "Walk me through how you handle a key technical decision being made by engineers without PM visibility." Leadership alignment round. Very Workday-specific. They care about how you operate in a matrixed organization with strong functional leaders. Not the place for "I just push things through."

Comp at offer: $195k base (Pleasanton), senior TPM level. RSUs over 4 years.

Honest take: Workday TPM is more heavyweight than most places I've interviewed. Good if you like operating in complex, regulated, enterprise environments. Not the right move if you want to ship a feature a week.

6 replies

ae_andre

The point about "matrixed organization with strong functional leaders" is the most important sentence in this post. If you come from a startup where you had authority to just decide things, Workday will feel like a different planet. The skill is influence and alignment, not command.

ops_omar

The integration scenario question (payroll system, dependency/data flow) sounds like they're actually testing whether you understand the technical constraints of their business. Makes sense given how much Workday's value proposition is around integrations. Did they go deep on error handling or idempotency specifically?

jordan_pm

Idempotency came up specifically. I walked through how retries can cause duplicate payroll records if you're not careful with the write semantics. That seemed to land. They weren't testing whether I could implement it, just whether I knew why it mattered.

hardware_hugo

How long between the panel and the offer? And did they negotiate at all or just present a number?

jordan_pm

About 9 days from final round to verbal offer. They presented a number first. I countered at 10k higher, got 5k of it. Pretty standard. Equity was non-negotiable, they said.

consultant_cam

The fact that they ask about technical decisions being made without PM visibility is a tell. That's a known friction point at Workday specifically. Good signal that they're at least aware of it.