Most first-round interviews are a waste of time. You ask someone to walk you through their resume, they give you a rehearsed highlight reel, you both pretend it was useful, and then you schedule a second round to figure out what you should have learned in the first one.
If you're a founder or operator making 2–4 hires a year, that inefficiency compounds fast. A bad first round doesn't just cost you an hour — it costs you pipeline momentum, delays your hire by a week, and occasionally lets a weak candidate survive into late-stage rounds where everyone has more skin in the game and bias kicks in harder.
The fix isn't a longer interview. It's better questions — ones that create signal quickly and separate people who can actually do the job from people who are good at talking about doing the job.
Here's what actually works.
What a good first-round question does
Before the list, it's worth being explicit about what you're optimizing for. In a first round, you're not trying to hire someone. You're trying to eliminate the people who aren't right and fast-track the ones who might be.
A good first-round question does at least one of these things:
- Reveals actual thinking, not a rehearsed answer
- Surfaces specifics — numbers, names, dates, outcomes — instead of vague generalities
- Tests for self-awareness, because someone who can't tell you where they've struggled is either lying or hasn't reflected enough to grow
- Predicts job-relevant behavior, not just likability
Keep that filter in mind as you read through these.
The questions that actually work
"Walk me through a project you owned end-to-end. What was the result, and what would you do differently?"
This is a better version of "tell me about yourself." The constraint — end-to-end ownership — immediately separates doers from people who were adjacent to good work. The "what would you do differently" clause is where the real filtering happens. Candidates who give a polished answer about what went great and then fumble on the second half either haven't reflected seriously or are performing rather than talking to you.
What you're listening for: specific context ("we were trying to hit 1,200 signups before the event on March 15"), real accountability ("I underestimated how long QA would take"), and genuine insight about what they'd change. Red flag: anyone who says "honestly, I wouldn't change much."
"What's something you taught yourself in the last 12 months to get better at your job?"
For small teams, you can't afford people who wait to be trained. You need people who identify gaps and close them independently. This question tests for that directly.
Strong answers are specific: "I learned SQL because I was tired of waiting two days every time I needed to pull a report. I did a free course on Mode Analytics and now I do it myself." Weak answers are vague: "I've been working on my leadership skills" — okay, how? What did you do? What changed?
This question also tells you something about intellectual curiosity, which is one of the best proxies for long-term performance in fast-moving environments.
"Tell me about a time you disagreed with a decision and what you did about it."
This one filters for two things simultaneously: whether someone has opinions (important) and whether they handle disagreement productively (also important). You don't want someone who just nods along, and you don't want someone who makes every disagreement a fight.
Listen for how they describe the other person. Candidates who tell this story by making themselves the hero and the other person the villain are showing you something real about how they operate. The best answers acknowledge complexity: "My manager had context I didn't have, so after I raised it once clearly, I let it go and focused on executing well."
"What does your ideal week look like in this kind of role?"
This is a sneaky calibration question. It surfaces whether they actually understand what the job involves day-to-day — or whether they've built a fantasy around the job title. A marketing manager who describes a week full of strategy sessions and presentations and zero time in spreadsheets has either never done the job or is applying for a role that doesn't exist at your company.
It also gives you a real-time opportunity to correct mismatches early. If their ideal week is nothing like what you need, better to know in round one than round three.
"What do you need to know about this role or company to decide if it's right for you?"
Most candidates come with a list of soft, safe questions because they don't want to seem demanding. This question gives them explicit permission to ask the things they're actually wondering about — and what they ask tells you a lot.
Strong candidates ask about specifics: how success is measured in the first 90 days, what the biggest challenge in this role is right now, what happened to the last person in this position. Candidates who have no real questions, or who ask only about salary and PTO this early, are either not genuinely curious or haven't done the work to understand what they're walking into.
Questions to stop asking in first rounds
A few common ones that generate almost no signal:
"Where do you see yourself in 5 years?" Nobody knows, and the people who give a confident answer are just pattern-matching to what they think you want to hear. Skip it.
"What's your greatest weakness?" Every candidate has a rehearsed answer that's either self-deprecating in a humble-brag way ("I work too hard") or completely safe ("I'm still building my public speaking skills"). You'll learn more from the "what would you do differently" question above.
"Why do you want to work here?" Unless someone says something that actually surprises you, this question mostly produces mirror-reflection flattery. It's fine as a rapport question, but don't count it as signal.
How to structure the first 30 minutes
If your first rounds are 30 minutes, here's a structure that works:
- Minutes 0–5: Brief context-setting. Tell them what you're covering, give them a 60-second overview of the role, and set expectations. This isn't just politeness — it reduces anxiety and produces better answers.
- Minutes 5–20: Three questions from the list above, picked based on what matters most for the role. Let answers breathe. Follow up when something is vague. "Can you be more specific about what you owned there?" is a completely fair follow-up.
- Minutes 20–27: Their questions for you. Take these seriously. Your answers set the tone for what kind of company you are.
- Minutes 27–30: Next steps. Tell them exactly what happens next and when. Candidates judge how you treat them before they're hired as a proxy for how you'll treat them after.
Scoring without a rubric
You don't need a formal scoring rubric for a first round. But you do need to force yourself to write down at least three specific things the candidate said — not impressions, actual quotes or paraphrases — within 10 minutes of ending the call. Memory is unreliable and degrades fast. If you're interviewing three people in a day, the first interview will be a blur by dinner.
A simple note template:
- What's the most specific thing they said?
- What's the one thing they said that gave me pause?
- Do I want to spend more time with this person? Why?
That last question matters. If you can't articulate the "why," that's data too.
Where Penroll fits
Penroll is built for founders and operators who are hiring without a full recruiting team behind them. Before you get to interview questions, Penroll helps you write a job post that attracts the right candidates in the first place — so your first-round conversations are already starting from a better pool. Less time filtering, more time actually hiring.