What does an EdTech designer do that a general product designer does not?
An EdTech designer works for two audiences who want different things from the same product. A learner wants to get to the next task without friction. A teacher or administrator wants to see who is stuck, assign work and report upward. A general product designer tends to optimise one of those flows and leave the other as an afterthought.
The role also carries constraints that most consumer products never meet. Learners can be children, so reading level, tap targets and consent screens change. Schools buy on accessibility conformance. Many tools run inside a learning management system, where your interface is a frame in someone else’s page. We place designers who have worked under those conditions, not generalists who read about them.
What we vet for
We interview designers on real learning products and ask for the decisions behind the screens. Our checklist for this role:
- Learner flows. Onboarding, lesson, quiz, feedback and return visit, with attention to where motivation drops. The designer should be able to explain why a screen exists, not only how it looks.
- Teacher and admin dashboards. Class overviews, gradebooks, assignment setup and reports. These are dense, data-heavy screens, and the test is whether a busy teacher can find the one student who needs help.
- Accessibility at WCAG 2.2 AA. Contrast, focus order, keyboard paths through quizzes and drag-and-drop tasks, captions for video, screen reader labels for charts. The designer annotates these in the file, so engineers do not guess.
- Age-appropriate design. Different patterns for young children, teenagers and adult professionals: text size, vocabulary, gamification that motivates without manipulating, and parental consent flows.
- Design for embedded tools. A tool launched from a school LMS has limited width, inherits the host’s navigation and may not control its own login. We look for designers who have shipped inside that frame.
- Research with real learners. Moderated sessions, think-aloud recordings and a written synthesis, not opinions from the product team.
What do the first weeks look like?
A typical start for a designer joining an EdTech team:
- Audit the current learner journey and the teacher dashboard against WCAG 2.2 AA and list the blockers.
- Interview a handful of learners and teachers to confirm where people stall.
- Rebuild the one flow that matters most, often onboarding or the first lesson, as a testable prototype.
- Set up or tidy the component library so engineers build from named tokens and documented states.
- Hand off with annotated specs, including empty, loading, error and offline states.
Proof from a learning product
A UK-based seed edtech had a working backend and two competing ideas for its core learning flow. We ran a five-day design sprint, tested both flows in six moderated sessions and handed the winner to the client’s React developers as a component library. The client shipped to beta eight weeks later with a 40% reduction in learner drop-off compared to their earlier pilot. The tested flow also cut required clicks on the critical path from five to two. Read the full product design sprint case study.
Where design ends and engineering begins
Design decisions in EdTech often depend on how the product connects to school systems. For the engineering side of learning products, such as LTI 1.3 launches, rostering and student data privacy, see our edtech software development page. A designer on your team will work alongside those engineers, and we can supply both.
If your tool is a SaaS product sold to schools, the SaaS development page covers the product architecture, and our design system agency work covers the component library behind it.
How can you engage an EdTech designer?
| Model | Fits when | Typical setup |
|---|---|---|
| Dedicated designer | You have engineers and need a full-time design owner | Joins your standups and tools, works to your roadmap |
| Team extension | You have one designer and need research or a second pair of hands | Added to your existing design team |
| Fixed-scope project | You need a sprint, an audit or a redesign of one flow | Defined deliverables and a handoff |
Rates fall in the usual “$50 to $150 per hour” band and depend on seniority and scope. For longer engagements, see IT staff augmentation and hire a dedicated team. Designers start after a short intro call, once you have interviewed and approved the candidate. For other design roles, browse hire a designer.
