There were no trap questions. A lot of scenario questions: What will you do in this case? How do you handle that? A lot of question about my motivation, my expectation, my personality. On the technical interview, there was an exercise on designing a scalable system.
Imagine you're the CTO of Verizon in ~10 years. What projects do you pursue?
Why is it so important to have listening skills?
What do you do when you find out two weeks before launch that a software feature still hasn't been implemented?
How much time to get a PCB from a supplier?
Very focused on scenarios and situation justifications and understanding status then speak up as the role
What's one time you didn't have the technical knowledge for a solution and had to bridge the gap.
What is Poisson's Ratio?
How do you deal with group work?
Why you change from your previous job
Viewing 71 - 80 interview questions