The Problem Solving Skills Assessment Test You Take for Yourself

A problem solving skills assessment test is a timed set of questions that scores how quickly and correctly you work through structured problems. Most run ten to thirty minutes, ask somewhere between ten and forty-five questions, and hand the buyer a number that ranks you against everyone else who sat it. For the job it was built to do, that works.

What is Problem Solving test?

Every problem solving skills test on this search does the same thing. It puts structured problems with one right answer in front of you, runs a clock, and totals the score. Complex problem solving is a transferable skill in the federal occupational database, defined there as identifying complex problems and reviewing the related information to develop and evaluate options and implement solutions. A ten-minute screen samples the front of that definition, the identifying and the reviewing, and never reaches the part where a solution has to survive contact with the work.

What topics are covered in the Problem Solving test?

Six, in most cases, and they are worth naming because people arrive expecting brain teasers and meet arithmetic. Logical reasoning asks you to continue or complete a rule. Numerical analysis gives you a table and asks what it implies. Verbal reasoning gives you a passage and asks what follows from it. Situational judgement puts a workplace problem in front of you and asks what you would do first. Data interpretation is numerical analysis with more rows, and pattern recognition is the shape-and-sequence family. The reasoning, numerical and verbal families are cognitive ability testing in the federal government's own terms, built to estimate whether someone can use mental processes to solve work-related problems. Situational judgement is catalogued separately there, as its own method, which is worth knowing when a vendor bundles all six behind a single headline score. Four of the six are worked as sample items further down this page.

What is the difference between an assessment and a test?

People use the two words as though they meant the same thing, and they do not. A test is one measuring instrument with a fixed item set and a scoring rule. An assessment is the process a decision rests on: which instruments get used, in what order, and what else sits alongside them. The problem solving assessment test most people mean is one test inside a wider assessment, which matters when a result comes back, because a low score on one instrument is a small piece of evidence about one hour of your life.

A timed screen never sees the week a real problem takes

A problem sitting in front of you for ten minutes, with the information complete and one right answer waiting, is not the shape of a problem that fills a working week. Those arrive underspecified, involve people who disagree, change while you work them, and reward whoever knows when to stop gathering and start deciding. A screen does not have to see that, because it exists to sort a stack of applications quickly. Our longer piece on what a problem solving skills assessment measures, and what it misses works through the style-versus-skill distinction underneath this one.

How does one measure problem-solving skills?

Two ways, and only one of them has an answer key. The first family is ability testing. Items have one correct answer, a clock runs, and your total is compared against a norm group, so the result comes back as a percentile or a band rather than a raw number. The problem solving aptitude test and the analytical problem solving assessment sold to employers both sit here, and so does nearly every result on this search.

The second family measures approach instead of ability. There is no key. Each item names two ways into the same problem, and you commit to one. Your picks over a long run place you on a continuum, and neither end of one is the better place to be. Both families answer to the same rules about what a psychological measure is allowed to claim. Pigment sits in the second family and calls its format forced-choice.

What questions are on a problem solving skills assessment test?

Vendors gate their sample questions and answers behind a demo request. Here are four ability items, worked, one from each of four of the six families named above, and then one item from the other family so the difference is visible rather than asserted.

Logical reasoning, a sequencing item. Four support tickets are worked one at a time. Ticket B must close before A starts. Ticket A must close before C starts. Ticket D must close before B starts. Which ticket is worked first? Chain the constraints into one line, D then B then A then C, and read off the front. The answer is D. It took you fifteen seconds or it took you ninety, and the fifteen is the part being scored.

Numerical analysis, a table-reading item. A support team logs four weeks. Week one: 220 tickets received, 198 closed. Week two: 240 received, 210 closed. Week three: 260 received, 275 closed. Week four: 300 received, 290 closed. In which week did the backlog shrink? Do not read the closed column on its own. Take closed minus received for each row and you get minus 22, minus 30, plus 15, minus 10. Only week three closed more than it took in, so the answer is week three. Week four closed the most tickets of any week and still fell further behind, and that gap between the biggest number and the right answer is the whole trap.

Verbal reasoning, a cannot-tell item. Read this: every analyst on the team completed the compliance course this year, two of them after the deadline, and the course has to be repeated every year. Now judge one statement as true, false, or cannot tell. The statement: the two late analysts will complete the course again next year. The pull is toward true, because the course repeats annually. The passage never says those two are still on the team next year, and a verbal reasoning item is scored only on what the passage itself supports, so the answer is cannot tell. Most people lose these by importing what they know about how workplaces usually run.

