Aptitude & Cognitive Ability · Competency Dictionary
What is Technology & Programming Logic?
Technology and Programming Logic is tracing what code or a process will do without running it — reading pseudo-code, following branches and loops, and holding the computing and data concepts a non-engineering role now needs. It measures logic applied to a technical notation rather than fluency in any particular language.
Technology & Programming Logic is one of 11 competencies in the AssessAll Aptitude Competency Set — the scoring layer every AssessAll aptitude instrument reports against. What a person can work out, rather than what they have already learned — the reasoning, comprehension, precision and pace that the AssessAll aptitude instruments report a band against. It is a separate published set from the 29 behavioural competencies of the AssessAll Capability Framework, and we say so rather than presenting one number of competencies: an ability you can test in twenty minutes and a behaviour colleagues observe over a year are not the same kind of thing.
Founder of AssessAll and of Bodhih Training Solutions, a corporate training company in Bangalore. Works on assessment design, scoring and reporting across hiring, L&D and certification programmes.
Last reviewed
What technology & programming logic looks like at four levels
Every AssessAll competency score is reported on a 0–100 scale and interpreted against four published anchors. The wording below is the same interpretation a person receives in their own report — published here so a manager can read a score without needing one.
Code traces and computing concepts are unfamiliar territory right now.
You follow linear pseudo-code but loops, conditions and state tracking break down.
You trace loops and nested conditions accurately and know the core concepts well.
You read program logic fluently and reason about edge cases like an experienced engineer.
Signs it is missing
Competencies are easier to spot by their absence. These are observable behaviours, not personality judgements — each one is something a colleague could describe from memory.
- Can run the report but cannot say what its filter excludes, so an empty result is read as a real zero.
- Describes a bug by what the screen showed rather than by what the step did, which makes it unreproducible.
- Copies a formula or a query forward into a case its conditions no longer cover.
Evidence to look for
You cannot interview for an ability. Asking somebody whether they are good with numbers, or careful with detail, measures their self-image and their confidence, and both are poor proxies. What an interview can do is send you to the work. Each prompt below points at something the person actually produced — the evidence is in the artefact, not in the answer.
- A spreadsheet or query they maintain: ask what happens to it when a new category appears in the source data.
- An automation or workflow they built — have them trace one edge case through it on paper, without opening the tool.
- A vendor system they configured, and what they can tell you it cannot do.
These are work-sample and observation prompts written for this page. They are deliberately not items from a live AssessAll instrument — published items stop measuring anything.
How to develop it
The development moves AssessAll puts in a growth plan when this competency is a person's priority area. Each is small enough to start this week.
- Trace pseudo-code on paper, writing every variable's value at every step — no shortcuts.
- Learn the five core constructs cold: assignment, condition, loop, function, array indexing.
- Rebuild each missed trace question in a real language and run it to confirm the answer.
What measures technology & programming logic on AssessAll
Every form below reports a band for this competency. Item counts and time limits are the configured values, published here because they are the two numbers that decide what a score means and the two that vendors most often leave off a product page — a form with 20 items in 10 minutes and a form with 20 items in 25 minutes are not measuring the same thing.
| Assessment | Items | Minutes | Seconds / item | What it is for |
|---|---|---|---|---|
| Computer & Digital Fundamentals | 25 | 18 | 43 | Core concepts; speed-weighted at about 43 seconds an item |
| Pseudo-code & Programming Logic — Basics | 20 | 25 | 75 | Reading and tracing logic; no language fluency assumed |
| Flowcharts & Process Logic | 18 | 22 | 73 | Branch and boundary tracing, shared with the deduction lane |
| Technical Reading Comprehension | 16 | 24 | 90 | Manuals and specifications; reports a verbal band too |
Seconds per item is arithmetic on the two published columns, not a separate claim. Read it as the working pace the form assumes: under about 45 seconds an item, pace is part of what is being measured whether or not the product says so. See speeded test for why that distinction changes how the score should be read.
Often confused with Logical Reasoning
The reasoning is the same; the notation is the difference, and the notation is what the score is for. A candidate strong on syllogisms who has never read a loop will score lower here, and that gap is trainable in weeks — which is the point of measuring the two separately rather than inferring one from the other.
Logical ReasoningHow AssessAll measures it
Technology & Programming Logic is not measured by a single question. Responses across an assessment map to the competency, roll up into a 0–100 score, and are interpreted against the four anchors above. Because every AssessAll assessment speaks the same competency language, results from different instruments accumulate into one profile rather than a pile of unrelated scores.
Aptitude items are multiple-choice and machine-scored against a key, so the band is reproducible and the whole form can be sat in under half an hour. That is the trade: an ability score is cheap, fast and comparable, and it tells you what somebody can work out — not what they will choose to do, which is what the behavioural competencies are for. Read one band beside the other rather than either alone, and browse the assessment catalogue or the store for the forms above.
How technology & programming logic aligns to public frameworks
Two rows, not five, and the absence is the honest part. O*NET publishes a taxonomy of cognitive abilities and the UK Civil Service Success Profiles carries an Ability element, so there is something real to align to in both. Australia's Integrated Leadership System, Canada's Key Leadership Competencies and ESCO's transversal skills are behavioural and occupational frameworks that contain no cognitive-ability elements — so this page leaves those rows out rather than inventing a correspondence. Alignment, not derivation; no proprietary instrument is reproduced.
| Framework | Corresponding element |
|---|---|
| O*NET | Abilities: Deductive Reasoning (1.A.1.b.4), Information Ordering (1.A.1.b.6); the domain knowledge corresponds to the O*NET Knowledge element Computers and Electronics |
| Civil Service Success Profiles | Success Profiles: Technical, with the reasoning half under Ability |
Further reading
- What is competency-based hiring?Why a trainable gap and a fixed one belong in different columns of a scorecard
- Cut scoreSetting a threshold on a knowledge-bearing form, where the standard is defensible
- Angoff cut-score calculatorRun the study rather than picking a round number