Skip to main content
Premier resource for practicing structural engineers
Go back to https://www.structuremag.org/articles Back
Article

Editorial: From Project Engineer to Project Manager

By Andrew Dolan, PE, SE
November 2, 2026

Most structural engineers measure early-career progress by the difficulty of the problems they can solve, and for good reason: a solid technical base is the foundation of a successful career in structural engineering. So when the first project management assignment arrives, it is easy to assume the hard part is over. It rarely is. Quite quickly, many new managers face challenges that are not technical at all, whether from the client or from a change in budget or schedule.

That experience is common across the profession. Engineers build careers by mastering codes, calculations, and increasingly complex structures, and then many are handed responsibility for scope, fee, schedule, clients, and staff, skills that receive far less formal attention than design. Technical proficiency does not automatically translate into project leadership. The move from project engineer to project manager is a change in responsibility, not simply a promotion, and it goes best when engineers approach it deliberately: by owning their growth, seeking out the right mentors, drawing on the collective experience of colleagues within their firm, and building a network of peers through structural engineering professional organizations and code development committees.

A project engineer’s success is measured by the quality of their own work. A project manager’s is measured by the performance of the entire team, and by whether the project succeeds as both a technical undertaking and a business commitment. An additional analysis, a revised framing layout, or a series of architectural changes may each seem manageable alone; together they can consume the project’s hours. A project that has used 70 percent of its fee but still needs substantial coordination and revisions is at risk, even if the drawings look nearly done. The question is not how much budget has been spent, but what it will take to finish.

Delegation is often one of the hardest adjustments. Holding on to every technical task feels efficient, but it limits the team’s capacity and denies junior engineers the experience they need to lead. Delegating well means matching work to experience, defining the deliverable, and scaling oversight to the task’s risk rather than the engineer’s title.

There is a reasonable case that project management is learned only by doing. Experience is irreplaceable, and no seminar substitutes for sitting across from a client whose project is over budget. That view deserves consideration. But learning purely by trial and error means learning on clients’ budgets and junior staff’s hours, and the cost shows up as overruns, rushed reviews, and burnout. Managing well is also not a retreat from technical engineering. It is an extension of it, applying the same discipline of defining the problem, weighing constraints, and making sound decisions to scope, schedule, and fee. A manager who protects the fee protects the hours needed for careful design and thorough review. Good project management is what makes good engineering possible on schedule and on budget.

No one hands a new project manager a curriculum. Firms can provide opportunities, and some have internal processes to support the transition, but engineers must own their development. That starts while they are still project engineers, by asking questions: how fees are developed, how client relationships are built, who outside the firm takes part in project meetings and why, and how the budget is tracked over the course of a project. The list goes on. Young engineers also need to seek out mentors, and the most productive mentoring relationships often begin because the less experienced engineer asks.

Support from outside the firm matters, too. Alongside strong mentors at my own firm, I have found that the Coalition of American Structural Engineers (CASE) offers something no single firm can: perspective from across the profession. Serving on the CASE Executive Committee has been a way to share knowledge about project management and to hear how structural engineers around the country handle the same challenges. Problems that feel unique, from scope creep to difficult client conversations, turn out to be shared across the profession, and others have already faced them and can pass along what they learned.

These lessons can become routine practice: confirm scope, budget, and assumptions at the start, track progress against remaining effort throughout, and record lessons at closeout. The benefits reach well beyond the bottom line: earlier intervention on budget problems, fewer late pushes that compromise quality, junior engineers who grow into leaders, and clients who trust that problems will be raised in time to solve them.

Firms can support this transition by treating project management as a skill to be developed, not a responsibility that arrives with seniority. But engineers making the move should not wait. Ask for the experience. Find the mentors. Use the resources CASE and its members have built, and, when ready, contribute to them. The best project managers do more than deliver sound designs; they create the conditions for their teams to do their best work. That is a skill worth learning on purpose.

About the Author

Andrew Dolan, PE, SE, is an Associate Partner at Gilsanz Murray Steficek in New York, where his work spans new construction and renovation, including several recent office-to-residential conversions. He is a member of the CASE Executive Committee and holds an MS in Civil Engineering from Virginia Tech and a BS in Civil Engineering from Manhattan College. He can be reached at andrew.dolan@gmsllp.com.