What this role’s resume is actually judged on — the language postings use, what a reviewer looks for in the first ten seconds, and the specific way Civil Engineer resumes go wrong.
A first pass takes seconds and is looking for three things. If they are not near the top, the rest of the page rarely gets read.
Most resumes fail one bullet at a time. The difference is almost always specificity — a number, a constraint, or a consequence.
Prepared structural drawings and supported site inspections.
Led redesign of pile layout after borings showed softer layer at 4m, avoiding a 6-week delay and £180k in contingency foundations.
Terms that recur in real postings for this role. They belong in the bullet that proves them, not in a list at the bottom — our own checker weights requirement coverage at 40% and raw keyword matching at 20%, and most serious systems make a similar trade.
A keyword you cannot defend in an interview is worse than a missing one. How the format checks work.
Civil resumes often read like a software inventory. Hiring managers scan for jurisdiction, structure type, dollar value, and what you signed off on site — without that, the page could belong to any graduate.
Site reality dominates: geotech surprises, coordination across disciplines, code and safety judgement, and how you communicate risk when the client wants certainty you do not have.
Drawings without outcomes
Component lists without system context
Generic 'process improvement' bullets
Listing technologies you have touched once
A resume that reads identically to a mid-level one
Abstraction with no anchor
Generic resume advice only goes so far — what matters is whether this resume covers this posting. Paste both and get requirement-by-requirement coverage, the keywords you are missing, and the format problems a parser will hit. The first check is free.