IEEE Essay Argues AI Redefines the Engineer as a Coordinator, Not a Task-Doer

An engineer can now ask an AI tool to search research and standards, generate design options, test them in simulation, and compare the results — but the final call on whether to proceed, argues a new essay published by IEEE Spectrum, "remains a human responsibility." The piece, titled "Systems Thinking Is Vital in the Age of AI," makes the case that AI is not shrinking engineering expertise. It is shifting where that expertise gets applied: from doing each technical step to deciding how people, machines, and specialists should work together.

That argument lands at a moment when engineering teams across energy, transportation, manufacturing, and medicine are folding generative and analytical AI into early-stage design work. The essay's core claim is that the profession's response should be structural — anchored in systems thinking and, notably, in IEEE itself as an institution setting common rules for human-machine collaboration.

What changes in the engineer's workflow?

Modern engineering projects increasingly combine human judgment with machine capability, the essay explains. The workflow it describes runs like this:

• An engineer defines the problem.
• An AI tool searches relevant research and technical standards.
• The tool generates design options, tests them in simulation, and compares results.
• The engineer brings the results to specialists who can judge what AI cannot — whether a design can be built safely, whether it fits a particular setting, and how it might affect users.
• A human makes the final decision on whether and how to move forward.

The practical effect, the essay says, is that AI can help single engineers complete early project steps that once required several people with different technical skills. The engineer's role therefore expands from performing each technical step to orchestrating the project — deciding how people, machines, and specialist knowledge combine.

Is AI replacing engineering disciplines?

The essay's answer is a firm no. Engineering has always been divided into disciplines — electrical, mechanical, civil, software, and others — "and for good reasons," the authors write. Those fields require deep knowledge that takes years to develop. AI does not replace that need. It changes how easily engineers can explore the parts of a problem that sit outside their own specialty.

The essay's example is a software engineer working on a medical device. AI can help that engineer review biomedical research, understand unfamiliar terms, analyze data, and build an early model. That does not make the engineer a physician or a biomedical expert, the essay stresses. It allows the engineer to ask better questions before working with the actual experts.

The same pattern holds in energy, transportation, manufacturing, and many other fields. A problem might begin as a software issue and quickly pull in hardware, safety measures, economics, human behavior, and regulations. The essay's prescription: engineers do not need to master every field. They need to recognize which expertise a problem requires and bring the right people and tools together.

Why does systems thinking matter more now?

This is the essay's central argument. Systems thinking requires looking at the whole problem — understanding how its parts affect one another, identifying constraints and failure points, and making trade-offs. AI adds a new layer to that discipline. Engineers must now decide:

• how the technical parts fit together,
• what work to give to AI,
• what a person must check,
• when a specialist should make a decision,
• and when the problem needs to be redefined.

"An engineer's value is not in knowing everything," the essay states. "It is in knowing how to frame the problem, how to ask the right questions, how to test the answers, and when another expert must lead the project."

The essay also pushes back against treating specifications as fixed. Technical challenges in engineering are seldom static, it argues. New insights emerge, objectives shift, unseen limitations surface, and the initial premise can prove flawed. Rather than rigidly following the starting specifications, an effective engineer adapts and refines the scope as understanding of the system deepens. Engineering, in this framing, is not only a body of technical knowledge but "a disciplined way of thinking about a project."

Where does human judgment stay in the loop?

The essay is blunt about AI's failure modes. AI can produce convincing answers even when its assumptions are weak. It can generate code that works in one test but fails in another. It can summarize research without understanding which evidence is strongest, or optimize a design for the wrong goal. "Such limits make human expertise more important, not less," the essay argues.

The division of labor it proposes is straightforward: machines are useful where speed, scale, search, pattern recognition, and data generation matter. People are essential where context, values, responsibility, and judgment matter. The challenge is deciding where each belongs.

The medical sensor example illustrates the layered review the essay has in mind. An AI system might generate several sensor designs and predict how each will perform. An engineer can test those predictions and reject designs that violate technical requirements. A clinician can determine whether the sensor can be realistically used. Patients and practitioners might reveal problems that neither the engineer nor the developer considered. "The final solution emerges from combining the perspectives," the essay concludes. The engineer, in this model, is still a builder and specialist — but increasingly also a coordinator of knowledge.

What role does the essay assign to IEEE?

The institutional call is the essay's most concrete proposal. IEEE's societies already bring together expertise across technologies, engineering education, technical standards, and other fields. That positions the organization, the essay argues, to help engineers work across specialties without weakening the value of specialization.

Specifically, the essay proposes that IEEE could create more communities organized around problems requiring several fields at once. The examples it names:

• trustworthy clinical AI,
• resilient infrastructure,
• energy reliability,
• scientific discovery,
• and safe autonomous systems.

An engineer could begin in a home discipline, then work with specialists from other IEEE communities as a project requires.

The essay also assigns IEEE a standards-setting role for human-machine collaboration itself. Engineers will need clear guidance on when AI-generated work must be checked, how uncertainty should be documented, when a specialist must make a decision, and who is responsible when a system blends human judgment with machine output. Those questions are becoming everyday engineering questions, the essay argues, and should not be left to each company or project manager to answer independently. A professional organization can provide common expectations that follow engineers as they move between jobs, industries, and technical fields.

What is the "unbound" engineer?

The essay closes by redefining the profession. AI does not make engineering disciplines less important, it argues — it makes the connections between them easier to use. Deep expertise gives engineers the foundation to judge what is sound. Systems thinking helps them see how the parts of a problem fit together. AI extends their ability to explore, test, and communicate across fields. Human judgment gives the work direction and responsibility.

"An engineer is not defined only by a job title or a fixed set of tasks," the essay states. "An engineer is someone trained to understand complex systems, define and redefine problems, bring together the knowledge and tools needed to solve them, test whether solutions work, and take responsibility for the outcome." That, the essay says, is what it means to be an "unbound" engineer.

The boundary-crossing and the machine assistance don't dissolve the profession's core. Deciding what problem is worth solving, what evidence is good enough, how the pieces fit together, and what to do when the answer is uncertain — that, the essay insists, remains human work. For IEEE, the immediate stakes are concrete: whether professional bodies will set shared rules for AI-assisted engineering before individual companies improvise their own.