Motion designer role-specific interview questions

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

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?