job-find

name	job:find
description	Find new remote job vacancies matching your profile. Scans Telegram channels and web sources. Filters by your stack, timezone, and pay requirements. Tags each job with its source. Updates job_search.md with new matches and source stats.
argument-hint	[optional: channel name or 'all']
user-invocable	true
disable-model-invocation	false

Job Finder

Profile to match against

Role: Senior [Your Role] (e.g. Full-Stack Developer, AI engineer) Stack: [Your primary technologies] Remote only. [Your timezone] — prefers [timezone preferences]. English [level] — [any language notes]. Pay: top-of-market only ([target market, e.g. US/EU rates]). Skip [boards/agencies to avoid].

Skip these:

• [List roles/stacks to skip, e.g. Data scientists, Java/PHP-only, DevOps-only, QA, PM, design]
• [List company types to skip, e.g. outsourcing agencies]
• [List geo/timezone exclusions, e.g. Australia/Asia timezone only unless async-first]
• [List visa/legal exclusions, e.g. US-only with visa sponsorship required]

Target:

• [List ideal role types]
• [List ideal stack combinations]
• [List ideal company types, e.g. YC-backed, US/EU product companies]

Sources — priority order

Prioritize sources with higher Applied/Added ratio from ## Sources — Effectiveness Tracker in job_search.md.

Source ID	Name	Language	Type
YOUR_CHANNEL_ID_1	[Channel Name 1]	EN	Telegram channel
YOUR_CHANNEL_ID_2	[Channel Name 2]	RU	Telegram channel
YOUR_CHANNEL_ID_3	[Channel Name 3]	EN	Telegram channel

Job tracking file

~/.claude/job_search.md

Instructions

1. Read job_search.md first — specifically:

   • ## Sources section to see which channels are performing best
   • ## Status table to avoid duplicates (check company names)

2. Check sources in priority order (highest effectiveness first).

3. For non-English channels: look for roles matching your stack at product companies. Native-language teams are fine.

4. Filter strictly. For each candidate role ask:

   • Is the stack matching your profile?
   • Is it remote and timezone-compatible?
   • Is it at a product company (not outsourcing)?
   • Is salary likely top-of-market?
   • Is it NOT already in job_search.md?
   • Is it likely open (recent post, not older than 3 weeks)?

5. For each match, extract:

   • Role title, company, salary (if mentioned), apply link
   • Timezone / remote policy
   • Why it fits (2-3 words)
   • Source channel (use the source name from the table above)

6. Present matches as a table:

   | # | Role | Company | Salary | Timezone | Why | Source | Link |
   

7. Ask user which ones to add. After confirmation, append to ## Status table in job_search.md with:

   • Next sequential number (max existing + 1)
   • Status: pending
   • Source: channel name from table (e.g. tg: Remote AI/ML)
   • Notes: salary range and any key detail

8. Update ## Sources — Effectiveness Tracker: increment Added count for each source where new jobs were added.

9. Do NOT add any role to the queue if it's clearly closed (404/deleted post) or if it's a duplicate.

Source reflection rules

During search — bail early from a dead source

While scanning a source, count invalid results (posts that are stale, closed, wrong stack, outsourcing agency, geo-blocked). If you hit 3 invalid results in a row from the same source with 0 valid matches so far — stop scanning that source. Mark it internally as low-yield this session and move to the next one.

Do NOT silently give up on the whole search. Always try the next source.

After the session — signal quality report

After presenting matches, show a one-line status per source checked:

📊 Session signals:
  Channel Name 1  — 2 valid / 8 scanned  ✅
  Channel Name 2  — 0 valid / 3 checked  ⚠️ bailed (3 invalid in a row)
  Channel Name 3  — not checked this session

If a source has Added >= 10 (lifetime) and Applied = 0 — flag it: "📉 Low-yield source — worth continuing?" If Applied >= 3 and Response >= 1 — flag it: "🔥 Strong source — prioritize next time."

When all sources are low-yield — ask the user

If after scanning all sources you found fewer than 3 valid matches, ask:

"Not many good vacancies today — only found N. Would you like to:

1. Expand the profile? (e.g. include adjacent roles, relax salary threshold)
2. Add new sources? (LinkedIn / HN Who's Hiring / YC Jobs / Wellfound)
3. Search for a specific company or role?"

Never decide on your own to relax the profile filters — always ask first.