Answering Questions as a Hiring Process
First published at Wednesday, 18 November 2026
Answering Questions as a Hiring Process
This is a blog article out of a series where I reflect on what I learned during funding, growing (, and selling) SaaS product companies. While I write those things down for myself, since I believe self-reflection helps me learn, I also want to share my thoughts with anybody who might be interested. An overview of all related topics can be found below. I have a bunch of these blog posts lined up, so you also might want to follow me if you like this one.
One of the most effective steps in every hiring process I have run was also one of the simplest. At the start, before the usual rounds, I would present the product and the business to the candidate and then open the floor for an "ask me anything" (AMA) session. The questions a person chooses to ask after a product pitch tell you more than most of the interviews that come after.
What the questions reveal
The questions split people fast. Some immediately want to know who the customer is, what problem we are actually solving for them, how the business makes money, where it is fragile. Others ask only about the framework, the tooling, the hardware they will get, the remote policy. Neither set is wrong to care about those things, but the first thing someone reaches for after hearing about a product tells you where their attention naturally goes.
I care most about whether someone can understand the business and its requirements, and whether they can organise and direct themselves. I care about those well above depth in any particular technology, because the technology can mostly be taught and those two traits mostly cannot. A product AMA is a remarkably good probe for both, because engaging seriously with a business you just heard about is exactly the skill, performed live.
The one-minute highlight
There is a companion to this that runs in the same opening session and probes the same thing from the other side. I had laid out the outline of the session and a clear time plan up front, so everyone knew what was coming and how long each part had. Within that, I would tell the candidate plainly that I had already read their CV, and then ask them for the one-minute highlight: the single most important thing on it, in their own words.
A surprising number read their CV aloud for five minutes anyway. I had just told them I knew it and asked for one minute and one thing, and they delivered the whole document. That tells you a great deal, and not mostly about the CV: how someone communicates when they have to compress to the important point, whether they actually listened to what I asked, whether they can prioritise under a mild constraint. It also ate into the time left for the AMA, its own small signal about what they chose to spend the session on.
The ones who did it well handed me the one thing that mattered, briefly, having heard the question. That is the same skill the AMA measures, efficient and business-aware communication, pointed inward at their own experience instead of outward at the product.
Not a gate, and it checked out
Two things kept this honest. First, it was never a gate. I did not reject anyone on the strength of the AMA; the only thing that disqualified a candidate there was not showing up. The normal interviews, fit, technical, product, all happened afterwards exactly as they would have.
Second, the signal turned out to be real. There was a high correlation between the people I came out of the AMA thinking we should hire and the people the team independently chose to hire through the rest of the process. When your early read keeps agreeing with a process you were not steering, the early read is measuring something.
I lean on that correlation deliberately, because the research on hiring is not kind to gut feel. The large meta-analyses of selection methods find unstructured interviews among the weaker predictors of job performance, while structured interviews and work-sample tests are among the strongest [1] . An AMA judged on a warm impression alone would be exactly the weak kind. This one was the same probe every time, checked against who actually got hired, which makes it closer to a work sample of business thinking than to a chat I happened to enjoy.
It also does a second job. A hiring process is two-way: the candidate is deciding about you at the same time. Opening with a real conversation about the product means good candidates learn what they would be working on early, and a senior leader taking the time to talk with them and answer their questions properly signals that people matter here. That is worth more than any careers-page copy.
The catch
It scales horribly. This worked because volumes were low enough that I could personally sit in on the start of each process, and it stops working the moment that is no longer true. It is not a repeatable system for high-volume hiring. For the scale we ran at, my time was easily worth the quality of the signal.
Summary
Open your hiring process by presenting the product and answering the candidate's questions, and pay close attention to what they ask. It surfaces business sense and self-direction, the two things I value most and the two hardest to teach, better than most formal interview steps. Keep it as a signal rather than a gate, and know that it doubles as the candidate's first real impression of you. Just do not expect it to survive past the scale at which a senior person can show up for every process.
References
- 1
- Schmidt, F. L., & Hunter, J. E. (1998). The validity and utility of selection methods in personnel psychology: Practical and theoretical implications of 85 years of research findings. Psychological Bulletin, 124(2), 262-274. https://doi.org/10.1037/0033-2909.124.2.262. Reported mean validities: structured interviews .51 and work-sample tests .54, against .38 for unstructured interviews.
Subscribe to updates
There are multiple ways to stay updated with new posts on my blog: