Interaction Designer Resume
Skills & ATS Keywords

Aim for 28 to 40 specific tools, motion primitives, prototyping platforms, and handoff formats grouped into 6 or 7 labeled rows. Under 20 reads thin for any IxD role above Mid; over 50 reads like a feature dump. Every line in the Skills row should resurface inside at least one shipped prototype, motion library, or gesture system reference.

Figma (Smart Animate, interactive components, Variables), Framer, ProtoPie, Origami Studio, Rive, Lottie, After Effects, motion design, micro-interactions, prototyping, gesture, state machine, prefers-reduced-motion, WCAG 2.2, iOS HIG, Material Motion, and easing curves are the non-negotiables. Multi-platform motion parity (web, iOS, Android, visionOS), spring physics, and a motion library publish separate Senior and Staff files.

Interaction Designer (this page) owns how an interface behaves over time: prototypes at fidelity, motion choreography, gesture systems, state transitions, and the motion library that the rest of the design org reuses. UX/UI Designer ships static visual surfaces. Motion Designer sits closer to brand and marketing, with After Effects work that lives in launch films, not in the product. Product Designer is the PM-adjacent end-to-end role. If your week is a Framer prototype on Monday, a gesture spec on Wednesday, and a Lottie or Rive handoff to engineering on Friday, you are on the right page.

In 2026, at least one high-fidelity prototyping tool beyond Figma Smart Animate is expected. ProtoPie, Origami Studio, and Framer all clear the bar. Name the tool, the kind of interaction you built in it (multi-touch, sensor input, conditional logic, state graph), and the artifact you handed off (clickable prototype reviewed in a research session, a Rive file shipped to engineering, a spec doc). A file that names only Figma reads as a UX/UI Designer who occasionally animates, not as an IxD specialist.

Name the timing language (spring physics, cubic-bezier curves, duration band 120 to 480ms), the choreography pattern (staggered list reveal, shared element transition, focus pull on modal open), the platform conventions (iOS HIG motion, Material Motion, Apple TV or visionOS spatial), and the outcome (perceived speed up 18 percent, gesture discoverability tested at 87 percent). A line like "Owned the cross-fade and shared element transition system for a 6-tab consumer app, published 14 motion specs against the Material Motion baseline" reads at the Senior band.

Baseline at Mid and above in 2026. Hiring managers expect a prefers-reduced-motion fallback for every animated component, a duration ceiling on auto-playing motion, focus order intact across animated transitions, and a time-out tolerance for any sequence the user has to follow. Name the standard (WCAG 2.2 AA, success criterion 2.3.3 Animation from Interactions), the fallback strategy (instant state swap with no motion), and the audit cadence. Run the file through an ATS Checker to confirm the parse. A motion system that ignores reduced-motion reads as a 2020 portfolio in 2026.

At Senior and Staff bands, yes. The proof is the artifact: a Framer prototype that won design review against 2 alternatives, a Rive file consumed by iOS and Android with one source, a Lottie set published with naming and easing tokens, a motion spec doc that engineering shipped from. Quote the platform reach (iOS, Android, Web), the file count (28 Lottie assets, 14 Rive components), the consumer (6 squads, 4 surfaces), and the engineering pickup rate (shipped within 1 release of handoff). "Shipped 14 Rive components consumed by iOS and Android from one source, cut motion implementation time per surface by 40 percent" beats "designed micro-interactions" copy.