Technical Interviews

A technical interview consists of a series of questions designed to test your technical knowledge in your major and your ability to solve problems. They can consist of coding challenges, word problems, peer discussions, design challenges, puzzles, or brain teasers.

Types of Technical Interviews:

There are usually two types of technical interviews:

  • The first type determines how well you know technology such as coding, software development, special algorithms, mapping, drawing in 2D vs. 3D, etc. and examines broad sets of technical skills.
  • The second type uncovers your problem-solving skills. The interviewer is looking at your approach to a problem, how you think through the issues to find a solution (not necessarily the most optimal solution).

Goal of the Technical Interview:

Demonstrate to the interviewer your technical skills and abilities, and how you solve real world problems in your field.

Should I Expect a Technical Interview, & When Should I Expect It?

  • If you are earning or have earned a degree in engineering or technology, or are applying for technical positions, expect to have technical interviews.
  • A combination of behavioral and technical questions are more common during first interviews. Technical questions are definitely part of later round or on-site interviews (because they are expensive).
  • Some employers will give homework in the form of programming or logic problems to do before the interview. This eliminates candidates before the technical interview.

How to Prepare for a Technical Interview:

  • Review the job description to highlight the key technical responsibilities and requirements of the position (software, hardware, testing, operating systems, circuits, areas of engineering knowledge, such as FEA, CFD, surveying, estimating, etc.).
  • Refresh on core principles and basics. Review relevant class notes. If the position calls for PHP developer skills or AutoCAD, and you want to refresh those skills, consider taking an online tutorial.
  • You may not have to be an expert in every technology listed but you should know the basics since many questions will not be specific in domain knowledge, but will focus on general principles.
  • Familiarize yourself with formal technical jargon and acronyms around the technology.
  • Study & practice answering (out loud) standard interview questions — as many variations as possible.
  • Prepare to use a whiteboard. Most programming is done on a computer, but most technical interviews do not use a computer. Practicing white boarding (and/or drawing things out on paper) is a key way to prepare and can make a big difference, especially if it doesn’t come naturally.
  • Be ready to discuss your projects, prior technical experiences and coursework in detail. It is not enough to say that you have done the project; you have to be able to share the details of the project. If you have a portfolio (either online or as a hard copy), show it to the interviewers.
  • Research the company and imagine you are head of your own technical or engineering team. What technical questions would you ask a candidate for this role to gauge their level of understanding?
  • If possible, find out who you will be interviewing with, their background, and their position. Check their LinkedIn profile. It may give you an idea of what their perspective and/or focus might be.
  • Have questions to ask at the end of the interview. For examples, see the Interview Prep handout.
  • Preparing in advance will go a long way towards increasing your confidence during the interview.

Do’s

  • Demonstrate the ability to think systematically (step by step). First, find the easiest solution, then, gradually improve on your solution.
  • Ask for clarification on a problem if you didn’t understand something or if there is any ambiguity.
  • Let the interviewer know what you are thinking.
  • Suggest multiple approaches to the problem.
  • Bounce ideas off the interviewer, such as design ideas, data structures or algorithms.
  • If you get stuck, don’t be afraid to let them know and politely ask for a hint.
  • Ensure you understood the question and then confirm. “Did that answer your question? Is there any part on which you’d like more details?” Don’t assume, because many times there can be a disconnect. Ask for clarification on the front end, answer the question, and then confirm on the back end.
  • Be honest:
    • If you can’t recall something, apologize and say something like, “I just used that command last week, but if I was offered this opportunity, here is what I would do to find the answer.” That way you will walk them through the problem and show them you’re resourceful.
    • If you are sure you don’t know: Draw a parallel or a connection to something relevant that you’ve done. You can say something like, “Unfortunately, I haven’t had the opportunity to work with C#; however, I have so much experience in VB.NET that I feel like I can transition easily.”

Don’ts:

  • Don’t be afraid to ask questions. Make sure you understand an interview question before answering.
  • Never give up! That determination is a large part of your ability to solve problems!
  • Don’t sit in silence while thinking. The interviewer has limited time to find out as much as possible about you. Help them understand how you think or find solutions as an engineer or a technologist.
  • If you already know the answer, don’t just blurt it out. Even if you have seen the question before, take the opportunity to think through how best to answer, and how to communicate your thinking process.

Remember:

  • The first technical interview can be tough: you may not have experienced anything like it before. Note that each interview will increase your knowledge and confidence for future interviews.
  • You may be asked to remember things from classes that you took a while ago.
  • You may need to come up with solutions to problems on the spot. Keep in mind that some companies ask harder and harder questions until you cannot answer the question, and then they move on. Some of the questions are ones that the companies have not yet solved themselves.

What are some companies that have Technical Interviews?

Amazon

AMD

Apple

Bose

Cisco

Citadel Harris

Dell

Expedia

Hewlett-Packard

IBM

Lockheed Martin

Microsoft

Orbitz

Qualcom

VMWare

Yahoo

Additional Resources:

Adapted from Carnegie Mellon Career & Professional Development Center and MIT Course Handouts