Every job eventually hands you something you have never done before: a report in an unfamiliar system, a customer request outside the usual process, a task your predecessor did from memory and never wrote down. “How do you approach a new task you have never done?” is the interviewer’s way of finding out what happens next. Do you freeze, guess, or work through it in a way they can trust?
This is an execution question, not a learning question. “Describe a time you had to learn something quickly” asks how fast you closed a knowledge gap against a deadline. This one asks how you carry out unfamiliar work safely: how you pin down the result, sequence the risky parts, decide when to ask, check the output and leave the task easier for the next person. Often you never need to master the whole skill at all. The strongest answers lay out that working method clearly and then prove it with a short example.
What the interviewer is really assessing
Behind the question sit a handful of skills that occupational frameworks describe explicitly. The US Department of Labor’s O*NET database defines several of them:
- Active learning: “Understanding the implications of new information for both current and future problem-solving and decision-making.”
- Critical thinking: “Using logic and reasoning to identify the strengths and weaknesses of alternative solutions, conclusions, or approaches to problems.”
- Monitoring: assessing your own performance, and that of others, to make improvements or take corrective action.
Public-sector employers frame it in similar terms. The UK Civil Service behaviours for its most junior grades include “ask for help when needed and support others when the opportunity arises” and “follow the relevant policies, procedures and rules that apply to the job”. Both matter here: an unfamiliar task is exactly when people are tempted either to struggle on alone or to improvise around the rules.
Put together, the interviewer wants to see that you find out what “done” looks like, judge where the risk sits, ask for help at the right moment, check your own work and stay inside the rules while doing something new. Your answer should touch each of those points.
A five-stage method you can describe
You may already work this way without naming it. Putting it into stages makes it easy to explain under interview pressure.
Stage 1: Clarify the outcome
Before starting, confirm what the finished task should look like, who it is for, when it is due and how much it matters. A ten-minute conversation at this point can save days of rework. Useful questions: “What does good look like?”, “Is there a previous example?”, “What’s the deadline, and is it firm?”
Stage 2: Split the familiar from the genuinely new
Most “new” tasks are mostly familiar work in an unfamiliar combination. List the parts: which ones you already do every day, which ones someone else in the organisation already does, and which ones nobody has done before. Only the last group needs real effort. Check for a procedure, template or past version before building anything, and decide whether a part is something you should do yourself or hand to the person who owns it.
Stage 3: Plan and check the plan
Break the task into steps, estimate how long each will take and flag the riskiest step. For anything high-stakes, share the plan with your manager before you start. This is where the critical thinking O*NET describes comes in: comparing approaches and choosing one for a reason.
Stage 4: Do the work, with early check-ins
Start with the riskiest or least familiar part, so problems surface early. Ask for a quick review of a first draft or a first sample rather than presenting a finished product that might be wrong from the start. Knowing when to ask is part of the skill: too early suggests you have not tried, too late wastes everyone’s time.
Stage 5: Review and record
Check the result against the outcome agreed in stage 1. Then record how the task was done: a short checklist, a note in the shared drive, an update to the procedure. This is what turns a one-off task into something the team can repeat without you.
Turning the method into an answer
Interviewers ask this question in two forms, and each needs a slightly different shape.
| Form of the question | Example wording | How to answer |
|---|---|---|
| Hypothetical | “How would you approach a task you’ve never done?” | Describe your method briefly, then say “for example…” and give a real case. |
| Behavioural | “Tell me about a time you had to do something completely new.” | Tell the story using situation, task, action, result, making sure your actions show the method. |
For the behavioural form, the UK Civil Service’s candidate guidance suggests the STAR method, which “allows you to set the scene, show what and how you did and the overall outcome”.
Even for the hypothetical form, end with a real example. A method without evidence sounds rehearsed.
A worked example, annotated
The answer below is illustrative. The notes in brackets show which part of the method each sentence demonstrates; do not say those parts aloud.
“My first step with anything new is to make sure I understand what the finished result needs to be. [Stage 1] For example, in my current job as an operations assistant I was asked to prepare our first quarterly supplier performance report, which nobody in the team had done before. I asked my manager who would read it and what decisions it would support, and she showed me a report from another department that she liked. [Stage 1, Stage 2]
I found that most of the data was already in our purchasing system, but the on-time delivery figures had to be calculated from two separate exports. That was the part I’d never done, so I tackled it first. [Stage 2, Stage 4] I drafted the calculation for one supplier and asked our finance analyst to sanity-check the method before applying it to the other forty. [Stage 3, Stage 4] She spotted that I wasn’t excluding cancelled orders, which would have skewed every figure.
The finished report went to the director on time, and it’s now produced every quarter. I wrote a two-page guide for the process, and a colleague has used it to produce the last two reports without my help. [Stage 5]”
Notice what makes this work. The candidate does not pretend to have known everything. They show judgement about where the risk was, they ask for a check at the right moment, and the result outlasts the task.
Adjusting for your level
Students and graduates
Use a dissertation, a group project, a part-time job or a society role. Interviewers expect you to have done many things for the first time recently, so lean into it. Emphasise how you found resources and asked for guidance.
Experienced professionals
Choose a task that was new in substance, not just new to your company, such as introducing a process, using unfamiliar technology or entering a new market. Show how you judged risk and when you chose to bring others in.
Managers
Talk about a new task for your team as well as yourself. The interviewer will want to know how you broke it down, who you assigned it to, and how you made sure the knowledge stayed with the team.
Answers that raise concerns
- “I’d just figure it out.” Confidence without a method sounds like guessing.
- “I’d ask my manager how to do it.” Asking is fine, but leading with it suggests you will not try first.
- “I’d look it up on YouTube.” Research is good; relying on it alone ignores internal procedures and the people around you.
- A story where everything went perfectly. A task you had never done that involved no difficulty is not convincing. Include the moment you caught or corrected something.
- Taking on something you were not qualified to do. For safety-critical, legal or licensed work, part of a good method is recognising when a new task should go to someone authorised, or be supervised, rather than attempted alone.
Prepare two examples, not one
Interviewers sometimes follow up with “Can you give me another example?” or “What would you do differently?” Have a second, shorter story ready, ideally from a different context (one technical, one involving people). If you are building your examples from scratch, look back through your CV: each bullet point that begins with “introduced”, “set up”, “launched” or “first” probably hides a new-task story. Our guide to common resume questions can help you phrase those bullets, and graduates can use the fresh graduate resume builder to surface academic and part-time examples.
FAQ
Is it bad to admit I needed help?
No. Knowing when to ask is one of the skills being tested. What matters is that you tried first, asked a specific question and used the answer well.
Should I give a hypothetical answer or a real example?
Both, ideally: a short description of your method, followed by one real example. If the question asks about a specific time, go straight to the example.
How is this different from “Tell me about a time you learned something quickly”?
That question focuses on how fast you closed a knowledge gap. This one focuses on how you plan and carry out unfamiliar work: scoping it, tackling the risky part first, getting checks at the right time and leaving a record others can use.
What if my example task failed?
It can still work if you explain what you learned and what you now do differently. Avoid stories where the failure caused serious harm or where you blame others.
Sources
- Browse by Basic Skills, O*NET OnLine (US Department of Labor)
- Success Profiles: Civil Service Behaviours, UK Government (Civil Service HR)
- Success Profiles: candidate overview, UK Government (Civil Service HR)