The entire process from application to hire took about two months (with a one-week delay). Once selected (which took about a week after initial application in my case), I got an email to do a phone interview. It was a two-phase interview (background screening then technical). The background screening was 30 minutes and included typical interview-type questions such as "what is your greatest strength", but it also included very simple coding-type questions (as a sanity check). The background screening actually included a couple of brain teasers as well (to assess communication and critical thinking skills).
Then, the second part of the phone interview was with someone else. Surprisingly, this was also mostly non-technical and included many of the same background questions, but with general "academic" OOP questions thrown in (like "explain polymorphism").
I got a call from a recruiter about a week after the phone interview asking me to come in for the full in-person interview. This interview was a full day and included lunch. It started and ended with the hiring manager, who is very warm and made me feel comfortable and excited to be there.
The interview was a series of (give or take) one-hour interviews. Each interview was a mixture of background and technical questions. There were no ridiculously hard Google-style questions to stress about, just one brain teaser question again to gauge communication and problem-solving skills. Everyone was very nice and very engaging, and they all made me feel like I belong there.
This is a job for people who care and take pride in what they do, and they are looking for that genuine quality, so don't try to fake it. This is a company that takes great pride in all aspects of quality, as our mission is to create products that save lives.
Finally, a few days after the interview, I got the offer via call. There is a thorough background check, and so it took another couple of weeks before I started working. Overall, it was very smooth and thorough.
Tell me about Course X.
What is your greatest strength?
What is your greatest weakness?
What language are you most comfortable with?
Do you prefer software or hardware engineering?
The following metrics were computed from 1 interview experience for the Motorola Software Development Engineer In Test (SDET) role in United States.
Motorola's interview process for their Software Development Engineer In Test (SDET) roles in the United States is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Motorola's Software Development Engineer In Test (SDET) interview process in United States.