Job ApplicatorTHE FIELD GUIDE
A good start
beats a rushed one.
A guide to the Mac development preview. Features and setup can change as the beta takes shape.
Before you start
You need an Apple Silicon Mac. macOS 14 is the declared minimum, but older macOS versions and the hardware matrix have not yet been validated. Intel Macs, Windows, and Linux are not supported. Keep your Mac awake while applications run.
Set up your workspace
- Sign in. A Job Applicator account is required. Review the policy documents presented during setup.
- Review your profile. Add your résumé PDF and confirm your details. Suggested name and email from sign-in still need your review. Accurate eligibility, work authorization, and other legal answers matter.
- Configure inference. Follow the model setup in your build. Options include Ollama, a local OpenAI-compatible server, and supported hosted providers. Hosted services may charge separately. Check the model connection before running the queue.
- Add a supported job. Use a Greenhouse or Ashby posting URL. Lever and Workday are not supported in this preview.
Know what the queue will do
Jobs run one at a time. Answers come from your confirmed profile first, then saved answers, then the configured model. Legal and eligibility answers must come from your profile or you. Questions the engine cannot answer confidently are asked in the app and reused.
Use the queue controls to pause or stop work. Your Mac must stay available. After an interruption, check the job’s status and the employer’s confirmation before trying again; an uncertain result is not proof that nothing was submitted.
Background checks, arbitration, drug checks, and credit checks are asked once and remembered. Review any saved answer before applying to a new employer.
Security codes and Gmail
In Settings, “Connect for security codes” grants read-only Gmail access. When supported submission needs an emailed security code, the app looks for ATS mail arriving after Submit and uses the code to finish the application.
Without Gmail, a visible browser gives you 90 seconds to enter the code. If you miss it, the job is saved as not submitted and the queue moves on. Use Continue for another visible-browser attempt.
Sending outreach needs a separate Gmail sending permission. Availability depends on the build and deployment configuration. Never share your Google password, tokens, or verification codes in a support report. You can remove granted access in your Google Account’s connected-app settings.
What leaves your Mac?
| Destination | What it receives |
|---|---|
| Employer / ATS | Application answers and your attached résumé when you authorize the queue. |
| Your AI provider | Selected context when you choose hosted inference. A local provider runs locally. |
| Account and cloud service | Sign-in and the data needed for enabled workspace and feed features. |
| Product diagnostics | Account-linked usage events, job links, failure/crash diagnostics, and security logs. Automatic redaction is best effort. |
| Gmail | OAuth access for the permissions you grant; security-code reading is distinct from sending. |
There are no app analytics switches. The draft privacy notice describes collection and retention. Read it before accepting the beta terms. Account deletion and export procedures still need launch validation; email Reuben Roy for requests, and do not assume uninstalling deletes server records.
Read the privacy draft →Still need a hand?
Start with the troubleshooting guide. For feature availability, check development changes and known limitations.