User Interview Question Generator
Generate a custom user interview script in 30 seconds. Pick your stage, audience, and focus to get a structured set of behavior-grounded questions you can use today.
Your interview script
18 questions across 5 sections. Plan for 30 to 45 minutes per interview.
- Q1Tell me about the last time you ran into this problem. Walk me through what happened.
- Q2When did you first notice this was a problem worth solving?
- Q3How often does this come up in your week, roughly?
- Q1When was the last time you tried to solve this problem and how did it go?
- Q2What have you already tried that did not work? Why did it fail?
- Q3Walk me through the most recent specific instance of this happening.
- Q4If you woke up tomorrow and this problem was magically solved, what would change about your day?
- Q1What are you doing today to work around this problem?
- Q2How much time per week do you spend on this workaround?
- Q3What other tools, spreadsheets, or workflows have you stitched together to handle this?
- Q1Who in the business owns this problem today?
- Q2What is your current process when this problem comes up?
- Q3How does this problem affect revenue, cost, or customer satisfaction?
- Q4What is the budget approval process for a new tool in this category?
- Q1Is there anything I should have asked but did not?
- Q2Who else should I talk to about this problem?
- Q3Can I follow up if I have more questions in a few weeks?
- Q4If we build something for this, would you be open to being a design partner or early user?
Interview rules of thumb
- 1. Ground every question in past behavior, not future intent.
- 2. Talk 20 percent, listen 80 percent. Resist the urge to pitch.
- 3. Ask "tell me more" three times before moving to the next question.
- 4. Watch for emotional words, not just logical answers. Frustration is the signal.
- 5. End by asking who else you should talk to. Snowball your sample.
- 6. Write up notes within 2 hours while the conversation is fresh.
Related tools
I know which AI tools are worth your time.
I build with AI every single day. I will send you what actually works, what is overhyped, and what you should be paying attention to next. No fluff, just signal.
Get the AI signal. Drop your email below.
No spam. Just useful AI intel for builders.
Frequently asked questions
How many user interviews should I do for MVP validation?+
For early discovery, aim for at least 10 to 15 conversations with target users in a tight segment before pattern-matching on insights. For solution validation, another 10 to 15 with the same or similar segment. The Rob Fitzpatrick rule from The Mom Test: stop when you can predict what the next person will say. If the 12th person tells you something the first 11 did not, keep going. If everyone is repeating the same pain, you have signal and should move to building.
What questions should I never ask in a user interview?+
Avoid hypothetical and leading questions. Never ask "Would you use a product that does X?" or "How much would you pay for Y?" because the answers are politeness, not data. Avoid pitch language and feature lists. Avoid asking about future behavior. Instead, ground every question in past behavior. Ask "Tell me about the last time you tried to solve this" not "Would you try our solution?" Past behavior is the only reliable predictor of future behavior in interviews.
Should I record user interviews?+
Yes, with explicit permission. Recordings let you focus on the conversation instead of note-taking, capture exact quotes for your pitch deck and marketing copy, and let team members review without re-running the interview. Use Zoom, Riverside, or Otter for recording plus auto-transcription. Always ask permission upfront and offer to send a summary or share the transcript if requested. Most professional users say yes when the purpose is clear.
How long should a user interview be?+
Thirty to forty-five minutes is the sweet spot. Shorter than 30 minutes and you cannot get past surface answers into the actual context, workarounds, and emotion behind the problem. Longer than 45 minutes and you risk fatigue, lower-quality answers in the final third, and lower scheduling acceptance rates. For senior enterprise stakeholders, default to 30 minutes and earn the right to ask for more if the conversation is going well.
Should I share my product idea during the interview?+
Not in the first 25 minutes. Spend the bulk of the interview on the problem space, current workarounds, and past behavior. Once you have a clear picture of how they experience the problem today, you can briefly describe the proposed solution in the last 10 minutes and observe their reaction. Watch for genuine curiosity (leaning in, asking follow-ups, wanting a demo) versus politeness. Sharing too early biases everything that comes after.
How do I recruit users for interviews?+
Five channels work best. First, LinkedIn outreach with a personal note targeting people who fit your ICP. Second, communities and Slack groups where your target customers hang out. Third, posting on Twitter or LinkedIn asking for 30-minute conversations. Fourth, your existing network with warm intros, which has the highest conversion. Fifth, paid recruiting services like UserInterviews.com or Respondent.io, typically $40 to $150 per session. Always offer a small thank-you (Amazon gift card, charity donation) for non-customer interviews.
What is the Mom Test in user interviews?+
The Mom Test, from Rob Fitzpatrick, is a framework for asking questions so neutral that even your mom cannot lie to you about whether your idea is good. Three rules: talk about their life instead of your idea, ask about specifics in the past instead of generics or opinions about the future, and talk less and listen more. The framework forces you to stop pitching and start learning. It is the single best book on user interviews for founders and a must-read before any customer discovery work.