Remote or onsite is often one of the first things an Epic consultant wants to know about an assignment. It should be clear. So should how often you will need to be onsite if the project is not fully remote.

But there is another question I would put near the top of the conversation: what are the expectations for this role, and what would I be expected to produce?

It sounds basic. The answer tells you a lot.

Consultants are usually brought in for a particular need. If the manager cannot explain that need, or describe what they want from you, you may be looking at a role where the expectation is to do a little of everything without a clear definition of success.

Before you accept, get specific about the assignment behind the job description.

1. What does remote actually mean here?

Ask whether the work is fully remote or includes onsite requirements. If there is travel, ask how often and for what purpose.

There is a practical difference between a clearly described onsite commitment and an open-ended expectation to be available whenever someone decides you are needed. You want to understand the arrangement you are agreeing to, not discover it after starting.

If the answer is still being decided, ask when it will be settled and who can confirm it.

2. What support work comes with the role?

A role described as project work may still include support responsibilities. Ask what those responsibilities are and when you are expected to be available.

Is there a ticket queue you will help cover? Are there particular days or hours you need to support? Does the assignment include any on-call or after-hours expectation? Who else provides coverage?

Do not assume the responsibilities are the same as your last contract. The point is to establish what this team expects, including how support work fits alongside the project deliverables.

3. Who will I be working with?

Ask about the rest of the team and its technical experience. Understanding the people around you helps you understand the role you are being asked to fill.

Are you joining an experienced group that needs additional capacity? Is the team looking for someone who can help colleagues work through unfamiliar problems? Which other teams will your work depend on?

These questions are about understanding the assignment, not judging people before you meet them. A clear answer can help both sides recognize whether the fit is right.

4. How are priorities decided?

I would want to hear that the team has defined criteria for different levels of work. Safety concerns need urgent attention through the appropriate process. High-, moderate-, and low-priority issues should also have understandable definitions and expectations.

The exact timeframes belong to that organization. What matters in the interview is whether the manager can explain them.

Ask what happens when several requests arrive at once. Who decides what takes priority? How are deadlines adjusted when a more urgent issue interrupts planned work?

If everything is described as urgent, keep asking. You need to know how the team makes choices when there is more work than can be done at the same time.

5. What would I actually be expected to produce?

Bring the conversation back to the purpose of the contract. Ask what work you will own, what falls outside the role, and how the manager will know the assignment is going well.

You do not need every future ticket mapped out. You do need a shared understanding of why they are hiring you and what contribution they expect.

Answers worth exploring further

A lot of turnover on the full-time team, managers openly complaining about operations, vague requirements, and unclear answers can all be warning signs.

None of those automatically proves an assignment will be bad. They are reasons to ask more questions. What is changing? What support is available? Is the role intended to address a defined problem, or absorb whatever nobody else has time to handle?

A quick checklist before saying yes

  • Confirm remote and onsite expectations, including frequency.
  • Clarify support responsibilities and required availability.
  • Understand the team's experience and your place within it.
  • Ask for the priority definitions and the process for conflicting requests.
  • Identify the work you are expected to own and produce.
  • Follow up on vague answers before treating them as settled.

A good interview gives both sides a clearer picture of the work. It is your opportunity to understand the assignment, and the manager's opportunity to explain what the team really needs.

Exploring your next Epic consulting assignment? Connect with BridgeLine Health about joining the consultant bench, and bring your preferences and questions about the work with you.