Run Your Job Search With Claude
The goal is not to apply to hundreds of jobs faster. It's one dedicated Claude Project that helps you find roles that fit, tailor your materials truthfully, research employers, and prepare stronger interview stories.
the setup
What you're actually building
One Claude Project holding your career context. Inside it, Claude plays four roles.
The role analyst
Reviews job descriptions and identifies the requirements that keep repeating.
The résumé strategist
Shows where your experience matches and where your evidence is thin.
The company researcher
Explains the company, product, market, and likely business needs.
The interview partner
Predicts likely questions and ties them to your real experience.
prep
Build a Job Search Master Folder first
- Your current résumé
- A longer career-history document (projects, tools, leadership examples, outcomes, lessons)
- Five to ten job descriptions you genuinely like
- Target job titles and preferred industries
- Your major projects and accomplishments
- Constraints: location, salary, work arrangement, travel
Redact before you upload
No SSNs, passport details, home addresses, employee IDs, confidential company information, customer data, proprietary code, or internal documents you aren't authorized to share.
- 1
Create the Project
Name it "[Your Name] — Job Search Command Center". Upload your résumé, career history, target-role list, and 3–5 representative job descriptions. Not 100 — start small so patterns are meaningful.
- 2
Give it operating instructions
Paste the project instruction below into the Project settings.
- 3
Find your role patterns
Run the role-analysis prompt before any rewriting happens.
- 4
Score each role
Use one consistent scorecard instead of applying because a title looked interesting.
- 5
Run a weekly system
Replace random job-board browsing with a planned week.
You are my job-search strategy assistant. Help me identify strong-fit roles, understand requirements, tailor my materials using only truthful information, research employers, and prepare for interviews. Rules: 1. Never invent experience, skills, employers, tools, certifications, responsibilities, dates, or results. 2. Always distinguish: evidence already in my materials / reasonable transferable skills / missing qualifications / things you need me to confirm. 3. Do not recommend keyword stuffing. 4. Prioritize clarity, relevance, truthful evidence, measurable outcomes. 5. For each role, say whether it's a strong, moderate, or weak fit — and why. 6. Flag any requirement that may be a genuine gap. 7. Ask me for missing information instead of assuming. 8. Never draft-and-send outreach without my review. 9. Keep a concise record of roles, requirements, and decisions. 10. Push me toward quality applications, not volume.
Analyze the job descriptions uploaded to this project. Report: 1. Most common job titles 2. The 10 responsibilities that appear most often 3. The 10 skills that appear most often 4. Frequently requested tools or platforms 5. Common leadership / communication expectations 6. Common education or certification requirements 7. Which requirements look essential vs. merely preferred 8. The problems these employers are hiring someone to solve 9. The parts of my background that align most strongly Then a table: Requirement | Frequency | Evidence from my background | Strength (strong/moderate/weak/missing) | What I should clarify. Do not rewrite my résumé yet.
Evaluate this job description against my project materials. Score each category as strong / moderate / weak / missing information: relevant experience, core skills, domain knowledge, leadership expectations, technical requirements, communication and stakeholder requirements, education, location and work arrangement, seniority, and evidence I can solve their likely problems. Then give me: - My 5 strongest reasons to apply - My 3 biggest gaps or risks - Questions I should answer before applying - Whether this is worth prioritizing - Which résumé version and career stories to use Don't reject the role just because I miss a listed requirement. Separate core requirements from optional preferences. Job description: [PASTE]
Build my job-search week based on my target roles and constraints. Give me a plan with: how many roles to research, how many quality applications to submit, who to reach out to, what to prepare for interviews, and what to improve in my materials. Prioritize quality over application volume. Keep it to what fits in [NUMBER] hours this week.
Research this company for an upcoming application/interview. Cover: what they sell, who their customers are, business model, competitors, recent strategic priorities, relevant challenges or opportunities, and how this role likely supports those priorities. Then give me 5 questions I could ask that show I understand the business.
Turn my career history into interview stories. For each significant project, structure it as: 1. Situation 2. My responsibility 3. Actions I took 4. Result (with numbers if I gave them) 5. What I learned Mark [NEEDS NUMBER] where a metric is missing. Never invent one.
What Claude should not do
Fabricate experience, mass-apply on your behalf, send outreach unreviewed, or talk you out of a role you're 80% qualified for. If it finds a real gap, that's information: strengthen a skill, build a project, target a better-fit role, or explain your existing experience more clearly.
Next guide
Improve Your Résumé Before You Apply