Hiring Workspace
Hiring Workspace is where your team reviews applicants against a role. Open each applicant beside your requirements, read the findings, then Advance, Hold, or Decline.
For employer accounts. Applying is free for engineers.
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.
Delivers partner payment events with bounded retries and a duplicate-event check.
dispatcher.tsdispatcher.tsdispatcher.tsretry.tsSelected requirement citesretry.ts · lines 18–27
Requirements
The loop stops after five attempts and exits on the first successful response.
Applications
Publish a role and share one link. Applicants send the projects they choose, at the versions they pin, and your team reads them requirement by requirement.
What an applicant leaves out never appears in the review, not even by name. What they share is exactly what you see.
One link per role
Requirements listed. Applications arrive with pinned projects.
Read by requirement
Supported, not yet enough, or not covered, with the finding beside it.
Ask or invite
A question on a gap, or a Simulation when the record leaves one open.
2 of 3 projects included
What the recipient sees
Jordan Hale
BackendFrontendFull-stack
retry.ts · lines 18-27validate.py · lines 18-23Simulations
When the record leaves a question open, invite a Simulation and read the changes, checks, and handoff in the Hiring Workspace.
Composer behavior, 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.
The draft is kept when the partner returns a 502 and cleared after a 200. Repeated submissions were not covered.
Limits