The Strategic Candidate Dossier

Why This Book Matters

I recommend this workbook because I kept having the same coaching conversation over and over. A friend, a peer, someone on my team would say "I have an interview next week" and then freeze up trying to recall specific projects, quantify their impact, or articulate what they actually did versus what the team did. The problem was never a lack of experience. It was a lack of structured recall, and that's an engineering problem, not a confidence problem.

The format inside the Dossier treats interview preparation the way I'd treat any infrastructure project: break it into phases, create repeatable templates, and build a system that works whether you're calm or stressed. The Story Bank section (which is where I recommend you spend the most time when coaching people) gives you structured templates for translating complex technical work into narratives that land with hiring managers and directors. Things like datacenter migrations, automation initiatives, or vendor consolidation projects that are genuinely hard to summarize without either underselling the complexity or losing the audience in implementation details.

I've used this personally for my own interview cycles, and the Company Dossier section is what I found most valuable on that side. It provides a framework for auditing prospective employers before you accept an offer (i.e., identifying whether you're walking into a mature environment or a chaos shop). The structured questions are tiered by audience, so you're asking different things of peers versus managers versus directors, and each tier reveals different information about the organization's actual maturity versus what they presented during the sell.

What I didn't expect was how much sitting on the other side of the table (as a hiring manager conducting interviews at my company) reinforced the framework's value. The candidates who stand out in our loops are the ones who've clearly done this kind of preparation, whether they used this specific workbook or not. They have structured stories with quantified outcomes, they ask targeted questions that show they've researched us, and they follow up with precision. That's the engineering mindset applied to interviewing: preparation is a system, not a vibe.

I've now coached probably a dozen friends and family members through interview cycles using this format, and the consistent feedback is that the structure removes the paralysis. Once someone has their Story Bank populated and their Company Dossier filled out, the actual interview feels less like a performance and more like a data exchange. That reframe alone is worth the time investment.