Run a campus drive you can trust
Assess a full campus batch or a single senior hire on the same platform: real code, real SQL, a live proctoring wall, and an AI first-round interview for everyone who clears the test.
Front-end Engineer · question 4 of 18
Built from the job description
Build a searchable product catalogue across three files. It must filter as the user types.
Explorer
src
components
ProductCard.tsx
SearchBar.tsx
hooks
useDebounce.ts
Catalog.tsx
types.ts
1import { useMemo, useState } from "react";
2import { SearchBar } from "./components/SearchBar";
3import { useDebounce } from "./hooks/useDebounce";
4
5export default function Catalog() {
6 const [query, setQuery] = useState("");
7 const [category, setCategory] = useState("All");
8 const search = useDebounce(query, 250);
9
10 // filter once per change, not on every render
11 const visible = useMemo(() => {
12 const term = search.trim().toLowerCase();
13 return PRODUCTS.filter((p) =>
Live preview running
Products
Search productsAllAudioWearables6 results
Tests0 / 6Console0 / 15 marksnot run yet
renders every product as a card8ms··/3
filters by name, case-insensitively12ms··/3
debounces the search by 250 ms31ms··/2
category chips filter the grid9ms··/3
result count matches the cards6ms··/2
empty state when nothing matches5ms··/2
Similarity 4%no match in your question librarytyped over 14 min · no paste events
A real project, a live preview, and every test scored as it runs · sample data
What a test for this role can look like
One example. You choose the sections, the question types, the length and how closely it is watched.
- Draft it from a job description, or build it by hand
- Review every question before a candidate sees it
- Reuse questions from your own bank
Graduate Engineer Trainee — campus drive
Entry-level software engineer
- Duration
- 90min
- Sections
- 5
- Questions
- 35
- 01×20
Aptitude and logical reasoning
Multiple choice - 02×10
Programming fundamentals and output prediction
Pick all that apply - 03×2
Data structures and algorithms
Write and run codeTheir choice of language - 04×2
Query a sample orders database
SQLLive MySQL - 05×1
Explain the approach to one coding problem
Written, marked by AI
Proctoring: Webcam + screen, live proctoring wall
Where volume technology hiring breaks down
- 01
One drive, a very large batch
A campus drive puts a whole graduating class through one test window. The platform, the proctors and the evaluation all have to keep up on the day.
- 02
Copied code looks like good code
Candidates share solutions in group chats and paste answers from AI tools. A passing test case does not tell you who wrote the code.
- 03
First-round interviews eat engineering time
Every candidate who clears the test needs a conversation, and your engineers are the ones pulled off delivery to hold it.
- 04
Lateral roles need different tests
A data engineer, a React developer and a support engineer should not get the same question paper, and someone has to write each one.
From an open req to a shortlist
- 1
Set the paper
Pick questions from your library or generate a draft from the job description. Mix coding, SQL, multiple-choice and written questions in one timed test.
- 2
Run the drive
Invite the batch. Proctors watch candidates on a live wall with chat, while window switches and face-detection events are flagged automatically.
- 3
Check the code
Code is scored against test cases, and plagiarism comparison shows submissions that match each other side by side.
- 4
Interview the shortlist
The AI Interviewer holds a structured voice interview with each shortlisted candidate. The recording, transcript and competency scores land on the same scorecard as the test.
What you would use
- Skill AssessmentsCandidates write and run code in 10 languages and query a live MySQL database, so you see working solutions, not guesses.
- CheqMate AIA live proctoring wall with chat lets a small team watch a large batch, and every flag is tied to a question.
- AI InterviewerEveryone who clears the test gets a first-round interview without taking engineers off delivery work.
- Candidate ScorecardsTest, integrity record and interview sit on one scorecard, so the panel reads one page per candidate.
Roles you can assess
- Graduate engineer trainee
- Java and Spring developer
- Python developer
- Front-end developer (React, Angular)
- Full-stack developer
- Data engineer
- SQL and database developer
- QA and automation engineer
- DevOps and cloud engineer
- Technical support engineer
- Business analyst
- Hackathon and coding contest participants
Common questions
Which programming languages are supported?
Candidates can code in 10 languages, including C, C++, Java, Python and JavaScript, in an in-browser editor with test cases. You choose which languages are allowed for each question.
How do you detect copied code?
Plagiarism comparison shows matching submissions side by side. Alongside that, the integrity record shows window switches, face-detection events and snapshots for each candidate, tied to the question they were on.
Can we run coding contests and hackathons?
Yes. Contests run with their own question sets and a live leaderboard, which works for hiring challenges and for campus engagement events.
How does the AI Interviewer fit with our panel interviews?
It replaces the first screening conversation, not your panel. It follows a question plan you approve, asks follow-up questions based on the candidate’s answers, and gives your panel a transcript and scores to start from.
See it with one of your own roles
Bring a job description to the demo. We will build the test with you and show you the report a candidate produces.