'What Do You Do If You Don't Know How to Do a Task?' Interview Answer: A Method

The don't-know-how answer interviewers want shows resourcefulness without recklessness: try to find out yourself for a bounded time, ask the right person early with a specific question, say plainly when something is outside your competence, and learn it properly afterwards so you are not asking twice. It overlaps with a time you had to learn something quickly and how do you learn new software, and the asking half connects to how well do you take direction. This page explains what the interviewer is really asking, gives a structure that works, three sample answers of forty to eighty words to adapt, the mistakes that sink the answer, and a ten-minute practice routine.

What the interviewer is asking

Two fears sit behind this question: the new hire who guesses and breaks something, and the new hire who asks about everything and never becomes independent. The interviewer wants to know where you sit between them. In safety-critical and regulated roles they want the 'I would not attempt it' line to be firm; in fast-moving teams they want to hear that you try first. The weak answers are 'I would figure it out' and 'I would ask my manager'; the strong one has a time limit on trying, a specific way of asking, a clear line for competence, and a habit of closing the gap.

A structure that works

1. Try, with a limit: documentation, the last example, a colleague's work, for fifteen or thirty minutes, not an afternoon.
2. Ask well: the right person, early, with what you have tried and the specific thing you need.
3. Know the line: if it involves safety, money, patients or something irreversible, you do not attempt it without someone qualified.
4. Close the gap: write it down, practise it, so the second time you do not need to ask.

Three sample answers

Entry-level

I would look first: is there a guide, has someone done this before, can I find the last example of it. I give that about twenty minutes, because beyond that I am wasting time I could spend asking. Then I ask the person who knows, with what I have tried, so they can see I did the work. If it is something where getting it wrong matters, I ask before I try at all. And I write down what I learned, because I do not want to ask the same question twice. In my last job I kept a notebook of exactly those things, and by month three it was the one new starters borrowed.

Skilled

It depends on what the task could break. For most things I try first: the documentation, a test environment, a colleague's previous version, with a time box so I do not burn a morning. If I am still stuck I ask a specific question rather than 'how do I do this', because specific questions get answered in two minutes. If the task touches production, a customer or a contract, I do not improvise; I say I have not done it and I ask to be shown or to pair with someone. Then I make sure I could do it alone next time.

Senior

By now the answer is usually about judgment rather than knowledge: I can learn most tasks, so the question is whether I should be the one doing it, and how fast. I find out who has done it, I read what exists, and I decide whether to do it myself with a check from them or to hand it over. I am comfortable saying 'I have not done this before' to a team, because pretending is how senior people make expensive mistakes. The thing I hold myself to is that I never ask the same question twice.

Mistakes that sink the answer

• 'I would just figure it out', which worries every interviewer in a regulated or safety role.
• 'I would ask my manager' with no attempt first.
• No time limit on trying.
• No competence line; say what you would not attempt alone.
• No habit of closing the gap afterwards.

A ten-minute practice routine

1. Write your four steps with the time limit and the competence line.
2. Pick one real example where you tried, asked well and then learned it properly.
3. Say it aloud in under ninety seconds.
4. Answer it in the browser demo or a mock interview and compare with the structured answer.
5. Prepare a second example for the learn-something-quickly question.

Where CoPilot Interview fits

CoPilot Interview is an AI interview assistant whose browser demo at /try lets you answer this question aloud and compare your answer with a structured one, free and with no signup, and whose free AI mock interview asks it in the context of your résumé and the job description and scores your spoken answer out of ten. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Practice is the use nobody objects to; if you consider live help in a real interview, follow your employer's rules.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

How do you answer 'what do you do if you don't know how to do a task'?

Try to find out for a bounded time, ask the right person early with a specific question and what you have tried, say plainly when it is outside your competence, and learn it so you never ask twice.

Should I say I would ask for help?

Yes, after a short attempt and with a specific question. Asking is a strength when it is specific and early.

What should I never attempt without help?

Anything involving safety, money, patients, customer data or irreversible changes. Say so; interviewers in those fields are listening for it.

How long should the answer be?

Sixty to ninety seconds.