Back to main siteThe LibraryFree · no sign-up · by Orpheus Executive TrainingBook a session

Free library · guide · 15 minutes

Interview skills for engineers.

Engineers often go into interviews well qualified and come out having undersold themselves. They answer like an engineer, with all the detail and none of the story, and they say 'we' when the panel wants to hear 'I'. Interviewing is a skill you can prepare for, and this guide shows you how.

Why good engineers interview badly

  • Too much detail, no story. You explain the pump curve when the panel wanted to hear how you got the client to agree.
  • "We" instead of "I". Engineering is teamwork, so it feels natural to say "we". But the panel is hiring you, and they need to hear what you did.
  • No result. The answer stops at what you did, without saying what happened because of it.
  • Rambling. Without a structure, answers run to four or five minutes and the point gets lost.
  • Underselling. Many engineers find it uncomfortable to talk about their achievements, so they play them down.

Every one of these can be fixed with preparation and practice.

Kinds of interview you'll face

Graduate interviews and assessment centres

Often a mix of behavioural questions, a group exercise and sometimes a short presentation. They’re looking for potential, teamwork and how you communicate, more than experience.

Job interviews

Usually a mix of technical questions (how you would approach a problem) and behavioural questions (tell me about a time when…). Most people under-prepare for the behavioural half.

Internal promotion interviews

Harder than they look. The panel already knows you, so you have to show you are ready for the next level, not just good at your current one.

Chartered professional interview

Engineers Australia’s Chartered assessment includes a professional interview, where you talk through your experience and how it shows the required competencies. Check Engineers Australia’s current guidance for the details.

Tender and shortlist interviews

Your firm has been shortlisted and the team has to present and answer questions. It’s a team interview, and the contract depends on it.

The STAR method

Most interview questions for engineers are behavioural: "Tell me about a time when…". The STAR method gives you a simple structure that keeps the answer short and complete. Aim for about two minutes.

  • Situation: the context, in one or two sentences. "We were six weeks from commissioning a wastewater upgrade for a regional council."
  • Task: what you were responsible for. "I was the project engineer responsible for the mechanical installation."
  • Action: what you did, in the first person. This is the longest part. "I…, then I…, and I made sure…"
  • Result: what happened, with a number if you can. "We commissioned on time, and the council extended our contract."

Many careers advisers add a fifth step: what you learned, or what you would do differently. It shows self-awareness, and it is a natural way to finish.

Use your voice to help. Pause before you answer, so you sound considered rather than rushed. Bring your voice down at the end of the result, so it sounds certain and the panel knows you have finished.

Build your story bank

Prepare six to eight real stories before any interview. Each good story can answer several questions. A story about recovering a late project, for example, works for questions about pressure, leadership and problem solving. Write each one out below using STAR. Your stories are saved in this browser only.

Stories worth having: A project you delivered under pressure or against a tight deadline; A technical problem you solved, ideally one you can explain simply; A disagreement or conflict you handled well; A mistake you made, and what you changed afterwards; A time you led a team or a piece of work; A time you persuaded someone, such as a client, a manager or council; A time you raised a safety or quality concern; A difficult client or stakeholder.

Your answer, read aloud

25 common questions, and what they're really asking

Behind every interview question is something the panel wants to find out. Knowing what that is helps you choose the right story. Tick the ones you've prepared an answer for.

Opening

Technical judgement

Delivery and pressure

People and conflict

Leadership

Safety and ethics

Closing

"Tell me about yourself"

Almost every interview starts here, and it sets the tone. Keep it to about a minute, and use present, past, future. There's a full guide to this question, with examples for engineers and a builder. In short:

  1. Present: what you do now, in one or two sentences. "I'm a mechanical engineer with eight years in water and wastewater, currently managing upgrade projects for councils."
  2. Past: one or two highlights that are relevant to this job. "Before that, I spent three years on site, which is where I learned to…"
  3. Future: why this role is the logical next step. "I'm now looking to…, which is why this role caught my eye."

Questions to ask them

  • "What would success look like in this role after the first six months?"
  • "What's the biggest challenge the team is facing right now?"
  • "How do engineers here develop into project and leadership roles?"

Online interviews

Camera at eye level, face lit from the front, and look at the lens when you're making a key point. Have your story bank notes beside the screen, but don't read them. Test your sound before the call.

How to practise

  1. Write out your story bank above.
  2. Open the practice room, choose "An interview question", and answer a random question out loud, using one of your stories.
  3. Play it back. Was it about two minutes? Did you say "I"? Did you finish with a result?
  4. Do it again, until it sounds natural rather than memorised.
  5. Before a real interview, do a full mock interview with someone who will give you honest feedback.

Definitions

Behavioural question
A question about what you have done in the past, usually starting "Tell me about a time when…". The idea is that past behaviour is the best predictor of future behaviour.
STAR
Situation, Task, Action, Result. A structure for answering behavioural questions with a short, complete story.
Story bank
A prepared set of six to eight real examples from your work, each of which can answer several different questions.
Competency
A skill or behaviour the employer is assessing, such as teamwork, leadership, problem solving or communication.
References and further reading

Everything here is free. If you ever want one-on-one help with your own material, coaching is available →