How shizzka/job-hunter works
Job Hunter automates a safety-first job-search workflow: it searches and deduplicates vacancies, filters and evaluates fit, grounds candidate-facing text in profile evidence, then skips, queues for review, or applies through platform adapters. Telegram provides human control and approval; separate workflows cover HH chat replies and recruiter Google Forms. Local profile-scoped state and analytics support isolation and outcome tracking. Edges reflect README descriptions and SOURCE INDEX references; several central implementations were not excerpted, so their internal links are documented rather than inferred from names.
Main entry points: search_pipeline.py Vacancy search · apply.py HH applications · answer_grounding.py Answer grounding · callbacks.py Telegram control
Components 24
Search and matching
- Vacancy search
search_pipeline.py - Board adapters
- Pre-filters
filters.py - LLM matcher
matcher.py - Apply decision
apply_orchestrator.py
Candidate evidence
- Candidate profiles
profile.py - Candidate facts
facts.py - Answer grounding
answer_grounding.py - Prompt context
prompt_blocks.py - LLM providers
llm_client.py
Applications and forms
- HH applications
hh/apply.py - HH adapter
hh_client.py - Browser safety
browser_action_boundary.py - Google Forms
google_form_filler.py - Form approvals
google_forms/workflow.py - Form drafts
google_forms/drafts.py
Human control
- Telegram control
telegram_app/callbacks.py - Notifications
notifier.py - HH chat replies
hh_chat_responder.py
State and insights
- Application analytics
analytics.py - Profile state
state_store/json_store.py - Runtime configuration
config.py
Other components
- Candidate
- Job boards
Connections 25
- Job boards → Vacancy search: provide vacancies
README.md - Vacancy search → Board adapters: queries sources
search_pipeline.py - Vacancy search → Pre-filters: filters results
search_pipeline.py - Vacancy search → LLM matcher: evaluates fit
README.md - LLM matcher → LLM providers: requests scoring
- Vacancy search → Apply decision: routes matches
- Candidate → Candidate profiles: sets up profile
README.md - Candidate profiles → Candidate facts: isolates facts
README.md - Candidate profiles → Profile state: isolates runtime state
README.md - Answer grounding → Candidate facts: loads evidence
answer_grounding.py - Answer grounding → Prompt context: builds context
answer_grounding.py - Answer grounding → LLM providers: grounds answers
answer_grounding.py - Apply decision → HH applications: selects apply path
README.md - HH applications → HH adapter: uses platform adapter
hh_client.py - HH applications → Browser safety: checks browser actions
hh/apply.py - HH applications → Application analytics: records outcomes
- Telegram control → Google Forms: routes form actions
telegram_app/callbacks.py - Google Forms → Form approvals: uses revisions
google_form_filler.py - Form approvals → Form drafts: claims drafts
google_forms/workflow.py - Form drafts → Profile state: persists drafts
google_forms/drafts.py - Telegram control → HH chat replies: routes chat actions
telegram_app/callbacks.py - Telegram control → Notifications: sends controls
- Vacancy search → Application analytics: records funnel
search_pipeline.py - Application analytics → Profile state: persists events
analytics.py - Vacancy search → Runtime configuration: reads search settings
search_pipeline.py