← DevSense

For engineering organisations

Your incidents, rehearsed.

Every postmortem you have ever filed is a lesson only one person learned. DevSense turns it into a simulator — your domain, your stack, the wrong theory somebody held at the time — that the graduates you hire and the engineers you already have can play in twenty minutes, with an AI teammate, before anything is at stake.

Talk to us Get the paper

custom worlds in weeks · cohorts at the universities you recruit from · a talent pool searched by evidence

01 · Custom worlds

Built from your postmortems, not ours.

A DevSense world is a small, fixed, fully authored engineering environment with one thing going wrong in it. We build yours from three things you already have: the product as your engineers know it, the stack they work in, and one or two incidents — anonymised — rewritten as evidence a player can find and consequences the world can report.

The player is a junior engineer on your team. Their AI agent can read anything and change anything, but only when told to — and it opens with a confident, plausible, wrong theory, the way the real one did. Whether they check it is the first thing the record shows.

  • Your domaina dispatch board, a ledger, a booking system — the numbers that matter to you
  • Your stackyour languages, log formats, deploy conventions; nothing proprietary leaves the building
  • Your incidentthe root cause, the tempting shortcut, the consumers nobody told, the earlier incident it rhymed with
  • Your valueswhat must be gated, who must be told, what is never done by hand — encoded in the commit gate, not a slide

02 · Two ways to use one world

Hire from transcripts. Onboard with incidents.

Campus pipeline

Sponsor a cohort where you recruit

Students at a university you hire from play your world as part of a course or a recruiting event. Your engineers read the transcripts of the students who chose to be seen: what each asked for, whether they checked the agent, what they did at the commit gate. You interview from evidence of judgment instead of a résumé and a whiteboard.

Inside the company

The incident before the incident

New hires play your last three incidents in their first week — they meet the runbook, the consumers and the trap before they meet the pager. Engineers at every level rehearse the class of decision that hurt you, in twenty minutes, with a debrief that quotes their own transcript. Build a world from the migration you have not shipped yet, and play it first.

What a player sees is narrow on purpose: no score, no rating, no leaderboard — one strength and one thing to try, each pointing at a moment in their own session. What you see is the transcript, the labelled moves and the rubric evidence with citations.

03 · The talent pool

Search by what sessions show.

Students and early-career engineers who play in the open pool can choose to be visible to organisations. When they do, you find them by evidence rather than by what a résumé claims, and you read the transcript before you read the name.

Priced per profile you unlock — not per seat, not per month. Searching is free; the filters you apply set the tier; reading a transcript is what you pay for. Ask for the rate card.

consent first · nobody is in the pool by default · candidates can withdraw at any time

FilterWhat it means
Hours in the simulatortime spent in assessed sessions — a proxy for having practised, not for skill
Worlds completedwhich challenges they finished, including yours
Competencies evidencedwhich of the seven their transcripts show, with the cited moments
Domain and stack tagsfrom onboarding and from the worlds played
Cohort and recencywhich programme, and when they last played

04 · What we claim

Evidence, not a number.

We may claim

  • Demonstrated performance across defined engineering-judgment competencies, within the simulator.
  • Inspectable behavioural evidence behind every conclusion — a verdict that cannot cite a transcript moment does not stand.
  • Worlds that are fixed, authored and fair: every trap is discoverable from evidence the player could have read.

We do not claim

  • That a result means someone is objectively a better engineer.
  • That any rating predicts on-the-job performance. That needs validation nobody has done, including us.
  • That one number captures the construct. We never show players one.

Read the transcripts. That is the product. The instrument exists so a reviewer finds the moment that matters in two minutes instead of twenty. An organisation that hired on a number we produced would be misusing it.

05 · How an engagement runs

Five weeks, one world.

  1. Discoverytwo postmortems, an architecture overview, an hour with the engineers who were there
  2. Authoringthe world files, the agent's wrong theory, the consequences table; your engineers review it for fidelity
  3. Pilota cohort, a team, or new hires play it; your reviewers read transcripts on the dashboard
  4. Reportwhere players stalled, which trap caught whom, what the world discriminated on — you keep everything

Custom worlds are priced per world. Cohorts and teams per player per world — university pilot cohorts free while we validate the instrument. The talent pool per profile unlocked. The rate card is one page.

Talk to us

Tell us what you are after and we will send the organisations paper — The Simulator Your Postmortems Wanted — and come back within a day.

I am interested in

Prefer email?