What should you ask a Workday consultant in an interview?

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. 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 Workday system, with your team. The resume cannot tell you that. Scenario questions can.

Give a consultant a real problem and listen. Someone who has done the work names the parts of Workday involved and what they would check first. Someone who has only watched others do it talks about process. The difference shows within a minute, even if you could not answer the question yourself.

How should you run a Workday consultant interview?

Run it in forty-five minutes, in three parts. Spend the first ten describing your real situation, and let the consultant ask questions. 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 specific Workday terms. People who have done the work name the parts they would touch. You will hear terms like these:

• Business process: the approval steps Workday runs for things like a hire or a pay change.
• Condition rule: an "if this, then that" rule inside those steps.
• Calculated field: a custom field that works something out, like years of service.
• Worktag: a label Workday uses to tag costs, such as a cost center.
• Security group: a set of people who all get the same access.

People who have not done the work talk about "working with stakeholders" and "understanding the requirements". That 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, by references and project history. Your time together is better spent on whether they can do your specific work with your team.

If the consultant comes through a staffing agency, ask what its screen covered. The recruiter is usually not a Workday practitioner and often matches on keywords like "Workday HCM". Then your interview has to do more of the vetting, so call the references yourself.

What to ask an HCM, Absence or Time consultant

Ask HCM, Absence and Time consultants about access, reorganizations, time-off balances and overtime. These are the four places these modules most often go wrong once Workday is live. HCM is Workday's core HR module. Absence handles time off, and Time Tracking handles hours worked.

