How it works

Four things happen here: postings are ranked against what you said you want, a resume is written from facts you confirmed, the browser extension reads the posting you are looking at, and what you sent is kept. This page says how each one works, and where it stops.

How a posting is ranked

Four things carry points: Pay, The Work, Enjoyment and Distance. What each one is worth comes from a budget you set, so the weighting is yours rather than ours. The total is out of 100, and the word beside it says Strong fit from 70 up, Worth a look from 40 to 69, and Weak fit below that.

Every job starts at zero and earns its way up. A category nobody has answered earns nothing there, and it is never scored as though the answer were bad. When a category earns nothing the row says why. When there was nothing at all to judge, the score is a gray Jobzeez ? with no number printed, because a zero that earned nothing reads exactly like a zero that was judged and lost.

A hard rule is not a preference. A preference earns points it can miss; a hard rule saying no holds the score at zero, because that is a decision you made rather than a gap in what the employer wrote. A score worked out from the short version of a posting is marked est., and reading the whole posting can change it.

What the browser extension reads, and what it never does

It reads the posting on the screen in front of you, and it is put into the page when you press the button and not before. What it hands to Jobzeez is the page's address, the page title, the markup of the posting itself, and the fields the board's map named. Scripts are stripped out of a capture before it leaves the page.

What it knows about a job board is one hand-edited map per board: selectors, and public knowledge about that site. No map holds anything about you. Indeed is the only board with a map today, and no board gets one on a guess, because a map is a reading of a live board that somebody has to sit down and do.

It never sends an application. It types nothing you have not seen and approved, it cannot submit a form, and it asks the board for nothing you did not ask for yourself. When a site changes its markup and the map's rule for the job title finds nothing, the capture refuses and says so - it names the rule that died rather than saving the page's own heading as the job title, which on a signed-in board is a greeting. That is not a hypothetical: Indeed's map records that the whole family of selectors it was first written from was gone within four days.

How a resume is written

Your career facts are the source of truth, and a resume is something generated from them. Only facts you have confirmed, or that are supported, reach a page at all. Every line carries the fact it came from, so any sentence can be checked back against your own record before it goes anywhere. A fact you mark as never on a resume stays in your record and stays off every page.

How far a fact may be used is decided by the state it is in:

Saying a confirmed fact in better words is allowed; inventing something it does not support is not. Where nothing supports a claim, the line is left out. Where a resume needs an answer from you first, preparation stops and waits for you rather than filling the gap, and it shows up as something needing attention. Changing what a fact says keeps the sentence it used to say and marks the resumes that cited the old one.

What it remembers

An application carries a status you set: saved, preparing, ready, submitted, interviewing, offer, hired, rejected, withdrawn, archived, or ghosted. The resume that went out with a submission is kept exactly as it was sent, so you can open an application later and read the same page the employer read.

It knows an employer replied because you told it. Nothing in this app reads a mailbox. The one adapter that was ever meant to has been deleted rather than left sitting there, and the record of what came back is the button you pressed saying what happened. Most replies are not email anyway, and a machine guessing which message was a rejection would be deciding something about your search quietly.

It also remembers what you already applied to, and says so before you start a second application for the same job. A different role at the same employer is not treated as a duplicate. For an application you made on an employer's own site, I already applied to this is how you tell it.

What it does not do yet