Interview guide · Training and L&D roles
Instructional designer interview questions
In short
Good instructional designer interview questions test how a candidate turns a business problem into practice that changes behavior: analysis, objectives, scenario design, assessment writing, working with subject matter experts, authoring tools, accessibility and evaluation. Below are 35 questions for instructional designers, learning experience designers and e-learning developers, with what to listen for and a scorecard.
An instructional designer's output is easy to judge on looks and hard to judge on what matters. A polished module with animations and a narrator can teach nothing, while a plain scenario with good decisions and honest feedback can cut errors in half. The interview has to get underneath the portfolio: why the designer made each choice, what the learner was supposed to do differently, how they handled the subject matter expert who wanted 90 slides, and whether anyone checked if it worked.
These questions cover instructional designers, learning experience designers who lean toward user research and journey design, and e-learning developers who spend most of their time in authoring tools. Run the portfolio review and the design questions for every candidate, then weight the technical or the analysis questions depending on the role. A short design exercise, done in the interview or as a small take-home, tells you more than any answer.
What to look for in a instructional designer
- Performance-focused analysisThe best designers ask what learners need to do on the job and what gets in their way. They cut information that does not support an action.
- Practice and scenario designRealistic decisions with consequences build skill. Designers who default to information screens and recall quizzes produce training that does not transfer.
- Assessment writingMost assessment questions in corporate training test memory, not judgment. Strong designers write plausible distractors and application-level questions.
- SME managementDesigners depend on experts who are busy and attached to their content. Getting accurate input on time without bloating the course is a core skill.
- Technical craftAuthoring tools, LMS packaging, accessibility and media production decide whether a design actually works for learners on the devices they use.
- Iteration and evaluationDesigners who prototype, test with real learners and check results build better courses than those who launch once and move on.
Portfolio and background questions
Pick one project from your portfolio and walk me through it from the original request to launch.
- Why ask it
- The single most useful question. It shows process, judgment and honesty about constraints.
- A strong answer
- Describes the business problem, audience, analysis done, objectives, why they chose the format and activities, SME and stakeholder process, testing, launch and results. Points out what they would change.
- Red flags
- Talks only about visual design and tools, or cannot explain why choices were made.
What was your role on this project, and what did others do?
- Why ask it
- Portfolios often show team work. You need to know what the candidate personally did.
- A strong answer
- Clear about their part (analysis, storyboard, build, assessments) versus graphics, voiceover or development by others.
- Red flags
- Vague, or takes credit for every part of a large team project.
How did you get into instructional design?
- Why ask it
- Many designers come from teaching, training or a subject field. Their path shapes strengths.
- A strong answer
- A clear path and deliberate skill building, such as formal study, mentoring, practice projects or learning on the job.
- Red flags
- Sees ID as a way to make slides without understanding learning.
Which design models or approaches do you use, and when do you depart from them?
- Why ask it
- Tests whether models are tools or rituals.
- A strong answer
- Can describe a structured approach like ADDIE, a rapid iterative approach, or action mapping, and explains when each fits. Adjusts for timelines and stakes.
- Red flags
- Recites ADDIE phases with no sense of how they apply in real projects.
Which authoring, media and LMS tools have you worked in?
- Why ask it
- Sets expectations for ramp-up.
- A strong answer
- Names the categories and depth: a slide-based authoring tool with variables and triggers, a responsive authoring tool, video and screen capture, graphics, and publishing packages to an LMS.
- Red flags
- Claims expert level in everything, or has only used slide software.
How do you stay current in learning design?
- Why ask it
- Learning science and tools move fast; myths persist.
- A strong answer
- Specific sources, communities or research they follow, and one change in their practice that came from it.
- Red flags
- Repeats discredited ideas like designing to individual learning styles.
Analysis and design questions
A stakeholder asks for 'a course on our new expense policy.' What questions do you ask first?
- Why ask it
- Shows whether they start from performance.
- A strong answer
- What mistakes are people making now, who submits expenses and how often, what does it cost when it goes wrong, which decisions are hard, could a checklist or system change fix it, and how will we know it worked.
- Red flags
- Asks only about length, deadline and branding.
Write a learning objective for a customer service agent handling a billing dispute.
- Why ask it
- Quick live test of objective writing.
- A strong answer
- Observable and measurable, for example: 'Given a customer disputing a late fee, the agent will apply the fee waiver policy correctly and explain the decision to the customer in one call.'
- Red flags
- 'Understand the billing dispute process.'
How do you decide what content to cut?
- Why ask it
- Cutting is the hardest and most valuable design skill.
- A strong answer
- Keeps what directly supports the required actions, moves reference information to job aids or a knowledge base, drops history and nice-to-know detail, and confirms with the SME and stakeholder.
- Red flags
- Keeps everything the SME provides.
How do you design a scenario-based activity? Describe one you built.
- Why ask it
- Scenarios are the strongest tool for judgment skills.
- A strong answer
- Starts from a realistic situation with a real decision, plausible wrong options based on common mistakes, consequences that play out, and feedback that explains. Describes branching or a series of decisions.
- Red flags
- Calls a multiple-choice quiz with a character image a scenario.
How do you write assessment questions that test application rather than recall?
- Why ask it
- Assessments show whether a designer understands learning.
- A strong answer
- Puts the learner in a situation and asks what they would do, uses distractors that reflect real mistakes, avoids 'all of the above' and trick wording, and aligns each question to an objective.
- Red flags
- Questions like 'Which year was the policy introduced?'
When would you recommend no e-learning at all?
- Why ask it
- Good designers know when a module is the wrong answer.
- A strong answer
- When the problem is motivation, tools, process or management; when a job aid will do; when the skill needs live practice with feedback; or when the content changes weekly.
- Red flags
- E-learning is always the answer.
How do you design for spaced practice and retention after launch?
- Why ask it
- Most forgetting happens after the course.
- A strong answer
- Short follow-up activities over weeks, scenario questions spaced out, manager prompts and job aids, and a check at 30 or 60 days.
- Red flags
- Considers the course complete when the learner finishes it.
How would you approach the design of a learning journey for a new hire's first 90 days?
- Why ask it
- Learning experience design question for broader roles.
- A strong answer
- Maps the new hire's real milestones, combines formal modules, practice, buddy and manager touchpoints, spaces content to when it is needed, and gathers feedback from recent hires.
- Red flags
- A single long course on day one.
Working with SMEs and stakeholders
An SME sends you 120 slides and says everything is essential. What do you do?
- Why ask it
- The most common ID situation.
- A strong answer
- Thanks them, walks through the objectives together, asks which slides support which action, uses scenarios to test what learners really need, and moves the rest to reference material. Keeps the SME involved in reviewing realism.
- Red flags
- Converts all 120 slides into e-learning.
How do you get timely reviews from busy SMEs?
- Why ask it
- Review delays sink project timelines.
- A strong answer
- Agrees review dates upfront, sends small chunks with specific questions, uses short review sessions instead of long documents, and escalates early when deadlines slip.
- Red flags
- Sends a full storyboard and waits.
How do you handle conflicting feedback from two stakeholders?
- Why ask it
- Common in projects with several sponsors.
- A strong answer
- Brings them together or to the project sponsor, ties the decision back to the agreed objectives, and documents the outcome.
- Red flags
- Tries to satisfy both and ends up with a muddled course.
Tell me about a time a stakeholder rejected your design. What happened?
- Why ask it
- Resilience and persuasion.
- A strong answer
- Understood the concern, adjusted where it made sense, argued for the core design with evidence or a prototype, and reached a decision.
- Red flags
- Has never had a design rejected, or gave up the core idea immediately.
How do you estimate and manage a project timeline?
- Why ask it
- Designers often manage several projects at once.
- A strong answer
- Breaks work into analysis, design, build, review and testing, uses past projects to estimate hours per finished minute or per module, builds in review cycles and tracks progress visibly.
- Red flags
- No estimating method, often late.
Technical and e-learning development questions
How do you make e-learning accessible?
- Why ask it
- Accessibility is a legal and practical requirement in many organizations.
- A strong answer
- Follows WCAG guidelines: keyboard navigation, screen reader support, alt text, captions and transcripts, color contrast, no information by color alone, and testing with assistive technology. Mentions Section 508 for US federal work.
- Red flags
- Adds closed captions and considers it done.
What is the difference between SCORM and xAPI, and when does it matter?
- Why ask it
- Packaging standards affect tracking.
- A strong answer
- SCORM packages content for an LMS and tracks completion, score and time. xAPI records a wider range of learning activities as statements in a learning record store, including outside the LMS. It matters when you need richer data or offline and mobile tracking.
- Red flags
- Has never published to an LMS.
A course works on desktop but breaks on mobile for frontline staff. How do you fix it?
- Why ask it
- Many frontline learners use phones.
- A strong answer
- Tests on the actual devices, uses responsive design or a responsive authoring tool, simplifies interactions, checks file sizes for slow connections and retests.
- Red flags
- Tells learners to use a computer.
How do you use video in learning, and what are its limits?
- Why ask it
- Video is overused as a default.
- A strong answer
- Short videos for demonstrations, real examples and emotional context, with scripts kept tight. Limits: passive, expensive to update, so pair with practice and avoid it for content that changes often.
- Red flags
- Plans long talking-head videos for everything.
How do you use AI tools in your design work?
- Why ask it
- Most teams now use AI for drafting; judgment about it matters.
- A strong answer
- Uses it for first drafts of scenarios, question banks, scripts and translation, then checks everything with SMEs for accuracy. Mentions data privacy and not pasting confidential material into unapproved tools. May mention AI role-play for practice.
- Red flags
- Publishes AI-generated content without expert review, or refuses to consider it.
Show me how you would build a simple branching interaction in your preferred tool.
- Why ask it
- For e-learning developer roles, a quick live check of technical skill.
- A strong answer
- Explains or demonstrates variables, triggers or states, how they track the path taken, and how they test every branch.
- Red flags
- Cannot describe how branching works in any tool.
Evaluation and behavioral questions
How do you know whether a course you designed worked?
- Why ask it
- Separates designers who care about results.
- A strong answer
- Defines measures with the stakeholder upfront, uses assessment data to find weak spots, checks behavior or performance data after launch, and gathers learner feedback on relevance.
- Red flags
- Relies on completion and satisfaction scores.
How do you test a course before launch?
- Why ask it
- Pilots catch problems early.
- A strong answer
- Prototype testing with a few target learners, a technical QA checklist across devices, SME accuracy review and a pilot group with data before full release.
- Red flags
- Only the SME reviews it.
Tell me about a project that did not go well.
- Why ask it
- Self-awareness.
- A strong answer
- Specific project, honest cause, what they learned and changed in later projects.
- Red flags
- Blames SMEs or stakeholders entirely.
Describe a time you had to deliver under a very tight deadline.
- Why ask it
- Tests prioritization and pragmatism.
- A strong answer
- Cut scope to the essentials, used templates, negotiated what could follow later, and kept quality on what mattered most.
- Red flags
- Worked nights and delivered everything as planned with no trade-offs, or missed it without warning.
Tell me about feedback from learners that changed one of your designs.
- Why ask it
- Learner-centered practice.
- A strong answer
- Specific feedback, the change made and the effect.
- Red flags
- Never asks learners for feedback.
Sample answers
I'd thank them, because it's genuinely useful source material, and then book an hour to go through it together. Before that meeting I'd draft the three or four things learners need to do differently and bring them along. In the meeting I'd ask the SME to tell me the mistakes they see most often, and for each one, which slides help someone avoid it. That usually shrinks it a lot without me having to argue. Things like regulation history or org charts I'd suggest moving into a reference page linked from the course. Then I'd ask them to help write the scenarios, because SMEs are great at saying what really happens, and it keeps them invested. On one project this took 110 slides down to a 20-minute module with six decisions.
For a pharmacy chain's technicians, the problem was errors when a customer asked for an early refill. I started by asking pharmacists for the real situations and the wrong decisions technicians usually made. The scenario put the learner at the counter with a customer who was polite but in a hurry, and the learner had to choose what to check and what to say. Each wrong option was a mistake people actually made, like processing it because the insurance approved it. The consequence played out, a pharmacist catching it or a call from the insurer, and then the feedback explained the rule in plain words. There were three decision points and two endings. We tested it with six technicians first and rewrote one option they all found obviously wrong.
Interview scorecard
| Competency | Weight | Strong (4–5) | Weak (1–2) |
|---|---|---|---|
| Analysis and objectives | 20% | Starts from performance problems, asks the right questions, writes observable objectives, recommends non-training fixes when appropriate. | Starts with content and format, vague objectives. |
| Practice, scenario and assessment design | 30% | Designs realistic decisions with consequences and feedback, writes application-level assessment questions. | Information screens and recall quizzes. |
| SME and project management | 20% | Keeps SMEs engaged and focused, manages reviews and timelines, resolves conflicting feedback. | Absorbs all content, frequent delays, no estimating method. |
| Technical and accessibility skills | 15% | Fluent in authoring and LMS publishing, designs for mobile and accessibility, uses AI tools with care. | Limited tools, accessibility treated as an afterthought. |
| Evaluation and iteration | 15% | Prototypes, pilots, uses data and learner feedback to improve. | Launches once and moves on. |
Score each competency from 1 to 5 straight after the interview, before discussing the candidate with anyone else, then multiply by the weight.
How to structure an instructional designer interview
Portfolios are where instructional design interviews start, but you need to see the thinking behind them. A process that works for most ID, learning experience designer and e-learning developer roles:
- Screen (20 to 30 minutes). Background, tools, types of projects and audiences, salary and location. Ask for portfolio links before the next round.
- Portfolio review (45 to 60 minutes). The candidate walks through two projects. Ask why at every step: why this format, why this activity, why this assessment, what the SME wanted, what they would change. The analysis and SME questions from this page fit here.
- Design exercise (45 to 90 minutes). Either live or as a short take-home of no more than two to three hours. Give a realistic brief, for example a one-page process and a description of the errors people make, and ask for objectives, a short outline, one scenario and three assessment questions. For e-learning developer roles, ask them to build one interaction instead. Pay for longer take-home work or keep it small.
- Team interview (30 minutes). A trainer or L&D colleague and, ideally, an SME they would work with.
If the role also involves strategy, prioritization and stakeholder management across a portfolio, add questions from the learning and development interview questions. For designers who will also deliver, borrow from the trainer interview questions.
Mistakes when hiring instructional designers
Hiring the prettiest portfolio. Visual polish is the easiest thing to judge and the least predictive of learning results. Ask what learners had to decide or do in each sample, and how anyone knew it worked.
Not separating team work from individual work. Many portfolio pieces come from teams with graphic designers, developers and voice talent. Ask exactly which parts the candidate did.
Oversized take-home assignments. A 15-hour unpaid project drives away experienced designers who have options. Keep exercises small and focused on the thinking.
Mismatched role definitions. 'Instructional designer' can mean an analyst and consultant, a storyboard writer or a developer in an authoring tool. Be clear in the job posting and interview for the actual mix of work.
Ignoring the frontline learner. Designers from academic or corporate office settings may never have designed for hourly staff on phones with ten minutes between tasks. Ask about the least-connected audience they have designed for.
Instructional design for high-volume training programs
Employers that hire hundreds or thousands of frontline staff a year, such as contact centers, retail chains, warehouses and care providers, need designers who can build for scale and speed to proficiency.
- Design for the shift, not the classroom. Modules of five to ten minutes on mobile, performance support that works mid-task and practice that fits between calls or deliveries.
- Build practice that scales. A trainer cannot run 40 role-plays a day for every new hire. Designers increasingly write scenarios for AI role-play practice, where learners rehearse conversations repeatedly with consistent scoring, and the trainer coaches from the results.
- Plan for frequent updates. Processes and products change often in operational settings. Modular content, shared templates and a simple update process matter more than a beautiful one-off course.
- Support the people who deliver. Facilitator guides, nesting checklists and coaching tools for team leaders are design work too. Designers often partner with a training coordinator to schedule and track cohorts; see our training coordinator interview questions for that role.
Ask candidates to describe the largest audience they have designed for and how they measured ramp time or error rates afterward. That answer tells you whether they have designed for volume before.
Frequently asked questions
What are the most common instructional design interview questions?
Expect a portfolio walkthrough, questions on how you analyze a training request, write objectives, design scenarios and assessments, work with SMEs, use authoring tools and make content accessible, and how you evaluate results. Many interviews also include a short design exercise.
What do learning experience designer interview questions focus on?
Learning experience designer interviews add user research and journey thinking: how you learn about your audience, how you design a sequence of experiences over weeks rather than one course, how you test prototypes with learners, and how you use data to improve the experience.
What should I expect in e-learning developer interview questions?
E-learning developer interviews focus on technical build skills: authoring tools, variables and triggers, responsive design, accessibility, video and graphics, SCORM or xAPI publishing, and testing across devices. You may be asked to build or explain a simple interaction live.
How should I present my portfolio in an instructional designer interview?
Pick two or three projects and explain each from the business problem to results: audience, analysis, objectives, design choices, SME process, build, testing and outcome. Be clear about your own role. Interviewers care more about your reasoning than about visual polish.
Is a design test common in instructional designer interviews?
Yes. Typical tests ask you to write objectives, outline a module, draft a scenario or write assessment questions from a short brief. Good employers keep them to a few hours. Developer roles may ask you to build one interaction in an authoring tool.
What is the difference between an instructional designer and a trainer?
An instructional designer analyzes needs and builds learning materials and experiences. A trainer delivers training to groups, usually live. In smaller teams one person often does both, so interviews may cover design and facilitation.