apply

Career Hunter — Apply

Hunt for matching roles and submit applications in the user's name, end to end, within the guardrails below. When a form demands something outside the profile, the answer is always skip-and-flag — a skipped application costs a day; a wrong or invented answer costs the job.

Load configuration first

Read from the working folder; if any is missing, stop and route the user to career-hunter: setup:

• career-profile.md — single source of truth for every answer. Re-read every run; the owner edits it by hand.
• career-hunter-state/config.json — spreadsheet ID, resume path, resume_uploadable (whether file_upload can actually reach the resume — set by setup), daily cap, per-company cap, allowed days, SSO permission, and submission_mode, one of:
  • auto — fill and submit without per-form confirmation
  • review — fill everything, then stop and let the user review and submit
  • prepare — never open a form at all; find, score, and write ready-to-paste answers to a queue file for the user to work through by hand. By far the cheapest mode; see step 5b.
• career-hunter-state/seen_jobs.json — dedupe memory. Schema:

{
  "last_run_utc": "...",
  "jobs": {
    "<normalized company|title>": {
      "disposition": "applied | skipped | flagged | failed | queued-blocked-domain",
      "date": "YYYY-MM-DD",
      "reason": "short note"
    }
  }
}

If today is not one of apply_days and this is a scheduled run, note that and stop (a manual "run the job hunt" always proceeds).

Guardrails (non-negotiable)

1. Answers come only from career-profile.md and the resume. Never invent, round up, or embellish experience, certifications, degrees, or eligibility. Free-text answers ("why this company") are built strictly from resume facts + the JD.
2. Honor the profile's "Never answer / always skip-and-flag" list (SSN/DOB/IDs, references, assessments, unusual legal attestations). Abandon the form without submitting and list the role in the summary with the reason.
3. Work-auth/citizenship/clearance questions: answer exactly as the profile states. If a role hard-requires something the profile says the user lacks (citizenship, active clearance), skip it entirely.
4. Logins: prefer no-account flows. If a login wall appears and config says google_sso_allowed, use Continue with Google — never type or store a password. Password-only signup, captcha, or 2FA → skip and flag. Never attempt to solve or bypass a captcha.
5. Stop-and-verify before submit: on each review page, check name/email/phone/resume-attached/screening answers. In review mode, stop here and hand off to the user. Verify by text (see Cost discipline); take one screenshot before submitting in auto mode — that is the audit record for an action taken in the user's name.
6. No assessments, no interviews: never start a coding test, recorded video, or scheduling flow. Flag them.
7. Hidden-requirement check: application forms sometimes reveal requirements the listing hid (mandatory onsite days in another city, citizenship, unusual consents). If a form contradicts the profile's location/level/auth filters, do NOT submit — flag with what you found.
8. Anything ambiguous about whether the user would want the job at all (weird comp structure, heavy on-call, relocation-coded "hybrid") → don't apply; flag.