Workday · Primly Community

Just finished a Workday PM loop. Here's what actually matters.

hardware_hugo · 4 replies

Finished my Workday Senior PM loop last month, got an offer. Sharing the breakdown.

Five rounds total: recruiter (30 min, standard background + salary), hiring manager (45 min, very conversational, she just wanted to hear how I think about enterprise customers), two panel rounds (one product, one cross-functional), and a final exec screen that felt more like a culture vibe check than a decision round.

The product round was interesting. They asked me to design a feature for Workday's absence management product. The trick: you have to think about the HR admin AND the employee AND the IT team who's configuring the thing. Enterprise PM means three stakeholders minimum. I'd practiced this framing but not for HR tech specifically, so I had to work through it live.

Cross-functional round was a behavioral + stakeholder scenario. They gave me a case where engineering said no to a feature that a major customer had contractually expected. They wanted to see how I'd manage that. My answer: get the data, align on priority, find a smaller deliverable that doesn't break the contract. They seemed satisfied, not wowed.

What surprised me: the exec screen was genuinely low-pressure. She asked about a career mistake. I told the truth. She appreciated it.

One thing nobody mentioned on forums: Workday's job levels matter a lot. Clarify before the loop what level you're interviewing for. Mine almost got misleveled mid-process.

4 replies

apm_aisha

this is really helpful. did they ask any metrics-heavy questions or was it more qualitative? i'm a bit worried about their analytics depth expectations.

pm_priya

mostly qualitative in the panel, but they did ask how i'd measure success for the feature i designed. i pulled in DAU on absence requests and reduction in HR ticket volume. that was enough. they're not expecting you to know their internal data stack.

growth_gabe

the three-stakeholder framing is a good catch. enterprise PM loops consistently punish people who design for one persona. i've seen candidates nail the feature spec and then get cut for ignoring the admin who actually configures it.

tired_recruiter

the leveling thing is real. happens all the time at enterprise companies. always ask the recruiter on screen 1 what the req level is AND whether it's a new headcount or backfill. that changes what they're optimizing for.