A browser agent that applies to jobs
A browser agent that clicks Submit is holding a loaded action. Everything in the design should be about being certain before that moment.
Read morePage 13 of 17 · 323 guides in total
A browser agent that clicks Submit is holding a loaded action. Everything in the design should be about being certain before that moment.
Read morePublishing browser control as MCP tools means an agent you did not write can drive a browser you are responsible for.
Read morePlaywright was built for tests, where the author knows the page. An agent does not, which changes which of its features matter.
Read moreThe usual comparison is written for test suites. Agents need different things, and the ranking changes once you weigh those.
Read moreGenerating forty versions is trivial. Keeping forty versions consistent with each other, and with the person, is the actual problem.
Read moreThe useful question is not whether you meet every requirement. It is which of the ones you miss would actually stop you.
Read moreTailoring should change what is emphasised, not what is true. The architecture is what enforces that, not the prompt.
Read moreEvery downstream feature — matching, tailoring, auto-apply — is limited by this one object. It is usually the least designed part of the product.
Read moreMost ATS scorers conflate document parseability with candidate fit. Separating deterministic text extraction from semantic role alignment is what makes the output technically sound and genuinely useful.
Read moreA tool that detects employment gaps is one design decision away from being a tool that discriminates against carers and the recently ill.
Read moreInserting the company name is not personalisation. Recruiters can tell, and a template with a merge field is worse than no letter.
Read moreHalf of what a gap analyser finds is not a gap at all — it is something the candidate has and never wrote down.
Read moreThe line that decides whether this tool is useful or harmful: surfacing a term the candidate earned, versus suggesting one they did not.
Read moreScale and personalisation pull against each other by definition. The useful question is which parts of a message can scale and which cannot.
Read moreMost of this system is not about sending. It is about knowing, accurately, what has already happened.
Read moreRecruiters decide in about four seconds. Almost everything a generated email wants to say is spent after that decision is made.
Read moreEvery job search tracker dies the same way: manual entry. If the user has to maintain it, they will not.
Read moreGuessing an address from a name pattern is the standard approach, and it is wrong on three separate counts.
Read moreAn agent reading a job seeker’s inbox has access to the most sensitive thing they own during a search. Design for that first.
Read moreGenerating the message is the easy tenth of this. The other nine tenths is sending infrastructure and the rules you enforce on yourself.
Read moreReading about ATS screening helps. Running your actual resume through one helps more.
New guides added regularly