Situational judgement, a first-move item. You are two days from a deadline when a teammate tells you the data feeding your report has been wrong for a week. What do you do first: finish the report and note the issue at the bottom, warn the person expecting it that the number will move, rebuild the analysis on corrected data, or work out how far off the number actually is? Work out how far off it is. Every other move depends on the size of the error, and you cannot choose between them until you know it. Warning the stakeholder feels like the responsible answer and is the common wrong one, because it hands over alarm with nothing attached to act on. One honesty note about this family: the key is set by the vendor from a panel of experienced people, so a correct answer here means agreement with that panel rather than a fact about the world.

And one item with no key at all. A project has stalled and you have one hour. You can map every dependency before touching anything, or you can clear the single thing blocking the person waiting on you. Pick one. There is no key here, and no answer worth defending over the other. Answer a long run of items like it and a shape appears: how far you go toward the complete picture before movement starts to matter more than completeness. That shape is the result.

What is a good score on a problem solving assessment test, and can you fail one?

A raw total means nothing by itself. It becomes a score once it is compared against a norm group, and it comes back as a percentile, a band, or a position in a ranked shortlist. No national pass mark exists for this kind of test. Whether a number counts as good is decided by where one company set its cut, for one role, in one hiring round, and the same percentile can sit above that cut at one employer and below it at the next. Plenty of teams never set a cut at all and simply rank the pile and interview from the top.

You cannot fail one the way you fail a driving test. You can land below a cut nobody told you about, for a role you would have been good at. Employers are not free to set that cut however they please: federal guidance on employment tests and selection procedures says a procedure that disproportionately excludes people on a protected basis has to be justified under the law. A serious vendor publishes reliability and validity evidence, and it is fair to ask for it before buying.

That bar applies to us, so here are the four research traditions Pigment is built on, named and numbered, with the number attached to each. One, person-environment fit: the Kristof-Brown et al. (2005) meta-analysis across 172 studies, where fit correlates .56 with job satisfaction and -.46 with intending to quit. Two, engagement and burnout: the Job Demands-Resources model, meta-analysed across 203 samples and 186,440 participants. Three, flow: Csikszentmihalyi's work establishing that flow depends on challenge-skill balance. Four, strengths psychology: Gallup's finding that people who use their strengths daily are six times more likely to be engaged, to which Pigment adds a two-ended framing where every strength orientation carries a matching shadow. Alongside those, a controlled Purdue pilot of about ninety students rated Pigment first for personal qualities against CliftonStrengths, MBTI and the Strong Interest Inventory.

Two limits on that, stated rather than buried. The peer-reviewed paper on the instrument itself is not out yet, which is exactly why nothing here is offered as a hiring-grade claim. And the rarity figures elsewhere on this page are computed against Pigment's own population, about 3,300 people in the March 2026 snapshot, not against the general public.

A score ranks you. It does not describe you, and most people stall right there when the result comes back. A rank says where you landed against a comparison group on one dimension. A description says what you did to land there: where you go deep, where you move fast, what you reach for first when a problem is underspecified, and what each of those habits costs you somewhere else. The second thing is the one you can act on, and it is the layer the tests on this search were never built to produce.

How do you use problem-solving skills in the workplace?

Problem solving at work is rarely one act. It is a sequence: noticing something is off, deciding how much information is enough, choosing who to involve, and knowing when an answer is good enough to ship. People differ far more in that sequence than in whether they can finish a number series. Someone who insists on the complete map catches the failure nobody else saw and misses the window. Someone who moves on partial information ships first and reworks twice. Neither is the correct way to do it, and the useful move is knowing which one you are before the pressure decides for you. Every strength in that description has a shadow to understand rather than fix.

Turning a problem solving test result into a career direction

Once you can name how you work a problem, the question changes from whether you passed to which kinds of work suit that pattern and which will grind against it. Pigment reports a position on 82 traits, across areas including Decision Making, Learning, and Knowledge and Intelligence, then names roles that suit the pattern and says which conditions in each one your result already clears.

Here is that layer worked on one pattern, the person who needs the complete map before moving. They read every dependency before the first commit, write the runbook nobody asked for, and are usually the one who spots the thing that would have broken in month three. The work that suits it is work where a missed dependency is the failure mode and the clock is measured in weeks: risk and compliance, platform and systems design, clinical and other safety-critical roles, diligence, audit, incident review. The conditions that grind against it are just as specific: a weekly ship cycle with a spec that moves mid-week, a role scored on the number of decisions rather than the quality of them, an early-stage team where half the information genuinely does not exist yet, and a manager who reads a request for more information as hesitancy. Same person, two environments, and the distance between thriving and grinding down is not effort. That is what a direction layer is: not a score, and not a job title either, but a named pattern with the conditions it needs written next to it.

