A grey-haired man in a meeting, resting his chin on his hand and smiling as he listens

How to choose your next engineering job: 7 questions to ask before you say yes

Most engineers know what it feels like to land in a role that does not quite fit. The technology is wrong, the work is too narrow, or the next step is impossible to see. Usually, the warning signs were there before you signed. You just did not ask the right questions.

Whether you are weighing a permanent job, a consulting assignment or your very first role, these seven questions help you judge an offer on what actually matters. Ask them in the interview, ask them of yourself, and compare the answers before you say yes.

The work itself

1. Does the role use what you are actually good at?

A job title says little. Two “Software Engineer” roles can mean feature work in a web app or driver development on custom hardware. Ask what a normal week looks like, which problems you would solve and which parts of the system you would own. Then compare that with what you do best and enjoy most.

Ask in the interview: “What will I spend most of my time on during the first six months?”

2. Will you learn something new?

The best roles combine what you already master with something you do not. That could be a new technology, a new industry or a new level of responsibility. If the answer is “more of the same”, the role may be comfortable but will not move your career forward.

Ask in the interview: “What would someone in this role learn in the first year that they could not learn elsewhere?”

3. What does the technical environment look like?

Tools and processes shape your daily work as much as the product does. Find out which languages, toolchains and test setups are used, how code is reviewed and how releases happen. In safety-critical industries, also ask which standards apply, since they affect how you design, document and verify your work.

Ask in the interview: “Can you walk me through how a change goes from idea to production?”

The people and the place

4. Who will you work with?

The team decides how much you learn and how much you enjoy the work. Ask who you would report to, how big the team is and how experienced the people around you are. If possible, meet someone from the team before you decide. A short conversation with a future colleague often says more than the whole interview.

Ask in the interview: “How does the team share knowledge and support someone who is new?”

5. Does the location and setup fit your life?

In engineering, much of the work happens on site, close to hardware, test rigs and production. That is often where you learn the most, but it also means commuting matters. Be honest with yourself about how far you can travel, whether you can relocate and how much flexibility you need in your working hours.

Ask in the interview: “How many days a week are on site, and how flexible are the working hours?”

The next step and the bigger picture

6. What happens after this role?

A good role leads somewhere. Ask what people in the same position have gone on to do, and how the company handles growth into senior, specialist or leadership roles. If nobody can answer, that is an answer too.

Ask in the interview: “Where are the people who had this role three years ago today?”

7. Do you believe in what you would be building?

Motivation lasts longer when the work means something to you. Ask what the product does, who uses it and what difference it makes. Engineers who care about the result, whether it is a safer vehicle, a more stable power grid or a faster network, tend to do their best work.

Ask in the interview: “What problem does this product solve, and for whom?”

Consultant or in-house?

The same seven questions apply whether you join a product company directly or work as a consultant. But the answers tend to look different.

  • Depth. In-house: deep knowledge of one product and codebase. Consultant: broad experience across products and companies.
  • Learning. In-house: grows with the product over time. Consultant: new technology and domains with each assignment.
  • Network. In-house: a strong network within one company. Consultant: a network across several companies and industries.
  • Change. In-house: requires changing employer. Consultant: possible between assignments, with the same employer.
  • Stability. In-house: often one long-term team. Consultant: teams change as assignments change.

Neither is better in general. Early in a career, consulting can give breadth quickly. Later, many engineers value the depth of owning one product. What matters is which answers fit you right now.

Looking for your next role?

We have open roles for engineers in Stockholm, Gothenburg and Mälardalen, across software, embedded, electronics, electrical, automation, mechanical engineering and project management. Bring your seven questions. We are happy to answer them.

See all open roles or send an open application.

FAQ

What questions should I ask in an engineering interview?

Focus on what you will actually do, what you will learn, who you will work with and what comes next. Asking how a change goes from idea to production is a quick way to understand the technical environment.

How do I compare two job offers?

Write down the answers to the seven questions for each offer side by side. Salary often ends up mattering less than the work, the team and the next step.

Is it a red flag if they cannot answer my questions?

Not always, especially in a first interview. But if nobody can describe a normal week or the next career step, ask to speak with someone from the team before you decide.

Should I choose consulting or an in-house role?

It depends on what you need right now. Consulting gives breadth and variety quickly, while an in-house role gives depth in one product. Both can be the right choice at different stages of a career.