Transportation / DOTA PE-licensed roadway designer, in-state, on a letting deadline
Why it stalls
A programme award creates demand for the same discipline across every consultant pursuing it, in the same state, at the same time. The licensed pool is small to begin with, and comity transfers between states take weeks the schedule does not have.
How we run it
- Establish first whether the role genuinely requires a seal or whether an experienced designer working under a licensed engineer satisfies the scope — this alone often multiplies the addressable pool.
- Confirm which state's licence is required, and whether a comity application would land inside the project timeline, before any out-of-state candidate is progressed.
- Work the brief across recruiters who cover that specific state's design standards and CADD environment, rather than transportation generally.
- Screen on plan production to the state's manual, not on years of experience.
CEI / InspectionState-certified inspectors, on site, at short notice
Why it stalls
Inspection requirements surface late, are fixed to a location, and are gated by certifications specific to the state's own qualification programme. A well-credentialed inspector from a neighbouring state frequently cannot be assigned without additional coursework.
How we run it
- Pin down the exact certifications the project requires — NICET subfield and level, ACI, IMSA, and the state's own programme — before sourcing begins.
- Treat the commuting radius as a hard constraint, and settle per diem and travel terms up front so they can be screened against rather than negotiated at offer.
- Draw on recruiters with existing regional inspection coverage, where knowing who is certified where is the entire value.
- Match the level to the decisions the role makes, not to a years-of-experience band.
StructuralA senior structural engineer where the qualified pool is countable
Why it stalls
At principal level in a narrow speciality — bridge load rating, complex retrofit — the population of genuinely qualified people in a region can be small enough to list by name, and most of them are not looking.
How we run it
- Map the market rather than source against it: identify the population, then approach it, because posting to a pool this size returns nothing.
- Be explicit that this is where a purely contingent model underperforms — the work is systematic identification, not sourcing volume.
- Handle the approach confidentially where the hire replaces an incumbent, or where the candidate is senior enough that discretion is a condition of engaging at all.
Government / ClearedCleared engineering roles where the clearance is the constraint
Why it stalls
An active clearance requirement narrows the pool severely, and sponsoring a new one converts a six-week hire into a multi-month project. The requirement is frequently added to specs that do not actually need it.
How we run it
- Challenge the requirement first: if the work does not need clearance at start, removing it is the single largest expansion of the pool available.
- Where it is genuinely required, treat active clearance as a hard filter and search only within it — a perfect candidate without one is not a candidate for that timeline.
- Build the full onboarding timeline, including background checks and project-specific training, into the offer conversation rather than discovering it afterwards.
About these playbooks
These describe our approach to each type of search, not specific engagements. We don't publish client names, placement figures or outcome metrics without the client's written approval — and until we have that approval, we'd rather show you the method than invent the results. Named case studies will appear here as clients agree to them.
Have a search that's stalled?
Tell us the discipline, the licensure and the location. We'll tell you honestly whether we can move it.
