One interview question template you can reuse for any role

Most “interview question templates” are a list of questions with a cover page. You download it, copy the questions you like, and paste them into whatever you’re running this week: a phone screen, a quick in-person chat, a one-way video interview. The list itself is fine. The problem shows up the next time you hire, when the format changes and you’re rebuilding the whole thing again.

That’s the part nobody’s template accounts for. If you hire the same handful of roles over and over, you don’t interview candidates the same way twice.

Low candidate volume this month means a phone screen. A flood of candidates for one opening means a one-way interview, because you can’t call eighty people back. A same-day hiring decision means in-person.

The questions should travel with you across all three. Most templates don’t, because they were built for one format and never asked to survive a second one.

Most interview question templates are just a list with a cover page

Search “interview question template” and you’ll find hundreds of PDFs and Google Docs, organized by category: behavioral, situational, cultural fit. Pick your favorites, fill in the role name, done. That’s a real starting point, and it’s why we’ve written about the questions themselves before: which ones surface real signal, which ones to retire, how to score the answers consistently.

But a question list assumes you’ve already decided how you’re delivering it. Sit across from a candidate and “tell me about a time you disagreed with your manager” works fine, because you can follow up. Send the same question as a one-way video prompt with no follow-up available, and you get a rehearsed, generic monologue. Put it on a phone screen where you’re taking notes one-handed, and half the nuance gets lost anyway.

The question list rarely breaks. What breaks is the assumption that a question written for one format works unchanged in another. A real template accounts for that from the start, instead of pretending the delivery format is a detail you’ll figure out later.

What rebuilding your questions every time actually costs you

Here’s the pattern we hear from owners hiring the same roles on repeat: questions and rubrics live in whatever Google Doc, Word file, or Slack thread survived the last round. Every new opening means digging up the old version, half-remembering what worked, and rewriting the parts that don’t fit this time’s format. It’s less a process than duct tape holding the last hire’s homework together.

The real cost is that candidates screened in different formats within the same hiring round stop being comparable, on top of the twenty minutes spent rewriting. Say you phone-screened the first six candidates for a coordinator role, then switched to one-way interviews once the pile hit fifty. If the questions weren’t built to hold their shape across that switch, you’re not comparing six candidates against fifty on the same evidence. You’re comparing two different interviews that happen to share a job title.

That’s the quiet failure mode of ungrounded question lists. You feel like you’re being consistent because you’re using “the same questions.” But if the questions only work in the format they were written for, switching formats mid-round means you were never actually comparing apples to apples. You just didn’t notice, because nothing forced you to. It’s the same comparability problem we’ve written about when choosing between resume screening, an interview, and an assessment: the evidence only means something if you’re weighing it on the same scale.

One template, three parts, one thing that changes

The fix is separating what stays fixed from what’s allowed to change.

A reusable template has three fixed parts, in this order:

• Context. A short line that orients the candidate to the role, asked or shown the same way every time. It sets the frame the rest of the interview sits inside, not a question in itself.
• Signal. Two to four role-specific questions that test judgment, reliability, or communication on the actual work of the role, not a generic competency.
• Close. One question that reveals self-awareness or motivation, plus a logistics check (availability, schedule, pay range) if you haven’t confirmed it earlier.

The one thing allowed to change is delivery. On a phone screen, you ask the signal questions out loud and follow up on what’s interesting. In-person, you do the same thing with more time and body language to read. In a one-way interview, the signal questions become recorded prompts with a response window, no follow-up available, so each one has to be self-contained.

If you’re still deciding which format fits a given opening, our breakdown of interview formats walks through the tradeoffs for a business hiring without a recruiter.

Same context, same signal questions, same close. Only the mechanics of asking them move. That’s what makes the template survive a format switch instead of getting rebuilt every time your candidate volume forces one.

The template, filled in for three roles you’re probably hiring right now

Here’s what that looks like for three roles that recur constantly at small, multi-location businesses and don’t have a dedicated question bank anywhere on this site yet.

Office and administrative coordinator

Context: “This role is the person who keeps the location running day to day. I’m going to ask about a few situations you’d actually run into here.”

Signal:

1. “You’re juggling three things at once: a vendor on hold, a customer at the counter, and an email that needs a same-day reply. Walk me through how you’d decide what gets your attention first.”
2. “Describe a time you caught a scheduling or paperwork error before it became a problem. How did you find it?”
3. “Tell me about a system or process you built or improved without being asked to. What made you do it?”

Close: “What’s one thing about how you stay organized that you’d want me to know before your first week?”

Sales or business development representative

Context: “I want to understand how you actually work a deal, not just how you’d describe selling in general.”

Signal:

1. “Walk me through the last deal you lost. What happened, and what would you do differently?”
2. “A prospect goes quiet after three good conversations. What do you do in the next 48 hours?”
3. “Describe how you’d handle a customer who’s frustrated with something outside your control, like a delayed shipment or a price increase.”

Close: “What part of selling do you actually enjoy least? How do you push through it?”

Scheduling and dispatch coordinator

