Galactic Reverse Interview
Knowledge: references/reverse-interview-guide.md, the question bank and advice from
galactic-reverse-interview-guide-for-developers.
Workspace layout: .claude/skills/galactic-job-search/references/workspace.md.
Before the interview → workspace/applications/<app>/questions.md
- Read
profile.md(must-haves, deal-breakers),company.md(what's already known) andfit.md. - Ask who the interviewer is (role) and how much time there will be for questions, if unknown.
- Pick 3–5 questions per round, plus 1–2 spares, from the bank (a [pack] rule in the reference; the guide only says don't ask them all). Prioritise the user's must-haves and deal-breakers (they must be answered before any offer), then what the research couldn't answer, then questions this interviewer type is best placed to answer. Prefer questions the company's site doesn't already answer (the guide: much can be found online).
- Adapt the wording to this company, for example by referencing something specific from
company.md. Keep the core of each question from the guide, and cite its category. - Order them: must-ask first, in case time runs out. For each, note what a good answer and a red flag would look like. This part is the skill pack's guidance (see the reference), not Guido's text, so don't attribute it to him.
- Agency or external recruiter (e.g. a Welyk recruiter screening for a client): they answer second-hand. Prefer questions about the process (next steps, who's in the technical round and what it covers, timing, salary range confirmed by the client) and the client's must-haves. Save culture and team questions for the company's own interviewers. The process questions are general practice; label them as such.
After the interview
Ask the user what they heard for each question and record it in questions.md. Flag worrying answers
using the reference's §4.2 ([pack] guidance, plus the negotiation guide's warnings on "senza orari" and fake
P.IVA), and questions left unanswered, to ask in the next round. Log a summary line with
galactic-tracker.
Comparing companies
When the user has several processes open, build a side-by-side table from all the questions.md files:
must-haves met / unmet / unknown per company. This feeds straight into galactic-negotiation when offers arrive.


