Most Workday consultant interviews are spent on the resume: which projects, which clients, how many years. The consultant has told that story many times and tells it well, and at the end of the hour you know little more than you did from reading it. What you need to know is whether they can do your work, in your tenant, with your team, and the resume cannot tell you that.
Scenario questions can. A consultant who has done the work answers a concrete problem with the objects involved and what they would check first; a consultant who has watched others do it answers with process. The difference shows within a minute, even to an interviewer who could not answer the question themselves.
How should you run a Workday consultant interview?
Run it in forty-five minutes on three rules. Spend the first ten describing your actual situation and let the consultant ask questions, because the quality of their questions is half the interview. Spend the next thirty on two or three scenarios from the module you are hiring for. Keep the last five for logistics: start date, hours a week, time zone.
While they answer, listen for nouns: business process, condition rule, calculated field, worktag, security group. People who have done the work name the objects. People who have not describe "working with stakeholders" and "understanding the requirements", which is true of every project and tells you nothing about this one.
Keep the interview for fit and module depth. Whether the consultant has done Workday work at all should be settled before you meet them, by references and project history. The hour you spend together is better used on whether they can do your specific work with your specific team.
What to ask an HCM, Absence or Time consultant
Ask HCM, Absence and Time consultants about access, reorganizations, accruals and time calculations, the four places these modules most often go wrong in a live tenant:
- A manager can see compensation for a worker two levels down that they should not. Where do you look first?
- We are splitting one supervisory organization into three. What breaks?
- An accrual is off by a fraction of a day for part-time workers. Why?
- Overtime is calculating on a paid holiday. How do you fix it without breaking the other calculations?
On the first, a strong answer goes to the domain security policy covering the compensation data, then the membership of the security groups it grants, then whether the manager's role is inherited down the organization. "I would check their role" is the weak version. On the reorganization, listen for business process definitions and approval chains inherited from the old organization, role assignments that need reassigning, cost center defaults and reports filtered on the old organization, with the change made effective-dated and tested in a sandbox first.
The accrual question has a short right answer: the accrual's calculation basis or the scheduled weekly hours on the position, prorated against the time-off plan, with the eligibility rule as the second suspect. On overtime, a practitioner names the time calculation tags and the order in which the time calculations run, checks them against the period schedule, and warns you about the downstream payroll input before you ask.
What to ask a Payroll consultant
Ask a Payroll consultant about retro pay, the pay components they built themselves, and how they check a run before completing it. These three separate people who have run payrolls in Workday from people who have only configured them:
- A retro pay change lands in a closed period. Walk me through what happens.
- Which earnings and deductions have you built from scratch?
- How do you check a pay run before you complete it?
On retro, a strong answer says retro processing picks up the difference in the next on-cycle run, and that they review the retro results before that run is completed rather than after. Good candidates also ask whether retro is enabled for the pay components involved. On the second question, "the standard ones" is the weak answer; a practitioner names specific pay components, their calculation rules, and which ones needed a custom calculation.
On checking a run, expect totals and headcount compared against the previous period, every worker with a large swing investigated, and off-cycle and retro results reviewed separately, with a reconciliation report they always run. Hiring for year-end specifically? The payroll year-end guide covers the timeline and scope to interview against.
What to ask Financials and Adaptive Planning consultants
Ask Financials and Adaptive Planning consultants questions with no single right answer, because how they respond shows whether they understand the accounting behind the configuration:
- Finance wants a new reporting dimension. Worktag or hierarchy?
- Our month-end close takes ten days. Where do you look?
- Adaptive Planning: our workforce plan and our finance model disagree on headcount. Why?
The best answer to the first question is a question: what is it used for? A custom worktag if it drives accounting and appears on transactions, a hierarchy if it rolls up something that already exists, and a strong candidate mentions the cost of adding a worktag to every business process that needs it. On the close, expect unposted journals and unmatched invoices first, then allocations and revenue schedules, then the approval chain, and a request to see the close checklist before proposing anything.
The Adaptive question has three or four usual causes, and a practitioner lists them: different level structures or time granularity between the sheets, a formula referencing the wrong version, or an integration loading actuals to one model and not the other. They will also ask how the models are linked, which is the right next question.
What to ask an integrations consultant
Ask an integrations consultant about tool choice, failure handling and integration security, because those decide whether a feed keeps working after the consultant leaves:
- EIB, Core Connector, or Studio for a nightly vendor file. How do you choose?
- An integration fails silently. What did you build to catch it?
- How do you set up the integration system user?
A strong answer to the first is EIB for a simple scheduled load or extract, a Core Connector when Workday delivers one for that vendor category, and Studio when the feed needs transformation, routing or error handling the others cannot express, followed by a case where they picked wrong. On silent failures, listen for notifications on failed integration events, a validation step that stops a bad file, a monitoring report someone actually reads, and a question back about who owns the alert.
On the integration system user, the answer is one per integration, with UI sessions disallowed, in its own integration system security group holding Get or Put access to only the domains it needs. Practitioners often mention constrained versus unconstrained groups without being asked.
What to ask a Security consultant
Ask a Security consultant about audits, reorganizations and testing. Practitioners answer in policies, groups and role assignments, never in individual users:
- An auditor asks who can both create a supplier and pay one. How do you answer?
- After a reorganization, some managers lost access and others kept access they should not have. Why?
- How do you test a security change before it goes live?
On the audit question, a strong answer starts from the domain and business process security policies involved, lists the security groups granted each, resolves those groups to people, and fixes conflicts by splitting permissions across groups rather than removing names one by one, keeping the before and after as evidence. On the reorganization, expect role assignments left on the old supervisory organizations, so constrained role-based groups point at the wrong people, and a check of any unconstrained groups that were masking the problem.
On testing, the answer is a sandbox, the pending security policy changes activated there, testing by proxying as the affected users, and a note of the timestamp so an earlier one can be reactivated if production goes wrong. For what Security work covers and what it costs, see the Security consultant guide.
What are the red flags in an interview?
The clearest red flag is process instead of objects: answers about gathering requirements and working with stakeholders in response to a configuration question. Close behind it is a consultant who has never been wrong. Every experienced consultant has a story about a business process that sent a thousand notifications or routed approvals to the wrong person; ask for it, and treat a blank as a warning.
Be wary of certifications without detail. Workday certifications are per module, and a long list with no modules, partner firms or years usually describes training rather than current certifications; the certification guide has the five-minute check. Watch, too, for a consultant who asks nothing about your tenant, your integrations or your last project. Someone planning to start on Monday wants to know what they are walking into.
Finally, ask what changed in their module in the last release. Workday ships two feature releases a year, and a consultant working in the module knows what changed in the most recent one. On Turbin, references and project history are checked when a consultant joins the network, and any certification they hold is validated against the partner record, so the interview can stay on module depth and on your situation.
Questions we get asked.
Forty-five minutes. Ten on your project so the consultant can ask questions, thirty on two or three scenario questions from the module you are hiring for, and five on logistics: start date, hours a week, time zone. If you find you need a second round, it is usually because the first one stayed on the resume instead of on your tenant.
Ideally a Workday administrator or a consultant already on your team sits in. If nobody can, use one release-specific question from Workday's release notes and lean on references for the rest. On Turbin, every consultant arrives with 3 verified references from recent engagements and a reviewed project history, which covers much of what a non-specialist interviewer cannot check from the answers alone.
Yes, for fit and module depth. Admission checked 3 verified references, the consultant's Workday project history and any certification they hold; it did not put them in front of your tenant or your team. Thirty minutes of scenario questions from your module confirms both, and it fits comfortably inside a median 48 hours from request to hire.