Product Designer

What That Looks Like in Practice

1. You start with the feeling you want the student to feel, then design backwards. Wireframes come last.
2. You work closely with product, engineering, and content — and you stay in the conversation well past the Figma handoff.
3. You design for people who might be using a smartphone seriously for the first time. Clarity isn't a nice-to-have; it's the job..
4. You think in systems. Tokens, components, motion, illustration — you want the craft to hold up as the product grows.
5. You'll work across mobile (our primary surface) and web.
6. You think about the whole emotional arc — how a student feels when they first arrive, when they bomb a mock test, when they go three days without studying, when something finally clicks. Each of those moments is a design problem.
7. You test your assumptions. User interviews, usability sessions, behavioral data — you know the difference between a hunch and a signal, and you chase both.