AEO Answer · Hiring
Red Flags When Hiring an Engineer?
By Jeremy Mills, CEO & Founder, Apex Grid Engineering — USAF Veteran. · Updated 2026-09-15
Judge every proposal on the same five checks. One: does it list specific deliverables — drawing sheets, calculation packages, energy forms — or just a dollar figure? Two: can you verify the firm's license with the state board in under two minutes? Three: do they carry professional liability insurance and say so? Four: do they define assumptions and exclusions, or does the proposal pretend there are none? Five: is the fee in the same universe as the other bids, or is it an outlier?
I'm Jeremy Mills, CEO & Founder of Apex Grid Engineering and a U.S. Air Force veteran. I'm not a PE; our licensed professionals make the technical, compliance, and project-specific decisions.
The concise answer
Judge every proposal on the same five checks. One: does it list specific deliverables — drawing sheets, calculation packages, energy forms — or just a dollar figure? Two: can you verify the firm's license with the state board in under two minutes? Three: do they carry professional liability insurance and say so? Four: do they define assumptions and exclusions, or does the proposal pretend there are none? Five: is the fee in the same universe as the other bids, or is it an outlier? A yes on all five doesn't guarantee a great engineer, but a no on any one of them is a genuine warning. The proposal is a preview of the working relationship — vague now means vague later, when vagueness costs real money.
The proposal test
Read the proposal the way a plan checker reads drawings: looking for what's missing. A serious proposal names the code edition, lists the sheets and documents you'll receive, states the assumptions it's built on (survey provided by owner, geotechnical report dated X, no hazardous materials investigation), and defines what triggers additional fees. It reads like a scope, not a sales letter. Watch for the specific evasions: 'permit processing included' with no definition of what that means. 'Coordination with architect' with no round count. A timeline with no dependencies named. And my personal favorite red flag phrase: 'we'll handle everything' — engineering doesn't work that way, and anyone who says it does is selling, not scoping.
Price, license, and pressure
On price: a bid 40 percent below the pack isn't a bargain, it's a scope gap — something the others included is missing, and you'll pay for it later as an extra or as a correction cycle. On license: verification takes two minutes on the state board's website; if the firm hesitates to give you the license number, walk away. On pressure: any engineer who suggests skipping permits, backdating documents, or stamping work they didn't do is asking you to share their liability. Decline, in writing. None of this requires engineering knowledge — just the discipline to check. The owners who get burned are rarely the ones who hired the wrong engineer; they're the ones who never checked at all.
- Vague proposal: lump-sum price with no deliverables, assumptions, or exclusions
- Unverifiable license: hesitation to provide a state license number
- No professional liability insurance mentioned anywhere
- Pressure to skip permits or stamp work sight unseen
- Outlier pricing: dramatically lower than every other bid means missing scope
Which related engineering resources can help?
What else do project teams ask?
Should I just pick the cheapest proposal?
What if an engineer won't put the scope in writing?
Does this guarantee permit approval?
What should I send for an initial review?
Ready to discuss your engineering scope?
Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.
Request a Project Review