Failed the Kenexa Test — What Next?

SEO title: Failed the Kenexa Test? What to Do Next

Meta description: What a Kenexa rejection means, how to work out which section let you down, whether to ask for feedback, and how to prepare before applying again.

Suggested URL: /tests/failed-kenexa-test-what-next

Quick answer

A rejection after a Kenexa stage means your results, across whichever assessments the employer assigned, did not put you in the group taken forward for that role in that round. It does not mean you fell below a universal standard, because none exists — employers set expectations per role, choose which sections to assign, and decide how to combine them.

The modular structure is genuinely useful here, because it makes diagnosis possible in a way that single-score tests do not. You sat separate, individually timed assessments — numerical reasoning, verbal reasoning, logical or inductive reasoning, perhaps a situational judgement or personality questionnaire, perhaps a job-skills test. One of them was probably weaker than the others, and the whole of your next preparation depends on working out which. A candidate whose numerical section suffered from misreading data exhibits has a completely different problem from one who over-inferred in verbal reasoning or had no method for shape sequences.

It is also worth checking whether the assessment was even the deciding factor. Personality questionnaires are not pass-or-fail — they produce a profile read against a role — and any hiring process contains knock-out criteria that have nothing to do with assessments: eligibility, right to work, stated requirements in the advert. If the rejection came quickly and does not add up, re-read the role requirements before concluding your reasoning scores were the cause.

What the rejection does and does not tell you

It tells you that, against this employer's expectations for this role, your results were outside the group progressing. That is narrower than it feels.

Employers set the bar per role, and they differ from one another for similar-sounding jobs. They also differ in how they combine sections: some treat each assigned assessment as a separate gate, so a weak result anywhere stops the application; some combine sections so strength in one offsets weakness in another; some weight by relevance, with numerical reasoning carrying more for an analytical role. None of this is usually published.

The comparison group matters too. Reasoning assessments are interpreted against a defined population, and which population is chosen for the role changes what any given performance looks like. A result that reads as solid against a general working-adult group can be mid-pack against a pool of graduate applicants for a quantitative role.

What the rejection definitely does not tell you is anything general about your ability. It reflects performance on specific sections, on one day, against one comparison group, for one role. Candidates who treat it as a verdict tend to abandon exactly the targeted preparation that would have worked, which is the real cost of over-reading it.

Work out which section was weakest

Do this the same day if you can. The detail fades fast, and it is the input everything else depends on.

Write down which assessments you actually sat, in order, and for each one note four things: whether you finished, whether you left items unanswered, which question types felt slow, and where you think your errors were. Then read the pattern per section, because the diagnoses differ.

For numerical reasoning, the key question is whether errors came from arithmetic or from reading. Misidentifying units, using the wrong column or period, or computing a different quantity from the one asked are reading errors, and they are both more common and more fixable than arithmetic weakness.

For verbal reasoning, ask how you handled the "cannot say" style items. Candidates who found themselves reasoning from background knowledge, or from an assumption the passage never made, have a discipline problem rather than a comprehension one.

For logical or inductive reasoning, ask whether you had a method. If you were staring at sequences waiting for the rule to appear rather than checking features in a fixed order, that alone explains most of the gap and is quick to fix.

For a job-skills assessment, ask whether you knew the operations but were slow in the application, or genuinely did not know them. Those need different practice — one is time in the software, the other is learning the feature.

Ask for feedback once, then move on

You can ask, briefly, via the recruitment contact named on your invitation. Keep it short: your name, the role and reference, thanks for the consideration, and a request for any feedback that might help a future application.

Some employers, particularly on graduate schemes and in markets where candidate experience is competitive, provide a short summary — occasionally even section-level, which is unusually useful here because it points straight at what to practise. Many decline, because results are calibrated to a role and a comparison group and individual feedback at volume is not resourced.

If you receive anything, read it structurally. "Below the level required on numerical reasoning" is a precise instruction about where to put your next fortnight. It is not a statement about your capability in general.

