What to ask in an interview when you've never interviewed anyone

You posted the job. Applications came in. Now someone is on your calendar for 30 minutes tomorrow, and you're staring at their resume wondering what you're supposed to say.

Most founders have been on the other side of the interview table dozens of times. But running one? That's a different skill. And the gap between "I've been interviewed" and "I know how to interview" is wider than it looks.

Here's the good news: you don't need training, a certification, or a 47-page interview guide. You need five questions, a structure, and a way to compare candidates after the conversation ends.

Why your interviews aren't working

The most common mistake first-time interviewers make isn't asking bad questions. It's having no structure at all.

Without a plan, interviews follow a predictable pattern. You spend the first ten minutes selling the company because you're nervous too. You ask "tell me about yourself" and get a rehearsed two-minute monologue. You evaluate charisma instead of capability. You leave the call with a gut feeling you can't explain to your cofounder.

The result: you hire the person you liked most in conversation, not the person who can do the job best. Those are often different people. Charismatic candidates are good at interviews. That doesn't mean they're good at the role you're filling.

The fix isn't complicated. It's preparation. Walk into every interview with the same questions, the same structure, and a simple scoring method. That's enough to separate signal from vibes.

The 30-minute structure

Thirty minutes is plenty for a first-round interview. Longer conversations feel thorough but produce diminishing returns. Here's how to spend the time:

0-5 minutes: Set the context. Tell the candidate what the role involves and what this conversation will cover. "I'm going to ask you five questions about your experience and working style, then leave time for your questions at the end." This puts them at ease and sets expectations. Nervous candidates give worse answers, and that's noise you don't want.

5-20 minutes: Five core questions. Ask every candidate the same five questions in the same order. This is what makes candidates comparable after the fact. Consistency matters more than cleverness.

20-25 minutes: Their questions for you. This section tells you more than you'd expect. What candidates ask reveals what they care about. Someone who asks about team structure and decision-making is thinking about the work. Someone who only asks about perks and remote policy is optimizing for comfort. Both are valid, but you should know the difference.

25-30 minutes: Next steps and timeline. Always tell candidates what happens next and when they'll hear from you. "We're interviewing through Friday and will get back to everyone by next Wednesday." Silence after an interview is the fastest way to lose a good candidate to another offer. It also signals that your company is disorganized. Even if you're a two-person team, you can be responsive.

5 questions that tell you something useful

These aren't trick questions. They're open-ended prompts that force candidates to give you specific, experience-based answers. Use them in order.

1. "Walk me through the last project you owned from start to finish."

Why it works: This question tests three things at once. Can they communicate clearly? Did they own the work or were they a contributor? Do they understand scope, constraints, and tradeoffs?

What to listen for: Follow the story structure. Did they define the problem or was it handed to them? Did they make decisions or execute someone else's plan? How do they describe the outcome? Strong candidates talk about what they learned, not only what they shipped. Watch for "we" vs. "I." Both are fine, but you want to know which parts were theirs.

2. "What's something you built or did that you're proud of, and what would you do differently?"

Why it works: The first half is easy. The second half is where the signal lives. Self-awareness is one of the hardest traits to screen for, and this question surfaces it directly.

What to listen for: Candidates who can't name anything they'd change are either not reflective or not honest. Both are concerns for a small team where feedback loops are short and egos need to be small. The best answers show someone who is proud of their work and clear-eyed about its gaps.

3. "Tell me about a time you had to figure something out with no guidance."

Why it works: At a company with fewer than ten people, nobody is writing detailed specs or training plans. You need people who can operate with ambiguity and find their own path forward.

What to listen for: How did they handle the uncertainty? Did they freeze, guess, or find a way to get the information they needed? Did they ask for help when they were stuck, or did they spin their wheels for weeks? The best answer usually involves a mix: they tried on their own, hit a wall, asked targeted questions, and moved forward.

4. "What's your understanding of what this role involves?"

Why it works: This tells you two things. Did they read the job post? And can they articulate what they think the work looks like day-to-day?

What to listen for: Candidates who can't describe the role in their own words didn't prepare. That's data. Candidates who describe it differently than you intended reveal a misalignment you want to discover now, not three weeks into the job. The best answers show they've thought about what the first 30, 60, 90 days might look like, even if they're wrong about the details.

5. "What would make you leave this job after 6 months?"

Why it works: This is an honesty test. Every person has conditions under which they'd walk. Candidates who say "nothing, I'm fully committed" are telling you what they think you want to hear. That's not useful.

What to listen for: Real answers sound like "If I felt like I wasn't learning anything new" or "If the role turned out to be entirely different from what was described" or "If there was no path to grow." These are legitimate concerns, and knowing them upfront lets you address them before they become reasons to leave. The best hires are honest about what they need.

The napkin scorecard

Here's where most first-time interviewers fall apart. The interview ends, you close your laptop, and you think "that went well." Two days later, you can't remember what distinguished Candidate A from Candidate B.

The fix takes 90 seconds. Within ten minutes of each interview ending, score the candidate on four dimensions. Use a 1-5 scale. Write it on a napkin, a sticky note, or a Google Doc. The medium doesn't matter. Doing it immediately does.

Can they do the job? Skills, experience, and evidence from their answers. Did their project walkthrough demonstrate relevant capability? Score based on what they showed you, not what their resume claims.

Will they thrive here? This is about fit with your environment, not culture fit (which usually means "are they like me"). Can they handle ambiguity? Are they comfortable with the pace of a small team? Do they need structure you can't provide yet?

Do they want THIS job? Not "a job." This one. Did they research your company? Did their questions show genuine interest in the work? Motivation predicts retention. Someone who wants any port in a storm will leave when a better port appears.

Would I want to work with them daily? Communication quality, honesty, energy. At a small company, you'll spend more time with this person than with most of your friends. This isn't about liking them. It's about whether the working relationship will be productive and honest.

Add the four scores. Compare candidates by total. If two candidates are within a point of each other, go back to your notes and look at the "will they thrive here" score as the tiebreaker. Skills can be developed. Environmental fit is harder to change.

What candidates are evaluating about you

The interview is two-way, and candidates at small companies know they're taking a risk. They're evaluating you as much as you're evaluating them.

They notice if you're late. They notice if the video link doesn't work. They notice if you haven't read their resume. They notice if you can't explain what the role involves or what the company does in a clear sentence.

Every detail of the interview signals something about your company. A structured, respectful 30-minute conversation tells candidates you take hiring seriously, even if you're a team of three. A chaotic, unprepared ramble tells them the rest of the job will feel the same way.

Show up on time. Have the video link ready. Know their name and background. Send a follow-up email within 24 hours. These basics cost nothing and separate you from the majority of small companies that treat hiring as an afterthought.

This is your employer brand. Not a logo or a tagline. The experience of interacting with your company. A branded careers page and a process that respects candidates' time go a long way.

Put it into practice

You have the questions. You have the structure. You have the scorecard. The only thing left is to use them consistently.

Track interview notes and candidate scores in one place. Bringboard keeps every conversation, score, and decision on the candidate timeline, so you can compare candidates weeks later without digging through email threads or sticky notes. Free during beta, no credit card required.