Best books for Design Engineers

This list follows the work between design and code. It starts with usability and collaboration, so you can argue for changes with evidence. The middle books cover components, layout, interaction patterns and prototyping in the browser. The lead books are about performance and the network, which decide what an interaction can cost in production.

10 books in 3 stages, about 620 pages (at least 16 hours of reading). The notes are ours, with no ratings or sales claims.

See the full Design Engineer roadmap →Best courses for Design Engineers →

How to choose your books

A short method, so you read the right book for where you are instead of the longest list.

Find your stage

Getting started · 3 books
Usability, collaboration and accessibility: how people use screens, how design and engineering work together and what an interface must do for everyone.
Jump to this stage ↓
Doing the job · 5 books
Components and layout: CSS, component systems, interface patterns and prototyping that can be built and maintained.
Jump to this stage ↓
Senior and leading · 2 books
Performance and the browser: what a design costs in speed and network terms, and how senior design engineers set those budgets.
Jump to this stage ↓

If you are unsure, start one stage lower than you think. Books in a later stage assume the working knowledge the earlier ones give you.

Begin with one book

Our starting pick

Don't Make Me Think

by Steve Krug · 2014

It shows how people scan, guess and give up on a screen. The ideas are short to read and give you the language to argue for a design change with evidence.

See the book ↓

Then pick by your situation

Choose the next book by the problem in front of you, not by its place in the list.

If you are building your first component library
read Atomic Design (doing the job)
If you are fighting CSS and want to understand why it behaves the way it does
read CSS Secrets (doing the job)
If you need to make an interface accessible before it ships
read Accessibility For Everyone (getting started)

Set a time budget

Stage	Books	Pages	Reading	At 3 hrs a week
Getting started	3	≥ 220	≥ 6 hrs	≥ 2 wks
Doing the job	5	n/a	n/a	n/a
Senior and leading	2	≥ 400	≥ 10 hrs	≥ 3 wks
All 3 stages	10	≥ 620	≥ 16 hrs	≥ 5 wks

Treat this as a ceiling, not a target. Read one book at a time, apply it, then move on; read reference-style books in sections. Totals are approximate.

Judge any book before you buy it

Age
This list runs from 2007 (Sketching User Experiences) to 2017 (Accessibility For Everyone). Older books earn their place by teaching principles that do not change. For tools and platforms, buy the latest edition.
Level
Check the stage before the title. A book from a later stage will make sense only once you have faced the problems it solves.
Format
Some books suit reading start to finish; others work as references. Read the reference-style ones in sections, when a problem calls for them.
Fit
Ask what you will do differently the week after you finish. If you cannot answer, the book is for a different moment. Come back to it when the situation arrives.

Getting started

Usability, collaboration and accessibility: how people use screens, how design and engineering work together and what an interface must do for everyone.

Start here
Don't Make Me Think
by Steve Krug · 2014
~220 pages~6 hrs to read
The clearest short introduction to usability: how people scan, guess and give up on screens. It gives you the vocabulary for arguing a design change with evidence.
View book →
Lean UX
by Jeff Gothelf, Josh Seiden · 2016
How design and engineering work together in short cycles, with users testing early versions. It describes the working relationship this role depends on.
View book →
Accessibility For Everyone
by Laura Kalbag · 2017
A practical introduction to building accessible interfaces, covering semantics, colour, forms and motion. Read it before you build your first component for other teams.
View book →

Doing the job

Components and layout: CSS, component systems, interface patterns and prototyping that can be built and maintained.

CSS Secrets
by Lea Verou · 2015
Techniques for backgrounds, borders, shapes and effects that are harder than they look. It builds the layout and visual judgment a design engineer uses daily.
View book →
Atomic Design
by Brad Frost · 2016
A method for building interfaces from atoms, molecules and organisms, and for keeping components consistent across a product. The core mental model for component libraries.
View book →
Designing Interfaces
by Jenifer Tidwell · 2010
A catalogue of interface patterns with the reasoning behind each one. Useful when you need to decide which pattern a team should use before building it.
View book →
Sketching User Experiences
by Bill Buxton · 2007
How designers explore ideas through sketches and prototypes before committing to code. It sharpens the prototyping step of the job.
View book →
Responsive Web Design
by Ethan Marcotte · 2011
The foundation of designing layouts that adapt to different screens. Short enough to read in a weekend and still shapes how most design systems handle breakpoints.
View book →

Senior and leading

Performance and the browser: what a design costs in speed and network terms, and how senior design engineers set those budgets.

Designing for Performance
by Lara Callender Hogan · 2014
How speed affects the design decisions you make, and how to set and keep performance budgets. Leads use it to argue for the trade-offs that interaction work needs.
View book →
High Performance Browser Networking
by Ilya Grigorik · 2013
~400 pages~10 hrs to read
How the network and browser shape what users actually experience, from connection setup to image loading. Senior design engineers need this to judge what an animation or asset will cost.
View book →

Book links go to Amazon and are affiliate links. As an Amazon Associate I earn from qualifying purchases.

Frequently asked questions

Which book should a Design Engineer read first?

Don't Make Me Think by Steve Krug. It shows how people scan, guess and give up on a screen. The ideas are short to read and give you the language to argue for a design change with evidence.

Do I need to read all 10 books?

No. The list is a menu, not a syllabus. Find your stage (getting started: 3, doing the job: 5, senior and leading: 2), begin with one book (we suggest Don't Make Me Think), then pick the next book by the problem you are facing at work. Come back to the others when the situation they cover arrives.

How long does it take to read these books?

The 2 books with a known page count add up to about 620 pages, roughly 16 hours at 1.5 minutes a page. At three hours a week that is about 5 weeks; at six hours a week, about 3. The list is meant to be read over time, one book at a time, not in one run.

Are these books up to date?

They range from 2007 (Sketching User Experiences) to 2017 (Accessibility For Everyone). Older titles are included because they teach principles that have not changed; for tools and platforms, we favor recent editions. Check the edition before you buy.

Some links are affiliate links: we earn a small commission if you buy, at no cost to you. It does not change what we list.