"Achieved results" is the resume equivalent of saying "I worked hard." It's not untrue — it's just empty. A bullet that starts with achieved and ends without a number tells the recruiter: I did something, somewhere, at some undefined scale. On a civil engineering resume, your actual outputs are permits, drawing sets, and change order resolutions. You have the raw material to be specific. You're just not using it.
What weak 'achieved' bullets look like
Four patterns that appear on real civil engineering resumes. Each reads clean until you ask: what specifically did this person do?
"Achieved project goals on time" "Project goals" is a restatement of the job description. "On time" is an expectation, not an outcome. There's no deliverable, no owner, no scale — nothing a recruiter can anchor to.
"Achieved compliance with local building codes" Compliance is the floor. Meeting code is what keeps your stamp; it's not a differentiator. This bullet reads as "I did what I'm licensed to do."
"Achieved good communication with the GC team" "Good" is self-scored. Communication isn't the output — what happened downstream because of it? Write that instead.
"Achieved significant cost savings on materials" "Significant" is a hedge. If you can write "significant," you almost always know the number. A recruiter sees this and reads: the savings didn't hold up under scrutiny.
Stronger swaps — 15 synonyms for 'achieved'
| Synonym | When it fits | Resume bullet |
|---|---|---|
| Delivered | Project handoff, permit package, IFC drawing set | Delivered the bridge rehab permit package — 22 sealed sheets — to FDOT 6 days ahead of the submission deadline |
| Completed | Closed-phase work with a hard endpoint | Completed 19 stamped structural drawings for a 6-story podium with zero revision cycles from the EOR |
| Secured | Permits, variances, agency approvals | Secured a grading permit in 9 business days by front-loading drainage coordination with the county reviewer |
| Exceeded | Performance above a stated spec or owner target | Exceeded the owner's LEED Silver target — project certified Gold after revising 3 stormwater management details |
| Reduced | RFI backlog, punch list count, inspection failures | Reduced open RFI count from 52 to 5 in 7 weeks by embedding with the GC super during MEP rough-in |
| Cut | Budget compression — sharper and more decisive than reduced | Cut structural steel cost overruns by $214K by re-speccing beam profiles at the 95% CD review after fabricator over-quoted |
| Resolved | Design conflicts, code discrepancies, scope disputes | Resolved a 3-way grading conflict between the geotech, architect, and city reviewer in one redline session |
| Drove | Pushed an outcome through competing stakeholder priorities | Drove early TCO approval by coordinating final fire-life-safety sign-offs across 4 city departments simultaneously |
| Accelerated | Schedule compression with a specific calendar delta | Accelerated foundation pour schedule by 11 calendar days by pre-submitting revised compaction test protocols |
| Finalized | As-builts, closeout docs, issued-for-construction sets | Finalized as-built drawings within 5 days of demobilization on a $4.2M utility corridor project |
| Executed | Construction admin with a defined scope and outcome | Executed CA for a 38,000 SF warehouse, closing 61 RFIs with zero design-error change orders |
| Closed | Punch list items, open change orders, project audits | Closed 84 punch list items across 2 buildings in 10 days, enabling COs 3 days ahead of the TCO deadline |
| Passed | Inspections or third-party reviews with a clean result | Passed all 5 scheduled foundation inspections on a Type IA commercial structure without a single correction notice |
| Earned | PE licensure, certifications, formal recognition | Earned PE licensure on first attempt, then led the firm's next 4 stamped submissions independently |
| Surpassed | Metric above an established project benchmark | Surpassed owner's on-time delivery target — 96% vs the contracted 88% across 9 concurrent task orders |
Three rewrites
Three of the bad bullets above, rebuilt with numbers and civil engineering specifics.
Before: "Achieved project goals on time" After: Delivered the transportation corridor final design — 18 sealed sheets — to the FDOT project manager 6 days ahead of the permit submission deadline. "Delivered" names a concrete handoff. The FDOT reference anchors the client, and the sheet count grounds the scope.
Before: "Achieved compliance with local building codes" After: Secured building permits across 4 jurisdictions for a $9.7M ground-up retail development by front-loading code compliance reviews at the 60% DD milestone. Permits are the measurable output of compliance work. Four jurisdictions and a dollar figure signal real complexity — not just showing up.
Before: "Achieved significant cost savings on materials" After: Cut HDPE pipe costs by $118K on a highway drainage retrofit by rebidding under a revised BOM after the fabricator's first quote came in over budget. Dollar figure plus a named cause equals a verifiable claim. "Re-speccing" is more credible than "recommended changes." The same principle applies to other resume action verbs — specificity beats polish every time.
When 'achieved' is genuinely the right word
A few places where swapping it out actually weakens the bullet:
Paired with a named certification. "Achieved LEED Gold on a 210,000 SF office tower" works — the certification name is the quantification. Don't replace it.
When the outcome is binary. "Achieved full NEPA environmental review compliance" is fine. Either the review cleared or it didn't. No synonym sharpens that.
When the JD uses the word. If a posting says "achieved on-time delivery of 95%+," mirroring the verb helps you land in the ATS keyword pass. Mirror first, optimize second.
Mirror the JD's verbs before you swap
The instinct to replace every "achieved" is mostly right — but there's a step that comes before it.
Open the job description. Highlight every verb in the requirements section. If the posting uses "delivered" twice and "executed" once, use each of those words at least once on your resume. ATS systems keyword-match against the JD text. A synonym that reads stronger to a human can score zero in the machine pass if the JD's exact verb was "delivered" and you wrote "finalized."
Civil engineering JDs cluster around a small verb set: deliver, coordinate, execute, review, resolve. If your resume mirrors those, you clear the ATS filter. If you use synonyms the JD never uses — even strong ones — you can miss the bucket entirely.
One exception: if the JD uses "achieved" all the way through, don't mirror it back. "Achieved" in a job posting usually means a recruiter copied a generic template. The real keywords are the nouns — BIM coordination, AutoCAD, construction administration, permitting, RFI management. Those are the terms worth matching exactly. Verb swaps are a polish pass. Noun matching is the keyword strategy.
AI applies for you, you swipe. 40 free a day.
For more: managed synonym, optimized synonym, coordinated synonym, implemented synonym, trained synonym
Frequently Asked Questions
- What is another word for achieved on a resume?
- Delivered, secured, completed, and exceeded are all stronger synonyms for achieved on a resume. Each anchors to a concrete output — a permit, a drawing set, a cost figure — instead of a vague claim.
- Is 'achieved' a strong word for a resume?
- Only when paired with a specific, quantified result. 'Achieved cost savings' is weak. 'Cut structural steel costs by $214K' is strong. Without a metric, achieved signals that something happened without saying what or how much.
- What synonyms for achieved work best on civil engineering resumes?
- Delivered, secured, resolved, and cut map best to civil engineering outputs: project handoffs, permit approvals, RFI closures, and budget reductions. Each points to something a hiring manager can verify.