A site development job and a bridge design job can both be called "Civil Engineer II," but they need different civil engineer resume keywords. This guide shows you how to pick the right terms for your discipline, where to put them on your resume, and how to back each one up with real project details.

Getting ghosted on Civil Engineer applications?

It usually comes down to missing keywords. Scan your resume against your target job description to find exactly what the ATS expects you to have.

Find my missing keywords
ATS Keywords Score card showing a 92 percent score and passing ATS screening

Start With the Posting, Not a Generic List

Civil engineering is a broad field, so a generic keyword list is a weak place to start. A municipal water utility, a state DOT consultant, and a structural firm designing parking garages all use different words for the work they need done.

When I recruited for engineering roles, the first thing I did with a new posting was mark it in three colors: software, licensure, and project type. A posting for a land development engineer would be full of "grading," "Civil 3D," "stormwater," and "entitlements." A transportation posting from a DOT consultant would say "MicroStation," "OpenRoads," "AASHTO," and "PS&E." Those two resumes had almost no keywords in common, even though both candidates had the same degree.

Before you edit anything, read two or three postings for the job you want and write down:

  • Software named more than once (Civil 3D, HEC-RAS, SAP2000, and so on)
  • License or certification wording (PE, EIT, "PE within 12 months," "FE required")
  • Project types (roadway, utilities, retaining walls, subdivisions, treatment plants)
  • Standards and agencies (AASHTO, ACI 318, ASCE 7, NPDES, a named state DOT)
  • Project phases (design, permitting, bidding, construction administration)

Terms that repeat across all three postings belong in your skills section. Terms that show up in just one posting go into the version of your resume you send to that employer.

Keywords by Discipline

The table below groups common civil engineer core competencies by specialty. You don't need all of them. Pick the column closest to your work and the jobs you're targeting.

DisciplineTechnical keywordsStandards and regulationsTypical software
Land development / site civilSite grading, stormwater management, erosion and sediment control, utility layout, site plans, subdivision designSWPPP, NPDES, local stormwater manual, ADAAutoCAD Civil 3D, HydroCAD, Bluebeam
TransportationRoadway geometry, horizontal and vertical alignment, traffic control plans, intersection design, pavement design, PS&EAASHTO Green Book, MUTCD, state DOT standardsMicroStation, OpenRoads Designer, Synchro, AutoTURN
Water resourcesHydrologic and hydraulic modeling, floodplain analysis, culvert design, detention design, water distribution, sanitary sewerFEMA, NPDES, TR-55HEC-RAS, HEC-HMS, WaterCAD, SewerGEMS, SWMM
StructuralStructural analysis, steel and concrete design, foundation design, load calculations, seismic design, retaining wallsACI 318, AISC 360, ASCE 7, IBC, AASHTO LRFDSAP2000, ETABS, RISA, Revit, Tekla
GeotechnicalSubsurface investigation, slope stability, settlement analysis, bearing capacity, soil classificationASTM, USCSPLAXIS, gINT, Slide, LPILE
Construction / fieldConstruction observation, inspection, quantity takeoff, submittals, RFIs, change orders, QA/QCOSHA, project specificationsProcore, Primavera P6, MS Project

A note for structural civil engineers

Structural engineer resume keywords tend to be the most specific. Hiring managers at structural firms often look for the material (steel, concrete, wood, masonry), the building type (mid-rise residential, industrial, bridges), and the code edition. "Designed steel moment frames per AISC 360 and ASCE 7-16" tells a reader much more than "structural design experience." If you've worked on bridges, say so directly, because bridge work and building work use different codes and are often hired separately.

Licensure Keywords Need Exact Wording

Keywords for professional engineers deserve their own section, because this is where small wording choices matter most.

Recruiters and hiring managers often search or filter by license status. The problem is that the same status can be written several ways: EIT, EI, Engineer in Training, Engineer Intern, "FE passed." Different states use different terms. A few years ago I had a search open for an EIT, and one strong candidate only appeared when I searched "Fundamentals of Engineering," because her resume said "Passed FE exam, 2021" and nothing else. After that I always searched three or four variations, but you can't count on every reviewer doing the same.

A safe approach is to include both the abbreviation and the full name once:

  • Professional Engineer (PE), Texas, License No. XXXXX (or "active PE license, Texas")
  • Engineer in Training (EIT), North Carolina; passed FE Civil exam, 2023
  • PE eligible, expected [month/year] if you have enough experience and plan to test soon

If you hold a PE in more than one state, list each one. Employers doing work across state lines care about this, and a posting that says "PE in Florida or ability to obtain via comity" is looking for exactly that detail.

Other certifications that show up in civil postings include PMP, ENV SP (Envision), CFM (Certified Floodplain Manager), OSHA 30, and state-specific stormwater or erosion control inspector certificates. Include them if you have them and they're relevant. A CFM matters a lot for a floodplain job and very little for a steel design job.

