Work skill · Solving problems and deciding

Solving problems

When a problem is unclear or has several causes, separates facts from guesses, finds what is really wrong, and picks a first fix to try; no technical knowledge is tested.

Updated 21 November 2026 · 4 min read · by the hire.center team

On this page (7)
  1. What it is
  2. What it looks like at work
  3. Why it matters in different kinds of jobs
  4. Why interviews often miss it
  5. How a work situation can show it
  6. What to ask in an interview
  7. What hire.center shows, and its limits
Solving problems and deciding

What it is

When a problem is unclear or has several causes, separates facts from guesses, finds what is really wrong, and picks a first fix to try; no technical knowledge is tested. This is about the approach, not about knowing the answer. An experienced person who jumps to the familiar fix without checking can miss the real cause; a newcomer who sorts out what is known from what is assumed can find it.

What it looks like at work

In everyday work, it often looks like this
  1. Separate facts from guesses
  2. Find what is really wrong
  3. Pick a first fix to try
The skill in general terms, from its definition. Real work mixes the steps.
  • Healthcare

    A ward nurse sees that evening medication rounds run late every day and checks whether the cause is staffing, the pharmacy delivery time or the handover before suggesting a change.

  • Software

    A software developer facing errors that come and go writes down what is known (one region only, since Tuesday) and what is only a guess, and tests the likeliest cause first.

  • Finance

    An accountant finds that two reports disagree and traces the gap to one setting instead of redoing every number.

  • Warehouse

    A warehouse supervisor looks into late shipments and checks picking, packing and the carrier's collection times one by one before blaming a person.

  • Retail

    A shop manager sees sales fall and checks whether fewer people come in, fewer buy, or the best-selling items are out of stock.

In each case the person does not accept the first explanation. They sort facts from guesses, find the cause and choose a first step that will show whether they were right.

Why it matters in different kinds of jobs

Clear problems with one cause are easy. The costly ones are unclear, have several causes at once, and come with missing information and people offering competing explanations. Researchers describe such complex problems in the same way: unclear goals, many connected parts, and a situation that keeps changing (Dörner & Funke, 2017). The usual failures are fixing a symptom, blaming the nearest person, or trying five fixes at once so nobody learns what worked. This matters in operations, health care, finance, technical work and management alike. Research also finds that this kind of problem solving overlaps with general reasoning ability (Stadler, Becker, Gödker, Leutner & Greiff, 2015), so it is best read alongside other information about the candidate. In jobs where technical knowledge matters most, use it next to a technical check, not instead of one.

Why interviews often miss it

Problem-solving stories are told after the problem was solved. The candidate already knows the cause, so the story makes it look obvious, and the dead ends drop out. A candidate with deep technical vocabulary can also sound like a strong problem solver while describing what they know rather than how they think.

How a work situation can show it

A realistic work situation can give the candidate a problem with several possible causes, some facts missing and colleagues who each have their own theory. You then see whether the candidate separates what is known from what is assumed, asks for the missing fact, and picks a first step to try, rather than adopting the loudest explanation. The situation matters: a way of working shows most clearly when the moment calls for it (Tett & Burnett, 2003).

What to ask in an interview

  1. "Tell me about a problem at work where the first explanation turned out to be wrong. How did you find the real cause?"

    Follow-up: "What did you check first, and why?"

  2. "Describe a problem that had more than one cause. How did you tell them apart?"

    Follow-up: "Which did you fix first?"

  3. "Tell me about a time you had to act before you knew the cause. What did you do?"

Listen for facts kept apart from guesses, a cause that was checked, and a first step chosen on purpose.

To see it with a situation from your own job, read how it works and pricing.

What hire.center shows, and its limits

In hire.center, a candidate handles one realistic work situation built from the job. The scorecard shows the candidate's own words for each skill the recruiter chose, or says there was not enough evidence. One situation shows one situation, not the whole job, and it does not test technical knowledge. A person makes the hiring decision. Our quality checks so far use AI-played candidates in six example jobs, most of them with customers or colleagues at the centre of the work. We are extending them to more kinds of jobs.

See the work skills a CV can't show

Take the candidate's seat in a 15-minute work situation, then read your own scorecard. Free, no card.