Job-Hunt Autopilot

Your morning job-search assistant

It runs inside your own Google account. Every morning it finds jobs that fit you, writes a tailored CV and cover letter for the ones you approve, and prepares email drafts ready for you to review.

No coding needed  ·  about 30-40 minutes to set up
It never sends anything by itself. You always approve, then click send yourself. Think of it as an assistant that does the boring 90%, not a robot that applies for you.

Before you start

You need two things:

The setup

1 Get your three free keys

Open each link, sign in, and copy the key into a blank note for now. You will paste them in Step 4.

2 Paste in the program (no terminal)

  1. Go to script.google.com and click New project.
  2. You will see a file called Code.gs with a couple of lines. Select all of it and delete it.
  3. Open manual-install/Code.gs from this pack, select everything, copy it, and paste it into the empty Code.gs. Press Save (the disk icon).
  4. Rename the project (top-left) to Job-Hunt Autopilot.

That is the whole program pasted in. You do not need to understand it.

3 Create your dashboard sheet

  1. In the toolbar, open the function dropdown (it says something like myFunction) and choose setupProject.
  2. Click Run. Google asks you to review permissions - choose your account, click AdvancedGo to Job-Hunt Autopilot (unsafe)Allow. This is normal: it is your own script asking to use your Sheets, Drive and Gmail.
  3. Open the Execution log at the bottom - it prints a link to your new Job-Hunt CRM spreadsheet. Open it and keep the tab handy. This sheet is your whole dashboard.

4 Answer the questions

In the spreadsheet, go to the Setup tab (the first tab).

  1. Fill in column B next to each question: your name, email, phone, location, LinkedIn, the roles you want, your skills, and a one-line summary. Some cells hold an example - just type over them.
  2. Paste your keys from Step 1 into the API KEYS rows.
  3. Optional Under Search filters: keep only certain regions, drop specific sub-areas, allow remote from anywhere, exclude job boards you dislike, and choose whether to tailor documents for portal roles or email applications only. Leave blank to search everywhere.
  4. Tick the Save checkbox at the bottom. If nothing happens (the box only works after Step 6), instead choose applySetup in the function dropdown and Run.

Your keys are stored securely and the cells are cleared on purpose. Come back and change any answer any time, then Save again.

5 Add your CV

The easy way: choose buildMasterCv in the function dropdown and click Run. It creates a clean, ATS-friendly CV document for you (with a {{SUMMARY}} placeholder the tool fills per job) and links it up automatically. Then open that document (link in the Execution log) and replace the example experience with your real history. Keep it a single column and keep the {{SUMMARY}} line.

ATS-friendly means simple and single-column, so the automated systems employers use can read it properly.

6 Test it, then turn on autopilot

Run these one at a time from the function dropdown, checking the sheet after each:

  1. dailySource - jobs appear on the Opportunities tab.
  2. scoreQueue - the AI scores them; strong ones show on the Approvals tab.
  3. On Approvals, pick Approve for one job.
  4. prepApprovedBatch - a tailored CV and cover PDF land in your Drive, and (if the job listed an email) a draft appears in Gmail.

Happy with that? Run installTriggers once. From now on it runs every morning by itself.

Timezone: the daily run is set to 06:00 Johannesburg time. To change it, open Project Settings in the script tab and set your timezone (or ask whoever gave you this pack).

Your daily 10 minutes

  1. Open the sheet → Approvals tab. Read the role, company, score and reasoning, open the link, and pick Approve or Skip.
  2. A bit later, open Gmail → Drafts. Review each prepared email, tweak it, and send. For portal-only jobs, open the link and apply by hand using the CV and cover from your Drive.
  3. On the Opportunities tab, set the status to sent or submitted (the date fills in for you). Later mark responded or interview as things progress.

The sheet's Readme tab has this same guide, always one click away.

Good to know

For developers - the terminal (clasp) path

If you are comfortable with a terminal, you can deploy the split src/ files with clasp instead of pasting the bundle. See docs/SETUP.md in this pack for the flow, then do Steps 4-6 above the same way. Tuning knobs and the daily runbook are in docs/RUNBOOK.md; the sheet layout is in docs/SHEET_SCHEMA.md.