Practicing against a posting you actually found
This is the point where a general search turns into a specific target, a structural engineer opening at a city public works department, a water resources posting at a private consulting firm, a transportation role that names a state DOT project directly in the listing. Civil engineering postings tend to be specific rather than vague.
They name a sub-discipline, structural, geotechnical, transportation, water resources or environmental, they often name the software the team runs, Civil 3D, HEC-RAS, SAP2000, and they frequently reference the codes the work has to meet, AASHTO for transportation projects, ASCE 7 for structural loads, a local building code for site work.
Pasting that exact posting in produces a session built around what the listing actually asked for, not a generic civil engineering question set that could apply to any sub-discipline at all.
What gets pulled from your posting
The AI reads the requirements, responsibilities, and any named software, codes, or certifications in the posting before asking the first question, then builds the session around them.
A geotechnical posting built around soil investigation and foundation design gets questioned differently from a water resources posting centered on stormwater management and drainage design, and a transportation listing that names AASHTO gets asked about that standard directly instead of about code compliance in general terms.
The same posting text already feeds a resume-versus-posting match score elsewhere on the platform, and this interview type puts it to a different use, turning the listed requirements into actual spoken questions instead of only a number describing how closely a resume lines up on paper.
Scoring
How scoring applies to a posting-specific session
Technical carries real weight here since the questions come straight from the posting's own sub-discipline and code language rather than a generic prompt, and the written reasoning behind that score reflects how directly the answers addressed what the listing actually asked for.
Calibration floors and caps work the same way they do on every type, so an answer that mentions a named code or software tool without explaining how it actually shaped a design decision won't outscore a shorter answer that engages with it directly.
A candidate who name-drops ASCE 7 or Civil 3D from the posting without describing how either changed a real calculation or a real deliverable is exactly the kind of thin answer calibration is built to catch.
Frequently asked questions
Does a civil engineering posting need to come from the Intervieux job board to use this interview type?
No. Any posting text can be pasted in, whether it's an opening found on the job board, a public agency's own careers page, or a private firm's site, as long as the description text is available to work from.
Will it ask about a specific code or software named in the posting, like AASHTO or Civil 3D?
If the posting names it, the session builds questions around it directly rather than asking about code compliance or design software in general terms. That's what separates this type from a general or comprehensive session.
How is this different from practicing a resume-based interview instead?
This type reads a job posting and questions you against that role's requirements. A resume-based interview reads your own resume and questions you about your own past projects, a different document and a different angle on preparation.
Can I use this for a posting I haven't applied to yet?
Yes. Pasting in a posting's text works whether or not an application is already in, which makes it useful for deciding whether a specific structural, geotechnical, or water resources opening is worth pursuing at all.
Related pages
Practice against the exact posting you found
Paste in a real structural, geotechnical, transportation, or water resources opening and get questioned on that posting's own requirements before a recruiter calls.