.

How Not to Lose a Job Interview as an Engineer

December 20, 20232 min read

Many engineers lose their interviews…
Not because they lack enough skills, but because they don’t know how to present themselves properly.

The interview is not a knowledge test,
It’s a test of awareness — how you present yourself, how you talk about your skills,
And how you show that you're ready to add value to the team, not just learn from it.

Over the years, I’ve heard many phrases that were enough to cost their owners the job before it even began…

Here are 3 of them… and with each one, the smart alternative that makes the difference between a trainee and a professional engineer:


1️⃣ "I learn quickly… but I don’t know Revit."

It sounds like a nice sentence, but it conveys one message:
“I’m here to train, not to work.”

The smart alternative:
“I know the basics and have worked on an actual project where I used Revit practically.”

This way, you show that you’re ready and proactive, thinking with a problem-solving mindset, not just learning.


2️⃣ "I’ll take any job… at any salary."

The intention is good, but the impression? Weak.
The interview is not the place to ask for a "lifeline,"
It’s the place to showcase your value.

The smart alternative:
“I’m looking for an opportunity where I can add value and grow professionally.”

This way, you show that you're aware of your value and are thinking long-term.


3️⃣ "I prefer to work alone."

In engineering, a project does not succeed with just one person.
Someone who works alone might complete a task,
But someone who works with the team… completes an entire project.

The smart alternative:
“I can work efficiently alone, but I’m even stronger as part of a team.”

This way, you give a balanced image: independent, yet collaborative.


Conclusion:
In the interview, don’t sell yourself as someone “looking for an opportunity”…
Sell yourself as an engineer ready to add value.
Speak with confidence, tell your small stories that prove your skills,
And let every word speak about what you bring to the table, not what you’re missing.

Back to Blog