The Deliverable Trap: How UK Jobseekers Can Gauge an Interview Exercise

The task that starts to feel like a job

A well-designed interview exercise gives a candidate a fair chance to show how they think. It can be a short written response, a structured case discussion, a work-sample review or a presentation to a panel. In a competitive UK market, such tasks are now routine in sectors from marketing and policy to software and finance. The difficulty arises when the exercise stops testing judgement and starts producing something the employer can use.

The line is not always obvious. A candidate may be asked to draft a campaign plan, analyse a dataset, write a policy briefing or propose a product roadmap. Each of these can be legitimate. Each can also become a speculative brief that transfers useful work from the organisation to the applicant at no cost. The difference usually lies in scope, time, ownership and what happens to the output afterwards.

Why employers set tasks

Recruiters use exercises for defensible reasons. A CV and a short conversation can reward confident presentation rather than the ability to do the work. A structured task gives candidates a common basis for comparison and can reduce the influence of background and interviewing style. Used well, it also gives the applicant a clearer sense of the role.

A fair task should be designed around the assessment, not around an operational need. It should have a defined question, a sensible time limit and a clear explanation of how the response will be marked. It should not require the candidate to solve a live commercial problem in full, produce client-ready material or hand over work that the organisation intends to implement.

The boundary between assessment and output

One useful test is to ask what the employer could reasonably learn from a smaller version of the task. If a two-page outline would reveal the candidate's analytical approach, a twenty-page report is unlikely to be necessary. If a fifteen-minute discussion would show how they structure an argument, a full presentation with designed slides may be more about production than assessment.

Another test is whether the brief describes a real, current problem in specific detail. Generic scenarios can still be demanding, but they keep the exercise at arm's length. A brief that includes live client data, internal figures, a forthcoming launch or a named account may be closer to free consulting. That does not automatically make it improper, but it raises the stakes and should prompt questions about confidentiality and use.

Candidates should also notice whether the task mirrors a role that is currently vacant or a project that is already underway. If the exercise looks like a piece of work that would otherwise be assigned to a freelancer or an existing employee, the employer should be able to explain why the assessment requires that level of detail.

A reasonable time budget

Time is the clearest practical signal. A task that is expected to take two to three hours can be reasonable for a shortlisted candidate. One that quietly consumes a weekend, or that comes with a request to 'just flesh it out', deserves scrutiny. The stated time limit and the real time limit are not always the same, particularly when the brief is vague.

Candidates should ask how long the employer expects the exercise to take and whether the time limit is strict. If the answer is that there is no limit, the task may be poorly designed rather than exploitative, but the risk of overwork is still real. A useful follow-up is to ask what a strong submission looks like in terms of length and depth. Employers who have thought about assessment should be able to answer without revealing the marking scheme.

Reasonable adjustments matter here as well. A candidate with caring responsibilities, a disability or a long commute may need a different timetable. A fair process should allow that conversation without treating it as a lack of commitment.

Ownership, confidentiality and credit

Before starting, candidates should understand who will see the work, how long it will be kept and whether it will be used beyond the recruitment decision. A simple question about data retention and access is not confrontational. It is the same question a sensible organisation should be asking itself under UK data protection rules.

Ownership of ideas is a related issue. If the task requires a new concept, campaign or solution, the candidate should know whether they retain authorship and whether the employer intends to use any part of it. In most recruitment exercises, the answer should be that the submission is used only for assessment. If the employer wants broader rights, that is a separate conversation and may warrant legal advice.

Confidentiality cuts both ways. Candidates should not be asked to disclose sensitive information from a current employer, and employers should not share confidential client material unnecessarily. A generic brief avoids both problems.

Who pays for the exercise?

Most interview tasks are unpaid, and that is not automatically unfair. A short assessment is part of the recruitment process. The position changes when the task involves significant expense, travel, software licences, materials or several days of work. Candidates should not be expected to absorb costs that are really the employer's.

If an exercise requires a paid tool or a specific piece of equipment, ask whether the employer will provide access or reimburse the cost. If it requires attendance at a site, clarify whether travel expenses are covered. A refusal to discuss reasonable expenses is a warning sign, particularly when the task is lengthy or the employer is a large organisation.

Questions that clarify scope

A few precise questions can resolve most uncertainty without sounding adversarial:

• How long do you expect the task to take, and is there a maximum length?
• Will the submission be assessed by the hiring panel only, or shared more widely?
• Is the scenario based on a live project, and if so, what confidentiality arrangements apply?
• Will the work be retained after the process, and for how long?
• Are there any costs associated with completing the task, and are they reimbursed?
• Would a shorter outline be acceptable if it covers the same reasoning?

Asking these questions is itself a demonstration of professional judgement. Employers who value clear thinking tend to welcome them. Employers who react defensively may be revealing something useful about how they manage work.

How to decline without closing the door

Sometimes the answer to those questions confirms that the task is too large, too close to live work or too poorly defined. A candidate can decline while keeping the relationship intact. A short, polite message is usually enough: explain that the scope appears to exceed what can reasonably be completed within the time available, ask whether a shorter alternative is possible, and thank the employer for the opportunity.

That approach leaves room for the employer to adjust. If they do not, the candidate has lost nothing except a process that was unlikely to respect their time. In a small professional market, a gracious exit is worth more than a frustrated silence.

When a task is really a vacancy

The strongest warning sign is a brief that could be issued to a contractor. If the employer wants a full strategy, a completed design, a working prototype or a detailed financial model, the candidate should ask why the assessment cannot be met with a smaller sample. There may be a good answer, but the question deserves to be asked.

Interview exercises should help both sides make a decision. They should test capability, not extract output. A fair process is clear about time, scope and use. It respects the candidate's other commitments and treats the submission as evidence, not as a deliverable. Candidates who apply those tests are better placed to recognise a genuine opportunity and to step away from one that is asking for free work under another name.