A recruiter at a civil firm reads your resume in a specific order: license status first, software second, project scope third. If "PE" isn't visible in the top third of the page, or your Civil 3D experience is buried in a skills list at the bottom, you lose the seven-second scan even when your project history is stronger than every other candidate's.

This page shows you a complete civil engineer resume example, then breaks down why each section works: how to present a Professional Engineer (PE) license so both the applicant tracking system (ATS) and the human find it, how to write project bullets with budgets and scope instead of duty statements, and which software keywords employers actually filter on. If you're pre-license, there's a full section on adapting the same structure as a project engineer or engineer in training (EIT).

Civil engineering resumes get screened on hard credentials before anyone reads a single bullet. That changes the structure. A marketing resume can open with a story; yours has to open with proof.

Here is the section order that works for most civil engineers, top to bottom:

Format matters less than civil engineers tend to think, but two rules are non-negotiable. Use a single-column, reverse chronological layout so ATS parsers read your work history in order. And submit as a PDF, always. A PDF locks your formatting; a Word file reflows on whatever machine opens it, which is how a clean resume arrives at the recruiter's desk with orphaned bullets and a broken header.

On length: one page is right up to roughly five years of experience. Past that, a licensed engineer with a real project list earns a second page, and cutting to one usually means cutting the scope details that get you hired. There's a fuller breakdown by experience level in should a resume be one page or two.

The example below is built for the most common mid-career situation: a licensed PE with several years across design and construction phases, applying to a consulting firm. Notice three things as you read it. The PE credential appears in the name line, the summary, and the licenses section, so no screening pass can miss it. Every project bullet carries a number that establishes scale. And the software section reads like a design team's actual toolbox, not a keyword dump.

What to lift from this example, even if your discipline differs: the bullets are project-shaped, not task-shaped. "Designed grading and drainage for a $14M, 42-acre mixed-use site" tells a hiring manager your level of responsibility in one line. "Responsible for grading and drainage design" tells them nothing they can't get from your job title. Scope numbers are the fastest credibility signal in this field because every reviewer has managed a budget and knows exactly what a $14M site involves.

What to change: the discipline-specific nouns. A transportation engineer swaps site grading for corridor design, signal warrants, and MUTCD compliance. A water resources engineer leads with hydraulic modeling, NPDES permitting, and floodplain analysis. The skeleton stays; the vocabulary is yours.

If you're a project engineer or EIT without a license yet, don't copy the PE resume and hope nobody notices the gap. Own the timeline instead. The adaptation is four moves:

One trap to avoid: inflating field roles into design roles. If your two years were mostly construction administration, say that with pride and precision. Firms need engineers who have watched their designs get built, and "resolved 40+ field conflicts between design drawings and existing utilities" is a stronger bullet than a vague claim to design work you supported from a distance.

Civil engineering is one of the most software-gated disciplines in the ATS. Recruiters at consulting firms routinely filter candidate pools on named tools before a human reads anything, and the tools they filter on are predictable. Civil 3D dominates private-sector and land development postings. MicroStation and OpenRoads show up heavily in DOT and public infrastructure work, because most state transportation departments standardized on Bentley products years ago. Scheduling tools, Primavera P6 above all, appear constantly in construction management and heavy civil postings.

The practical consequence: which tools you name, and where, should follow the job you're applying to, not the full list of everything you've ever opened. A land development posting that names Civil 3D three times wants Civil 3D in your summary and your bullets, not just your skills list. A DOT-adjacent posting wants MicroStation and the relevant state design manual named explicitly.

A tool in your skills list is a claim; a tool inside a bullet is evidence. "Produced grading plans and utility profiles in Civil 3D for a 200-lot subdivision" survives both the keyword filter and the human read. A bare "Civil 3D" in a skills box only survives the first.

The honest way to know which keywords a specific posting filters on is to check that posting, not a generic list. Paste the job into Roleframe and the fit report shows the exact keywords the posting asks for, which ones your resume already covers, and which are missing, along with an ATS score for that specific job. For the general method behind keyword matching, see ATS resume keywords: stop guessing and start matching.

Civil engineering hands you quantification for free. Every project you've touched has a construction value, a size, a schedule, and a regulatory framework. The engineers who struggle to quantify their resumes aren't missing numbers; they're leaving them in the project files instead of the bullets.

A reliable bullet formula for this field: action verb + deliverable + scope number + standard or outcome. Work through your project list and pull one number per project. The categories that land hardest:

Estimates are fine when exact figures are confidential or lost to time. "Approximately $10M" and "40+ acres" are honest and specific. What you must be able to do is defend every number in an interview, because a civil hiring manager will ask about the project behind the bullet, and they'll know if the answer doesn't match.

Licensure is the axis the entire civil career ladder rotates around, so treat it as a first-class resume section, never a footnote. A PE can stamp drawings, which changes what a firm can bill for your time; that's why postings so often require or prefer it, and why recruiters look for it before anything else.

How to present each stage:

Where the licenses section physically sits depends on the posting. If the job requires a PE, the section belongs in the top third of page one. If licensure is preferred rather than required and your project experience is the stronger card, the section can sit after experience. The placement logic is covered in more depth in where to put certifications on a resume.

Secondary credentials, PMP, LEED AP, OSHA 30, Envision SP, belong in the same section, below the engineering license. They matter most when the posting names them; otherwise they're supporting cast.

Engineers tend to write resumes the way they write technical memos: complete, accurate, and passive. "Was responsible for the design of stormwater management facilities in accordance with local requirements" is a true sentence that says almost nothing a reviewer can grade you on. The fix is usually surgical: a stronger verb, a scope number pulled forward, a named standard.

This is the kind of edit Remi, the career copilot inside Roleframe's editor, is built for. It reads the fit report for the job you attached, sees which keywords and findings apply to the bullet you're on, and proposes a rewrite as a word-by-word diff. You see exactly what would change, and nothing touches the document until you accept it. Remi doesn't write your resume for you, on purpose: a bullet claiming a $14M project you can't discuss is worse than a weak bullet, and every civil interview digs into the projects. You approve each change, so every line stays something you can defend when the hiring manager asks about the pump station.

The workflow that works: duplicate your base resume for the specific posting, read the fit report's keyword gaps, then work through the flagged bullets one at a time with Remi suggesting and you deciding. It's the fast version of tailoring without the generic-AI failure mode. The base-plus-variants system itself is worth understanding; see why you need a base resume and tailored versions.

Most civil engineers have a resume that's structurally fine and two years stale. The barrier to fixing it is retyping, and that barrier is gone. Upload your existing resume as a PDF to Roleframe and it comes back as editable blocks, roles and dates and bullets in place, inside a real drag-and-drop editor. The import runs a resume analysis automatically, so the first thing you see is your current document scored, with its weak sections named.

From there the updates are mechanical: add your newest projects with scope numbers, move your licenses section to match what your target postings require, drag sections into the order that argues your case, and export a clean PDF that matches the editor exactly. A free account includes an import, and the editor itself is free to use without an account.