Free guide

Structured Interview Questions by Role: 50+ Examples with Strong-Answer Guides

A structured interview means every candidate for a role gets the same core questions, in the same order, and is scored against the same standards. It is one of the most reliable ways to predict job performance and one of the easiest ways to make hiring fairer. The hardest part is writing good questions. This guide gives you a bank of tested questions for five common roles, explains what a strong answer sounds like, and shows you how to build your own question set in under an hour.

Two types of questions that work

Behavioral questions ask about the past: "Tell me about a time you…". The logic is that past behavior in similar situations is a good predictor of future behavior. Listen for a specific situation, the candidate's own actions and a measurable result. The STAR format (Situation, Task, Action, Result) is a useful lens.

Situational questions ask about a hypothetical: "What would you do if…". They are useful for junior candidates with limited experience, or for testing judgment on scenarios unique to your company.

Avoid brainteasers ("How many golf balls fit in a plane?") and vague prompts ("Tell me about yourself" as a scored question). They are poor predictors and mostly measure confidence.

Universal questions for any role

1. Tell me about a project you're proud of. What was your specific contribution?
2. Describe a time you received critical feedback. What did you change afterward?
3. Tell me about a time you had to deliver with incomplete information.
4. Describe a mistake you made at work and how you handled it.
5. Tell me about a time you disagreed with your manager. What happened?
6. How do you decide what to work on when everything feels urgent?

Strong answers name a real situation, use "I" for their own actions, quantify the result where possible, and include a reflection ("Next time I would…"). Weak answers stay general ("I always communicate well"), use "we" throughout, or blame others.

Sales (account executive, SDR)

1. Walk me through a deal you closed that almost fell apart. What saved it?
2. How do you research a prospect before a first call?
3. Tell me about a quarter where you missed quota. What did you learn?
4. Describe how you handle a prospect who says "it's too expensive."
5. How do you organize your pipeline week to week?
6. Role-play: sell me our product in two minutes, then handle one objection.

Listen for: concrete numbers (deal size, cycle length, conversion rates), curiosity about the customer's problem rather than pushing features, and honest ownership of misses. A candidate who can describe their own funnel math is usually a disciplined seller.

Customer support

1. Tell me about the most frustrated customer you've helped. How did the conversation end?
2. Describe a time you couldn't give the customer what they wanted. How did you say no?
3. How do you prioritize a queue of 40 tickets with different urgencies?
4. Tell me about a time you spotted a recurring problem and got it fixed upstream.
5. Written exercise: reply to this angry email (provide a sample).
6. How do you keep your energy up on a heavy day?

Listen for: empathy combined with boundaries, clarity in writing, and evidence they think beyond the single ticket to root causes.

Software engineering

1. Describe a technically difficult bug you tracked down. How did you approach it?
2. Tell me about a design decision you made that you'd change today.
3. How do you approach working in a large codebase you didn't write?
4. Describe a time you pushed back on a requirement. What was the outcome?
5. Tell me about a code review where you strongly disagreed.
6. Work sample: extend this small function / review this pull request.

Listen for: systematic debugging, explicit trade-offs (speed vs. quality, build vs. buy), and the ability to explain technical choices to a non-engineer. A short, realistic work sample is far more predictive than whiteboard puzzles.

Operations / office manager

1. Tell me about a process you created or fixed. What changed as a result?
2. Describe a time several urgent requests landed at once. What did you do first?
3. How do you track recurring tasks so nothing gets missed?
4. Tell me about negotiating with a vendor.
5. Describe a time you caught an error before it caused a problem.
6. What would you do in your first week to understand how our office runs?

Listen for: systems thinking (checklists, trackers, documentation), calm prioritization and attention to detail backed by examples.

Marketing

1. Walk me through a campaign you ran end to end. What were the results?
2. Tell me about a campaign that failed. How did you know, and what did you do?
3. How do you decide which channels to invest in with a small budget?
4. Describe how you work with sales to define a good lead.
5. What metrics would you look at in your first month here?
6. Exercise: critique our homepage and suggest three improvements.

Listen for: comfort with numbers (CAC, conversion rates), experimentation habits, and a clear link between activity and business results rather than vanity metrics.

Free mini question-bank template

Use this structure to build a question set for any role:

How to build your own question set in an hour

1. List the outcomes the person must achieve in the first 6–12 months (15 minutes).
2. Translate outcomes into 4–6 competencies (10 minutes). "Reduce churn in our SMB accounts" becomes relationship building, data analysis and proactive communication.
3. Write one behavioral and one situational question per competency (20 minutes).
4. Write the anchor for a "3" and a "5" for each (15 minutes). This is what makes scoring consistent.

Then put the questions onto an interview scorecard so interviewers can record evidence and ratings in one place.

Tips for asking good follow-ups

• "What did you do, specifically?" — separates personal contribution from team effort.
• "What was the result? How did you measure it?" — tests impact.
• "What would you do differently?" — tests self-awareness.
• "What alternatives did you consider?" — tests judgment.

Keep follow-ups neutral. Don't hint at the answer you hope to hear, and give every candidate roughly the same amount of probing.

Questions to avoid

Avoid any question about age, family plans, religion, health, nationality or other protected characteristics. These are illegal or risky in many countries and irrelevant to performance. Also avoid leading questions ("You're comfortable with long hours, right?") and trivia that can be looked up in seconds.

Frequently asked questions

How many questions fit in a 45-minute interview? Usually five to seven, with follow-ups. Leave ten minutes for the candidate's own questions.

Is it okay to deviate from the script? Yes for follow-ups, no for the core questions. The core set is what makes candidates comparable.

Want this done for you? The Interview Scorecard Pack includes role-specific questions and rating anchors for five common roles, ready to edit in Word or Google Docs.

← More hiring guides