Project Controller

Days tend to involve cost reports, schedule updates, earned value analysis, change order processing, and the steady reconciliation between the project plan and where it actually is. You might be loading a baseline schedule Monday, reviewing contractor invoices Tuesday, and presenting variance analyses on Friday. The work tends to live in Primavera P6, cost engineering software, Excel, and the project's reporting cadence.

The harder part is often the gap between what the schedule shows and what's really happening on the ground. Field progress, contractor optimism, and reporting lag can hide problems until they're large. Asking the right questions of project teams is a real skill. Variance across employers is real — federal and energy projects run heavy EVM; commercial construction can be more cost-focused and less formally controlled. Trend-spotting in weekly variances can be the early-warning system.

People who tend to thrive here are numerically rigorous, diplomatically firm, and comfortable being the person who flags bad news early. They tend to enjoy the satisfaction of catching a variance before it becomes a crisis. The trade-off can be the friction of being the messenger of cost overruns — project teams sometimes resent the truth-telling that the role requires.