Building a job recommendation engine
The hard part of a job recommender is not the model. It is that the inventory expires, the user has no history, and the feedback you collect is biased by what you showed.
Read morePage 12 of 17 · 323 guides in total
The hard part of a job recommender is not the model. It is that the inventory expires, the user has no history, and the feedback you collect is biased by what you showed.
Read moreA relevance score is a promise to the user. If 80% does not mean something specific and consistent, the number is decoration.
Read moreSemantic search feels magical in a demo and disappoints in production for reasons that are entirely predictable — and mostly avoidable.
Read moreMost teams cannot tell whether a change improved their matching. That is not a metrics problem — it is that nobody built the evaluation set first.
Read moreA model ranks job listings well and inconsistently. Both halves of that sentence determine how you should use it.
Read moreA career assistant is a retrieval problem wearing a chat interface. Most of the work is deciding what it is allowed to see.
Read moreMCP makes your job tools portable across clients. It also means a component you did not write is deciding what your agent can see.
Read moreA job search is not a request. It runs for weeks, across restarts and deploys, and every assumption that suits a request breaks.
Read moreMultiple agents are worth it when the subtasks genuinely differ. They are not a way to make one unreliable agent reliable by cloning it.
Read moreScoring a job is easy. Deciding whether it is worth the ninety minutes a good application costs is a different question entirely.
Read moreThe risk is not failing to learn. It is learning too fast from too little and locking someone into a version of themselves from three weeks ago.
Read moreAn agent is mostly its tools. Most agent failures that look like reasoning problems are tool design problems wearing a disguise.
Read moreThe reason to model an agent as a graph is not elegance. It is that a job search runs for days and something will crash in the middle.
Read moreMemory is not a bigger context window. It is deciding what is worth keeping, and being willing to throw the rest away.
Read moreMost teams reach for multiple agents too early, for a problem that was really a tool design problem.
Read moreThe form is the easy part. What decides whether the application is any good is the custom questions the employer added underneath it.
Read moreThe parse-and-prefill step is the whole game here: it saves the candidate effort and quietly introduces the errors a recruiter will read.
Read moreWorkday is where most application automation quietly stops working, and the reasons are structural rather than technical.
Read moreOperating a screen is the most general form of automation and the most expensive. Use it where nothing else reaches, not as a default.
Read moreApplicant tracking systems are a small number of products dressed in thousands of skins. Detect the product and most of the difficulty disappears.
Read moreReading about ATS screening helps. Running your actual resume through one helps more.
New guides added regularly