Instructional designer interview questions and how to answer them

Instructional design interviews test your judgment more than your software skills. Expect to walk through past work, defend what you cut, and show how you'd handle a stakeholder who wants a course when the real problem is a broken process. Many teams also give you a short design exercise, so come ready to think out loud.

11 questions7 minute read

Part 1

1.Walk me through a project from the first request to launch.

Why they ask

They want to see your process in action, not a textbook recital of ADDIE. The details you choose to mention tell them what you think matters.

How to answer

  • Name the request as it arrived, including what the stakeholder thought they needed
  • Explain the questions you asked to find the real performance gap
  • Describe the format you picked and why you ruled out the others
  • Cover review rounds, the pilot and what you changed after it
  • Close with what happened to learner behavior or the business problem

2.A manager asks you for a course, but you suspect training won't fix the problem. What do you do?

Why they ask

Plenty of training requests are really about bad tools, unclear expectations or missing incentives. They want someone who can spot that without being difficult.

How to answer

  • Ask what people are doing now and what they should be doing instead
  • Check whether they could do it if their job depended on it, which separates a skill gap from a process gap
  • Suggest the smaller fix first, like a job aid, a checklist or a conversation with the process owner
  • Offer training for the part that's truly a knowledge gap

3.How do you work with a subject matter expert who wants to include everything?

Why they ask

This is the most common friction in the job. They're checking whether you can cut content without making an enemy.

How to answer

  • Anchor the conversation on the specific tasks learners must perform after training
  • Sort content into must-know, reference and nice-to-have, then move reference material into a job aid
  • Show the expert a draft early so the cuts feel collaborative
  • Give a real example where an expert agreed once they saw the learner's view
4.How do you measure whether training worked?

Why they ask

Teams are tired of reporting completion rates. They want someone who can connect learning to what changes on the job.

How to answer

  • Mention the Kirkpatrick levels briefly, then move past reaction surveys
  • Explain how you agree on a success measure with the stakeholder before building
  • Give an example of on-the-job evidence you tracked, like fewer support tickets or faster onboarding
  • Be honest about what you couldn't measure and what you did instead
5.Tell me about a design decision you made that you'd change now.

Why they ask

Self-awareness matters in a role where your work gets critiqued constantly. They're also testing whether you learn from learner data.

How to answer

  • Pick a real decision, such as a branching scenario that confused people or a video that ran too long
  • Say how you found out it wasn't working
  • Explain what you'd do differently and why
  • Show that the lesson carried into later projects

Part 2

6.Which authoring tools have you used, and how deep does your experience go?

Why they ask

They need to know how much ramp-up you'll need on their stack, and whether you can build or only storyboard.

How to answer

  • Name the tools you've shipped real work in, such as Storyline, Rise, Captivate or Camtasia
  • Describe something specific you built, like triggers and variables in a Storyline scenario
  • Mention how you publish, whether SCORM or xAPI, and which LMS you've loaded content into
  • Be clear about tools you only know lightly
7.How do you make a course accessible?

Why they ask

Accessibility complaints and audits are real risks, and many designers treat it as an afterthought.

How to answer

  • Mention WCAG and building accessibility in from the storyboard, not at the end
  • Cover alt text, captions, keyboard navigation, focus order and color contrast
  • Explain how you test, such as running through with a screen reader
  • Note that drag-and-drop interactions often need an alternative
8.You have a tight deadline and a stakeholder who keeps changing the content. How do you handle it?

Why they ask

Scope creep in review cycles is where projects die. They want to see how you protect the timeline.

How to answer

  • Set review rounds and sign-off points at kickoff, with a named approver
  • Lock content at the storyboard stage before you build in the authoring tool
  • Explain the cost of late changes in plain terms like pushed dates or dropped modules
  • Describe a time you did this and kept the relationship intact
9.How would you design training for people who have almost no time, like frontline retail or warehouse staff?

Why they ask

Designing for desk workers is easy. They want to know if you can design for the learners with the least attention to spare.

How to answer

  • Start with where and when they'd actually use it, like a phone on a break or a tablet at a station
  • Favor short, task-focused pieces and job aids at the point of work
  • Involve a shift lead or supervisor in reinforcement
  • Mention testing a draft with a few real workers before rollout
10.Tell me about a time you disagreed with a colleague or manager.

Why they ask

Designers work across departments and need to argue a point without damaging trust.

How to answer

  • Describe the disagreement plainly and what was at stake
  • Explain how you brought evidence rather than opinion
  • Share how it resolved, including if you were wrong
  • Say what you'd repeat next time

Part 3

11.Why do you want to work on our team specifically?

Why they ask

They want to know you've looked at their learners, industry and training setup, not just the job title.

How to answer

  • Name something concrete about their audience or product that interests you
  • Connect it to a project you've done with a similar group of learners
  • Mention what you'd want to learn in the first stretch of the job

Questions to ask them

Ask at least two. It shows you're picking them too.

  • How do training requests reach this team, and who decides whether a request becomes a project?
  • Which LMS and authoring tools do you use, and are there plans to change either?
  • How does the review and sign-off process usually run, and where do projects tend to stall?
  • How does the team show leadership that a program worked?
  • What would a successful first project look like for the person in this role?