About This Test
Diagrammatic reasoning is applying process rules and operators as inputs flow through a diagram.
Diagrammatic reasoning presents information as flowcharts, process maps, or grids of symbols, and asks you to work out what a system does to its inputs. A typical item shows shapes entering a chain of boxes, where each box is an operator that transforms them by rotating, recolouring, adding, removing, or reordering elements. You must first deduce what each operator does from worked examples, then apply the same rules to a fresh input and select the correct output.
Some versions run the process backwards, asking which input produced a given result, or ask you to identify a faulty operator. The challenge is holding a sequence of transformations in mind and tracking exactly how each step changes the objects passing through the diagram. This format is heavily used in graduate and technical recruitment, particularly by test publishers such as SHL and Kenexa, and appears often in screening for software, engineering, and IT roles.
It rewards the same ability that programming and systems design demand: understanding how a defined set of rules acts on data as it moves through a process. Because the symbols are abstract and language independent, employers use diagrammatic tests internationally to compare candidates fairly regardless of background.
Anyone whose work involves procedures, logic gates, workflows, or automated pipelines is effectively doing diagrammatic reasoning, so the test predicts how quickly a candidate can grasp an unfamiliar system and reason about its behaviour. Success depends on decoding operators one at a time before attempting the full chain.
Compare each example input with its output and isolate the single change that box is responsible for, then note it in shorthand so you do not have to rederive it. Apply operators strictly in the given order, since swapping two steps usually produces a different and wrong result. When a diagram feels overwhelming, track just one element through the whole process to confirm your rule before checking the rest.
A high score indicates you can internalise procedural rules quickly and apply them accurately under time pressure; a lower score suggests you lose track of intermediate steps or misread how a particular operator transforms the input.
What This Test Measures
Decoding operators
Working out what each process box does to its inputs, such as rotating, recolouring, adding, or reordering elements, by comparing worked example inputs against their outputs.
Sequencing transformations
Applying a chain of operators strictly in order, since swapping two steps usually produces a different result, and holding each intermediate stage clearly in mind.
Reverse processing
Running a diagram backwards to find which input must have produced a given output, or identifying which single operator in a chain is faulty.
Rule based logic
Grasping how a fixed set of rules acts on data as it moves through a flowchart, the same thinking that programming and systems design demand.