Civil Engineering Software Skills: Be Precise

Software is often the most searchable part of a civil resume, and it's also where resumes get vague. "Proficient in CAD" doesn't tell anyone much. "AutoCAD Civil 3D (grading, corridors, pipe networks)" does.

Some practical rules:

Use the full product name at least once. Write "AutoCAD Civil 3D," not only "C3D." Write "OpenRoads Designer," not only "ORD." You can use the short form later.

Watch the spelling variants. I've seen "Civil3D," "Civil 3-D," and "Civil 3D" on resumes for the same role. Match the posting's spelling.

Show depth, not only names. A list of 20 programs looks like you've opened each one once. Five programs with the tasks you did in them are more believable.

Separate design tools from general tools. Microsoft Excel and Bluebeam Revu are useful, but they shouldn't sit on the same line as HEC-RAS if HEC-RAS is what the job is about.

One more point for transportation engineers. Many DOTs work in the Bentley environment (MicroStation, OpenRoads), while private land development firms usually work in Autodesk (Civil 3D). If you're moving between the two, list both and be honest about which one you know better. Hiring managers often ask about this directly in a phone screen.

Project Management Keywords by Project Stage

Civil engineering project management keywords make the most sense when you connect them to the project lifecycle. This also helps you place them in the right bullets.

Planning and design
Feasibility studies, alternatives analysis, preliminary design, 30/60/90% plan submittals, design criteria, cost estimates, engineer's estimate

Permitting and approvals
Permit applications, agency coordination, stormwater permits, right-of-way coordination, utility coordination, public meetings, plan review comments

Bidding
Bid documents, technical specifications, PS&E packages, bid tabulation, addenda

Construction
Construction administration, submittal review, RFIs, change orders, pay applications, field observation, punch lists, as-built drawings

Project control
Budget tracking, schedule management, scope, client communication, QA/QC, subconsultant management

If you're mid-career and moving toward a project engineer or project manager role, these words show that step. "Managed 60% and 90% submittals for a $4.2M roadway widening, including responses to 140 DOT review comments" says more about your readiness than "strong project management skills."

Civil Engineer Action Verbs, With Before and After Examples

Verbs matter because they show what you did on a team project. Civil projects usually involve a lot of people, and "worked on" or "assisted with" hides your part.

Here are verbs that fit civil work well:

Design and analysisDocuments and permitsField and constructionLeadership and coordination
DesignedPreparedInspectedCoordinated
ModeledDraftedObservedManaged
AnalyzedPermittedVerifiedLed
CalculatedSpecifiedResolvedMentored
SizedSubmittedDocumentedPresented
EvaluatedReviewedTestedNegotiated

Now some realistic rewrites.

Before: Assisted with stormwater design for commercial projects.
After: Designed stormwater detention and conveyance systems for 12 commercial sites (2 to 15 acres) using HydroCAD and Civil 3D pipe networks; prepared drainage reports for county approval.

Before: Responsible for construction oversight.
After: Provided construction administration for a 1.8-mile water main replacement: reviewed 45 submittals, answered RFIs, and tracked quantities for monthly pay applications.

Before: Did structural calculations for buildings.
After: Designed cast-in-place concrete foundations and steel gravity framing for 3 to 5 story mixed-use buildings per ACI 318 and AISC 360; modeled lateral systems in ETABS.

Before: Worked with traffic team on roadway projects.
After: Developed horizontal and vertical alignments and cross sections in OpenRoads Designer for a 2.4-mile rural highway widening; prepared traffic control plans following MUTCD.

In each "after" version, the keywords aren't added on top. They're part of a description of real work: the software, the standard, the project type, and the size. That is what makes them believable to a human reviewer.

Entry Level Civil Engineer Resume Keywords

If you're a new graduate, you probably don't have professional project numbers yet. You still have plenty to work with.

Licensure progress. "Passed FE Civil exam" or "FE exam scheduled for [month]" is one of the most useful lines on an entry-level civil resume. Many employers hire new graduates specifically on the EIT-to-PE track.

Capstone or senior design. Treat it like a project. Name the project type, the software, the standards, and your role. "Led grading and drainage design for a 20-acre senior design subdivision project; produced a 14-sheet plan set in Civil 3D" reads like work experience because it basically is.

Internships and co-ops. Even short internships often include quantity takeoffs, field inspection, survey support, or drafting. Use the specific words: "concrete cylinder testing," "compaction testing," "redlines," "as-built survey."

Coursework, used lightly. A short line listing relevant courses (Hydraulics, Steel Design, Geotechnical Engineering, Transportation Engineering) can help, especially if the posting asks for a specific area. Don't let it take more space than your projects.

Lab and field skills. ASTM testing procedures, total station, GPS survey equipment, and soil sampling are all real, searchable skills for construction materials testing and inspection roles.

