What Good Problem Interviews Feel Like (Customer Side, Technical Founders)

Most posts about problem interviews are written from the founder's side. Here is the other side, specifically for engineering audiences. What does a good interview feel like for the engineer being interviewed? It matters. The quality of your data depends on whether the person across from you wants to keep talking.

It Feels Like Being Listened To

The single thing engineers report most consistently after a good problem interview is that they felt heard. Not interrogated, not pitched, not surveyed. Heard. The founder asked something, leaned in, did not interrupt, and asked one more follow-up that showed they had actually been paying attention.

This sounds soft and turns out to be the entire game. Most engineers rarely get listened to about their own work outside of one-on-ones. When someone does it well, they will keep talking far past the scheduled thirty minutes.

It Does Not Feel Like a Sales Call

Engineers have a specific allergy to sales energy. They will detect it within the first minute. The moment they sense pitch incoming, every answer becomes guarded. They start saying the things people say to salespeople, which are mostly polite filler.

A good interview is recognizable to the engineer because nothing about it feels like a sales pitch. The founder does not bring up their product. The founder does not ask leading questions about features. The founder does not tee up an offer at the end. The interviewee leaves the call thinking, "huh, that was interesting," not, "huh, what were they trying to sell me."

It Feels Technically Specific

Generic interviews bore engineers. "Tell me about your team" gets a stock answer they have given a hundred times. They have a recruiting-pitch-shaped reply ready.

Good interviews ask about specific incidents. The 3am page from last week. The migration that locked the table. The internal tool someone built last quarter. Specifics jolt engineers out of stock-answer mode and into actual memory. They will remember the incident in detail because it cost them sleep.

From the engineer's side, this feels like the founder is interested in their actual life rather than their resume bullets. That feels good and makes them more generous with detail.

It Tolerates Technical Tangents

Engineers go on tangents. They will spend ten minutes on a Postgres edge case that seems unrelated. The good founder follows the tangent for a while. Tangents are usually adjacent to the problem in a way the engineer has not consciously connected. They produce unexpected information.

From the engineer's side, being allowed to follow the technical thread is generous. It signals the founder respects the messiness of real engineering. They will be more honest about other things because of it.

It Does Not Solutioning Out Loud

The fastest way to ruin the conversation is for the founder to start designing the solution out loud. The moment that happens, the conversation tilts away from the engineer's actual world and toward the founder's hypothesis. The engineer politely engages with the hypothesis instead of describing their reality.

From the engineer's side, a founder who does not solution feels different. It feels like they are genuinely curious instead of looking for confirmation. Engineers respond to that with more honesty.

It Feels Mutual

Even though the founder is asking most of the questions, the best interviews feel like a conversation. The founder reacts. They say "huh, I had not thought about it that way." They share a small observation now and then. They thank the engineer for an insight that was actually insightful.

The engineer comes away feeling like they helped someone. People who feel like they helped you tend to take your follow-up calls. That matters - the same fifteen interviewees become your launch list.

It Feels Honest

If you do not know what you are building yet, say so. The engineer can tell when you are hiding behind generic research framing, and they trust it less.

The honest version sounds like, "I am thinking about building something in this space and I am genuinely not sure if the problem is real, so I am asking before I commit. Your honest answer is way more useful to me than a polite one." Engineers read that as integrity and match it.

Why This Affects Your Data

Engineers who enjoy the interview tell you more, including things they would not normally share - which internal tool was held together with bash, which dashboard nobody trusts, which workflow nobody owns. Engineers who do not enjoy the interview tell you less and tell you safer things.

So the experience design of the interview is also the data quality of the interview. Founders who become great at this are not running it as a transaction. They are running it as a thirty minutes the engineer will remember as one of the better calls they had this month. That is the bar.