1. A manager can see pay details for a worker two levels down that they should not see. Where do you look first?
2. We are splitting one supervisory organization (a team in Workday's reporting structure) into three. What breaks?
3. Time-off balances are off by a fraction of a day for part-time workers. Why?
4. Overtime is calculating on a paid holiday. How do you fix it without breaking the other calculations?

1. A manager sees too much. A good answer starts with the security rule that covers pay data, which Workday calls a domain security policy. Next, they check which security groups that rule lets in. Then they check whether the manager's access flows down the org chart. A weak answer is "I would check their role" and nothing more.

2. Splitting a team. A good answer lists what breaks. Approval chains still point at the old team. People's roles there need reassigning. Default cost centers and reports filtered on the old team need updating. Listen for two habits too: setting the change to take effect from a set date, and testing it in a sandbox (a test copy of Workday) first. A weak answer is "we would update the org chart".

3. Time off that is slightly wrong. This one has a short right answer. The likely cause is how the balance is worked out for part-timers. That is either the calculation itself or the weekly hours set on the worker's position. The second suspect is the rule for who is eligible. A weak answer blames "a system bug" without naming where to look.

4. Overtime on a holiday. A good answer talks about the rules that label hours as regular, overtime or holiday (time calculation tags), and the order those rules run in. They check them against the schedule for the pay period. A strong candidate also warns you, unprompted, that the fix changes what flows into payroll. A weak answer is a one-off manual fix to the hours.

What to ask a Payroll consultant

Ask a Payroll consultant about back pay, the pay items they built themselves, and how they check a pay run before they finish it. These three questions separate people who have run payrolls in Workday from people who have only set them up.

1. A back-dated pay change (retro pay) lands in a pay period that is already closed. Walk me through what happens.
2. Which earnings and deductions have you built from scratch?
3. How do you check a pay run before you complete it?

1. Back-dated pay. A good answer says Workday works out the difference and pays it in the next regular run. They also say they review those retro results before that run is completed, not after. Good candidates ask whether retro is switched on for the pay items involved. A weak answer is "we would make a manual payment", with no word about review.

2. Pay items built from scratch. Earnings (like overtime or a bonus) and deductions (like a benefits deduction) are the building blocks of a paycheck. A good answer names specific ones, the rules behind them, and which ones needed a custom calculation. "The standard ones" is the weak answer.

3. Checking a pay run. A good answer compares totals and headcount with the last period. They look into every worker whose pay swung a lot. They review one-off (off-cycle) runs and retro results on their own. And they name a reconciliation report they always run. A weak answer is "I spot-check a few paychecks".

Hiring for year-end specifically? The payroll year-end guide covers the timeline and what to interview for.

What to ask Financials and Adaptive Planning consultants

Ask Financials and Adaptive Planning consultants questions with no single right answer. How they respond shows whether they understand the accounting behind the setup. Adaptive Planning is Workday's budgeting and forecasting tool.

1. Finance wants a new way to slice its reports. Worktag or hierarchy?
2. Our month-end close takes ten days. Where do you look?
3. Adaptive Planning: our workforce plan and our finance model disagree on headcount. Why?

1. Worktag or hierarchy. A worktag is a label added to each transaction. A hierarchy groups things that already exist into a roll-up. The best first response is a question: what will it be used for? Then a good answer picks a worktag if it drives accounting and shows on transactions. It picks a hierarchy if it only rolls up something that already exists.

A strong candidate also warns that a new worktag has to be added to every approval process that needs it. A weak answer picks one at once, without asking what it is for.

2. A slow close. A good answer starts with journals not yet posted and invoices not yet matched. Then it moves to cost allocations and revenue schedules, then the approval chain. A strong candidate asks to see your close checklist before suggesting anything. A weak answer is "we would automate it", with nothing specific.

3. Plans that disagree. This has three or four usual causes, and a good answer lists them. The two plans may be built at different levels of detail or time periods. A formula may point at the wrong version of the plan. Or a data feed may load actuals into one model and not the other.

A strong candidate also asks how the two models are linked, which is the right next question. A weak answer blames "bad data" and stops there.

What to ask an integrations consultant

Ask an integrations consultant how they pick a tool, how they catch failures and how they set up access. Those decide whether a data feed keeps working after the consultant leaves. An integration is a connection that sends data between Workday and another system.

1. EIB, Core Connector or Studio for a nightly vendor file. How do you choose?
2. An integration fails silently. What did you build to catch it?
3. How do you set up the integration system user?

1. Picking a tool. Workday has three main tools here. EIB is Workday's spreadsheet upload tool. A Core Connector is a ready-made link Workday provides for common types of vendor. Studio is for custom builds.

A good answer: EIB for a simple scheduled load or extract, and a Core Connector when Workday offers one for that kind of vendor. Studio is for a feed that needs reshaping, routing or error handling the others cannot do. A strong candidate adds a time they picked the wrong one. A weak answer is "I always use Studio".

2. Silent failures. A good answer mentions alerts when an integration fails, and a check that stops a bad file before it loads. It also mentions a monitoring report someone actually reads. A strong candidate asks who on your team owns the alert. A weak answer is "the vendor would tell us".

3. The integration system user. This is the system account an integration logs in as (ISU for short). A good answer: one per integration, blocked from normal logins, in its own security group. That group can read or write only the data that one feed needs. Experienced people often bring up how broad that access should be without being asked. A weak answer is one shared account, or an admin's own login, for every feed.

What to ask a Security consultant

Ask a Security consultant about audits, reorganizations and testing. In Workday, a security group is a set of people who get the same access. Security policies decide which groups can see which data and approve which steps. Experienced people answer in terms of policies, groups and roles, never individual users.

1. An auditor asks who can both create a supplier and pay one. How do you answer?
2. After a reorganization, some managers lost access and others kept access they should not have. Why?
3. How do you test a security change before it goes live?

1. The audit question. A good answer starts from the security policies that cover suppliers and payments. Next, they list the groups each policy lets in, then trace those groups to named people. They fix clashes by splitting permissions across groups, not by removing names one at a time. And they keep the before and after as evidence. A weak answer is "I would pull a list of users".

2. Access after a reorganization. A good answer: roles were left on the old teams, so groups tied to those teams now point at the wrong people. A strong candidate also checks for broad groups, not limited to any team, that were hiding the problem. A weak answer suggests fixing people one by one.

3. Testing a change. A good answer has three parts. They make the change in a sandbox first. They test by logging in as the affected users, which Workday calls proxying. And they note when the change went live, so they can roll back if the live system goes wrong. A weak answer is "we test it live".

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 specifics. You ask how they would set something up, and they talk about gathering requirements and working with stakeholders. Close behind is a consultant who has never been wrong.

Every experienced consultant has a story about an approval process that sent a thousand notifications, or sent 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. A long list with no modules, partner firms or years usually means training, not current certifications. The certification guide has the five-minute check.

Watch, too, for a consultant who asks nothing about your system, 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. 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. Any certification they hold is checked against the partner records. So the interview can stay on module depth and on your situation.