GoKawiilGitHub Next engineer Maggie defines the 'design engineer' role at Granola meetup
Speaking at a Granola-hosted meetup for design engineers, Maggie, a Staff Research Engineer at GitHub Next, described her career path through illustration, art direction, UX/UI and product design before landing in a hybrid research-engineer role. She argued that design engineering should not be reduced to flashy micro-interactions, but instead means designers who understand software's technical materials—state, data flow, databases, APIs, auth and latency—and who act as a bridge between design and engineering teams.
GoKawiil's interpretation of the reporting above, not reported fact.
Maggie's framing suggests a push within the industry to formalize 'design engineer' as a distinct discipline rather than a marketing label, which could influence how companies structure design and engineering teams. Her comment that AI agents make superficial micro-interaction work easier implies that the role's value may increasingly shift toward deeper technical fluency rather than surface-level polish. As a GitHub Next researcher, her views may also hint at how GitHub thinks about the future skillsets needed in software development.
- Maggie is a Staff Research Engineer at GitHub Next, GitHub's R&D lab, speaking at a design engineers' meetup linked to Granola.
- She defines 'design engineer' as someone deeply involved in software's technical material, not just visual micro-interactions.
- She argues design engineers should understand data flow, APIs and architecture, and serve as a bridge between design and engineering teams.
Source: maggieappleton.com, 2026-11-10
Published there as: “Fortune Telling and Speculative Design”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.