Person-environment fit is a measured quantity rather than a metaphor. The satisfaction coefficient for fit is .56; the coefficient for intending to quit is negative, at -.46. Both numbers rest on 172 studies (Kristof-Brown et al., 2005). That is the case for treating direction as a question with an answer rather than a hunch. For the wider version of this read, the career test guide covers the whole category.

Why does one use problem solving tests?

Because they sort a large stack of applicants quickly, consistently, and at a low cost per head, which is a real job and the reason five vendors own most of this search. The trade is that consistency comes from a fixed item set with a fixed key, so what the buyer gets is a clean comparison on a narrow thing. Here are those five, side by side, so nobody has to open six tabs to compare them.

The five problem solving test platforms on this search, compared

• TestGorilla, Problem Solving. Nine minutes; question count not published. Built as a pre-hire cognitive screen for administrative, project management, customer service, web development, hospitality and sales roles, on tasks like scheduling under constraints and prioritising against a set of rules. The hiring team gets the result as a ranked list. An individual cannot buy a seat; the only self-serve route is a candidate profile recruiters can search.
• Mercer Mettl, Problem-solving Assessment. Thirty minutes, thirty questions. Built for early-career hiring, aimed at candidates with nought to two years of experience, and reported against analytical ability, critical thinking and numerical ability. The hiring team gets the result. An individual cannot take it; the page's exit is a demo request.
• Testlify, Problem Solving. Ten minutes, ten questions, intermediate difficulty, available in eight languages. The fastest filter of the five, covering critical thinking, analytical thinking, decision making and stakeholder management. The hiring team gets the result, and sample reports are published. No individual route.
• Alooba, Problem Solving. Twenty minutes, forty-five questions, medium difficulty, and the largest item count on this shelf. Built for technical screening, with named sub-skills including algorithmic thinking and debugging strategies. The hiring team gets the result. The page's only two exits are a preview and an employer signup.
• Adaface, Problem Solving. Thirty minutes, twenty multiple-choice questions, split four each across logical reasoning, data interpretation, spatial reasoning, abstract reasoning and critical thinking. Built for employer screening, with candidates invited by email or a shared link. The hiring team gets the result. An individual cannot start one.
• Pigment, for comparison. About eighteen minutes, paired questions with one pick each, and no right answers anywhere in it. Built for the person taking it rather than for a hiring process. You get the result, the moment you finish. Buying it yourself is the only way in, and no employer can send it to you.

Those specs were read from each vendor's own test page in September 2026, and vendors change them, so check the spec sheet before you buy. The pattern across all five is the same and worth saying plainly: five out of five are sold to employers, five out of five send the result to the hiring team, and none of the five has a route for an individual to sit one and keep the answer.

Three people type this phrase. An employer sourcing a screen for a role they are filling. A candidate told to sit one on Thursday who wants to know what is coming. And a working professional, usually a decade or more in, who wants to understand their own pattern well enough to decide with it. The first two get their answers below, because their questions have answers and a screen is the right instrument for both. The third is the one this page as a whole is written for, and the one page one of this search leaves stranded.

What roles can I use the Problem Solving test for?

Ability screens earn their place where the work is truly constrained by reasoning speed under time pressure and the applicant pool is large: analyst and graduate intakes, high-volume support and operations roles. They earn it less where the job is slow, political, or heavy on judgement, because a twenty-minute test has nothing to say about a six-month problem. A problem solving skills assessment for employees already in post is weaker still, since you have their working record in front of you.

Why do employers test core skills such as Cognitive Skills, Attention to Detail, and Problem-Solving?

Because those three show up in almost every knowledge role, they are cheap to measure at volume, and a structured measure is more even-handed than an impression formed in six seconds. Where it goes wrong is treating one score as a whole picture of a person, which is a mistake about the instrument rather than about testing. Our guide to the skills assessment category covers how the families fit together.

How to use the Problem Solving test for hiring?

Two rules keep it defensible. Use it to remove clear mismatches, not to rank the top of the pile to two decimal places, because those differences sit inside the measurement error. And pair it with a work sample, since a screen predicts a screen and a work sample predicts the work. Two more things make it fairer at almost no cost: tell candidates which platform they are about to sit, since the five above differ by more than twenty minutes in length and by thirty-five items in count, and write down the cut before you see any results rather than after.

Where in my recruitment process should I use this test?

