Job Search

Multi-Source Job Search

A Codex and Claude Code skill for searching jobs across LinkedIn, Hacker News Who's Hiring, and Twitter/X. Scores and ranks results against your saved preferences, highlights network advantages, and saves structured output.

Phase 1: Load Preferences & Parse Overrides

Step 1: Load Profile

Follow the bundled answer-memory skill ($job-apply:answer-memory in Codex; /job-apply:answer-memory in Claude Code). Resolve <plugin-root> as that skill directs, run python3 "<plugin-root>/scripts/job-apply-store.py" init, load preferences with preferences-get, and load location or other profile facts with profile-get. Never read or write persistent Job Apply files directly.

If no preferences found, say:

No search preferences found. Invoke the bundled job-preferences skill first to set your target titles, salary range, and filters.

Then STOP. Do not prompt the user to set preferences inline.

If preferences exist, load them:

{
  "targetTitles": ["Staff AI Engineer", "Principal ML Engineer"],
  "minBaseSalary": "$250K",
  "remotePreference": "remote only",
  "excludePatterns": ["junior", "associate", "intern", "entry level"],
  "defaultTimeRange": "last week"
}

Step 2: Parse User Overrides

The user may pass overrides when invoking the skill:

• Time range: last week, 2 weeks, month — overrides defaultTimeRange
• Source filter: linkedin, hn, twitter, or any combination — limits which sources to query (default: all three)
• Keywords: any additional keywords to use alongside targetTitles

Display the active search config before proceeding:

Search config:

• Titles: Staff AI Engineer, Principal ML Engineer
• Salary floor: $250K
• Remote: Remote only
• Exclude: junior, associate, intern, entry level
• Time range: last week
• Sources: LinkedIn, HN, Twitter

Phase 2a: LinkedIn Search (visible host browser)

Navigation

1. Use the host-managed visible browser (Codex Browser plugin or Claude in Chrome) and reuse an appropriate existing tab or create a new one
2. Keep that browser/tab binding for the search instead of switching automation surfaces
3. Navigate to https://www.linkedin.com/jobs/
4. Verify the user is logged in from visible page state. If not logged in, say: "Please log into LinkedIn in this browser tab, then let me know when you're ready." and wait.

Build Search URL

Base URL: https://www.linkedin.com/jobs/search/

Map remotePreference:

• "remote only" → f_WT=3
• "remote preferred" → f_WT=2,3
• "open to hybrid" → f_WT=2,3
• "open to all" → omit f_WT

Map time range:

• "last week" → f_TPR=r604800
• "2 weeks" → f_TPR=r1209600
• "month" → f_TPR=r2592000

Extract Job Listings (max 25)

For each job card:

1. Read visible job cards from the results list with the host browser
2. Click into a job detail page through the same visible browser surface
3. Wait 2-3 seconds for detail page to load
4. Extract: title, company, location, posted date, applicant count, work type, apply method
5. Look for visible connection indicators such as "connections work here" or "connections at"
6. Look for "Meet the hiring team" or "hiring manager"
7. If hiring manager found, extract name, title, profile URL
8. Store result, navigate back to results list
9. 2-3 second delay between each job

Scrolling for More Results

LinkedIn uses infinite scroll:

1. Scroll the results list through the host-managed browser
2. Wait 2-3 seconds for new results
3. Read the newly loaded visible cards
4. Repeat until desired count or no more results

Phase 2b: Hacker News Who's Hiring (shell + host web search)

Find Current Thread

1. Use the host's supported web-search tool to search for: "Ask HN: Who is hiring?" site:news.ycombinator.com {current_month} {current_year}
2. Extract the thread ID from the HN URL in the search results (e.g., https://news.ycombinator.com/item?id=XXXXXXXX → XXXXXXXX)

If no thread found for the current month, try the previous month. If still nothing, skip HN and report it.

Fetch Comments via Firebase API

3. Fetch the thread: curl -s "https://hacker-news.firebaseio.com/v0/item/{THREAD_ID}.json"
4. Parse the kids array — these are top-level comment IDs (job postings)
5. Fetch each comment (up to 50): curl -s "https://hacker-news.firebaseio.com/v0/item/{COMMENT_ID}.json"
6. 0.5 second delay between API calls

Parse Comments

HN Who's Hiring comments typically follow this format in the text field:

Company Name | Role Title | Location | Remote | Salary Range
Description text...
Apply: URL

For each comment:

• Extract company, title, location, remote status, salary from the first line (pipe-delimited)
• Extract application URL if present (look for "apply" or "http" links)
• Parse salary range if present (look for patterns like $XXXk-$XXXk, $XXX,XXX)
• Extract the full text as description

Filter Against Preferences

Skip comments that:

• Don't match any targetTitles (fuzzy match — "AI Engineer" matches "Staff AI Engineer")
• Match any excludePatterns
• Don't meet remotePreference (if "remote only", skip non-remote postings)
• Fall below minBaseSalary (if salary is listed)

Phase 2c: Twitter/X Search (visible host browser)

Navigation

1. Use the existing host-managed browser context (or create a new tab in that browser)
2. Navigate to https://x.com/search
3. Verify login from visible page state by checking for a profile avatar or compose button. If not logged in, skip Twitter entirely and continue with other sources. Report: "Skipped Twitter — not logged in."