# Technical AI interviews for mechanical, civil, and electrical engineers

A technical AI interview on Intervieux questions a non-software engineering candidate on discipline fundamentals out loud, a statics problem for a mechanical candidate, a circuit question for an electrical one, a load calculation for a civil one, through a spoken conversation with no code editor involved at any point.

That distinction matters more here than it does for a software candidate, since a mechanical, civil, or electrical engineer was never going to open a code editor during a real interview for that kind of role in the first place. A written design calculation or problem, when one comes up, belongs to a separate feature, technical challenges, not this type.

## What the conversation actually covers by discipline

A mechanical candidate might get asked to reason through a heat transfer problem with an unfamiliar boundary condition, thinking out loud about which assumption to make first. A civil candidate gets pushed on how a load path moves through a structure and where a safety factor would matter most. An electrical candidate explains how to size a circuit for a stated current requirement and defends the margin chosen. None of these live inside a code editor or a written challenge screen. They're spoken answers the AI interviewer follows up on the way a person running a technical phone screen would, asking why a second time when the first answer stays too general.

## What actually gets asked

Expect discipline-specific reasoning questions matched to whichever fundamentals apply, statics and materials for mechanical, structural and load analysis for civil, circuits and power for electrical, worked through verbally rather than solved on paper or typed into a screen. The interviewer pushes for the reasoning behind a chosen approach, not just a final number, and follows up harder where an explanation stays thin. Technical challenges, a separate feature that supports a written format for design-style problems alongside coding, debugging, and SQL, is where a problem gets worked through on the page, but that's a different session entirely.

## Why Technical carries more weight here than on other types

The Technical dimension gets the most scrutiny in a session built entirely around discipline reasoning, and its written reasoning explains specifically whether the approach taken was sound, not just whether a final number landed close to right. Calibration floors and caps matter more here than on a type with softer, more subjective content, since a fluent explanation that skips the actual physics or circuit logic behind a claim can otherwise sound convincing without being correct, and calibration is built to catch that gap. Communication still gets scored too, since explaining a load path or a circuit tolerance clearly out loud is a separate skill from getting the underlying calculation right in the first place.

## Frequently asked questions

### Do I have to type or write anything during a technical interview for an engineering role?

No. The technical interview type is a spoken conversation about discipline fundamentals. A written or numeric problem worked through on the page happens in the separate technical challenges feature, which supports a written format.

### Will the technical interview know which engineering discipline I'm in?

The technical type asks discipline-relevant fundamentals based on the conversation itself, a statics or circuits question, for example, though pairing it with a job-description session first sharpens how closely the questions track one specific posting.

### How is a technical interview different from a project walkthrough question?

A technical interview asks discipline fundamentals, a calculation or a concept explained out loud. A project walkthrough asks about a specific past project and the tradeoffs behind real decisions made on it.

### Can I make the technical interview harder with a specific interviewer personality?

Yes. Twelve interviewer personalities are available, including analytical and challenging options, paired with a formal or semi-formal style, for a tougher technical conversation.

## Related pages

- [Engineering interview questions](/interviews/engineering-other)
- [Technical AI interviews](/features/technical-interviews)
- [Browse open roles](/jobs)

## Practice discipline fundamentals out loud

Start a technical AI interview and work through statics, circuits, or structural reasoning verbally, then review a scored, dimension-by-dimension report.

Start practicing free: https://www.intervieux.ai/register · Hire with Intervieux: https://www.intervieux.ai/employers/signup