What needed solving.
Reduce repetitive job-search and application form work while grounding answers and resume tailoring in a candidate's own profile and preferences.
- 01Resume + preferences
- 02Matching + paced ATS worker
- 03Application receipt + replies
Simplified from the implementation and project notes.
How it fits together.
Build a profile and rank relevant roles
Resume upload begins a private draft, with profile and search preferences completed before account creation. Posting embeddings narrow candidates; location, preferences and parsed requirements apply rule checks, with model judgment reserved for ambiguous fit decisions.
Dispatch with explicit missing-fact handling
A paced worker uses supported ATS handlers in Browserbase, chooses a role-family resume and fills known profile answers. Missing required facts become questions; employer-specific free text stays tied to that posting, and submission receipts represent a browser outcome only.
Route employer email for human review
Inbound messages are signature-verified and retained, with selected messages forwarded. Follow-up drafts cite saved profile evidence; sending requires a single-use, version-bound approval. The isolated PGlite QA uses real routes while disabling external requests, payments, mail and application workers.
Building and checking it.
Candidate uploads or builds a profile, selects roles and location, reviews match counts, chooses a plan, then applications are paced to plan quota and only sufficiently strong fits are queued. Applicants can answer unresolved questions in dashboard/chat.
The admin interface includes funnel and application operations. Advertising workflow drafts content and applies a factual lint before human review; Meta actions depend on app review.
ATS support is platform-specific; unsupported or uncertain submissions need explicit handling. An automated submission receipt is not evidence of an interview or employment outcome.
Source notes
Based on repository code and project records reviewed on October 30, 2026. Historical checks are described as recorded, not rerun for this article. Screenshots, renders, and mockups are labeled individually.
joblessnomore/README.mdjoblessnomore/docs/SEPARATION.mdjoblessnomore/package.jsonjoblessnomore/lib/plan.tsjoblessnomore/lib/apply/questions.tsjoblessnomore/scripts/qa-onboarding.mjsjoblessnomore/tests/fixtures/workday/posting.html