Preparing for Interviews

When a company invites you to a call, /seekter-interview does your interview prep: it writes a prep file you read out loud before it, from the job posting, what your application said, the company's own site and your own stories. It covers every stage, from a recruiter screening call to the final round.

Starting a Prep

/seekter-interview

Tell it the company. It asks only for what it can't find: the stage, the date and who you're meeting, if the invitation isn't in your inbox. A time given in another zone is converted to yours, and both are written down.

It handles every stage: a recruiter screening, a hiring-manager round, a portfolio or case-study presentation, a design or take-home test, a technical round, an async video, a final round.

What It Reads

• Your profile: the fact bank, your voice, your standard answers and salary bands.
• Your story bank: profile/interviews/README.md by default. Your stories, ready answers, questions to ask back, and your rulings on how a story may be told.
• Earlier preps for the same company, including how those calls went. A second round builds on the first.
• What your application said: the salary you gave, your location and visa answers, the resume type you sent. The prep never contradicts it.
• The posting, if it's still open, and the company's own site: product, values, team, recent posts. Reviews, salary sites and social media aren't sources.

The Shape of an Answer

Each answer opens with how you work, in two or three sentences, then one story as proof, then one closing line. An answer that opens with a story tells the interviewer what happened once, not how you think.

• Stories come only from your story bank and fact bank. No new anecdote, no detail a story doesn't have, no number it doesn't give.
• Gaps are named, not hidden. For each requirement you don't meet, one honest line: what you have instead.
• Spoken, not written. Short sentences in your speaking voice, with two or three key phrases to practise. Never a script.

The Prep File

It's saved as profile/interviews/<date>-<company>-<stage>.md, in this order:

1. When, how long, where, who and what comes next.
2. What to know about the company, from its own pages.
3. What the role asks for, one answer per ask, gaps included.
4. "Tell me about yourself", timed to the stage.
5. Likely questions and answers for this stage.
6. What to decide before the call: the salary to name, relocation timing, a portfolio piece to have open. Listed for you, never answered by guessing.
7. Questions to ask back.
8. Practical checks for the format.
9. How it went, left empty for you.

The file is checked for invented numbers and banned phrases before you see it.

After the Call

Tell Seekter how it went. Your notes go under "How it went" in your own words. A new story or a correction goes into your story bank, so the next prep tells it your way. The outcome goes into the tracker through /seekter-log when it arrives.

What It Won't Do

It never answers, confirms or reschedules an invitation, never picks a slot in a scheduling link, never messages an interviewer, and never joins a call. The prep stays in profile/, which is git-ignored.

The more stories you keep in your story bank, the better the prep gets.