Motion designer interview questions

As asked

A mobile app moves users from a list of cards to a detailed view. How would you design motion that helps comprehension rather than just looking polished?

Sample answer outline

Use motion to preserve object continuity: the selected card can expand or hand off into the detail surface so users understand where they went. Keep timing short, easing natural, and hierarchy clear so the transition does not delay the task. Define what moves, what fades, and what remains stable, then specify behaviour for interruption and back navigation. Respect reduced-motion settings with an alternate transition that preserves orientation without large movement. Candidates who talk only about delight miss the core product motion goal: reducing cognitive load.

Expect these follow-ups

• How would you specify this for iOS, Android, and web engineers?
• What changes for a low-end device?
• How do you decide whether the motion is too slow?

As asked

A dashboard card can move from loading, to partial data, to complete, to error. How would you design the motion so users understand the state without being distracted?

Sample answer outline

A strong answer starts with information hierarchy, not animation taste. Loading should set expectation without pretending precision, partial data should reveal structure progressively, complete should settle quickly, and error should draw attention only enough to prompt recovery. The candidate should discuss duration, easing, stagger, interruption, and reduced-motion behaviour. Interviewers look for restraint: motion should clarify continuity and state, not decorate the interface. A common miss is designing one beautiful transition while ignoring rapid state changes, network retries, or users who prefer reduced motion.

Expect these follow-ups

• How would this change for a finance dashboard that updates every second?
• What is your rule of thumb for when motion should be removed?
• How do you hand this off so engineering does not guess timings?

As asked

Your team wants a dramatic parallax onboarding animation. How do you make the motion accessible without stripping all personality from the product?

Sample answer outline

Start by identifying motion risks: vestibular discomfort, attention capture, reduced readability, and delayed task completion. Honour system reduced-motion preferences and provide a lower-motion variant that keeps sequencing and hierarchy through opacity, scale restraint, or instant state changes. Avoid large z-axis movement, endless loops, and motion behind text. Test the experience with real users where possible and with implementation constraints in mind. A senior motion designer frames accessibility as part of the creative brief, not a compliance tax at the end.

Expect these follow-ups

• Which motion patterns are most likely to trigger discomfort?
• How would you document reduced-motion behaviour in a spec?
• What if brand stakeholders insist the full animation is essential?

As asked

You have designed a complex loading-to-success animation for a fintech product. What does a good engineering handoff include?

Sample answer outline

A good handoff includes the states, triggers, timing, easing curves, delays, interruption rules, and reduced-motion variant. It should specify which elements are layout-affecting and which should animate on transform or opacity for performance. Provide a prototype or exported values, but do not assume a video is enough for implementation. Include acceptance criteria so QA can tell whether the motion is correct. Candidates who understand handoff speak in implementation-ready constraints while still protecting the intention of the motion.

Expect these follow-ups

• How do you handle an engineer saying the animation is too expensive?
• What should happen if the success response arrives before the loading animation finishes?
• How would you QA this across devices?

As asked

Your product uses page transitions, animated charts, skeleton loaders, and celebratory effects. How do you design a reduced-motion strategy that still feels coherent?

Sample answer outline

Reduced motion is not the same as no feedback. Keep semantic state changes but swap spatial movement for opacity, colour, instant layout changes, or shorter fades where appropriate. The answer should reference OS-level prefers-reduced-motion, product settings, QA coverage, and documentation in the motion system. The candidate should separate essential motion that supports comprehension from ornamental motion that can be removed. A weak answer treats accessibility as a final toggle rather than a design constraint from the start.

Expect these follow-ups

• Which animations would you keep even in reduced-motion mode?
• How would you test this with users who experience vestibular discomfort?
• How do you prevent teams from bypassing the motion tokens?

As asked

How do you hand off a motion-heavy interaction so engineers can implement it accurately across web and mobile?

Sample answer outline

The answer should include a prototype, but not rely on the prototype alone. Specify states, triggers, timing, easing curves, delays, interruption rules, token names, and fallback behaviour for low-power devices and reduced-motion users. Good candidates explain how they collaborate with engineers early to check platform constraints rather than throwing over an After Effects file. They should also mention acceptance criteria and a review loop using real builds, because motion often changes once it meets real data. The common trap is specifying pixels and frames without explaining the purpose of the movement.

Expect these follow-ups

• What do you include in the spec for interrupted gestures?
• How do you handle different animation APIs on iOS, Android, and web?
• When would you accept an implementation that differs from your prototype?