Engineering assessments

See how candidates
solve real problems.

Assess how candidates investigate problems, test changes, and use AI. Review their approach alongside the final solution.

View a fictional example. No sign-up or live assessment.

Sample assessment01 / Investigate
ScenarioX workspaceProduction IncidentSample environment

Explorer

scenario-workspace

  • README.md
  • src/checkout.ts
  • src/catalog.ts
  • tests/checkout.test.ts

src/checkout.ts

export async function checkout(cart: Cart) {  const items = [];  for (const product of cart.products) {    items.push(await catalog.get(product.id));  }  return createOrder(items);}

Your scenario

Production Incident

Investigate elevated latency in the checkout service. Find a way to restore service and explain what you would validate.

Investigate. Make a change. Validate it.

Terminal read-only preview

$ pnpm test checkout
PASS  checkout.test.ts
  creates an order with available items
  handles an unavailable product

$ curl localhost:8080/health
{ "status": "ready" }

AI assistance Optional

Help me think through where to start.

I can help you compare the request path with the latency samples. Which part would you like to look at together?

Fictional conversation, not a live assistant.
Representative workspace · fictional code and conversation · no customer or candidate data

Code, tests, and optional AI assistance in one workspace.

Realistic tasks. Clear results. You make the hiring decision.Self-hosted V1 preview

What to assess

Review more than
the final answer.

A correct answer does not explain how a candidate reached it. Review what they investigated, tested, and changed.

When you only review the output

Problem / Submission / Result

What did they produce?

When you can discuss the work

Investigate / Experiment / Validate

How did they approach it?

Review the solution.
Understand the approach.

More examplesBrowse by engineering area

These are illustrative examples, not a catalog of certified or available assessments.

Application engineering

  • Code reviewIllustrative example
  • Performance debuggingIllustrative example

Systems engineering

  • Linux kernel debuggingIllustrative example

Service operations

  • Incident investigationIllustrative example

Interactive example

What would you do next?

Read the task, choose a starting point, and explore the sample workspace.

Interactive demonstrationFictional scenario and sample content

Backend engineering

Production Incident

Checkout is slowing down. The service is up, but customers are waiting.

  1. 01The brief
  2. 02A closer look
  3. 03The workspace
  4. 04The conversation

Sample walkthrough · Start here

What would you investigate first?

Investigate elevated latency in the checkout service. Find a way to restore service and explain what you would validate.

Choose a starting point. This is an exploration, not a test.

A short product demonstration. No signup, no live environment, no evaluation.

Review the approach

See what they checked.
Plan your follow-up.

Use examples of investigation and testing to prepare follow-up questions. Activity provides context; it does not reveal a candidate's thoughts.

Illustrative work sequence · fictional activity, not a live replay
  1. 09:41 UTC

    Investigate the symptom

    Compare slow checkout requests with basket size.

    Request samples
  2. 09:47 UTC

    Check an alternative

    Use optional AI assistance to discuss a different request strategy.

    Tool-assisted exploration
  3. 09:58 UTC

    Validate the change

    Run the relevant checks and describe what still needs testing.

    Tests and follow-up

This sequence explains the kind of work an assessment can explore. It does not show a shipped activity-replay interface.

Optional AI assistance

Let candidates use the tools
they would use at work.

Include AI assistance when it fits the role. Review how candidates use it alongside their own investigation and testing.

How it works

From invitation
to review.

  1. 01

    Create assessment

    Start with a scenario that reflects the role.

  2. 02

    Invite candidate

    Send the candidate their assessment link.

  3. 03

    Complete the scenario

    The candidate investigates, makes changes, and tests their work.

  4. 04

    Review results

    Review the assessment and prepare follow-up questions.

For recruiters

Review the work.
Make your own decision.

Review the candidate's approach, results, and areas to discuss. Use the assessment to prepare for your next interview.

Assessment results support your review.
The hiring decision stays with you.

Contact us
Assessment overviewIllustrative example

Alex Lee

Backend Engineer

Completed
Scenario
Production Incident
Scenario outcome
Proposed a focused fix and validation plan

Overall assessment

A focused investigation, a practical proposal, and clear next steps to discuss.

Strengths

  • Strong debugging approach
  • Clear system-level reasoning
  • Thorough validation plan

Areas to explore

  • Initial diagnosis and alternatives
  • Trade-offs before a wider rollout
Fictional candidate and result. Not a score, ranking, or hiring recommendation.

Self-hosted / V1 preview

Run ScenarioX
on your infrastructure.

Deploy on a single Linux host with Docker Compose. Review the requirements and known limitations before deploying.

Read the deployment guide

Deployment requirements

Deployment
Single Linux x86_64 host
Runtime
Docker Engine + Compose v2
TLS and network boundary
Customer-managed
Recovery and upgrades
Not certified for V1
Review the V1 limitations Read the privacy policy

Explore ScenarioX

See an assessment.
Start with a scenario.

Explore a fictional example before planning your own assessment.