new-joblisted

# Start a new application ## Check the deal-breakers first If the prompt carries a Deal-breakers section, test the posting against it before doing anything else. Salary band, location and working pattern are usually in the posting itself, so this costs one read rather than a research pass. If the role breaks one, say which and stop: > This pays £70,000–90,000 and your floor is £90,000. Want me to set it up > anyway? Then do as you are told. The point is not to refuse work, it is to make the person decide before an evening goes into it rather than after. A role that breaks a deal-breaker and gets set up anyway is fine; a role that breaks one silently is the failure. ## Step 1: Get the job description If given a **URL**, call `boulot_fetch_job` first, always. Ashby, Greenhouse, Lever and Workable publish the description as structured JSON, and about half of this vault's applications come from those boards. Fetching the page instead returns a JavaScript shell and a title. It will also tell you if a posting has been closed or unlisted, which is a different problem from being unable to read it, and worth relaying accurately. Only if that fails, try `WebFetch`. If that also fails, say so plainly and ask for the text: > I could not read that page, a lot of job boards block it. Paste the > description and I will carry on. Never guess at a job's contents from its URL, and never half-fill a folder from a failed fetch. An application built on an invented JD is worse than non