One small thing I noticed when screening graduate applications: candidates who put "AutoCAD" in their skills list but never mentioned a plan set, drawing, or sheet anywhere else were almost always asked "What have you actually drawn in it?" on the first call. If you list a tool, have one line that shows you used it.

Where to Put Your Keywords

Placement affects how easily a recruiter can find what they're looking for, both when reading and when searching.

Headline and summary. Put your title, discipline, and license here. For example: "Civil Engineer (PE, Colorado) | Land Development and Stormwater | 7 Years in Site Design." That single line covers several important terms without any stuffing.

Skills section. Group it into short categories: Software, Design Areas, Standards, Licenses and Certifications. Groups are easier to scan than one long line of commas.

Experience bullets. This is where keywords get proof. Every important term in your skills section should appear at least once in a bullet that shows how you used it.

Project list (optional). Civil engineers with long project histories often add a "Selected Projects" section: project name, client type, value, and your role. This works well for consulting firms, where project experience is often reviewed closely.

A practical check: after editing, run your resume and the job posting through a tool like the Resume Keyword Scanner to see which terms from the posting are missing. Then decide one by one whether each missing term reflects work you've actually done. If it does, add it with context. If it doesn't, leave it out. An interviewer will ask about it.

Reading the Job Description for Hidden Keywords

Some of the most useful civil engineer job description keywords aren't in the "requirements" list. They're in the paragraph describing the team or the projects.

Take a typical posting line: "Our Denver office supports residential and commercial developers with site plans, grading, utilities, and drainage design through municipal approval."

That sentence tells you:

  • Client type: private developers
  • Project type: residential and commercial site work
  • Tasks: site plans, grading, utilities, drainage
  • Phase: design through approval, so permitting and agency coordination matter
  • Location: local jurisdiction experience in the Denver area could be relevant

If you've done municipal submittals in a nearby county, that's worth naming. "Prepared site development plans for approval in Arapahoe and Douglas counties" can matter more to this hiring manager than another software name.

For public sector postings, look for funding and compliance language: "federally funded projects," "Buy America," "Davis-Bacon," "NEPA." If you've worked on projects with these requirements, mention them. They signal familiarity with paperwork that takes time to learn.

Common Keyword Mistakes on Civil Resumes

Listing every discipline. A resume that claims structural, geotechnical, transportation, and water resources expertise can look unfocused. If you have broad experience, lead with the area that matches the job and mention the rest briefly.

Using only abbreviations. SWPPP, PS&E, H&H, and CA are clear to people in the field, but a recruiter without an engineering background may search the full terms. Spell out each one once.

Old code editions without context. Writing "ASCE 7-10" isn't wrong if that's what your projects used, but if the posting mentions current editions, make sure your recent work shows you've used them too.

Soft skills with nothing behind them. "Excellent communication skills" appears on a huge number of resumes. "Presented design alternatives at three public meetings for a city council street project" shows the same skill with evidence.

Copying the posting word for word. Matching key terms is useful. Copying whole sentences reads as copied, and experienced reviewers notice.

Quick Checklist Before You Apply

  • License status written with both abbreviation and full name
  • Top 3 to 5 software tools from the posting included, spelled the same way
  • Discipline and project types named in the summary
  • At least one relevant code or standard mentioned in a bullet
  • Project phases (design, permitting, construction) visible in your experience
  • Each skill in your skills section supported by at least one bullet
  • Numbers where you have them: acres, miles, project value, number of sheets or submittals
  • Abbreviations spelled out once

If you want a second check on formatting and structure, the ATS Resume Checker can flag layout issues such as tables or text boxes that some systems read poorly. If you're adapting one resume to several different postings, the AI Resume Optimizer can help you draft tailored versions faster, and you can then edit the details for accuracy.

FAQ

How many keywords should a civil engineer resume include?

There's no fixed number. A focused resume usually covers the main software, the license status, the project types, and the key standards from the posting. Relevance matters more than volume, since every term should connect to real experience.

Should I include software I used only in school?

Yes, if it's relevant and you can talk about it. For an entry-level role, "HEC-RAS (coursework, floodplain modeling project)" is honest and useful. As you gain professional experience, move it lower or remove it.

Do I need a separate resume for each discipline?

If you're applying across disciplines (for example, site civil and water resources), it helps to keep two base versions. The keywords, project examples, and summary will be different enough that one resume won't serve both well.

Is "PE eligible" worth listing?

It can be, especially for roles that say "PE required within 12 months" or "PE preferred." Include your expected exam date if you have one. Check your state board's experience rules first so the claim is accurate.

What are the most important keywords for a senior civil engineer?

At senior level, reviewers usually look for PE licensure, project management terms (budget, schedule, client management, QA/QC), mentoring or supervising staff, and the size and type of projects you've led. Technical keywords still matter, but leadership and responsibility carry more weight.