Interviewing a Founder: Questions That Draw Out a Story

Every founder has a story, and most of them tell it badly. They tell it in the shorthand of pitches: a problem, a solution, a market, a traction slide. What they leave out is the part readers actually remember, the specific night, the argument, the doubt, the small decision that turned out to matter. Your job, as the person asking the questions, is to help them find it.

This guide is for anyone who interviews founders, whether for a magazine-style feature on a launch site, a company blog, a podcast or a case study. It covers preparation, the shape of a good conversation, the kinds of questions that work and what to do with the recording afterwards.

Do the reading first

A good interview starts days before the conversation. Read everything the founder has published: the company site, earlier interviews, posts, product pages, any public talks. Look for gaps and contradictions as well as facts. If the site says the company was founded in one year and a profile says another, ask. If three earlier interviews tell the same neat origin story, you will want to ask about the bits they leave out.

Make a short list of what you already know, so you do not waste the founder's time asking for it, and a list of what you cannot find out any other way. That second list is the real agenda: motives, doubts, turning points, relationships, mistakes.

Agree the purpose and the terms

Before you meet, tell the founder what the piece is, where it will appear, how long it will be and whether they will see it before publication. Be clear about what is on the record. If you plan to record, ask permission and say how the recording will be stored and for how long. Treat the recording as personal data and handle it with care.

Say what you will not do. For example, you will not publish anything told in confidence, and you will check quotes that depend on figures or names. This sets a tone of trust, which is what makes people open up.

Prepare topics, not a script

A list of twenty written questions invites reading from a page and ignoring the answers. A better approach is a handful of topics, with one or two question stems under each, and a willingness to leave the plan.

A sensible shape for a founder interview:

1. Before the idea. Who were you, what were you doing and what did you care about?
2. The spark. When did the problem become real to you?
3. The first steps. What did you do in the first week, the first month?
4. The hard parts. What nearly ended it? Who helped?
5. The change. How is the company different from what you imagined?
6. The people. Who else matters in this story?
7. What next. What are you afraid of and excited about?

Keep the list in front of you, but treat it as a map, not a track.

Start easy and concrete

The first questions set the mood. Avoid abstract openers such as "Tell me about your vision." Ask something the founder can answer without thinking too hard.

• "Where were you working when this started?"
• "What was the first version, and what did it look like?"
• "Who was the first person you showed it to?"

Concrete questions produce concrete answers, and concrete answers are the raw material of story. They also let the founder warm up, forget the recorder and settle into the telling.

Ask open questions, then follow them

The best questions begin with "what", "how" and "tell me about". Questions that begin with "did you" can be answered with a word.

Compare:

• "Was it hard to raise money?" invites "Yes."
• "What was the hardest conversation you had while raising money?" invites a scene.

The follow-up is the real craft. When the founder says something interesting, stay with it rather than moving on to the next item on your list.

• "What did that look like?"
• "Who was in the room?"
• "What did you say?"
• "How did you feel afterwards?"
• "What did you do the next morning?"
• "What would you tell yourself then?"

Each follow-up pulls the story from summary toward scene. Summary says "we struggled with cash." Scene says "I sat in the car outside the bank for twenty minutes before going in."

Use silence

Many interviewers rush to fill pauses. Resist. After a founder finishes an answer, wait a few seconds. Often they will add the thing they were not sure whether to say, and it is frequently the best part of the conversation. Silence also signals that you are interested and not in a hurry.

Ask about doubt, failure and cost

Founders rarely volunteer weakness, but readers trust stories that include it. Ask gently, and only after you have built some rapport.

• "When did you think about stopping?"
• "What did this cost you that people do not see?"
• "What was the worst decision you made, and what did you learn?"
• "Who did you let down?"

Respect limits. If a founder declines to answer, move on. Never press for something that would hurt other people, such as former colleagues, unless it is both true and necessary.

Ask about other people

A founder's story is never only theirs. Ask about co-founders, early customers, family, mentors and employees. "Who believed in this before anyone else?" often opens a warm, vivid thread. Remember that anyone named may deserve a chance to check what is said about them.

