A project engineer is the person on a construction job who makes sure the paperwork and the building agree with each other. You'll spend part of the day in the site trailer chasing RFIs and submittals, and part of it in a hard hat checking that what's going up matches the drawings. This guide follows a day on a mid-size commercial building for a general contractor, which is where a lot of people start.
You get to the trailer before most of the trades do. First job is the RFI log in Procore: which questions the architect answered overnight, which ones are still sitting, and which ones the superintendent will ask you about before you've finished your coffee. You flag anything that's holding up work this week and send a polite nudge to the design team. Polite, but specific. "We need this by Thursday or the drywall crew stops" gets answered. "Just following up" doesn't.
The superintendent runs a short meeting with every trade foreman on site. You're there with the look-ahead schedule and the open issues list. The electrician says the ceiling grid is going in before his rough-in inspection. The mechanical foreman says his duct won't fit where the drawings put it. You write it all down, because half of it turns into an RFI or a change order by lunch.
Back at your desk you work through submittals. A steel fabricator's shop drawings, a door hardware package, a product data sheet for a roof membrane. You check each one against the spec section and the drawings in Bluebeam before it goes to the architect, because sending a wrong one wastes a whole review cycle. This is quiet, detailed work. Some people love it. Some people hate it.
You're walking the third floor with the superintendent when you find a plumbing sleeve cast in the wrong spot in the slab. Now the afternoon is gone. You photograph it, pull the drawings, call the plumber's project manager, and get the structural engineer on the phone to ask whether coring a new hole is allowed near that beam. Your job isn't to decide the fix. It's to get the right people answering the right question fast, and to write down who said what.
You write up the sleeve issue as an RFI with photos, log a potential change so cost is tracked from the start, and update the daily report. Then you check the submittal register, answer a subcontractor asking about a pay application backup, and send the project manager a short note on anything that could cost money or time. You leave when the log is clean enough that tomorrow won't start with a fire.
Nobody expects a new project engineer to know how to build a building. What your project manager watches is whether things you own stay closed. An RFI you sent should never go quiet. A submittal should never sit on your desk for a week. When a sub asks you something, they should hear back the same day, even if the answer is "I'm checking." Keep that up and you'll start getting handed a scope of your own, like the whole interiors package or the site work, and that's the real sign you're on your way to assistant project manager.
This is the most common route. Civil engineering, construction management and building science grads get hired straight out of school, often after an internship or co-op with the same contractor. Summer internships matter a lot here, so if you're still in school, chase one.
Some contractors hire you as a field engineer doing layout and quality checks, or as a project coordinator handling logs and closeout. Either one teaches you the paperwork and the site, and moving up to project engineer is a normal next step once you've shown you can run a log without being chased.
A carpenter or electrician who's good with plans and computers can make the jump, and they're often great at it because they already know how the work goes together. People from architecture or engineering firms cross over too, bringing a strong eye for drawings but needing to learn cost and schedule.
4% of openings are fully remote.
$85,200 – $135,000
Typical range in the 40 of the newest 60 postings that list pay.
Usually not in the licensed sense. At a general contractor, the title means you manage the technical side of the job: RFIs, submittals, drawings, schedules and change tracking. You don't stamp designs. A Professional Engineer license belongs to design roles, and rules differ by state, so check your state board if you want that route. Plenty of great project engineers have construction management degrees and no engineering license at all.
Procore is the one you'll see in a lot of postings, and Bluebeam Revu for marking up drawings is close behind. You should be comfortable in Excel for logs and quantity takeoffs. Knowing how to read a schedule in Microsoft Project or Primavera helps, and some teams use Autodesk Construction Cloud instead of Procore. You'll learn the specifics on the job, but walking in already fluent in Bluebeam makes a good first impression.
The usual next step is assistant project manager, then project manager, where you own the budget, the client relationship and the subcontracts. Some people move toward the field instead and become assistant superintendents. Others go to the owner's side, working as an owner's rep or in facilities for a hospital or university, where the hours tend to be steadier.
HeroApply applies to them for you, so you can keep doing the job you have.