Non-Fiction

Engineering Title Generator

Engineering books range from bridge histories to circuit design manuals, and their titles split the same way. Generate titles that make a structure, system or failure sound worth reading about, or that state a technical scope exactly.

Ink and watercolor illustration: a delicate wooden bridge model spans a shallow workshop bench, its fine trusses mirrored in a puddle of spilled water
A delicate wooden bridge model spans a shallow workshop bench, its fine trusses mirrored in a puddle of spilled water

Optional: a few words about your story give sharper titles. 100 characters left.

A dozen to start with
  • Sample

    Load Path

    How forces travel through a building, for non-engineers

  • Sample

    Tolerances: Precision, Error and the Parts That Almost Fit

    A popular history of precision manufacturing

  • Sample

    Why Did the Culvert Fail?

    Case studies in small civil engineering failures

  • Sample

    Mud, Rebar and the Tunnel Under Harbor Street

    Building one city tunnel from bid to opening day

  • Sample

    Solder and Small Victories

    Hobby electronics projects for adult beginners

  • Sample

    Grace Pell and the Water Tower

    Biography of an early woman civil engineer

  • Sample

    Spec It Twice

    Writing specifications that contractors can actually follow

  • Sample

    Bridges I Would Not Cross

    A bridge inspector's memoir of aging infrastructure

  • Sample

    The Physics of Potholes

    Pavement engineering explained through one city's roads

  • Sample

    Redundancy: Why Good Systems Have Backups

    Fail-safe design in aircraft, grids and hospitals

  • Sample

    Torque

    How car engines work, explained without the jargon

  • Sample

    Measure From the Datum

    Engineering drawing and dimensioning basics

The craft

Naming Engineering books: what works

Engineering combines science and math to solve problems. This genre covers various fields, providing insights into engineering.

Titles should encapsulate the ingenuity and complexity of engineering, focusing on technologies, achievements, or advancements.

  1. Ask why it stands or falls

    Popular engineering titles often promise to explain how something works or why it broke. Mario Salvadori's Why Buildings Stand Up and Matthys Levy and Salvadori's Why Buildings Fall Down are near-perfect pairs. A 'why' title promises answers a curious non-engineer wants.

  2. Name the great work

    Books about one project lead with the thing itself. David McCullough's The Great Bridge is the Brooklyn Bridge, and his The Path Between the Seas is the Panama Canal. If your structure is famous, use it; if not, use a vivid description and name it in the subtitle.

  3. Be exact in technical titles

    Practitioners want the scope, not a mood. The Art of Electronics by Paul Horowitz and Winfield Hill gets away with 'art' because 'electronics' pins it down. For a textbook, name the discipline, the subfield and the level.

  4. Keep jargon out of trade titles

    General readers bounce off acronyms and specialist terms. Mark Miodownik's Stuff Matters uses an everyday word for materials science and saves the detail for the subtitle. Translate the term the way you would for a friend at dinner.

On the shelf

Well-known Engineering titles

Titles that already work in this genre. Read them for shape and length: how many words, how much they give away, what they leave out.

TitleAuthorPublished
The Design of Everyday ThingsDon Norman1988
Structures: Or Why Things Don't Fall DownJ.E. Gordon1978
The Wright BrothersDavid McCullough2015
Skunk Works: A Personal Memoir of My Years at LockheedBen R. Rich1994
The Soul of a New MachineTracy Kidder1981
Ignition!: An Informal History of Liquid Rocket PropellantsJohn D. Clark1972
To Engineer Is Human: The Role of Failure in Successful DesignHenry Petroski1992
Elon Musk: Tesla, SpaceX, and the Quest for a Fantastic FutureAshlee Vance2015
The Innovators: How a Group of Hackers, Geniuses, and Geeks Created the Digital RevolutionWalter Isaacson2014
Steve JobsWalter Isaacson2011
The Code Book: The Science of Secrecy from Ancient Egypt to Quantum CryptographySimon Singh1999
Invention by Design: How Engineers Get from Thought to ThingHenry Petroski1996
The Mythical Man-Month: Essays on Software EngineeringFrederick P. Brooks Jr.1975
Lean In: Women, Work, and the Will to LeadSheryl Sandberg2013
The Art of Innovation: Lessons in Creativity from IDEO, America's Leading Design FirmTom Kelley2001
Clean Code: A Handbook of Agile Software CraftsmanshipRobert C. Martin2008
The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business WinGene Kim2013
Thing Explainer: Complicated Stuff in Simple WordsRandall Munroe2015
Make: Electronics: Learning Through DiscoveryCharles Platt2009
Where Good Ideas Come From: The Natural History of InnovationSteven Johnson2010
Non-Fiction

More Non-Fiction title generators

Or see the whole shelf: Non-Fiction title ideas.

Good to know

Questions about Engineering titles

Should a popular engineering book use technical terms in its title?

Rarely. One familiar term (bridge, engine, circuit, dam) helps, but specialist vocabulary narrows the audience to people who already know the subject. Use the subtitle to name the discipline for search.

How do engineering textbook titles differ from popular ones?

Textbook titles are descriptive and often include the subject, level and sometimes a lead author's name as the brand. Popular titles lead with a story, a question or a structure. The two rarely borrow from each other, and readers expect that.

Is the project's name a good title for a book about one build?

If the project is well known, yes, because people search for it. If it's local or obscure, open with an image or stakes and put the project's name in the subtitle so the right readers still find it.

A title deserves a book.

Put it on a cover, write the first chapter under it, and see if it holds.

Plans from $9.99 a month. Cancel any time. Your words are always yours.