FIELD NOTES / 001

i optimize things for a living. nobody knows what that means.

Every company I’ve worked in had one person who quietly held the place together. The line ran smoother on their shift. The numbers were better and nobody could say exactly why. They weren’t the loudest engineer in the room. Half the time their job title made no sense to anyone outside the building.

That person is usually an industrial engineer. It’s the field I work in — and almost nobody, including the people who hire us, can tell you what it is.

So let me.

FIRST PRINCIPLES

engineering for the whole system, not the product

Most engineers build a thing. A bridge, a chip, an engine, an app. Industrial engineering doesn’t build the thing. It builds the system that builds the thing — and the system that moves it, stores it, sells it, and serves it.

The discipline is about a century old. It started on factory floors with a stopwatch and an almost rude question: why does this take so long? Time studies became motion studies. Motion studies became flow. Flow became the assembly line, then operations research, then Lean and Six Sigma. The tools got sharper. The question never changed.

Strip the jargon and IE is the engineering of how work happens. Less waste. Less waiting. Less variation. More flow. We treat a hospital, a warehouse, an airport, and a checkout line as the same kind of problem: a system with bottlenecks, and someone has to find them.

WHAT WE ACTUALLY ADD

everybody’s an industrial engineer — until you ask them why

Walk into any workplace and you’ll find people optimizing without knowing it. The operator who rearranged her station so the parts she reaches for most sit closest. The dispatcher who learned which route jams at four and quietly stopped using it. They’ve done the job a long time, and they’ve made it better — by feel, one small tweak at a time. That instinct is real, and it’s valuable.

Here’s the gap. They usually can’t tell you why it works. They can’t repeat it on the next line, and they can’t hand it to whoever replaces them. The improvement lives in one person’s head, and it walks out the door when they do.

That’s the line between doing the work well and engineering it. An industrial engineer brings structure and discipline to what was instinct — naming the steps, measuring the flow, finding the why, and writing it down so it holds after everyone goes home. We don’t replace the person who figured it out. We turn their hunch into a system that lasts.

THE PERSON

part engineer, part detective, part diplomat

An industrial engineer is a strange hybrid.

Part engineer: we run on data, math, and models. Queuing theory, statistics, optimization, simulation. The rigor is real.

Part detective: most of the job is figuring out why something is broken when everyone has already told you the wrong answer. You go to where the work happens. You watch. You ask why until it gets uncomfortable.

Part diplomat: here’s the part the curriculum doesn’t warn you about. You’re not changing a machine — you’re changing how people work, and people don’t love being told their process is the problem. The math is the easy half. Getting humans to adopt the better way is the actual job.

THE MANY DOORS

one degree, twenty job titles

This is why IE confuses people. We don’t have one title. We have all of them.

Walk out of an IE program and you might become a process engineer, a quality engineer, a continuous-improvement lead, a supply-chain analyst, an operations manager, a logistics planner, an operations-research analyst, a management consultant, a project manager, a human-factors specialist, a data analyst. Same toolkit. Twenty doors.

And it isn’t only factories anymore. Hospitals use us to cut patient wait times. Banks use us to unclog their back office. Airlines, e-commerce, software teams — anywhere work moves through steps, the work can be engineered.

NO FIXED LANE

the ambiguity is the point

Most engineering roles come with a spec. IE comes with a mess.

You get handed a system nobody fully understands and a vague goal — make it faster, cheaper, safer, better — and no instructions. That’s not a flaw in the job. That is the job. The openness is exactly what makes it hard, and exactly what makes it worth doing.

You can’t optimize what you don’t understand, so every assignment starts with learning a domain that isn’t yours. One quarter you’re learning how a foundry pours metal. The next, how an ER triages patients. You’re never the expert in the room on the content. You’re the expert on the system. Sitting in that gap — permanently a little uncomfortable — is the skill.

THE INVISIBLE TAX

good industrial engineering is invisible — that’s the problem

Here’s the part that stings.

When the work goes right, you can’t show anyone. No launch, no ribbon cutting, no incident. The line just runs. Costs fall. The thing that was about to break doesn’t. Our best days produce a silence — and silence is impossible to put on a slide.

Credit tends to diffuse. A working system benefits everyone who touches it, and that’s as it should be. The engineer who rebuilt the system tends to disappear into the result.

The hiring piece makes it worse. Most companies don’t know exactly what an IE does, so when they bring one in, they can’t connect the real problems to the person who could fix them. We get handed the narrowest version of the job instead: the time studies, the audit checklists, the Excel sheets nobody else wanted. They hire someone trained to see the whole system and ask them to watch one corner of it.

This isn’t a niche problem. The BLS counted roughly 351,000 industrial engineers in the U.S. as of 2024, with 11% growth projected through 2034 — well above average, median wage over a hundred grand. There’s no shortage of work, or of us. There’s a shortage of people who know what to do with us after the hire.

The thing that makes this hard to fix: our value is counterfactual. “We saved two million” is easy. “We avoided spending two million we were about to waste” is the truth, and it never lands as hard. You can’t photograph prevention.

Most people’s picture of industrial engineering is a guy with a stopwatch on a factory floor. That picture is about a hundred years old. This is my attempt to update it — through actual work, actual numbers, shown in the open.

So that’s what this is: field notes from inside the field. Real projects, real before-and-afters, real numbers, shown in the open. Not a pitch — a record of the work as it happens.

If you’ve ever been the person who quietly kept the system running, you already know the part that never makes it into a job description. I’ll write down the rest. Pull up a chair. →

notes & sources — current figures are cited to 2024–2026 data; the historical milestones are, by nature, older. The opinions are mine.

Recent (2024–2026):

Historical milestones (necessarily older):