Taro Logo

Software Engineer Interview Experience

February 1, 2023
Negative ExperienceNo Offer

Process

The interview process was weird.

  1. Recruiter phone screen
  2. Engineering Manager phone screen
  3. Take-home (10+ hours if you do it right)
  4. Didn't make it to the final round

The role required experience in seemingly every language, including strong Java, but Typescript/React, etc., were also role requirements (my primary languages).

I made it known in the screen with the manager that I had minimal Java experience. I was moved forward to the take-home portion.

I was given a full Java app with testing, Docker containment, edge cases, and a readme (estimated total time of 2-4 hours; it easily took me 12+ hours. Even if you were proficient in Java, it would be a 10+ hour program to do it right).

Giving a take-home in a language different from a candidate's primary is weird, especially after disclosing it. It was a waste of time, and I got no feedback.

Questions

Basic questions of past experience.

Was this helpful?

Interview Statistics

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

Success Rate

37%
Pass Rate

New Relic's interview process for their Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive56%
Neutral7%
Negative37%

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

New Relic Work Experiences