(00) About Job Atlas
Why this exists
A job search is notone problem. It is six,pretending to be one.
Boards, spreadsheets, resume tools, referral threads, and a calendar that nobody updates. Each one holds a piece of the truth and none of them talk. Atlas is the assumption that the pieces were always one system, and that treating them that way is what finally makes the search legible.
- Launch market
- India, across boards, startups, and internships
- Inputs
- Six live signal sources, versioned and timestamped
- Scores
- Candidate, company, and fit, computed separately
- Ranking
- Deterministic weights today, outcome-learned next
Youalreadyknowwhichpartsofyoursearcharebroken.Whatyoudonothaveisasystemthatagreeswithyouinwriting,ranksthedamage,andtellsyouwhichrepairpaysforitselffirst.
(02) The stack
Data, scoring, control
Three layers, and
a hard line between them.
Six inputs, one shape.
Postings, company records, resumes, code evidence, professional profiles, and contacts are parsed into versioned features with a source and a timestamp on every one. If a number moved, you can find the row that moved it.
Three scores, kept apart.
Candidate strength, company quality, and match fit are computed independently. Bundling them into one figure is how products end up unable to explain themselves, and how candidates end up improving the wrong thing.
Manual override, always.
Every automated step has a hand-operated version sitting next to it. Atlas is meant to remove the tab management and the spreadsheet, not the judgement.