Skip to main content
Qorium

Platform overview

One engine. Three SKUs. The content layer the assessment industry was missing.

Below the platform UI you click. Below the test runner. Below the candidate dashboard. The questions themselves — that's where every assessment platform's quality bar gets set, and where every leak originates. QOrium owns that layer.

The problem

Every Senior Java question on HackerRank is on Reddit by Friday.

After 15 years running Talpro India staffing, the same thing happened every year: hiring teams paid HackerRank or Mettl ₹15-25K/year for assessment libraries that leaked in days.

By Friday, every Senior Java question was on Reddit. The 95%-on-screen candidate flunked the technical interview. The hiring manager called us, frustrated.

The assessment platforms know this. They just don't solve it — their moat is the platform. Content was always somebody else's problem.

The Content Engine

Seven stages, every question.

Same pipeline regardless of SKU. The stages flex per SKU (JD-Forge skips human review on the Standard tier; Stack-Vault doubles SME validation). The architecture is the moat.

01

Spec in

02

AI draft

03

Self-critique

04

SME review

05

Calibrate

06

Release

07

Post-deploy

Three SKUs

Pick the shape that fits your IP posture.

Same underlying library. Different exclusivity. Different price. Different velocity.

SKUWhat it is
ReadyBankShared, multi-tenant question library indexed by skill / role / difficulty.Explore
JD-ForgeOn-demand custom pack generated per uploaded JD in 30 seconds.Explore
Stack-VaultCustomer-exclusive private library aligned to one company's tech stack.Explore

The moat

Anti-leak rotation, not anti-leak claims.

Continuous crawl of Glassdoor, LeetCode, Reddit, GeeksforGeeks, public github gists, and indexed PDFs.

Semantic similarity match — not string match. Variants count.

When a hit fires: AI regenerates a semantic variant; SME validates; new question releases as v2; original retires.

ReadyBank target: 15% of library rotated quarterly. Continuous-rotation tier available for high-stakes platforms.

Stack-Vault: per-customer watermarking enables forensic attribution if a leak crosses the contractual boundary.

The role-graph

Roles map to skills map to questions, in a normalized graph.

A "Senior Backend Engineer (Java Spring Boot, 5+ yrs)" decomposes into a tree of skills, each tagged with format-mix preferences and difficulty bands. The graph compounds with every JD parsed. Coverage gaps surface automatically.

Senior Backend Engineer (Java Spring Boot, 5+ yrs)
├── Java 21 fundamentals (band: 3-4 · MCQ × 4, Coding × 2)
├── Spring Boot
│   ├── @Transactional propagation (band: 4 · SJT × 2, Coding × 1)
│   ├── Configuration & profiles (band: 3 · MCQ × 3)
│   └── Security & filters (band: 4 · SJT × 1, Coding × 1)
├── JPA / Hibernate
│   ├── N+1 query patterns (band: 4 · Coding × 2)
│   └── Optimistic vs pessimistic locks (band: 5 · SJT × 1)
├── PostgreSQL
│   ├── Index design (band: 4 · MCQ × 2, SQL × 1)
│   └── Explain plans (band: 5 · SQL × 2)
└── System design
    ├── Idempotency (band: 4 · SJT × 1)
    └── Rate limiting (band: 4 · SJT × 1)

Quality bars

We've codified the rules so you don't have to ask.

Test coverage

≥80%

on every changed file

TypeScript errors

0

tsc --noEmit must pass

API errors

RFC 7807

Problem Details on every public failure

Security headers

Always

CSP, HSTS, X-Frame-Options on every response

Logging

Pino

structured logs on every significant code path

Secrets

gitleaks

pre-commit + CI; .env-only

Want to see this run live?

A 30-minute demo covers the engine, both pricing toggles, and one of your JDs.