Engineers are interviewed by engineers. At a construction firm, an NGO building schools and boreholes, a water utility or a municipality, the panel usually has a senior engineer or project manager, someone from HR and often the programme or finance manager. The engineer scores your technical answers; the others score how clearly you explain, how honest you are about your limits, and whether they would trust you alone on a site 200 km from the office.
- Safety first. They want to hear that you would stop unsafe work even with the deadline a week away, and that you run a system: risk assessment, PPE, toolbox talks, near-miss reporting.
- Quality control and standards. Checks before work starts, inspections at each stage, tests (concrete cubes, slump, pipe pressure, compaction) and a signed record before the next stage begins.
- Project control. You can read and prepare a BoQ, measure progress against a schedule, certify payments only for work actually done, and report a delay early with options.
- Working with contractors and communities. Firm and in writing with contractors, respectful with village committees and elders, clear with unskilled labour hired locally.
- Software, truthfully. AutoCAD for drawings, Excel for quantities, EPANET for water networks, MS Project for schedules. Name only what you can use in front of them.
The process usually has three parts. First, a technical written test of 60 to 90 minutes: the concrete volume of a footing, the steel weight from a bar schedule, the pump head for a borehole, a short question on site safety. Second, a BoQ or drawing review: they hand you a bill with two planted mistakes, or a drawing where the beam sizes and the section disagree, and ask what you notice. Third, the panel, where at least one question is a site scenario. Bring your CV, your certificates and photos of your projects on your phone; a panel that sees a finished school believes the story.