Problem Interview Examples for Non-Technical Founders

Reading about problem interviews is one thing. Watching non-technical founders run them well is another. Below are sketched examples that look like real calls. Names and details are illustrative. Steal the patterns.

Example 1: A Founder Researching Tools for Course Creators

Founder asks: "Walk me through the last time you launched a course. What were you trying to do, and where did things get messy?"

Interviewee: "Oh man. Videos were done. Landing page was on Carrd. Email list on ConvertKit. The thing that almost broke me was getting Stripe to talk to the LMS at the right moment. I spent a Saturday wiring up Zapier flows that kept breaking."

Founder follows up: "Tell me more about that Saturday. What kept breaking?"

Interviewee: "Two students DM'd me asking where their access was. Zapier had silently rate-limited and the welcome emails did not fire. I only found out because of the DMs."

Notes: Trigger - launch day. Workaround - duct-taped Zapier flow. Pain - silent failures discovered via student complaints. Vocabulary: "silently rate-limited," "wiring up."

Example 2: A Founder Researching Tools for Small-Agency Operators

Founder asks: "What is annoying about how your team handles client status updates right now?"

Interviewee: "It is fine, mostly. We use a Notion template."

This is a vague answer. A novice founder writes "fine, uses Notion" and moves on. The follow-up cracks it.

Founder follows up: "Tell me about the last time it was not fine."

Interviewee: "Last week. Three project managers updating the same Notion page, one of them overwrote the others. The client saw a half-finished update and got upset. We had to call them."

Founder follows up: "Has that happened before?"

Interviewee: "Maybe twice a quarter. We just live with it."

Notes: First answer was "fine." Real answer was a recurring failure they have normalized. Pattern: people minimize their own pain until you ask for a specific event.

Example 3: A Founder Researching Tools for Indie Newsletter Creators

Founder asks: "Have you ever paid for or built anything yourself to help with this?"

Interviewee: "Yeah, I bought a $19/month tool a while back. Used it twice. Cancelled. Then I made a Google Sheet that does basically the same thing in a clunkier way and I have used the sheet for six months."

Founder follows up: "Why did you cancel the tool?"

Interviewee: "It had way too many features. I just wanted one button. The sheet is the button."

Founder follows up: "What does your sheet do that the tool did not?"

Interviewee: "Less. It just does the one thing."

Notes: Real spend, real abandonment, real DIY replacement. Customer self-described positioning: "the sheet is the button." Vocabulary gold. The complaint about "too many features" is product positioning info you cannot get from a survey.

What These Examples Share

Three patterns. The founder asks an open-ended story prompt, not a yes-or-no question. The founder follows up at least twice on the most interesting thread, instead of moving on to the next question. The founder takes notes that include exact phrases and specific events, not paraphrases.

Notice also what is not in any of them. The founder never described their own product. The founder never apologized for being non-technical. The founder never pulled out a no-code prototype. The conversation stayed entirely in the interviewee's world.

Stealing the Pattern

You do not need to script every line. You need the same shape every time. A clean opening that announces no-pitch. An open-ended story prompt as the first question. Two or three follow-ups for every answer. Notes that include the words they used and the events they described.

Run five of these and you will see the texture starting to repeat. The same kind of triggers, the same kind of workarounds, the same kind of disappointments with existing tools. That texture is your map.

What Bad Examples Look Like

Bad example: founder opens by apologizing for not being technical. Then describes a no-code build they have been working on. Asks "would you use this?" Person says yes. Founder writes down "positive signal." Walks away validated. Hires a developer based on it. Six months later, no traction.

The difference is not intelligence or effort. It is conversational discipline. The good examples sound almost ordinary. That is part of what makes them work.