Where do engineering companies pull there interview questions from?

I am in ME, but have held interviews along with a panel and we all had our questions for the interviewer. I have not heard of anyone using a reference specific to interview questions, though I am sure you can find example questions online. As far as I know, we all have written our own questions. Every interviewer comes up with their questions differently though. For example, I ask questions based on what I expect you to do within the first few months (hand calcs, material selection, machining/drafting questions). It is not as important to me that you know the answers off the top of your head. What is important is that you can communicate what you know, and I want to see how you respond to guidance I am giving you. If you are completely lost, then you're probably not the right fit. If you can continue to communicate and work through the problem, I mean that's what engineering is and things will be looking good for you.

I have also seen other interviews ask strictly personal questions: Where do you see yourself in five years? What do you hope to learn/get out of this role? Etc. So it depends on the interviewer. If you are really interested in the job and show that you can work with the interviewer then you'll be fine. So be yourself and don't be afraid of not knowing the answer, just show what you know and your interest in the questions being asked.

I don't think there are any sources; however, there are books that cover questions that companies have asked in the past, particularly for computer and data science. See for some examples

You obviously have access to a computer, the internet, etc., so Google for interview questions

TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! faq731-376 forum1529 Entire Forum list

I've never had an interview where there was a series of questions. I haven't had one for nearly 2 decades. Interviews were conducted like a conversation where the person interviewing just asked a few technical questions in the conversation. I was employed as a senior engineer with Lavalin for about a decade, and nearly didn't get the job because I couldn't easily respond to the salary. The interviewer eventually asked if I would accept $???. The job was great... I was supposed to supervise the concrete work at the exit of the floodway...

I had worked out mileage charges and figured I could get a nice BMW sportscar with the mileage... They had a month introduction to the office work, which was completed in a couple of days... they found me helpful in the office that I stayed there and never got my BMW sportscar.

-----*****-----
So strange to see the singularity approaching while the entire planet is rapidly turning into a hellscape. -John Coates

-Dik

When I have been the interviewer, my questions depend on both the position being applied for and the level of expertise the applicant says they have. For someone in the beginning of their career, questions pertain to early career impetus (see gb2935's post above) and how the individual approaches a problem. Can they correctly identify what I'm asking? Can they get started down the correct path to a solution? Do they know when to ask for more information or more help in solving? Do they know the basic engineering that goes toward the solution (e.g., applying laws of physics to determine range of motion)? For higher-level applicants or positions, the questions get more complex - and may include topics related to developing information, disseminating information to coworkers, disseminating information to non-technical personnel, and - in some cases - how they approach teaching a subject to another individual.

The questions are going to vary widely - I don't think I've ever asked the same thing twice in 30 years, with one notable exception: "Can you give an example of an ethical dilemma you faced and how you resolved it?"

As to applying to a company like the one listed: expect questions related to both math and language (vocabulary, reading, writing) skills. Also questions on finding a "theoretical" solution to a "theoretical" programming issue. And finally, be prepared to face both a panel (2-8 individuals at once) and multiple interview sessions (usually with smaller groups) where you'll be questioned by some or all the members in quick succession - not always taking turns.

Converting energy to motion for more than half a century

My two favorite interviewees
> He came in and I asked him to calculate the input threshold of a simply TTL logic gate, which he couldn't answer, so I showed him how to do the calculation. At the end of the day, I mentioned this problem, and another engineer said, "Yeah, I asked him the same question and he couldn't do it, but I showed him how to." A 3rd engineer then offered, "Hey, I also him the same question and he still couldn't do it." We wound up hiring him anyway, because he was being laid off from a sister division; he didn't last long, though, since he was pretty clueless.

> I read this interviewee's resume and saw that they had experience with this simulation program I use a lot. "Great! Tell me what sorts of systems you simulated with the tool." They, blushed and said, "Oh, well, I didn't actually use the program, I only watched someone use it."

TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! faq731-376 forum1529 Entire Forum list