Listen for the specific

Keep an ear out for details that carry feeling: a date, a smell, a phrase, an object. A founder who says "we had a whiteboard that nobody was allowed to erase for six months" has handed you an image. A founder who says "we pivoted several times" has handed you nothing. When you hear a vague phrase, ask for the instance. "Can you give me an example?" is one of the most useful sentences in interviewing.

Handle polished answers

Some founders have given many interviews, and they speak in sound bites. Do not argue with the polish. Honour it, then go underneath.

• "That is a great way of putting it. What was the version you would have said at the time?"
• "If a friend had asked you over a drink, what would you have said?"
• "What did you leave out of that story?"

Be especially careful with big claims. If a founder says the company is the first or the largest at something, ask what evidence supports it. Accuracy is part of trust, and readers, search engines and AI assistants all favour pages with clear, verifiable statements.

Take notes, even when recording

A recorder is a safety net, not a substitute for attention. Make short notes of moments to return to, phrases that struck you and facts to check. Note the time on the recording so that you can find them later. Keep eye contact where you can, and let the founder see that you are listening.

End well

Save a few closing questions that invite reflection and give the founder control.

• "Is there something I have not asked that you hoped I would?"
• "What do you want people to understand about this that they usually miss?"
• "Who else should I speak to?"

Thank them sincerely. Remind them of what happens next: when you will send the draft or quotes for checking, and when the piece will appear.

After the interview

Within a day, while memory is fresh:

• Back up the recording and note where it is stored.
• Write a short summary of the main story beats and your favourite moments.
• List facts to check: dates, names, figures, spellings.
• Mark potential pull quotes. A pull quote is a key phrase or excerpt pulled from the text and used as a graphic element to entice readers or highlight a key topic. Choose lines that carry feeling or insight, not just a claim.
• Transcribe or have the recording transcribed, and review it carefully.

Shaping what you heard

Raw interview material is not yet a story. Look for the arc: a person who wanted something, met an obstacle, made a choice and changed. Choose the scenes that carry that arc and cut the rest, even if they are interesting. Use direct quotes for emotion and personality, and paraphrase for facts. Keep the founder's voice recognisable.

Check every factual claim with the founder or an independent source. Send quotes for approval if you agreed to. Credit people accurately. If the piece has a structured profile, make sure details such as titles and company names match what the founder uses elsewhere.

A worked example

Imagine an interview with the founder of a small company that makes reusable packaging. The interviewer has read three earlier profiles that all begin with "I saw too much plastic waste." Her opening question is not about waste but about the founder's job before the company: "What were you doing the week you decided to start?" The answer, a logistics job at a distribution centre, leads to a scene: forty pallets of single-use wrap being thrown away at the end of a shift. "Whose job was it to throw it away?" "Mine, that night." She asks what he did next. He took a roll home and tried to make a reusable version on his kitchen table. She asks what it looked like and who he showed it to. His sister, who laughed.

Later, she asks about the worst moment. After a pause, he talks about a customer who returned the entire first batch because it leaked. She asks what he said to the customer. He tells her that he drove to the customer's warehouse that evening and spent the night repacking the order by hand. The piece builds on that scene, with the plastic-waste line as a footnote. Readers remember the kitchen table and the night repacking, which no earlier profile had mentioned.

Common mistakes

1. Arriving unprepared.
2. Reading from a list.
3. Asking closed questions.
4. Interrupting.
5. Moving on from the interesting thing.
6. Letting polish stand.
7. Forgetting to check facts.

Where it leads

Founder stories are at the heart of many launch pages. The about-the-founders page here shows how founders introduce themselves and their work, and the contact page shows how to reach a team for a conversation. If you are a founder preparing to be interviewed, a separate guide covers how to prepare.

Frequently asked questions

Do I need professional recording gear? No. A phone in a quiet room is enough if you test it first.

Can I interview by video or text? Yes. Text interviews give less spontaneity, but they let people reflect. Video suits conversations where tone matters.

What if the founder gives short answers? Slow down, ask for an example and use silence.