AI Summary
5 min readMaggie Appleton, a design engineer currently prototyping at GitHub Next, came into tech from an unusual starting point: a degree in cultural anthropology. She studied how humans construct meaning and how flexible our worldviews are, then fell into web design and illustration to pay the bills. Over time, she moved from illustrating developer education content at Egghead to becoming the founding designer at the AI startup Elicit, where she learned product design end-to-end in a fast-moving, small-team environment. Her trajectory shaped a perspective on design that is deeply practical, grounded in user behavior, and unafraid of technical depth.
What a design engineer actually does
Appleton defines product design as problem solving with different materials: space, size, weight, color, motion, and — crucially — the nouns and verbs of a product. The hardest design challenges come when the nouns are abstract and new, as in developer tools or AI products. You cannot rely on familiar objects like "sneaker" or "cart." Instead, you need to invent coherent containers — like "session," "plan," or "skill" — that users can point at and manipulate without confusion. This is not a purely visual task; it requires understanding the shape of the backend data, the capabilities of the models, and the constraints of the system. Appleton distinguishes this from the kind of design that stops at p
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of The Pragmatic Engineer
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 (02:17) **From Anthropology to Design Engineering** - Maggie explains her unconventional path from studying cultural anthropology to becoming a design engineer
- 2 (09:19) **What a Designer Actually Does** - Maggie reframes product design as problem solving with different materials than engineering
- 3 (15:30) **Design Engineering vs Traditional Design** - Maggie distinguishes design engineering from purely visual design work
- 4 (17:30) **Tools of a Design Engineer** - Maggie walks through her current toolkit, from paper to agents
- 5 (19:59) **Prototyping Better Agent Planning Interfaces** - Maggie shows her notebook sketches for a new approach to agent planning
- 6 (26:28) **Why Pen and Paper Persist** - Maggie explains why physical sketching remains essential even in an AI-powered workflow
- 7 (30:46) **Woodworking as a Software Designer** - Maggie shares why she's learning woodworking and what it has in common with design engineering
+ Full timestamped outline available in the app
Show Notes
Brought to You By:
• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.
• O'Reilly Early Release: Scaling AI Adoption in Engineering – a free book on how to adopt and scale AI in a pragmatic way inside of engineering orgs. Complimentary, thanks to Antithesis.
• Entire – every agent prompt, tool call, stored in your repo, and mirrored.
—
What can everyone else learn from designers and design engineers? As it turns out, there’s plenty, as I discovered when one of the best design engineers in the industry, Maggie Appleton, came onto the Pragmatic Engineer Podcast. She’s a staff research engineer at GitHub Next, where she builds prototypes to explore how software engineers might collaborate with AI in new ways. Maggie is at the intersection of design, anthropology, and web development, and was the first designer hired by AI startup Elicit, and Lead Design engineer at AI startup, Normally.
Today’s episode is more visual than usual because Maggie brought her notebook along, so there are peeks inside its pages of prototypes and more:
We got into designers’ work and how their design processes are adapting to and changing with AI. We explore why Maggie starts projects with pens and notebooks, what distinguishes design engineers from other designers, and why understanding engineering constraints leads to better collaboration with engineers.
We also discuss how Maggie uses jigs to gain more control over AI agents, why human judgment and style still matter when models can generate designs, and how inconsistent AI capabilities can mislead us.
Timestamps
00:00 Intro
03:24 From anthropology to tech
10:18 What does a designer do?
18:23 How Maggie works
24:55 The case for planning with physical tools
31:53 Why Maggie is learning woodworking
33:13 Design engineers and engineering constraints
38:49 How Maggie uses Figma
40:30 Design at GitHub Next
45:12 How has AI changed design
50:37 When models design and why humans are still needed
53:30 UX and UI
58:29 Capability gaslighting
1:00:33 One Developer, Two Dozen Agents, Zero Alignment
1:07:21 Craft and AI tells
1:14:17 Visual gardens, home-cooked software, and barefoot developers
1:21:02 Advice for engineers and lessons from anthropology
1:2
More from this podcast
The Pragmatic Engineer →