Create a test
Build a reusable assessment definition: pick a template (or skip), add questions from the bank or write your own, then publish. Online or offline mode is chosen later, when you send it.
Open the tests page#
From the dashboard, expand Interviews in the left nav and click Test List. The page renders as a two-column grid of test cards - each card shows the title, the question count, a private/public lock indicator, the description, the duration, the candidate counts, and a row of question-type icons on the right.
We are looking for someone who can: -Write code…
test1
To evaluate candidates' technical skills, problem-solving ability, and understanding of full stack development.
to determine whether a candidate can think, analyze, and solve problems effectively in real-world scenarios.
The goal of these advanced IT hiring assessments is not just to evaluate theoretical knowledge, but to identify candidates who can solve real-world problems effectively.
The purpose of the test is to evaluate programming skills, logical thinking, problem-solving ability, and ob readiness.
Interviews group in the left nav, alongside Interview List, Pending Requests, and Archived Tests. Backend objects: a Test = Interview, an Interview = InterviewItem.Start a new test#
- Click '+ Create New Test'The button is in the top-right of the Test List page.
- Pick a starting pointEither start blank, or use
Cloneon an existing test card. Cloning is the easiest way to riff on a known-good assessment - it copies the metadata, every question, the workspace shape, and the time budget.
Pick a template (or skip)#
A test boots its own private workspace for each candidate. Pick a template that defines what's inside that workspace - which machines boot, which recipes run, what's pre-installed. You can also skip the template entirely and start from a blank workspace if your test is text-only or you'd rather compose machines from individual recipes later.
Title, role, and difficulty#
Fill in:
| Field | Type | Description |
|---|---|---|
| Titlerequired | string | Visible to candidates. Use the role wording, not the internal codename. |
| Role | enum | Backend, frontend, full-stack, devops, data, etc. Used for filtering and analytics. |
| Difficulty | enum | junior / mid / senior / staff. Helps candidates calibrate. |
| Estimated duration | minutes | How long the test should take. We show this on the candidate intro page. |
Edit the questions#
A test is a list of questions. For each question slot, you have two options: pick an existing question from the bank, or write your own.
Pick from the question bank#
The question bank is your account's library of every question you (and your teammates) have ever written, plus EasyEnv's catalog of pre-built challenges. Filter by type, role, stack, or difficulty and add a question with one click.
Create your own question#
If the bank doesn't have what you need, click + Create your own. The Custom Question modal opens with a type selector at the top - the rest of the form swaps out based on the type you choose.
Question types#
EasyEnv ships six question types. You can mix them freely inside one test.
| Field | Type | Description |
|---|---|---|
| Challenge | hands-on | A recipe-backed exercise the candidate solves inside a real machine. The pass condition runs on submission. Strongest signal for engineering depth. |
| Single-choice | auto-scored | Classic radio-button question with exactly one correct answer. |
| Multi-choice | auto-scored | Checkbox question. Mark one or more options as correct. Useful when more than one answer applies. |
| Text-based | reviewer-scored | A markdown-supported free-text response. Reviewer-scored using your rubric. Best for design rounds and trade-off reasoning. |
| Whiteboard | reviewer-scored | Candidate diagrams the answer on an interactive whiteboard. The drawing is saved with the submission for manual review. |
| True-False | auto-scored | A binary "the statement is correct" / "the statement is incorrect" prompt. One-tap to answer. |
Each type has its own form fields. See Add questions for the per-type field breakdown.
Set a time limit#
For offline tests, the time limit starts the moment the candidate opens the link. They can pause once if your account allows it. After the limit, the workspace switches to read-only and submits whatever was there.
Publish the test#
Click Publish. Until you publish, the test is in draft and cannot be sent to candidates. After publishing, you can keep editing, but changes only affect new interviews, not ones already in flight.