Maintain ~/.openclaw/job-tracker.json:

{
  "applications": [
    {
      "company": "NVIDIA",
      "role": "GPU Systems Engineer",
      "url": "https://...",
      "applied_date": "2026-03-27",
      "status": "applied",
      "next_step": "wait for response",
      "notes": "Referred by Dr. Wu",
      "salary_range": "$120K-$160K"
    }
  ]
}

Status values: researching → applied → phone_screen → interview → offer → accepted / rejected / ghosted

Commands

"Track application at [company] for [role]" → add to tracker
"Update [company] to [status]" → change status
"Show my applications" → display table
"What's next?" → show applications needing follow-up (>7 days no response)

Application Table

# Job Applications — March 2026

| Company | Role | Applied | Status | Next Step |
|---------|------|---------|--------|-----------|
| NVIDIA | GPU Eng | Mar 15 | Interview | Prep system design |
| AMD | Verif Eng | Mar 20 | Applied | Follow up Mar 27 |
| Google | SRE | Mar 22 | Rejected | — |

Resume

"Update my resume" / "Build a resume"

Ask for: current role, target role, key achievements
Generate a clean, ATS-friendly resume in markdown
Save as resume.md
Offer to convert to PDF if pandoc/wkhtmltopdf is available

Resume Rules

Use action verbs: Built, Designed, Implemented, Led, Reduced, Improved
Quantify everything: "Improved test coverage from 65% to 92%"
No superlatives ("world-class", "revolutionary")
No buzzword stuffing
1 page for <5 years experience, 2 pages max for senior
Tailor to the specific job description when provided

Cover Letter

"Write a cover letter for [job posting]"

Read the job posting URL or description
Match the user's experience to the job requirements
Write 3 paragraphs: hook, match, close
Save as cover-letter-[company].md

Cover Letter Rules

Never start with "I am writing to apply for..."
Open with something specific about the company
Match 3-4 key requirements from the posting to user's experience
Close with enthusiasm + specific availability
Under 300 words

Interview Prep

"Prep me for [company] interview"

Research the company and generate:

Company overview — what they do, recent news, culture
Likely questions — based on the role (behavioral + technical)
Your stories — STAR format answers using the user's experience
Questions to ask — 3-5 smart questions for the interviewer
Red flags — things to watch for (Glassdoor reviews if available via web search)

"Mock interview for [role]"

Ask questions one at a time
Wait for user's answer
Give feedback: what was strong, what to improve
Score on: clarity, specificity, relevance, confidence

Job Search

"Find [role] jobs in [location]"

Use web_search to find current openings:

Search: "[role] [location] jobs site:linkedin.com OR site:greenhouse.io OR site:lever.co"
Present top 10 results with: company, title, location, link
Filter out recruiter spam and expired postings

Rules

Never fabricate experience — only use what the user tells you
Never exaggerate achievements
Always save files locally — never send resume data to external services
When suggesting resume edits, explain why each change helps
Track everything in job-tracker.json for persistence across sessions

job-hunter

Job Hunter

Application Tracker