Failed a Cubiks Assessment — What Next?

SEO title: Failed the Cubiks Assessment? What to Do Next

Meta description: What a Cubiks (Talogy) rejection means, how to tell which Logiks block let you down, whether to ask for feedback, and how to prepare before applying again.

Suggested URL: /tests/failed-cubiks-assessment-what-next

Quick answer

A rejection after a Cubiks stage means your results did not place you in the group taken forward for that role, in that round. It does not mean you fell below a universal standard, because no such standard exists — employers set expectations per role, choose which components to assign, and decide how to weigh them.

The block structure is genuinely useful here, because it makes diagnosis possible in a way a single-score test does not. Logiks reports verbal, numerical and abstract as separate abilities, so one of them was probably weaker than the others, and everything about your next attempt depends on working out which. A candidate who misread data exhibits in the numerical block has a completely different problem from one who over-inferred in verbal or had no method for shape sequences — and a fourth possibility is that nothing was wrong with your reasoning at all, and the abstract block simply ran out from under you, which is the most common single experience candidates report.

It is also worth checking whether the reasoning test was even the deciding factor. PAPI is not pass or fail — it produces a personality profile read against the role — and hiring processes contain 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 Logiks results were the cause.

What the rejection does and does not tell you

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

Employers benchmark by role, and they differ from one another for similar-sounding jobs. They also differ in how they use the ability breakdown: some treat each ability as a threshold, some weight by relevance — numerical more heavily for an analytical role, verbal for one involving dense written material — and some read the overall general ability figure and little else. None of this is usually published.

The comparison group matters too. Ability results are interpreted against a defined population, chosen for the role, and that choice changes what any given performance looks like. A result that reads as solid against a general working-adult group can sit mid-pack against a pool of graduate applicants for a professional scheme.

Which version you sat matters as well. Logiks General Intermediate is a fast screening-level measure; Advanced asks harder questions with more time; standalone single-ability tests probe one ability in depth. A result on one is not a statement about how you would have performed on another.

What the rejection definitely does not tell you is anything general about your ability. It describes a handful of short timed blocks, on one day, against one comparison group, for one role. Candidates who read it as a verdict tend to abandon exactly the targeted preparation that would have worked.

Work out which block was weakest

Do this the same day if you can, while you still remember the experience. It is the input everything else depends on.

Write down which components you sat, then for each Logiks block note four things: whether the timer beat you, whether you left items unanswered, which question types felt slow, and where you think your errors came from. Read the pattern per block, because the diagnoses genuinely differ.

For numerical, ask whether errors came from arithmetic or from reading. Misidentifying units, using the wrong column or period, or solving for a different quantity than the one asked are reading errors — more common and much faster to fix than arithmetic weakness.

For verbal, ask how you handled items the passage did not settle. If you found yourself reasoning from background knowledge or from a plausible assumption the text never made, that is a discipline problem rather than a comprehension one.

For abstract, ask whether you had a method or were waiting for the rule to appear. That single distinction explains most of the gap for most candidates, and it is the fastest thing in this whole page to fix.

And ask a separate question that the block structure makes possible: was this an ability problem or a timing problem? Running out of time in a block while answering accurately is a pacing issue and needs pacing practice. Finishing a block with wrong answers is an accuracy issue and needs content work. They look identical in a rejection and need opposite responses.

Ask for feedback once, then move on

You can ask, briefly, via the recruitment contact named on your invitation. Keep it to a few lines: 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 summary — occasionally broken down by ability, which is unusually useful here because it points straight at the block to work on. Ability and personality assessment feedback is also an area where professional practice in some jurisdictions encourages giving candidates something, so the request is not unreasonable. Many employers will still decline, because results are calibrated to a role and comparison group and individual feedback at volume is not resourced.

If you receive something, read it structurally. "Below the level required on numerical reasoning for this role" is a precise instruction about where your next fortnight goes. It is not a statement about your capability in general.

Requesting a retest is a separate matter and usually unsuccessful where the reason is a disappointing result. A genuine technical fault affecting a specific block is a different and much more actionable request — and because the blocks are separable, naming the affected one makes it easier to grant.

Check the reapplication rules before planning

Reapplication policy belongs to the employer, not to Cubiks or Talogy. Many organisations publish a waiting period on their careers pages — often 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.

A result at one employer does not follow you to another. Assessment records belong to the organisation that commissioned them, so applications elsewhere start fresh — including at other employers using Cubiks or Talogy material. 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 equivalent but different questions. Nothing carries over, and you are evaluated on what you produce this time.

Rebuild the specific block that was weak

Resist starting from zero. Almost always one block was the problem and the others were fine, and general preparation dilutes the days you have.

If abstract was weakest — the most common answer — build a fixed feature checklist and run it on every item until it is automatic: rotation, reflection, number of elements, shading, size, position, then whether two rules alternate between successive figures. That last check unlocks a disproportionate share of harder items. This is where candidates see the fastest visible improvement, because the whole gap is familiarity with a finite rule set rather than any deeper ability, and because the abstract block typically carries the shortest allocation, speed here converts straight into marks.

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

If verbal was weakest, drill judging statements strictly against the passage, read the statement before the passage, and watch quantifiers, since turning "some" into "all" is the block's favourite trap.

If pacing was the issue in any block, practise in short timed sets at that block's tempo rather than long untimed ones, and rehearse an abandonment threshold so a stubborn item gets an answer and gets left.

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 rather than staking a cycle on one employer.

It is also worth being clear about how narrow the evidence is. A Logiks sitting is a handful of short blocks — on some configurations only a few minutes each — sampling three specific skills on one particular 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 you are "bad at aptitude tests" and treating that as fixed. It rarely is. The block structure means the weakness is usually specific and often procedural — no method for figural sequences, a habit of over-inferring, misreading units — 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 block was weak, worked on that one thing, and went again.

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 test and the practice are block-level, that maps cleanly: drill Logiks-style verbal, numerical and abstract blocks separately under time pressure and find out where the marks and the minutes actually go.

The worked explanations turn that into improvement. Seeing which figure in an exhibit the question depended on, why a statement overstates its passage, or that a shape sequence resolves once you separate the odd and even figures replaces the route you improvised with the intended one. And reviewing mistakes across a batch usually shows the weak block 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.