Requesting a retest is a separate matter and usually unsuccessful when the reason is a disappointing result, since granting one candidate a second attempt undermines comparability. Where a genuine technical fault affected a specific section, that is a different and much more actionable request — and because the assessments are modular, asking for that one section to be reissued is a smaller ask than starting over.

Check the reapplication rules before you plan

Reapplication policy belongs to the employer, not to the assessment. Many organisations publish a waiting period on their careers pages — often measured in months for the same role — while others allow reapplication at the next cycle and some place no restriction. Look it up rather than assuming, because candidates get this wrong in both directions: some sit out a window that was never closed, others reapply immediately into an automatic rejection.

Note also that a result at one employer does not follow you elsewhere. Assessment records belong to the organisation that commissioned them, so applications to other companies start fresh, including at employers using the same assessment content. That matters practically: a rejection is not a mark against you across the market, and there is no reason to stop applying while a waiting period runs at one company.

If you do reapply to the same employer, expect fresh assessments rather than reused results, and expect equivalent but different questions. That is good news — nothing carries over, and you are evaluated on what you produce this time.

Keep it in proportion

High-volume processes screen out most applicants at the first assessment stage. That is a fact about the shape of the funnel rather than a measurement of your potential, and it is why experienced applicants run several processes in parallel instead of staking a cycle on one employer.

It is also worth being clear about how narrow the evidence is. A reasoning section is a short, tightly timed sample of one specific skill — reading data exhibits, or judging statements against a passage, or spotting a rule in a shape sequence — taken once, often at an awkward time of day. Employers use these because they scale and are reasonably predictive across large groups, not because any single result captures much about an individual. Most organisations use them alongside interviews and other stages for exactly that reason.

There is a particular trap after a rejection at this stage, which is deciding that you are "bad at aptitude tests" and treating that as fixed. It rarely is. The section structure means the weakness is usually specific and often procedural — no method for figural sequences, a habit of over-inferring in verbal items, misreading units in a table — and each of those is a few weeks of work rather than a permanent ceiling.

The candidates who convert are generally not the ones who were strongest on a first attempt. They are the ones who identified which section was weak, worked on that one thing, and applied again.

Rebuild the weak section specifically

Resist the urge to start from zero. Almost always one section was the problem and the others were fine, and general preparation dilutes the time you have.

If numerical reasoning was weakest, practise orienting to a data exhibit before calculating — units, categories, periods, footnotes — and drill the recurring operations: percentage change, ratios, unit rates, proportional scaling. Practise estimating when answer options are widely spread. Confirm whether a calculator is permitted and practise under that condition rather than the other one.

If verbal reasoning was weakest, drill the discipline of judging statements strictly against the passage, read the statement before the passage, and pay attention to quantifiers — turning "some" into "all" is the section's favourite trap. Get comfortable choosing "cannot say".

If logical reasoning was weakest, build a fixed feature checklist — rotation, reflection, number of elements, shading, size, position, alternating rules — and run it on every item until it is automatic. This is where most candidates see the fastest visible improvement, because the gain is familiarity with a rule set rather than any deeper ability.

If pacing was the issue in any section, practise in short timed blocks rather than long untimed sets, and rehearse an abandonment threshold so that a stubborn item gets an answer and gets left.

How TestSolve can help

TestSolve lets candidates practise realistic question types, see worked explanations, and review their mistakes before a real online assessment. After a rejection the immediate need is diagnostic, and because both the assessment and the practice are section-level, that maps cleanly: drill numerical, verbal and logical sections separately under time pressure and see where the marks and the minutes actually go.

The worked explanations are what turn that into improvement. Seeing which figure in an exhibit the question depended on, why a statement overstates its passage, or which feature check resolves a shape sequence replaces the route you improvised with the intended one. And reviewing mistakes across a batch usually reveals that the weak section is narrower than it felt — a specific habit rather than the whole subject — which is exactly what makes a second attempt worth making.

Frequently asked questions

TestSolve is independent and not affiliated with any test provider or employer named on this page. All product names and trademarks belong to their respective owners.