Assignments

AI Powered Assessments. Results In Minutes.

A quiz tells you who can answer questions. An assignment tells you who can do the job. Describe the role, get a take-home built for it, and have every submission — a document, a GitHub repo or a ZIP of code — read and scored the moment it lands.

candidate_review_card
The gap

Take-homes are the best signal and the worst workflow.

Someone writes the brief on Friday. Candidates email zip files and Drive links back. Two engineers lose an afternoon reading them, score them differently, and nobody can say afterwards why one candidate beat another. The signal is excellent; the process is why teams stop running them.

How it works

Four steps, no email threads.

1

Describe the role, not the task

Enter the job role, the skills you are testing and a difficulty — Easy, Moderate, Advanced or Expert. A complete assignment comes back: scenario, requirements, deliverables, submission guidelines and evaluation criteria. Edit any of it, or write your own from scratch instead.

2

Pick how the work comes back

A typed answer, a Word/PDF upload, a GitHub repo link, or a ZIP of code — set the submission format the role actually calls for.

3

Share the link and watch it arrive

Share the assignment link with a due date. Candidates open it, read the brief and submit in the format you chose. You watch submissions arrive with their status.

4

Read the scored result

Every submission comes back with a score and written feedback against the criteria in the brief. Open the work itself in the browser — the document, the repository, or the ZIP unpacked file by file — adjust the score if you disagree, and add your own review.

Three kinds of work

Whatever the role actually produces.

Document

Written answers and reports

Case studies, campaign plans, test strategies, analyses — anything a candidate writes rather than builds.

Types into the browser or uploads .doc / .docx
Repository

Repositories

For work where commit history and project structure are part of what you are judging, not just the final file.

Submits a repository link; the code is read in place
Zip

Zipped code

For candidates without a GitHub account, or work where a full repo is overkill.

Uploads a .zip; you browse it file by file in the review screen
Calibration

Pitch it at the person you are hiring.

Easy Moderate Advanced Expert

The same role generates a different brief at each level, so a graduate and a team lead are not handed the same take-home — and the scoring is judged against the level you chose, not an absolute bar.

What you get

Everything the review needs, in the review screen.

Review

The work, in the browser

Documents render, repositories open file by file, ZIPs unpack in place. Nothing to download, unzip or clone before you can judge it.

Control

The reviewer has the last word

Override the score, write your own feedback, rate the submission. The automatic pass is a first read, not a verdict.

Tracking

Due dates and status

See who has submitted, who is late and who has been reviewed, with the score beside each name in one list.

Reporting

Export the whole cohort

Names, emails, due dates, statuses and scores as a spreadsheet — with links back to each submission.

Part of iScalePro

One step in a longer process.

Smart ATS — Screen applicants against the JD, then send this assignment in one action.

Skill Assessments — MCQ, Q&A, coding and video rounds when a take-home is too much.

Upskilling — Turn the gaps a submission exposed into training for the people you kept.

Everything the review needs, in the review screen.

Documents render, repositories open file by file, ZIPs unpack in place. Nothing to download, unzip or clone before you can judge it.

Scroll to Top