Context: “This role keeps our people and our calendar aligned. I’m going to describe a few situations from the job.”

Signal:

1. “Two team members both request the same day off during your busiest week. Walk me through how you’d handle it.”
2. “A job runs long and it’s going to push back the rest of the day’s schedule. What do you do first?”
3. “Tell me about a time you had to tell someone news they didn’t want to hear, like a schedule change. How did you say it?”

Close: “What’s the most chaotic scheduling day you’ve handled? What got you through it?”

Notice what stays constant across the three: one context line, three signal questions built around a real decision in that job, one close. That’s the whole template. Swap the role, swap the specifics of the scenarios, and the structure holds.

Won’t the same questions feel canned by the third candidate?

Here’s the honest objection. If every candidate gets the same three signal questions, doesn’t that start to feel scripted? Won’t candidate five notice you’re reading off a sheet?

The structure repeats. The wording doesn’t have to. You can rephrase “walk me through how you’d decide what gets your attention first” as “which of those three would you deal with first, and why” without losing the question’s job. What stays fixed is what you’re testing and where it sits in the sequence, not the exact sentence.

That’s the difference between structure and script. If you want to score the answers instead of just comparing them by memory, pair the template with an interview scorecard so each signal question has a rubric behind it.

There’s also an honest limit worth naming. If a role pulls a thin, hard-to-fill pool, you might choose to skip the one-way format entirely and go straight to in-person, because losing a candidate to interview friction hurts more than the format mismatch. The template still works there. You just never activate the one-way delivery mechanics for that role.

This is where the format-switching problem actually gets solved instead of just described. Truffle is a candidate screening platform that combines one-way video interviews, talent assessments, and resume screening, and it’s built for exactly this kind of recurring, format-shifting hiring. You write your context and signal questions once. When a role needs a one-way delivery, Truffle handles the mechanics your template already accounted for: built-in thinking time before recording, a response window per question, and configurable retakes, so the same signal question that worked live still gets a fair shot on video.

AI-generated question suggestions, tailored to your role description, give you a faster starting draft, though you’ll still want to edit them to match the specifics above. When the responses come back, Candidate Shorts pull the most relevant moments so you’re not watching every recording in full to compare your six phone-screened candidates against your fifty one-way ones.

The template is what makes that comparison fair in the first place. The tool just means you don’t rebuild it every time the format changes.

The template is the process you don’t have to reinvent every quarter

Zoom out past a single opening and the real payoff shows up. A recurring role, hired every few weeks or every season, is exactly the kind of role where a from-scratch process quietly compounds into a real cost. Every rewrite is small. Twenty of them, across a year of coordinator and sales postings, is a lot of evenings spent recreating something you already built once and half-remember.

A template you actually reuse turns that into infrastructure instead of homework, the same shift we’ve written about for screening candidates more broadly. Write the context, signal, and close for each recurring role once. Store it somewhere you’ll actually find it again, not a Slack thread from March.

The next time that role opens, you’re not starting from a blank page or from a general-purpose question list. You’re deciding which delivery format fits this round’s candidate volume, and asking the same three questions you already know work.

That’s a smaller shift than it sounds like, and it’s the one most “best questions” lists never get to, because they’re solving for the wrong problem. The questions were rarely the hard part. Keeping them intact while everything else about how you hire keeps changing is.

Frequently asked questions about interview question templates

How many questions should be in an interview question template?

Keep the signal block to two to four questions per role. Add the context line and the close, and you have five or six total per format. More than that and completion rates or attention drop, especially in a one-way format where every extra question is another response window a candidate has to sit through.

Can I use the same interview question template for a phone screen and a one-way interview?

Yes. Keep the context, signal, and close fixed, and change only the delivery: asked live with room for follow-ups on a phone screen or in person, recorded as a self-contained prompt with a response window for a one-way interview. If a question falls apart without a follow-up, it needs a small rewrite to be self-contained before it goes into a one-way format. See our breakdown of one-way interview questions for what that rewrite usually looks like.

What’s the difference between a question template and a structured interview?

A question template is the reusable object: the same context, signal, and close questions for a given role. A structured interview adds a scoring layer on top, an anchored rubric that turns each answer into a comparable score across candidates. You can run a template without formal scoring, but pairing the two is what actually makes candidates screened in different formats comparable.

Where do I store an interview question template so I actually reuse it?

Anywhere you’ll find it again in three months, which usually rules out a Slack thread or an email. A shared doc per role, named by role and not by hire date, works for a one-person operation. If you’re screening more than a couple of open roles at a time, keeping the template inside the platform you’re already screening candidates in avoids the copy-paste drift where the doc and the actual interview stop matching.

Building this template once per recurring role, and keeping it in a place where the format can flex without a rewrite, is what separates a hiring process from a folder of half-remembered documents. If you’re ready to run that template across phone, in-person, and one-way rounds without rebuilding it each time, see how Truffle’s one-way video interview software carries your questions from a live conversation into a recorded round, with the same context, the same signal questions, and a shortlist you can actually compare.