Limits

Limits

What AIHawk does not do, what nobody has checked, and where you have to step in.

Not verified

• How well the ranking fits you. The title search and the two readings of the postings are heuristics. This wiki records no measurement of how often the shortlist holds the jobs a person would pick. The repository's tests use fake models; the browser test uses a scripted model against a local form (tests/test_real_browser.py).
• Each site, as it is today. A plugin is a prompt written against one site's form. Sites change their forms. Sites and plugins records what happened on each site on real forms, and a confirmed send rests on one send per site, so whether a given plugin still fills its form today is not verified. A form that no longer matches its plugin can leave the model stuck or filling the wrong field; check the form before you say yes.
• Field contents. AIHawk does not compare each field with your CV in code. The model is told to write only what the CV and your answers say, and to ask you for anything else.
• Whether a send went through. After a send, the model reads the page and says whether it was submitted, rejected or unknown. "Unknown" is what it says when the page does not show either. What the page said after a send is kept in applied.csv and data/proofs/; s lists them.
• The job database. It merges public job sources, and each posting belongs to its employer; the sources and licences are in NOTICE. It is rebuilt every five hours by a workflow in the repository, and each search says when the database it used was built. Postings older than 60 days are left out by default.

What the script cannot stop

• A form can be sent. The model is told not to send and to leave that to AIHawk, after your yes. Nothing checks its calls, so it could send early or half filled.
• Captchas. The model clicks a box to tick. A puzzle ends the form as blocked, and that form is left for you.
• Accounts. On Workday the plugin creates the candidate account with your email and the password AIHawk made for you (it is in Settings, "Your answers", as account_password), and reads the verification code from your mail; this was run end to end on a local copy of a Workday flow, not yet on a real Workday site. On any other site, a login wall where you have not signed in is blocked: press e, choose "Sign in to a job site", sign in in the browser that opens, and press Enter in the terminal when done. The browser profile is kept in your AIHawk folder, one for everything. Your mail is set up once, after the resume, or from e, "Your mail".
• What your CV does not say. A form does not stop to ask. The model works out what your CV implies, and where it has nothing it writes "Please see my attached CV", picks the closest option and ticks the required boxes, statements such as the right to work included. It goes out in your name, and you answer for it.
• Sites with no plugin. AIHawk lists them with their link. Apply to those by hand.

Postings with little to read

• No description. Some sources publish none. Such a posting is judged on its title and location alone, and the judge is told its requirements and seniority are "unclear". Its score says less than a score from a full posting.
• The decision model fails. A posting it cannot read is ranked by its title alone, and the log says so.
• Titles that score low. Each m reads the next 100 postings by title, so a posting whose title matches your plan poorly is read only after the better-titled ones.