PM 구직을 실행하기 위해 Claude Code에 AI 구직 에이전트를 구축했습니다.

A personal AI agent for job search. One engine, many profiles. Built on Claude Code + a small TypeScript-free Node toolkit; all the AI lives behind the CLI. A job-search pipeline that scans ATS feeds and job boards, filters roles against my preferences, drafts tailored cover letters, pushes everything into Notion as a Kanban pipeline, and reads my Gmail to move cards when recruiters reply. I built it for myself. When a family member also needed a job search, I rebuilt it so one codebase could serve multiple candidates without code duplication. It started as a single-user Python + AppleScript Frankenstein — hardcoded to me, hardcoded to one Notion workspace. After ~1 month of daily use and a clear picture of what actually mattered, I rewrote it from scratch: - v1 (prototype) — single-user, monolithic. Shipped fast, was good enough to land interviews, accumulated drift as fast as I shipped features. - v2 (this repo) — engine cleanly split from profile data, so one deployment serves multiple candidates. Per-profile Notion DBs, per-profile resume archetypes, per-profile salary models. Onboarding a new candidate is a 10-minute markdown questionnaire (see Stage 18), not a day of copy-paste. The old v1 codebases are not public — they predate the clean-slate rewrite and carry personal data in their history. engine/ shared code — no PII, no personal preferences modules/ discovery/ ATS / board adapters (Greenhouse, Lever, Ashby, SmartRecruiters, Workday, CalCareers, USAJOBS, RemoteOK). Auto-registered. generators/ Resume DOCX / PDF, cover letter PDF. tracking/ Gmail delegation (via Claude MCP, not OAuth-on-disk). core/ filter / dedup / validator / notion_sync / company_resolver / salary_calc / url_check / jd_cache / email_* / fit_prompt / profile_loader commands/ scan · prepare · sync · validate · check cli.js dispatch + arg parse profiles/ _example/ template profile, synthetic data (committed) / personal profile (gitignored) data/ shared master pool (jobs.tsv, companies.tsv) — gitignored scripts/stage18/ onboarding wizard for new profiles skills/job-pipeline/ Claude skill that drives the flow rfc/ design docs (001-core split, 002-check, 004-onboarding) Mental model: Profile = data. Engine = service. Anything in engine/ must work for any candidate; anything candidate-specific lives in profiles// . - Scan — Poll ~8 ATS / job-board adapters for roles at target companies. Dedup across profiles via shared data/jobs.tsv . - Filter — Rule-driven (title / company / location blocklists, level caps, per-company active caps). Retroactive sweeps via validate . - Prepare — Two-phase (pre / commit) with a human review gate. Assigns resume archetype, drafts cover letter with per-profile voice, computes a salary band from Tier × Level × cost-of-living. - Sync — Push / pull against Notion. Defaults to dry-run; --apply writes. Uses Notion SDK v5 (dataSources.query ). - Check — Reads Gmail replies via Claude MCP, classifies (rejection / interview invite / info request / recruiter outreach), updates Notion status and adds comments. - Onboarding wizard — A markdown intake form generates profile.json /filter_rules.json /resume_versions.json / cover letter templates, provisions per-profile Notion databases, and (optionally) imports a prior hand-rolled prototype. git clone https://github.com/ymuromcev/ai-job-searcher.git cd ai-job-searcher npm install npm run setup-hooks # installs the PII pre-commit guard npm test # 490+ tests, no network required cp -r profiles/_example profiles/me cp .env.example .env # then fill in ME_NOTION_TOKEN etc. node engine/cli.js scan --profile me Full onboarding (per-profile Notion DB provisioning + resume archetypes + cover-letter voice) goes through the Stage 18 wizard. - Node 20+ - A Notion integration token per profile (the pipeline writes to per-profile databases it creates during onboarding) - Claude Code for the end-to-end flow (the job-pipeline skill drivesprepare → human-in-the-loop review →sync ). The CLI itself runs without Claude for scan / validate / filter use cases. All tokens live in a root .env , namespaced by profile id: ME_NOTION_TOKEN=secret_... ME_USAJOBS_API_KEY=... ME_USAJOBS_EMAIL=... profile_loader.loadSecrets(id, env) strips the _ prefix so engine code sees NOTION_TOKEN etc. The .env file is gitignored; a pre-commit hook scans diffs for common leak patterns as backup. npm test # Node's built-in test runner, no framework - Pure helpers are the default; side-effectful code lives in commands/ andscripts/ . - Network calls go through modules/discovery/_http.js#defaultFetch (ctx.fetchFn in tests) — neverfetch directly. - Architectural changes go through an RFC under rfc/ before code. - PRs welcome but please open an issue to discuss direction first — this is a personal tool, not an open-source product. See CLAUDE.md for agent-facing rules, docs/ai-assistant-notes.md for the longer "how this codebase thinks" note. MIT © 2026 Jared Moore Jared Moore — Senior AI Product Manager. Bay Area. Contact: [email protected]