Taro Logo

Software Engineer Interview Experience

March 1, 2020
Neutral ExperienceGot Offer

Process

  1. Round 1: HR call. Normal HR call.

  2. Round 2: Video interview for an hour. Covered a wide range of questions, like basic Oops, volatile, SQL, and coding questions (Merge Sort). How would you debug a SQL server performance issue? What are Generics? How would you implement a Web API attribute to stop access of PUT and POST for a specific user?

  3. Third Round: 2 hours of video interview.

1st hour: There is no defined pattern to take the interview. Asked to open Visual Studio on a corporate laptop. CLI to create a .net core project. Create a project and add some files. Implement an extension to sort objects by multiple members. Write a unit test for it. Asked questions on the resume. Very vague questions.

2nd hour: Asked questions on Microservices and deployment. Challenges faced. Grilling on .Net internals; low-level .net implementation knowledge. Nice to learn, though. Internals of Dictionary, hashing collision. Memory Management in CLR. Which method would you implement in a custom object when using it as a key in a Dictionary? Async Await internals. Algorithmic complexity discussion on List functions. Different ways to sort a list and dive into the internal implementation of these ways. No coding questions. More grilling on internals.

Questions

Asked questions about microservices and deployment challenges faced.

Grilling on .NET internals, specifically low-level .NET implementation knowledge. Nice to learn though.

Internals of Dictionary, hashing collisions, memory management in CLR. Which method will you implement in a custom object when using it as a key in Dictionary?

Async/await internals. Algorithmic complexity discussion on List functions. Different ways to sort a list and a dive into the internal implementation of these ways.

No coding questions. More grilling on internals.

Was this helpful?

Interview Statistics

The following metrics were computed from 40 interview experiences for the Motorola Software Engineer role in United States.

Success Rate

53%
Pass Rate

Motorola's interview process for their Software Engineer roles in the United States is on the easier side as most engineers get an offer after going through it.

Experience Rating

Positive57%
Neutral28%
Negative15%

Candidates reported having very good feelings for Motorola's Software Engineer interview process in United States.

Motorola Work Experiences