Questions to Ask in an Engineering Interview
For mechanical, electrical, civil, manufacturing and process engineers deciding which questions to ask in an engineering interview, whether the person across the table is the hiring manager or the engineers on the panel. The list follows the order the conversation usually takes: the work itself, the tools and standards behind it, the team and manager, workload and deadlines, licensure and growth, and a few to close on. Each question has a note on what a good or a worrying answer sounds like, or what to ask next.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The work
Which project, product or unit would I be working on in my first six months?
Why ask it
A group that is ready for you can name it, and often the engineer you would work beside. If the answer is that it depends on what comes in, ask what the last new engineer was handed in their first month. That tells you whether you start on real design work or on drawing updates and backlog.
How much of a typical week would I spend at my desk, and how much on the plant floor, in the lab or on site?
Why ask it
Put it to one of the engineers on the panel as well as the manager, and ask about last week in particular. Rough proportions are enough: three days at the desk and two on the floor is a different job from five days in front of a CAD model. If the split is not the one you want, it is better to learn it now than in month three.
What does a project look like here from the first request to handover, and which stages would I be part of?
Why ask it
Listen for named stages: concept, detailed design, review, build or construction, commissioning, closeout. Seeing only the middle of that chain usually means learning less about why a design succeeds or fails. The stage where the last project ran long is worth hearing about too, since that is where the pressure sits.
How do design reviews work here, and who signs off before a design is released?
Why ask it
You want to hear who is in the room, at which stages, and whether a review can actually send a design back. A review held the day before release has little chance of changing anything. Ask one of the engineers what the last review changed in their own work.
What would you want me to have finished or taken over by the end of my first year?
Why ask it
Good answers are concrete: a unit you are the responsible engineer for, a product through validation, a set of drawings issued for construction. 'Up to speed' is not one of them, so ask what being up to speed would let you do alone.
Why is the position open, and what was the person before me working on?
Why ask it
Growth, a promotion and a resignation each leave a different desk behind. If someone left partway through a project, you are likely to inherit their files, their open issues and their promises to other departments. Without a written handover, the first months go to working out what was agreed.
What is the hardest technical problem the group is working on right now?
Why ask it
Best asked of the engineers on the panel, who will usually light up or wince, and either reaction is information. If confidentiality limits what they can say, ask what kind of problem it is, such as thermal, tolerance, soils or controls, and leave the details alone.
How much of the work is new design, and how much is keeping existing products, lines or assets running?
Why ask it
Sustaining work, such as fixing field problems, cutting cost and replacing obsolete parts, teaches a great deal, but it is a different job from a clean-sheet design. Postings tend to describe the new work. The share of last quarter that went to each is the number to get.
Would I be responsible for a whole product, unit or project, or for one part of a larger design?
Why ask it
On a big program you may spend a year on one bracket, one circuit or one drainage run and learn it very deeply. On a small team you may cover everything thinly. Say which of the two you want at this point in your career, since some groups can offer either.
Who is the customer for this group's work: an outside client, the production floor, or another team?
Why ask it
Whoever receives the work sets its rhythm. A paying client brings scope, fees and change orders. A plant brings whatever broke this morning. The follow-up is how much direct contact you would have with them, and how early in a project.
How much do cost targets shape a design here, and who decides when cost and performance pull apart?
Why ask it
In product and manufacturing work a design often has a cost target next to its specification, and on capital projects someone has to hold a budget. Find out whether the engineer sees those numbers or only hears about them when a quote comes back high. The trade-off they describe, a cheaper material or a dropped feature, shows whose opinion carried the day.
How is a design verified before it is built: analysis, prototype testing, an independent check, or all three?
Why ask it
The answer shows how far the group trusts calculation alone. Where there is testing, ask who writes the plan and who stands at the rig, since in some places that is the design engineer and in others a separate team. Where there is none, ask who checks the numbers.
After something I design is built or goes into production, do I get to see how it performs?
Why ask it
Seeing your own design in service is one of the quickest ways to get better at the next one. If designs go over the wall to a plant or a contractor and nobody hears back, ask how the group finds out about its mistakes. Site visits, commissioning, warranty returns or a call from the floor are the routes you hope to hear about.
What happened the last time a design problem was found late, after tooling was ordered or construction had started?
Why ask it
Most groups that have been around a while have one of these stories. Listen for where the conversation went afterwards: to the process that let the error through, or to the person whose name was on the drawing. Then ask what changed as a result.
What work is in the pipeline for the next year or two: new products, capital projects, or contracts already signed?
Why ask it
Engineering headcount tends to follow the pipeline. A funded capital plan, a signed backlog or a product roadmap with dates points to steady work. If the group is waiting on one bid or one approval, ask what happens to the team if it does not come.
Tools and standards
Which design and analysis software would I use every day, and how current is it?
Why ask it
Get the names of the CAD, simulation and calculation tools, then ask whether the group is partway through moving from one to another. If you have not worked in theirs, say so and ask how long other newcomers took to become productive. Running a few versions behind is not a warning by itself, but ask what holds the upgrade back.
Which codes and standards govern the work, and how do engineers get access to them?
Why ask it
These are the documents you would live in, and they differ by industry and by where the work is built or sold, so ask instead of assuming. Follow up on access. A current subscription that every engineer can open suggests the company pays for doing things properly, and a single old paper copy in someone's drawer suggests the opposite.
How are calculations and drawings checked before they leave the group?
Why ask it
Listen for a second person: a checker, a peer review, a lead who initials the calculation. Self-checking alone puts a lot on a new engineer. If they are able to show you a checked calculation or drawing, look at the marks on it: they tell you how seriously the check is taken.
Once a design is released, how does an engineering change get made?
Why ask it
A formal change process with a request, a reviewer and a record is slower and leaves a trail. An informal one is quick until two people revise the same part. Ask how long a simple drawing revision took the last time someone needed one.
Does the team have its own lab, shop or prototype capability, or does that work go outside?
Why ask it
In-house capability means you can try an idea this week and stand next to the person making it. Sending it out adds lead time and a purchase order to every question. If there is a shop, ask whether engineers are allowed on the equipment themselves.
What quality system or regulator does the group answer to, and how much of an engineer's week goes to documentation?
Why ask it
In regulated work, such as medical devices, aerospace, pressure equipment or public infrastructure, the paperwork is part of the engineering and not an extra. Ask an engineer on the panel for the real share of the week, then decide whether you can live with it.
How is safety handled for engineers on the floor or on site, and what training comes before I go out there?
Why ask it
Specifics are what you are after: an orientation, the protective equipment issued, who you shadow, and what you may not touch until you are signed off. Vague reassurance is the worrying version. Requirements vary by site and by country, so ask what applies at this one.
Where do old calculations, test reports and lessons learned live, and could a new engineer find them?
Why ask it
Groups repeat mistakes when the reason behind a design decision leaves with the person who made it. A searchable archive or a design history file means the reasoning outlasts the people. 'Ask whoever has been here longest' holds only while that person stays.
If I needed a test fixture, a software license or a prototype run, how would that get approved?
Why ask it
This shows how much money an engineer can commit without a meeting, and how long a good idea waits. Ask for the last such request and how many days it took. If the story involves three signatures for a small purchase, picture that on every project.
Team and manager
Would I report to an engineer in my own discipline, and if not, who would be the technical authority for my work?
Why ask it
A manager who came up through your discipline can review your technical work and argue for it. One from another discipline or from project management may be a fine boss, but then someone else has to judge whether your calculation is right. Get that person's name and how often you would see them.
How big is the engineering group, and how is it split by discipline and by years of experience?
Why ask it
Set the number of senior people against the number of junior ones. A group of recent graduates with one overloaded lead offers little coaching. A group where everyone has twenty years in offers plenty of coaching and perhaps few openings above you.
Would I be the only engineer in my discipline on the team?
Why ask it
Being the sole electrical engineer among mechanical ones, or the reverse, brings a lot of say and nobody to test your reasoning against. If that is the setup, ask where a second opinion would come from: another site, a consultant, or a corporate specialist.
Who would review my technical work in the first year, and how much time do they have for it?
Why ask it
If the manager names someone, ask to meet them before you decide, and find out how many others they already review. Feedback from someone carrying a full project load of their own tends to arrive late and in shorthand.
How does a new engineer learn the product, the plant or the local way of doing things in the first few months?
Why ask it
Some employers run a rotation through the shop floor, the lab and the field. Others put you on a live project beside a senior engineer. Either can work. A stack of procedures to read and nobody assigned to answer questions is the version to worry about.
How closely do engineers work with technicians, operators, machinists or contractors?
Why ask it
The people who build and run what you design know where it fails. Notice the tone of the answer: respect for the floor or the field crew usually means engineers are welcome there and hear the truth early. If the two sides barely speak, expect surprises at build time.
How much would I deal with suppliers, vendors or outside consultants, and who manages those relationships?
Why ask it
In some groups the engineer writes the specification and purchasing does the talking. In others you are on the phone with a foundry, a board house or a subconsultant every week, and may travel to approve first articles. Ask who has the authority to reject a supplier's part or a consultant's report, because that is where the pressure lands.
How does engineering get along with production, operations or construction when the two want different things?
Why ask it
Design wants it right and the people building it want it today, and that tension is part of the trade. What differs is whether it gets settled in a conversation or by escalation. Ask for the most recent disagreement and who made the call.
When an engineer says a design is not ready, or raises a safety concern, what happens to the schedule?
Why ask it
This is the one that shows what the place values under pressure, so ask for a time it happened. A story in which the date moved, or the scope was cut to hold it, is reassuring. If nobody can remember an engineer objecting, that is not.
Who has the last word on a technical decision when the engineers and the project manager disagree?
Why ask it
Some organizations give a chief engineer or technical authority the power to overrule the schedule. In others the project manager decides and engineering advises. Know which you are joining, because it decides how much your signature on a calculation means.
How long have the engineers on the team been here, and where did the last few who left go?
Why ask it
A mix of long-serving engineers and recent arrivals suggests people stay and the group still hires. If several left in one year for the same competitor, ask once what drew them, and leave it at that. A manager who knows where people went, and speaks well of them, has kept those relationships.
Workload
How many projects does each engineer carry at once, and how big are they?
Why ask it
Five six-week jobs and five multi-year capital projects are different loads, so get both numbers. Then ask how new work is handed out. If it goes to whoever has the fewest fires, find out how the manager knows who that is.
Where do project dates come from, and how much weight does an engineer's estimate carry?
Why ask it
Dates can come from a customer contract, a launch, a plant shutdown or a sales promise, with the estimate asked for afterwards. Ask how the last project's planned hours compared with the actual ones. A manager who knows that figure without looking it up has been watching the load.
What do the hours look like in an ordinary week, and what do they look like before a release, a shutdown or a bid deadline?
Why ask it
Ask for both, because many engineering jobs have a calm pace and a crunch pace. Then ask how many weeks of the past year were the second kind. A crunch that comes twice a year is something you can plan a life around. One that never ends is a staffing problem.
If a line goes down or something fails on site outside working hours, who gets the call?
Why ask it
Mostly one for manufacturing, process and plant roles, and for anyone supporting construction. Find out whether there is a rotation, and whether a phone call usually settles it or someone has to drive in. Then ask the person answering how many times it happened to them in the past three months.
How is extra time handled for engineers here: paid, given back as time off, or covered by the salary?
Why ask it
Practice differs by employer and by the law where you work, so this is one to ask and not assume. It sits more comfortably with a recruiter, or late in the process. Get the answer in the offer paperwork too if it matters to your decision.
How much travel does the role involve, and how long is a typical trip?
Why ask it
Day trips to a supplier, a week at a customer's plant and three months at a commissioning site all get described as 'some travel'. Get the number of nights away last year from someone doing the job now, and ask how much notice people usually have.
Do engineers here log hours against projects or clients, and is there a utilization target?
Why ask it
This matters most at consulting and design firms, where the billable share of your week is watched. If there is a target, ask what counts toward it and what happens to training, proposals and helping colleagues, which often do not. The answer shows how the firm treats time spent learning.
Which days does the work need me on site, and is there room to work from home on the others?
Why ask it
Hardware, plants and construction sites cannot be visited from a laptop, so the room for flexibility depends on the work. Ask what the team actually does, not what the policy allows. If the arrangement changed recently, ask whether it is settled.
Growth
Does the company support engineers working toward a professional license or chartership, and what does that support look like?
Why ask it
Support can mean exam fees, study time, a review course, or simply a manager who signs the forms on time. Ask how many engineers in the group are licensed and how many earned it while working here. In some industries few engineers hold a license at all, and you should know that before you count on it.
Would my work here be supervised by a licensed engineer in a way that counts toward my own license?
Why ask it
Licensing bodies set their own rules on qualifying experience and on who has to vouch for it, and those rules differ by state, country and discipline. Ask how it has gone for engineers on this team, then confirm with the board or institution you would apply to. An interviewer's summary is a starting point and not the last word.
Who stamps or seals the work that leaves this group, and when would I be expected to?
Why ask it
Signing as the engineer responsible carries professional weight, so the answer shows where accountability sits. If you already hold a license, ask whether using it is part of the role and how the company backs the engineers who sign. If nothing is sealed, ask who approves a design for release.
Is there a technical track for engineers who do not want to manage people, and who is furthest along it?
Why ask it
Plenty of employers describe a dual ladder. The test is whether a real person sits near the top of the technical side, with standing comparable to a manager's. What that person spends their week on shows whether the title carries real technical authority.
What does the step from this role to the next level require, and how long did it take the last engineer who made it?
Why ask it
The answer you want is a set of criteria you could work toward: leading a project, signing off other people's work, holding a license. 'It depends on business need' usually means an opening has to appear first. The real timeline of the last promotion is worth more than the official one.
Does the company pay for courses, conferences, society memberships or a graduate degree?
Why ask it
A budget on paper and a budget that gets spent are different things, so ask what someone in the group attended last year. Some tuition programs ask you to stay for a period or repay the money. Ask to read the terms before relying on one.
Has anyone here moved from design into manufacturing, field work or another discipline, and how did it come about?
Why ask it
A year in manufacturing or in the field tends to make a design engineer better at design. If someone has made a move like that, ask whether they or the company started it. If nobody can think of one, the job you take is likely the job you keep.
How is an engineer's performance judged here: projects delivered, hours billed, technical quality, or something else?
Why ask it
What gets measured is what the place really wants from its engineers. If schedule has a measure and quality has none, expect the pressure to run one way. Ask how the manager would tell a careful engineer from a slow one.
What can an engineer who has spent three years in this group do that they could not when they arrived?
Why ask it
An engineer on the panel can answer from experience. Concrete skills, such as running a commissioning, taking a part through tooling or leading a client meeting, mean the group develops people. If the answer is mostly about knowing the company's own systems, the experience may not travel well.
Closing
Is there a tool, a code or a kind of work in this job that you are not sure I have done enough of?
Why ask it
Asked this plainly, a panel will often name the gap: a software package you have not touched, an unfamiliar code, no time on a shop floor. You are still in the room, so give one example that bears on it or say how you would learn it, then move on.
Could I see the plant floor, the lab or a current project before a decision is made?
Why ask it
A walk-through shows the housekeeping, the age of the equipment and how people on the floor greet the engineers, none of which an interview room can. Ask early enough that a visitor pass and safety gear can be arranged. Confidentiality or site rules may limit what you see, and a polite no is not a bad sign.
What has kept you in this group, and what would you change about how engineering is done here?
Why ask it
Put it to an engineer, not the manager, and let them finish the first half before the second. Specifics, such as the problems, the people or the equipment, are convincing. The change they wish for is quite likely one you would wish for within a year.
Is there anything about this role that candidates tend to misjudge until they start?
Why ask it
It lets the panel raise what the posting left out: the amount of paperwork, the noise and heat of the floor, the travel, the age of the systems. Give them time to think before you say anything else. An interviewer who answers frankly is doing you a favor, so thank them for it.
Is there a technical exercise, a presentation or a site visit still to come, and when do you expect to decide?
Why ask it
Some engineering employers add a design problem, a portfolio review or a talk to the team, and knowing which lets you prepare the right thing. Get the date they expect to decide, and the name of the person to contact if a question comes up before then.
How to use your questions in an engineering interview
Practical guidance for the conversation itself
Before the interview
Find out who will be in the room
Engineering interviews often put a hiring manager beside two or three engineers, and sometimes someone from production, quality or project management. The manager knows why the role exists, how work is handed out and what promotion takes. The engineers know what a design review is really like, which software version is on the machines and what last week held. Pay rules, overtime and benefits usually belong to a recruiter or HR. Mark each question you plan to bring with the person it is for.
Read the posting for its nouns
The software, the standards, the product and the site named in the posting are your starting points. 'The posting mentions pressure vessel work. Which code edition are you designing to, and who checks the calculations?' gets further than asking what tools the team uses, and it shows you read what they wrote.
Work out what kind of employer it is
A consulting or design firm sells engineering hours, so the questions on utilization, clients, checking and who seals the work matter most there. A manufacturer makes a product, and the questions on new design against sustaining work, time on the floor and calls when a line stops come first. An owner, a utility or a public agency runs assets and often hires others to build them, which puts the capital plan, the standards and the work with contractors at the front. Sort your list that way before you go in.
Decide what you need from this job
An engineer two years out of school may need checked work and supervised experience more than anything else. Someone ten years in may care about design authority, budget and whether a technical track exists. Pick the three answers that would change your mind about the job and put those questions first. The rest are spares.
Look up the licensing rules yourself
If a professional license or chartership is part of your plan, read what the board or institution you would apply to requires before the interview. The rules on qualifying experience and supervision differ by place and by discipline. Knowing them lets you ask something exact, such as who would supervise your work and whether they have signed for anyone before.
In the room
Ask when the opening comes
If the manager starts by describing a project, a question from The work fits right there: which stage it is in, who the customer is, what you would pick up. The answer tells you what to emphasize for the rest of the hour, and the interview becomes a conversation between engineers.
Ask about the last job, not the procedure
'How do design reviews work?' gets the procedure. 'What did the last review change?' gets what happened. The same move works for the last late design problem, the last drawing revision and the last time someone was called in on a weekend.
Put one question to two people
Ask the manager and one of the engineers how a week divides between desk, floor and meetings, or how often the schedule gives way to a technical concern. Where the two accounts match, you can trust the picture. Where they differ, ask the engineer for an example and go by that.
Ask about the problem they set you
If the interview includes a design problem, a calculation or a walk through one of your past projects, ask afterwards whether the problem came from the group's own work. When it did, you have just seen a sample of the job, and you can ask how the real one was solved and what it took.
Respect what they cannot tell you
Unreleased products, client names and anything under a confidentiality agreement are off limits, and pressing makes you look careless with secrets. Ask about the kind of problem and the stage of the work. Hold yourself to the same rule when you describe projects at your current employer.
Use the tour if there is one
A walk through the plant, lab or shop is the best place for the questions under Tools and standards, because the equipment is in front of you. Ask ahead what to wear or bring for the floor. Watch how the people working there react to the engineers who are showing you around.
Reading the answers
Look for numbers and names
A named reviewer, a software version, a count of nights away last year or the date of the last promotion means the person has the facts. 'We have a strong review culture' tells you nothing until an example follows, so ask for one before you judge.
Listen hardest on schedule against safety
How a group talks about the time an engineer said 'not ready' is the clearest view you will get of what it does under pressure. An account with some discomfort in it, where a date moved and someone senior backed the engineer, counts for more than a statement that safety comes first.
Turn each answer into a week
After the interview, write out what an ordinary week in the job would hold: days on the floor, hours in reviews, share of documentation, projects in parallel. If you cannot fill it in, those are the questions for the next round or for the offer call.
Weigh it against where you are
Thin checking is a serious gap for a new graduate, who needs the corrections, and a different kind of concern for a senior engineer, who would be carrying the risk alone. Heavy travel suits some lives and not others. Judge each answer against what you need at this stage, not against an ideal employer.
Mistakes to avoid
Asking only what any candidate would ask
Culture and next steps are fine, but a panel of engineers notices the candidate who asks how calculations are checked or how a change gets made after release. Those questions show how you work as well as getting you an answer.
Opening with hours and overtime
The Workload questions matter and you should get them answered. Asked first, before anything about the work, they color how the rest is heard. Put them after the questions about projects and reviews, or take the policy ones to the recruiter.
Making a question sound like a verdict
Asking how current the software is, or what happened when a design problem surfaced late, can come across as criticism. Keep the tone curious and give a reason: 'I learned a lot from a late change at my last job, so I am interested in how you handle them here.'
Treating a licensing answer as settled
An interviewer can tell you how things have gone for engineers on the team. Only the body that grants the license can say what counts. Confirm anything your plans depend on with them, and ask for employer commitments, such as fees or study time, in writing.
Reading too much into the equipment
An old CAD release or a worn machine shop does not by itself mean weak engineering, and a new lab does not prove good practice. How work is checked, how changes are controlled and whether engineers hear back from the field say more. Ask about those before you judge the place by what is on the benches.