The Structured IT Interview: Realistic Tasks Instead of Trick Questions

What classic interviews often miss

Many technical interviews follow one of two patterns. Either a loose conversation about the CV, where the evaluation depends heavily on gut feeling. Or a series of trick questions and abstract algorithm tasks under time pressure that have little to do with the actual job.

Both approaches have weaknesses. The loose conversation is hardly comparable because each person gets different questions. The trick questions mainly measure who prepared well for interviews or stays calm under pressure. Whether someone can structure an unclear problem, communicate in a team and make pragmatic decisions remains open in both cases.

What makes an interview structured?

A structured interview follows a predefined process. All candidates for the same role receive comparable questions and tasks, and they are evaluated against defined criteria. This makes decisions more transparent and reduces the influence of personal liking and chance.

A typical process for a technical role might look like this:

1. Short introduction: explain the role, the team and the interview process. State explicitly that questions are welcome.
2. Experience: two or three questions about specific projects from the CV, focusing on personal contributions and decisions.
3. Practical task: a short, realistic problem from everyday work.
4. Reflection: how would the person proceed with more time or different constraints?
5. Candidate questions: enough time for questions about the team, tasks and ways of working.

Choosing the right task

The practical task is the core. It should come from the real working environment, be manageable in 20 to 40 minutes and deliberately not contain all the information. Some examples:

• Development: "An interface sporadically delivers duplicate records. How do you proceed?"
• Operations: "After an update, users report that an application is slow. What do you check first?"
• Cloud and architecture: "We want to move an existing application to the cloud. Which questions do you ask before proposing an architecture?"
• Security: "An alert reports unusual sign-ins on a service account. How do you assess the situation?"

What matters is not the one correct solution but the path to it. Which questions does the person ask? Which assumptions do they make, and do they state them? How do they prioritise? How do they explain their approach?

Plan to room for questions deliberately

Questions are not a sign of uncertainty but of professionalism. Design the task so that it cannot be fully solved without asking, and prepare answers to the obvious questions: How many users are affected? Which systems are involved? Are there log files? How urgent is the problem?

This shows you whether someone clarifies the context before acting. In everyday work, this very ability often decides whether a problem is solved quickly or time is invested in the wrong direction.

Define evaluation criteria in advance

To keep the evaluation fair and comparable, the criteria should be set before the first interview. Four to six criteria with a simple scale have proven effective, for example:

• Understanding the problem: does the person clarify goals, scope and constraints?
• Approach: is the solution path structured and comprehensible?
• Technical depth: do the methods and tools fit the task?
• Communication: does the person explain clearly and respond to questions?
• Pragmatism: do they distinguish between a quick fix and a sustainable improvement?

Each member of the interview panel first evaluates independently. Only then are impressions compared. This prevents the loudest opinion from prevailing.

Giving feedback

An often neglected part of the process is feedback. Candidates invest time and energy in an interview. Short, specific feedback, even with a rejection, is appreciated and shapes a company's reputation in the job market. With clear criteria, feedback is also easier to justify.

What companies gain

A structured interview with a realistic task offers several advantages:

• Better prediction: the task reveals skills that are actually needed in everyday work.
• Comparability: all candidates are evaluated against the same criteria.
• Faster decisions: clear criteria shorten alignment within the team.
• Better candidate experience: candidates experience a fair, transparent process and get a realistic picture of the role.

What candidates gain

For applicants and freelance IT experts, this format is a win as well. They can show how they actually work instead of reciting memorised knowledge. And they get to know the team, the problems and the working culture before making a decision. Our tip for candidates: use the invitation to ask questions. It is not a test of whether you dare to, but an invitation to work the way you would in a real project.

Common mistakes in technical interviews

Even with good intentions, patterns creep in that weaken an interview's value:

• Too much at once: a task covering three topics at the same time overwhelms candidates and is hard to evaluate.
• The perfect solution in mind: interviewers unconsciously expect their own approach and overlook good alternatives.
• Silence instead of dialogue: letting candidates work silently for minutes reveals little about their thinking.
• Different standards: without shared criteria, each person in the team evaluates something different.
• No time for counter-questions: if only two minutes remain for candidates' questions at the end, it seems their perspective does not matter.

A short trial run with a colleague helps to spot such weaknesses before the first real interview takes place.

Frequently asked questions

Is a take-home assignment better than a task during the interview?

Both have pros and cons. Take-home assignments show results under more realistic conditions but cost candidates a lot of time. A short task during the interview is fairer in terms of effort and additionally shows how someone thinks and communicates. If you use a take-home assignment, limit its scope clearly.

How many people should take part in the interview?

Two to three people is a good guideline, ideally from the business unit and the team. More participants increase pressure without improving the quality of the decision.

Conclusion

A good IT interview leaves room for questions. A short, realistic task from everyday work, a clear process and evaluation criteria defined in advance reveal more about a person than any trick question. Companies make better decisions, and candidates experience a process that takes their work seriously.

At Suppliance, we help companies design clear and fair selection processes for IT roles and connect them with the right specialists. What information are you still missing to improve your interviews? Ask us for an interview guide for your role.