Home Industrial Designer Interview questions
Industrial Designer interview questions
The questions people actually get asked for this role, and what each one is really testing.
What to expect
Industrial design interviews tend to centre on your portfolio and process as much as your qualifications. Panels want to see how you think through a brief, where your ideas came from, and whether you can hold your own with engineers, manufacturers and clients who each pull the design in different directions.
- Portfolio and process walkthrough: You'll be asked to talk through a project from brief to final prototype, explaining decisions rather than just showing finished renders.
- Technical: Questions on specific CAD tools, modelling approaches and how you handle manufacturing constraints.
- Behavioural: Questions about past collaboration with engineers, manufacturers or clients, often framed as 'tell me about a time'.
- Scenario and judgement: Hypotheticals testing how you'd handle conflicting requirements, tight budgets or disagreement with a client's brief.
- Client-facing communication: Questions on how you present and defend design rationale to people without a design background.
Most interviews open with a portfolio review, since it's the fastest way to see your actual work and thinking. From there the panel typically moves into technical questions about your tools and process, then behavioural and scenario questions to test judgement and teamwork, before leaving time for your own questions at the end.
- 1
Walk us through your design process on one project in your portfolio, from initial brief to final prototype.
Why they ask: This is the core question in almost every industrial design interview. The panel wants to see structured thinking, not just a nice-looking end result.
How to structure your answer: Walk through it in stages: the brief and constraints you were given, your research and ideation, key design decisions and why you made them, how the prototype tested, and what changed as a result.
Example answer
“I was given a brief to redesign a handheld product where users had reported discomfort during extended use. I started with quick usability observations of people actually using the current version, then sketched a handful of grip and form variations before narrowing to two directions. I built low-fidelity prototypes using workshop tools to test grip comfort quickly, then modelled the preferred direction properly in Fusion 360 once I had user feedback to back it. The final prototype went through another round of testing before I handed the CAD files and technical drawings to the manufacturing team, along with notes on the constraints that had shaped the final form.”
- 2
Tell me about a time you had to change a design because of a manufacturing or cost constraint raised by an engineer.
Why they ask: Industrial designers work inside real production limits, and panels want evidence you can adapt a design without losing what made it work for the user.
How to structure your answer: STAR: situation, task, action, result, focusing on how you balanced the constraint against the original design intent.
Example answer
“I'd designed a housing with a curved shell that looked good and felt comfortable to hold, but the manufacturing engineer flagged that the curvature would require expensive tooling and a longer cycle time. My task was to keep the ergonomic feel while getting the geometry within a standard tooling process. I reworked the surface in Rhino to simplify the curvature into sections that could be moulded more simply, then retested the grip with a quick prototype to check comfort hadn't dropped. The revised design kept the same feel in testing and moved forward without the tooling blowout.”
- 3
How would you handle a project where your user research findings conflict with the client's original brief?
Why they ask: This tests judgement under pressure and whether you can push back on a client professionally when the evidence points elsewhere.
How to structure your answer: Set out how you'd weigh the evidence, communicate the conflict to the client, and propose a way forward rather than simply picking a side.
Example answer
“I'd first make sure the research findings are solid, not just a small sample giving a misleading signal. If they hold up, I'd bring the client into the findings directly rather than just telling them the brief is wrong, showing them the usability issue we found and why it matters for the product. Then I'd propose one or two design options that address the research finding while still respecting as much of the original brief as makes sense, so the client has a real choice rather than a take-it-or-leave-it change.”
- 4
What CAD packages have you used, and how do you decide between surface modelling and parametric modelling for a given product?
Why they ask: Technical fluency across tools like Fusion 360, SolidWorks and Rhino is expected, and this checks you understand when to use which approach rather than just which buttons to press.
How to structure your answer: Answer directly and technically: name the tools, then explain the decision logic with a concrete example.
Example answer
“I've worked mainly in Fusion 360 and SolidWorks for parametric modelling, and Rhino for surface work. I lean on parametric modelling when a product has a lot of engineered detail that needs to update cleanly if dimensions change, like housings with fasteners and internal components. I switch to surface modelling in Rhino when the form itself is the main design challenge, such as a consumer product with organic curves, because it gives more control over surface quality before locking anything into rigid features.”
- 5
How do you present design rationale to a client who wants a change you think would hurt usability?
Why they ask: Client-facing communication is a big part of the role, and panels want to see you can disagree constructively without being difficult.
How to structure your answer: Describe your communication approach: how you frame the trade-off, what evidence you bring, and how you land on a resolution.
Example answer
“I try to bring the conversation back to the usability testing rather than my own opinion, showing the client what we observed and why the current approach addresses it. I'll usually mock up a quick visual comparison so they can see the trade-off rather than just hear about it. If the client still wants the change after that, I'll flag the risk clearly, offer a way to test the revised version with users if time allows, and move forward with their decision documented.”
- 6
Describe how you validate that a prototype actually solves the usability problem it was designed for.
Why they ask: This checks whether user testing is a genuine part of your process or an afterthought.
How to structure your answer: Walk through your validation method step by step, from what you're testing for to how you interpret the results.
Example answer
“I start by being clear on the specific usability problem the prototype is meant to fix, then set up a short testing session with people who match the target user profile. I watch how they use the product without prompting first, then ask direct questions about the problem area afterwards. I look for whether the original issue actually disappears in use, not just whether people say they like the new version, and I feed anything unexpected back into the next iteration.”