Your recruiter just sent a CCAT link for a product role, and you want one thing: a straight number for the score you actually need. The honest answer is that no company publishes a fixed product manager cutoff, but the ranges the major prep sources cite for product managers cluster in a clear band, and there is a defensible target you can aim at. This page gives you that range, reconciles the conflicting figures floating around Reddit and prep blogs, explains why product roles sit where they do, and walks a real candidate’s score through so you know what “good enough” looks like. One quick disambiguation first: this is the Criteria Cognitive Aptitude Test from Criteria Corp, the workplace hiring test, not the Canadian Cognitive Abilities Test used in schools. Same acronym, different test.
Quick takeaways
- Product manager roles are commonly cited at a CCAT range of 26 to 41 out of 50, roughly the 60th to 98th percentile.
- The CCAT average is 24 correct, the 50th percentile, so an average score sits just below the product manager band.
- No employer publishes an official cutoff. Every range here is a prep-provider or forum estimate, not a Criteria Corp rule.
- Do not confuse Product Manager with Project Manager (commonly 22 to 37) or Production Manager. The product role’s band sits higher for a reason.
- Very few people finish all 50 questions in 15 minutes, so pacing moves a product score as much as raw ability does.
- The number worth chasing is the one your weakest question type is costing you, not a headline benchmark.
What the CCAT is, and why product teams screen with it
The CCAT is a 50-question test with a 15-minute limit, about 18 seconds per question. According to Criteria Corp, it measures your ability to solve problems, digest and apply new information, learn new skills, and think critically. There is no penalty for a wrong answer, and less than 1 percent of test takers finish all 50 in time.
Read that list of abilities as a product manager job description. You inherit an unfamiliar market or feature area, absorb messy inputs from engineering, design, sales, and customers, and are expected to reason to a defensible call quickly, then defend it. A timed aptitude test surfaces exactly that profile: fast, accurate reasoning across problems you have not seen before. That is why product and product-adjacent teams, especially in tech, use the CCAT as an early filter. It predicts how quickly a new hire can ramp up on a novel problem, and ramp-up speed is much of the job in product.
The test pulls from three domains: verbal reasoning, math and logic, and spatial or abstract reasoning. Criteria Corp does not publish a fixed per-section split, so treat any “exactly X verbal questions” claim as an estimate rather than gospel. What matters for a product candidate is that all three show up, and you cannot afford to punt an entire domain, especially the spatial and abstract items that trip up otherwise strong verbal thinkers. Here is the part you came for. Across the prep sources that publish role tables, product manager lands at a suggested CCAT range of 26 to 41 out of 50. JobTestPrep’s study guide, a widely-shared Medium write-up by a candidate who took the test, and public CCAT score-report walkthroughs all cite the same 26 to 41 band. Here is how product sits next to the roles it is most often benchmarked against:
| Role | Commonly-cited suggested range | Rough percentile band |
|---|---|---|
| Product Manager | 26 to 41 | 60th to 98th |
| Analyst | 26 to 42 | 60th to 99th |
| Software Engineer | 23 to 40 | 45th to 97th |
| Senior Manager / VP | 29 to 42 | 72nd to 99th |
| Project Manager | 22 to 37 | 40th to 92nd |
| Sales Manager | 23 to 37 | 45th to 92nd |
Two honest caveats. First, these are prep-site and forum estimates, not official Criteria Corp cutoffs. Criteria does not release per-role passing scores, and each employer sets its own bar. Second, the sources disagree at the edges, which is normal for crowd-sourced data.
The practical read: treat roughly 28 (the 68th percentile) as the point where you start looking competitive for a product seat, and the mid-30s, around 34 to 36 (the high 80s to 92nd percentile), as the range that clears most product bars comfortably. A 41 sits near the top of the scale for essentially any CCAT-tested job, so you do not need a perfect score, and chasing 50 wastes prep time you probably do not have. Glassdoor threads on the CCAT converge on the same rough line: several commenters put “above 30” as the informal marker of a good score.
Product Manager vs Project Manager vs Production Manager
These are three different roles with three different score expectations, and mixing them up is the single most common mistake in this search. The score you need depends on which one you are actually interviewing for.
This matters because the sources themselves blur the line. Criteria Corp’s own sample score report lists Project Manager, with a benchmark range shown around 21 to 50, and Production Manager or Supervisor, around 19 to 50, but no row literally labeled “Product Manager.” JobTestPrep’s job table, by contrast, lists Product Manager (26 to 41) and Project Manager (22 to 37) as separate rows. So if you searched “CCAT project manager score” and landed on a 22 to 37 figure, that number is not your target if the role is product.
Why does product sit higher than project? A quick contrast:
- A Product Manager owns the “what” and “why”: deciding what to build under uncertainty and weighing tradeoffs with incomplete data. That is close to the open-ended reasoning the CCAT rewards, so the benchmark band sits higher, around 26 to 41.
- A Project Manager owns the “when” and “how”: coordinating a defined scope to a deadline. Real cognitive load, but a slightly lower published band, around 22 to 37, in the prep tables.
- A Production Manager runs an operational or manufacturing process. Criteria’s wide 19 to 50 benchmark reflects how much that role varies by employer.
If your title search is ambiguous, anchor on the product manager band and prepare to the higher target. It is safer to over-prepare for a 34 than to aim at a 27 and find the employer wanted more.
How raw scores map to percentiles
Employers usually think in percentiles, not raw counts, because a percentile tells them how you did against everyone else who took the test. Here is the raw-to-percentile mapping, cross-confirmed across the most detailed public sources:
| Raw score | Percentile |
|---|---|
| 20 | 32nd |
| 24 | 50th (average) |
| 26 | ~60th |
| 28 | 68th |
| 31 | 80th |
| 34 | ~88th |
| 36 | 92nd |
| 40 | 97th |
| 41 | ~98th |
So the product manager band of 26 to 41 spans a huge stretch, from just above average to near the ceiling. When a recruiter says “we want top 20 percent,” that is roughly a raw 31. “Top 10 percent” is around a 34 to 36. Knowing this lets you turn a vague comment into a concrete practice target, which is the first thing any serious prep should do.
A worked example: does this product manager clear the bar?
Let’s make it concrete. Say you are Priya, a candidate for a senior product manager role at a mid-size SaaS company. You take a timed 50-question practice set and get 30 correct, with 6 questions left blank when the clock ran out.
- Raw score: 30 out of 50.
- Percentile: roughly the 76th, sitting just below the 31/80th anchor.
- Read against the product band (26 to 41): Priya is inside the range, above the competitive floor, but not yet in the comfortable mid-30s zone.
Now the useful part. Priya’s 6 blank questions are the real story. On the CCAT there is no penalty for a wrong answer, so leaving 6 unanswered means she left free points on the table. If even 4 of those were quick verbal items she could have guessed, her raw score climbs to 34 and her percentile jumps into the high 80s, comfortably inside the product band. Pacing usually moves a product-bound score more than raw ability does. Priya does not need to get smarter. She needs to stop leaving questions blank and to spend fewer seconds on the two hard abstract-reasoning items that ate her clock.
That single insight, found by looking at where the points leaked rather than at the headline number, is worth more than another ten hours of untargeted practice.
