Free template, updated June 2026
Interview Questions for Startup Managers (Free Template)
A ready-to-use bank of structured interview questions, plus a simple way to score answers, for founders and managers who run interviews without an HR team.
In one sentence
Ask every candidate for a role the same core questions, listen for real examples instead of charm, score each answer against what the job actually needs, and decide as a group: the question bank and rubric below give you everything you need to do that today.
How to run a startup interview that actually works
A good interview is not a friendly chat. It is a short, fair test that helps you predict how someone will do the job. The single biggest upgrade you can make is to run a structured interview: the same core questions, asked in the same order, scored the same way for every candidate. Research on hiring has shown for decades that structured interviews predict job performance far better than gut-feel conversations, because they cut down on bias and stop one charming answer from coloring the whole call.
- Ask everyone the same core questions. Pick your questions before the first interview, then ask them of every candidate so you compare like with like.
- Score against the role, not charisma. Decide what a strong answer looks like in advance, and rate the answer, not how likeable the person felt.
- Take notes during the call. Write down what they actually said. Memory fades and favors whoever spoke last.
- Let the candidate talk. Aim to listen about 80 percent of the time. You learn nothing while you are the one talking.
- Decide as a group. Have each interviewer score independently before you discuss, so nobody just echoes the loudest voice in the room.
The question bank (copy this)
These are behavioral questions: they ask for a real past example, not a hypothetical. Past behavior is the best signal you have for future behavior. Pick four to six per interview, mix the groups, and ask the same set of every candidate for that role.
1. Ownership and bias to action
- Tell me about a time you saw a problem nobody asked you to fix, and you fixed it anyway. What happened?
- Describe a project you owned end to end. What did you decide, and what would you do differently now?
- Tell me about a time you shipped something before it was perfect. How did you decide it was good enough?
- Give me an example of a goal you set for yourself, with no one checking on you. Did you hit it?
- Tell me about a time something you owned went wrong. What did you do next?
Look for: A strong answer shows the person took the problem as theirs, made a real decision, and acted without waiting to be told. Watch for "we" with no clear sign of what they personally did.
2. Problem solving and judgment
- Walk me through a hard problem you solved recently. How did you break it down?
- Tell me about a decision you made with incomplete information. How did you choose?
- Describe a time you had to pick between two good options under a tight deadline. What did you weigh?
- Tell me about a time your first solution did not work. How did you find the real cause?
- Give me an example of a time you said no to a request to protect a bigger goal.
Look for: A strong answer is structured: here was the problem, here is how I broke it down, here is what I tried, here is the result. You want to hear a clear chain of reasoning, not just a lucky outcome.
3. Working in ambiguity and change
- Tell me about a time the plan changed halfway through. What did you do?
- Describe a project where you started with almost no instructions. How did you get going?
- Tell me about a time priorities shifted on you suddenly. How did you handle it?
- Give me an example of a time you had to learn something new fast to get a job done.
- Describe a situation where there was no clear right answer. How did you move forward anyway?
Look for: A strong answer shows the person stayed calm, made a sensible first move without a full map, and adjusted as they learned. Startups change weekly, so comfort with mess matters more than a love of process.
4. Collaboration and conflict
- Tell me about a time you disagreed with a teammate. How did it end?
- Describe a time you had to give someone hard feedback. What did you say, and what happened?
- Tell me about a time you changed your mind because of something a coworker said.
- Give me an example of a time you helped a teammate who was stuck or struggling.
- Describe a project that needed people from different teams. How did you keep everyone moving?
Look for: A strong answer shows the person can disagree without making it personal, can take input, and cares about the result more than being right. Watch for stories where every coworker is cast as the problem.
5. Motivation and role fit
- Why this role, and why a small company instead of a big one, right now?
- What kind of work makes you lose track of time?
- Tell me about the best month of work you have had. What made it good?
- What do you want to be doing or learning a year from now?
- What is something about this job you are honestly unsure about?
Look for: A strong answer is specific and honest about what they want, and it lines up with what this job really offers. You want genuine pull toward the work, not a rehearsed pitch about loving challenges.
6. Red-flag probe questions
- What is the real reason you are leaving or left your last role? (Then stay quiet and let them fill the space.)
- Tell me about a piece of critical feedback you got. Did you agree with it, and what did you do?
- What would your last manager say you need to work on? (Vague non-answers here are the signal.)
Look for: A strong answer is honest and shows self-awareness, even about a flaw. The flag is not having a weakness, it is being unable to name one, blaming everyone else, or having no real example at all.
How to score answers (simple rubric)
After each answer, rate it against the signal it was meant to test, not against how nice the person was. Keep it to a 1 to 3 scale: weak, okay, strong. Score on real outcomes and real examples, not on vibes. Use this table to tell the difference.
| Signal | Weak answer | Strong answer |
|---|---|---|
| Ownership | "We" with no clear personal role. Waited to be told what to do. | Took the problem as theirs, made the call, owned the result good or bad. |
| Structured thinking | Jumps to the outcome. Cannot explain how they got there. | Breaks the problem into steps, explains the trade-off, walks you through it. |
| Real examples | Speaks in general claims: "I always handle pressure well." | Names a specific time, place, action, and result you could check. |
| Self-awareness | No real weakness. Blames managers, teammates, or bad luck. | Names a genuine flaw and what they changed because of it. |
Questions you must not ask
In the United States, you cannot base hiring on protected traits, and certain questions can put you in legal trouble even if you meant nothing by them. Title VII, the Americans with Disabilities Act (ADA), and the Age Discrimination in Employment Act (ADEA) make it unlawful to discriminate on these grounds. Do not ask about:
- Age or date of birth. Ask instead: "Are you legally able to work in this country?"
- Race, ethnicity, or national origin. Ask instead: "Are you authorized to work here, and will you need sponsorship now or in the future?"
- Religion. Do not ask. If schedules matter, ask: "Can you work the hours this role requires?"
- Marital or family status, kids, or childcare. Off limits, even as small talk.
- Pregnancy or plans to have children. Off limits.
- Disability, health conditions, or medical history. You may ask if they can perform the specific tasks of the job, with or without reasonable accommodation.
- Citizenship beyond work authorization. You may confirm they are authorized to work, but not where they were born.
A simple rule: only ask about things that relate directly to doing the job. Laws also vary by state and city (for example, many places now bar asking about salary history), so check your local rules or a qualified employment lawyer before you finalize your questions.
Mistakes managers make in interviews
- Talking too much. If you are talking more than the candidate, you are learning nothing.
- Leading questions. "You are good with deadlines, right?" only ever gets one answer.
- Taking no notes. Without notes you remember the vibe, not what was actually said.
- Different questions for each candidate. You cannot compare people fairly if you asked them different things.
- Hiring for likeability. The most charming person in the room is not always the one who can do the work.
Interview the right people in the first place
The best interview is one you only run with strong candidates. Your time is the scarce thing, so the goal is to spend it on the few people worth meeting, not on a pile of resumes. CurriculoATS reads every application and ranks candidates by an Impact Score, with a short written reason for each, so the people most likely to do the job rise to the top before you book a single call. Candidates apply by emailing a resume to a unique address for each job, everything lands in a Gmail-style inbox, and your interview notes and pipeline stay in one place instead of scattered across spreadsheets and inboxes. It is free to start: Free Starter is free forever and covers unlimited job listings, 1,000 candidates ranked by Impact Score, advanced pipelines, and team collaboration. Pro is a flat $100 a month (currently $50 early-bird), with no per-seat fees and unlimited users. New to this? Read what an ATS is, see the best ATS for startups, or grab our startup job description template to write the post that brings these candidates in.
Frequently asked questions
How many questions should a startup interview have?
For a 45 to 60 minute interview, plan four to six core behavioral questions and leave room to follow up on each one. It is better to go deep on a few real examples than to rush through a long list. Save the last five to ten minutes for the candidate's own questions, which tell you a lot about what they care about.
What is a structured interview and why is it better?
A structured interview means you ask every candidate for a role the same core questions, in the same order, and score the answers the same way. It is better because it lets you compare people fairly and cuts down on bias and gut-feel. Decades of hiring research show structured interviews predict job performance far more reliably than unstructured chats.
What interview questions are illegal to ask?
In the United States, do not ask about age, race, religion, national origin, marital or family status, pregnancy, disability, or medical history, since these can violate Title VII, the ADA, and the ADEA. Instead, ask only about things tied directly to the job, such as whether the person can perform the required tasks and is authorized to work. Rules vary by state and city, so check your local laws or an employment lawyer before finalizing your questions.
How do I interview candidates with no HR team?
Use the question bank and rubric on this page: pick four to six questions, ask them of every candidate, and score each answer against the job rather than the person's charm. Take notes during the call and have each interviewer score on their own before you discuss. That simple structure gives a small team most of the fairness and accuracy a full HR process would.
How do I decide who to interview?
Screen on the resume and the role first, so you only interview people who clearly fit, since interview time is your most limited resource. CurriculoATS does this for you by reading every application and ranking candidates by an Impact Score with a short written reason, so the strongest people surface first. It is free to start, and Pro is a flat $100 a month (currently $50 early-bird) with no per-seat fees and unlimited users.