Taro Logo

Principal Software Engineer Interview Experience

March 1, 2021
Negative ExperienceNo Offer

Process

This was a very slow interview, spanning four sessions in a nine-week timeframe. Things didn't start on a good note when I had an initial interview scheduled with the recruiter, who asked me to reschedule. The next available appointment was 10 days out.

There were long pauses between steps in the interview with no communication, and the platform they use provides no way for a candidate to reach out with questions or comments.

The technical aspects of the interview included an hour-long session with a lead architect and a take-home component focused on presenting an architecture in written form.

During the final face-to-face interview, the chief architect had some questions about the content, but no one else during the interview did.

Questions

Design a distributed system with varying changes going in based on growing business problems.

Was this helpful?

Interview Statistics

The following metrics were computed from 6 interview experiences for the New Relic Principal Software Engineer role in United States.

Success Rate

17%
Pass Rate

New Relic's interview process for their Principal Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive17%
Neutral0%
Negative83%

Candidates reported having very negative feelings for New Relic's Principal Software Engineer interview process in United States.

New Relic Work Experiences