For engineers
Show the work behind your resume.
Build an Engineering Passport from your projects. Each project gets a Builder Report that links every finding to its code, and hiring teams can invite you to a Simulation. You choose what to share, with whom, and for how long.
Free for engineers. Your Engineering Passport, Builder Reports, applications, and Simulations never require a paid plan.
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.
- Event receiveddispatch starts delivery for one event
dispatcher.ts - Duplicate checkAn event_id already seen is skipped
dispatcher.ts - Post to partnerMarked seen only after a successful post
dispatcher.ts - Retry on failureUp to five attempts, with backoff
retry.ts
Backed by evidence
The retry loop stops after five attempts and exits on the first successful response.
retry.ts · lines 18-27
Connections
Connect GitHub, GitLab, or a local folder to build your Engineering Passport.
Connect a repository, upload a ZIP, or capture a folder on your machine. You review what is read before anything is added to your Engineering Passport, and each project gets a Builder Report: findings that cite source lines and state what was not checked.
Connections are for evidence you already own. Fydell does not scrape public profiles or invent projects you did not select.
Pick the sources
Repositories, ZIP uploads, or local capture. Nothing is added until you confirm.
One Builder Report per project
Findings cite source lines and state what was not checked.
- Passport
- Builder Report
- Hiring Workspace
Project from this source
Webhook delivery service
Partner event delivery with retries and a duplicate-event gate.
Files in the snapshot
retry.tsdispatcher.tskeep-draft.test.ts
Sharing
Share your Engineering Passport on your terms.
Pick the projects from your Engineering Passport, preview what the recipient sees, set an expiry, and revoke at any time.
What you leave out never appears in the shared record, not even by name. Recipients see your statement marked as self-reported, and the Builder Report findings with their limits beside them.
Only the projects you tick
At the versions you pin, with source excerpts only if you include them.
Preview before you send
The recipient view is on screen while you choose.
Expiry and revoke
Cut access when the conversation ends. Saved copies cannot be recalled.
Share your Engineering Passport
Include in share
2 of 3 projects included
What the recipient sees
Jordan Hale
BackendFrontendFull-stack
- Webhook delivery serviceBounded retries · Duplicate event gate
retry.ts · lines 18-27 - Ledger export pipelineInvalid row hold · Batch size cap
validate.py · lines 18-23
Simulations
Simulations, disclosed up front.
A Simulation is a timed engineering task a hiring team assigns. Before anything starts you see the brief, the time (90 minutes for about 50 of work), the AI tool policy, and what is recorded.
You can ask the simulated teammates questions, run the checks, and submit with a handoff that says what is still open.
Brief and policy first
Scope, time, and recording are shown before the timer starts.
Say what is open
The handoff is yours. Fydell shows it beside the results.
Keep the draft when a send fails
Behavior after a failed send
Composer, recorded at submit
Partner returned 502 · send failed
Draft kept
Reply to Northwind supportCan you confirm the partner retry window before we close this ticket?
Submitted behavior - the typed message stays available after the failed send.
Checks
3 passed · 1 not assessedPassedPassed3
- CHK-01PassedDraft kept after a 502Observed
- CHK-02PassedDraft cleared after a 200Observed
- CHK-03PassedRetry still editableObserved
Not AssessedNot Assessed1
- CHK-04Not AssessedRepeated submissionsNo run
FAQ
Questions from engineers.
Do I pay anything?
No. Your Engineering Passport, Builder Reports, applications, and Simulations are free. A Pro plan is in preview and will never be required to apply.
Can I use private or employer code?
Upload a ZIP of a project you are allowed to share. It is read the same way as a public repository and labelled as uploaded source, with no public link to the code. For work you can't share at all, describe it in your own words; recipients see it marked as described by you, with no source analyzed.
I don't have public repositories. Can I still use Fydell?
Yes. Upload a project as a ZIP or describe your work in your own words. If a hiring team invites you to a Simulation, you can take it without any repositories.
What can an employer see?
Only what you share: the projects you tick, at the versions you pin. Applying to a role uses the same choice. You can set an expiry and revoke a link at any time, but copies someone already saved cannot be recalled.
Can I use AI tools in a Simulation?
Yes, the same way you would at work, unless the brief says otherwise. Fydell cannot see your tools and does not try to detect them. You describe any AI help in your own words.
What if a finding about my code is wrong?
Flag it, add context, or propose a different reading. Your note is attributed to you and shown next to the finding; the original stays visible.
Do I need to install anything?
No. Everything works in the browser. The Fydell desktop app for Windows and macOS lets you take Simulations in your own editor, with the task folder on your computer. Its installers are not code-signed yet; the download page shows the first-launch steps.
Put your work where it can be seen.
Free for engineers, always.