Creates stage-specific interview preparation documents for job seekers at any stage of the hiring process.
Use when someone asks to prep for an interview, HR screen, professional interview, or home assignment, or asks what to say or bring to a specific interview stage.
Generate a prep document tailored to the specific interview stage the user is in.
Instructions
Ask inputs one at a time:
"Which stage are you prepping for?"
Options: "Applying now — I need an application package" / "HR / recruiter screen" / "Professional / hiring manager interview" / "Home assignment"
(Wait for response.)
Check whether ./job-search-tracker/cv.md exists and is non-empty.
If found: say "Found your saved CV — using it." and use its contents. Do not ask the user to paste anything — skip to the next input.
If not found: ask "Please paste your CV below." (Wait for response.) Once given, save it verbatim to ./job-search-tracker/cv.md (creating the job-search-tracker/ folder first if it doesn't exist).
If the user pastes a new CV unprompted later even though a saved one was used, overwrite cv.md with the new content immediately — no confirmation needed.
"Paste the job description." (Wait for response.)
"Do you have any company research or intel to share? Paste it here, or say 'none'." (Wait for response.)
Generate the appropriate document based on the stage chosen:
Stage: Applying now
Application Package: [Role] @ [Company]
Fit verdict
[One honest line: Strong fit / Reasonable stretch / Long shot — with brief specific reasoning from the CV vs JD]
Why you — the pitch in 3 bullets
[The 3 strongest overlaps between the CV and JD. These power the cover letter opening.]
Gaps to acknowledge or bridge
[What's missing. For each gap: address in cover letter / ignore / reframe.]
Cover letter angle
[Specific hook for THIS company and role drawn from JD or any research provided — not generic.]
Application checklist
CV tailored and exported
Cover letter reviewed and personalized
Application submitted
Track: [Company] | [Role] | Applied [date]
What to expect next
[Based on any Glassdoor intel the user provided, or what's typical for this role type]
Stage: HR / recruiter screen
HR Screen Prep: [Role] @ [Company]
Company snapshot (30-second version)
[2–3 sentences from research or JD: what the company does, stage, recent news]
Your headline for this role
[1-sentence framing of who this candidate is relative to this specific role]
Tell me about yourself
[Full first-person spoken answer, 60–90 seconds, ready to read near-verbatim. Follow a Present → Past → Future shape: Present — current role/title and the specific slice of it most relevant to this role; Past — 1–2 career beats from the actual CV that build the throughline to this role; Future — why this specific role/company is the logical next step, tied to the JD. Pull specific facts (titles, companies, concrete achievements) from the CV — never generic filler like "I'm a passionate professional." End on a concrete bridge to the JD's core requirement, not a vague "I'm excited about this opportunity."]
"Why are you leaving your current role?" — [brief, positive-framed]
"What do you know about us?" — [3 specific things from research or JD]
"Salary expectations?" — [anchor high, defer if possible]
Red flags to defuse proactively
[Any CV gaps or career transitions an HR screener might flag. How to address briefly and positively.]
Questions to ask the recruiter
[4 questions that show research depth and help the candidate assess fit]
Stage: Professional / hiring manager interview
Professional Interview Prep: [Role] @ [Company]
Company deep-dive
[Key products, strategy, recent moves, known challenges. Reference any research provided.]
Glassdoor process intel
[What candidates report about this stage at this company, or for this role type if company-specific data is unavailable]
Stories to bring (STAR format)
[6–8 bullets, each tied to a specific JD requirement]
[Short story title] — [1–2 sentences: situation + result]. Maps to JD: [requirement]
Tell me about yourself
[Full first-person spoken answer, 60–90 seconds, ready to read near-verbatim. Follow a Present → Past → Future shape: Present — current role/title and the specific slice of it most relevant to this role; Past — 1–2 career beats from the actual CV that build the throughline to this role; Future — why this specific role/company is the logical next step, tied to the JD. Pull specific facts (titles, companies, concrete achievements) from the CV — never generic filler like "I'm a passionate professional." End on a concrete bridge to the JD's core requirement, not a vague "I'm excited about this opportunity."]
Likely questions and angles
"Walk me through your experience with [key JD skill]" — [which CV thread to lead with]
"Tell me about a failure or challenge" — [which story to use]
"How do you work cross-functionally?" — [specific approach from their experience]
"Why [Company]?" — [specific, research-backed answer]
[Add 2–3 more questions specific to the role from the JD]
Questions to ask them
[4 substantive questions drawn from research or JD gaps]
Key intel to reference in conversation
[3–5 specific, citable things from research the candidate can drop in naturally]
Stage: Home assignment
Home Assignment Prep: [Role] @ [Company]
Company context for the assignment
[From research or JD: current focus, known challenges, product priorities — shapes the angle to take]
What they're likely evaluating
[Based on JD and role type: what thinking, skills, and judgment do they want to see?]
Framing principles for the submission
Lead with the business problem before jumping to solutions
Reference company-specific context (cite from research if available)
Show thinking process, not just output
Be opinionated — companies use home assignments to see judgment, not hedging
[2–3 more role-specific principles based on the JD]
Format and delivery tips
[Length and format norms for this role type]
[How to structure the doc / deck / code submission]
[What to include as appendix vs main body]
Rules
Reference actual details from CV and JD throughout — not generic advice
If no company research was provided, note it and write the best document possible from CV + JD alone
If the user's stage is ambiguous, ask before generating