Questions to ask in a technical or skills interview

Short answer

Ask one or two short questions. You have just been tested. Your questions here should be about how the work is really done, not about whether you passed. A good one to start with: "How close was that task to the work I would actually do?"

Each question below comes with what it reveals and what to listen for in the answer — the answer is information you can use, not only a chance to look interested.

Practise the whole interview, including your questions — free — The practice interview ends with your chance to ask questions, like a real one. No card needed.

Questions to ask

How close was that task to the work I would actually do? — Why it helps: It turns the test into information about the job, and it is a natural question after any practical assessment. What to listen for: If they say 'not very', ask what the day-to-day actually involves. That gap is worth knowing before you accept.
How do you decide when a piece of work is finished and good enough? — Why it helps: Standards vary a lot between teams. Knowing theirs tells you what 'doing well' would mean here. What to listen for: A real process — a check, a review, a sign-off. If it depends entirely on one person's opinion, expect the standard to move.

A question to keep for later

How did I do? — It puts them on the spot and they usually cannot answer honestly yet. Ask the recruiter for feedback afterwards instead.

For specific kinds of work

Technology roles: How does work get from finished to live here? — Why it helps: The path to production says more about a team's maturity than the tools they list. What to listen for: Whether it is routine or an event. 'It depends who is around' means you should ask about on-call before accepting.

In simple English

If English is new for you, a short question you can say comfortably is better than a long one you have to remember. These are easy to say:

How close was that task to the work I would actually do?
How do you decide when a piece of work is finished and good enough?
What will I do on a normal day?

Common questions

How many questions should I ask in a technical or skills interview?

Usually one or two. Two good questions you listen to the answers for are better than a long list.

What if they already answered my questions during the interview?

Say so — "You already explained the training, thank you" — and ask one of your other questions, or ask what happens next.

All questions to ask, by stage — every stage of the interview process
Questions to ask in a phone screen or recruiter call
Questions to ask in a hiring manager interview
Interview English phrases — how to start, pause and end well

Practise out loud before the real interview. Practise the whole interview, including your questions — free