FydellFydell
Get started

Solutions

Three workflows. One evidence model.

Hire with Simulations and requirement review in the Hiring Workspace. Compare agent setups on the same task. Or build an Engineering Passport you control, with a Builder Report for each project. Every path leaves findings you can open.

Start an evaluationCreate your Engineering Passport

Overview

Review engineering work from people and agents.

Lumen Ledger · Backend opening

In progress

5

  • Working2
  • Preparing2
  • Interrupted1

Ready for review

4

  • Human submissions3
  • Agent runs1

Needs attention

3

  • Setup failures1
  • Grading errors1
  • Expiring invitations1

Simulation runs

342

The record of how engineering work gets done.

  • Owen BlakeBackendHuman
    BugWebhook recoveryReport ready8 passed · 1 failedReview report
  • Agent configuration v3BackendAgent
    ReliabilityWebhook recoveryRunningExecuting checksView run
  • Claire HoffmanBackendHuman
    BlockedDraft preservationNeeds attentionUpload interruptedView details
  • Ellen MarshFrontendHuman
    BugComposer raceReport ready12 passed · 0 failedReview report
  • Setup v2 · keep-draftBackendAgent
    ReliabilityDraft preservationPreparingQueued on runnerView run

What each path leaves

Three records. One evidence model.

Whether you hire, compare agent setups, or share your own work, the record stays inspectable: what Passed, what Failed, what was Not Assessed, and what was left open.

Engineering Passport

Shared record

Snapshot Ready

Jordan Hale

BackendFull-stack

  • Webhook delivery serviceGitHub · pinned
  • Ledger export pipelineGitLab · pinned

Expires in 14 days · 2 of 5 projects included

Engineering Passports

Selected projects with contribution context and evidence a recipient can open.

Simulation

Keep the draft when a send fails

In Review

Jordan Hale · Lumen Ledger · 41 min · Backend

  • CHK-01Draft kept after a 502
  • CHK-02Draft cleared after a 200
  • CHK-03Existing delivery tests
  • CHK-04Repeated submissions

Observed: after a 502 the typed reply stays in the composer.

Simulations

Timed task, checks, file changes, and handoff in one artifact.

Agent comparison

Setup v1 to v2

Completed

From Clear the composer on any error

To Keep the draft until a 2xx is confirmed

  • AGT-01Draft kept after a 502 · setup v1
  • AGT-02Draft kept after a 502 · setup v2
  • AGT-03Draft cleared after a 200 · both setups

Acme keep-draft · held-out sealed until after the run

Agent comparison

Same task, two setups, held-out outcomes you can inspect.

Engineering hiring

Shared work, reviewed requirement by requirement.

In your Hiring Workspace, run a Simulation only when the record leaves a question open. Applicants send selected projects as Engineering Passports with cited Builder Report findings, and your team reads them against the opening, not against a resume score.

Each requirement opens its finding and source. Cited, Partial, and Not Assessed stay distinct. Your team drafts the interview question from the gap, then Advance, Hold, or Decline with a private note.

Start with
An opening and the requirements your team will assess against.
Candidates send
Selected projects with Builder Reports and cited findings, not a resume score.
Your team decides
Advance, Hold, or Decline, with a private note. Fydell never ranks.

Try the labelled sandbox

Hiring for employers

Applications

Lumen Ledger · Backend Engineer · Partner integrations

Owen Blake

BackendLumen LedgerPartner integrations2 projects shared

What the shared work demonstrates

A webhook service that stops retrying after five attempts and skips events it has already delivered. Concurrent workers and load behavior were not shown.

Webhook delivery service

Delivers partner payment events with bounded retries and a duplicate-event check.

  1. Event receiveddispatch starts delivery for one eventdispatcher.ts
  2. Duplicate checkAn event_id already seen is skippeddispatcher.ts
  3. Post to partnerMarked seen only after a successful postdispatcher.ts
  4. Retry on failureUp to five attempts, with backoffretry.ts

Selected requirement citesdispatcher.ts · lines 38–45

Requirements

  • The seen check is there, but two workers could both pass it. No test covers that.

Coding-agent evaluation

Change one instruction. Keep the same Simulation suite.

Practice and held-out checks stay separate, so a setup that passes the public retry test but fails the held-out keep-draft test is visible as exactly that.

Change one instruction, keep the same suite and seed, and inspect Passed, Failed, and Not Assessed side by side. One labelled run never crowns a model or claims a setup is ready to ship.

Setup v1
Clear the composer after a transport failure. Public retry Passed. Held-out keep-draft Failed.
Setup v2
One instruction changed: keep the typed reply. Same task suite. Held-out keep-draft Passed.
Read as
Same task, two setups. Practice and held-out stay separate so you can see what changed.

Get started

Open Agents
Lumen Ledger

Setup v1 and v2

Same task, same held-out checks, run once each
CriterionSetup v1Setup v2
TaskKeep the draft when a send failsKeep the draft when a send fails
InstructionClear the composer on any non-OK responseKeep the draft until a 2xx is confirmed
Files changedsrc/composer.tsxsrc/composer.tsx tests/keep-draft.test.ts
Draft kept after a 502FailedPassed
Draft cleared after a 200PassedPassed
Repeated submissionsNot AssessedNot Assessed

Building a work record

Add a project, state your contribution, share a link you can revoke.

Your Engineering Passport collects your projects, each with a Builder Report that keeps observations labelled and what could not be checked open, so a recipient reads the work as it is.

Pin versions, preview the recipient view, set an expiry, and revoke when the conversation ends. Excluded project names never appear on the shared link.

You control
Which projects appear, which versions are pinned, and when the link expires.
Recipients see
Selected work only. Excluded project names never appear.
Limits stay visible
Observations stay labelled. What could not be checked stays open.
For engineers
Lumen Ledger

Jordan Hale

Engineering PassportBackendFull-stackLumen Ledger2 projects shared

At Harbor Pay I own partner payment delivery. The webhook service keeps posts reliable with a and an . Next: show how it holds up with .

Featured project

Webhook delivery service

Delivers partner payment events with bounded retries and a duplicate-event check.

  1. Event receiveddispatch starts delivery for one eventdispatcher.ts
  2. Duplicate checkAn event_id already seen is skippeddispatcher.ts
  3. Post to partnerMarked seen only after a successful postdispatcher.ts
  4. Retry on failureUp to five attempts, with backoffretry.ts

Backed by evidence

  • The retry loop stops after five attempts and exits on the first successful response.

    retry.ts · lines 18-27

2 projects shared · link open for 14 days

Start where your work already is.

A role you are hiring for, an agent setup you are unsure about, or a project you already built.

Create an accountBrowse resources