Early, and never alone. The usual place is right after the application and before any human time is spent, because that is where a cheap consistent filter is worth most. Later in the process it costs more than it returns: by the interview stage you have richer evidence in front of you, and a twenty-minute score sitting next to a work sample adds noise rather than information.

A problem solving skills assessment test for your own career, not a hiring file

The third reader is the one with nowhere to go on this search. If you are mid-career, know you are good at this, and want to know what to do with it, no screen on page one helps, because none of them return anything to you. This is a problem solving test for adults with a decade of evidence behind them, and what you want back is a description of the pattern you have been running all that time. Two related reads: the executive skills assessment guide and the psychometric aptitude test guide.

Three situations, three answers. If you are screening applicants, buy an ability test from a vendor that publishes its validity evidence, put it early, and pair it with a work sample. If you have been told to sit one, treat it as a timed reasoning exam and drill the format. If you want to understand how you solve problems, no ability test reaches that, and what you want is an instrument with no right answers in it.

Pigment is the wrong tool for the first situation. Pigment was never designed to screen anyone, the result goes to whoever took it, and using it to sort candidates would be a misuse. If your question is who to hire, the vendors on this search are the right shelf.

Why is Problem Solving test important?

It matters to the two sides for different reasons, and conflating them is where most of the confusion on this search comes from. To an employer it is the cheapest consistent filter that exists at volume, and reasoning ability does predict performance in roles where the work is genuinely constrained by it. To you it matters mostly as a gate: it stands between you and the conversation you actually want, and clearing it is a format skill. What it is not important for is telling you anything about yourself, because it was not built to and does not claim to.

How do you practice problem-solving skills?

For the test, practise the format. Timed number series, table reading, syllogisms, and passages where the correct answer is that you cannot tell. Twenty minutes a day for a week moves your speed on the format more than any amount of general puzzling, because what you are training is recognition: seeing which of the six families an item belongs to before you start working it. Take one full-length run under a clock as well, so the timer stops being a surprise on the day.

How can one refine their problem-solving abilities?

That is a slower and completely different job from drilling a format, and no workbook does it. Take a problem you own, write down what you would need to know to be certain, then decide with half of that and record what happened. Do it thirty times and you will have something no test result gives you: a calibration, in your own handwriting, of how much information you personally need before you move and how often the extra gathering changed the answer. Most people find they need less than they thought on ordinary decisions and more than they thought on the rare irreversible ones, and knowing which is which is the whole refinement.

How do you test problem-solving skills and knowledge in an interview?

Better than a screen does, if you run it properly. Give the candidate a problem from last quarter, with the information as incomplete as it was on the day, and ask them to think out loud. Score the questions they ask before you score the answer they reach. Then ask for something from their own past they got wrong, and listen for whether they can name the decision point instead of the outcome. That takes forty minutes and tells you more than a twenty-minute test.

What strategic approach can help reduce anxiety and improve problem-solving speed?

One approach does both, and it is mechanical. Timed tests punish rereading, so settle your rule before you start: read once, answer, move, and flag anything you are unsure of instead of sitting on it. Most people lose more points to the four questions they overworked than to the ones they could not do. Find out the scoring rule beforehand too, because a test with no penalty for a wrong answer means you never leave a blank. Anxiety here is mostly uncertainty about the format, and the format is the one part you can settle in advance.

What is the cost for using this test?

For an employer, none of the five named platforms puts a price on the page. It is quoted per seat or bundled into a hiring plan, and the figure moves with volume, which is exactly why every one of those pages ends at a demo request rather than a checkout. Budget for it as a per-candidate cost and remember the screen is the cheap part of a hiring process, not the expensive one. For an individual, the ability route costs nothing to practise and something to prepare properly: free question banks plus paid packs from test-prep publishers. For the approach route, Pigment is $99.99, paid once, with no subscription and no per-use charge afterwards.

Is there a free problem solving skills assessment test?

For practice, yes. For Pigment, no, and it is worth saying plainly: there is no free version and no trial, it is $99.99 once, and every route to it is a purchase. The closest free option is a practice bank rather than a scored instrument. Practice Aptitude Tests publishes free question sets with the working shown across logical reasoning, numerical reasoning, verbal reasoning and situational judgement, which is four of the six families a hiring screen draws from; a free account saves your scores, but the questions themselves sit in front of the paywall. What no free version can give you is a scored comparison against a maintained norm group, because building and keeping a norm costs money, so treat a free score as feedback on your pace rather than a read on your standing. For the paid ability route, online aptitude testing maps the vendor shelf. For the paid approach route, that is the Pigment career test.