New Relic logo
New RelicBackend Engineer
Updated Nov 25, 2022

New Relic Backend Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Backend Engineer at New Relic, newest first and distilled into what to expect across the loop.

Get your personalized New Relic Backend Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
> 1 year
Average Negative Spain

I went through a longer, multi-step process that started with recruiter coordination and then moved into an engineering manager interview. I talked through past experience, the tech stack, and typical behavioral questions, and I felt like that round went well. After that, I completed a take-home technical challenge with pretty intense requirements—one part involved building something like a server that could handle millions of TCP connections on a frequent interval. I submitted it as agreed, but the next step still wasn’t the end of the work.

They requested a follow-up to go deeper into the implementation details and then added a systems design whiteboard session. After that, the waiting got long. I was told I passed filters, but there were internal discussions before a final decision, and weeks passed without meaningful updates. Eventually I got a rejection email that boiled down to “cultural fit,” with no real feedback beyond that. In a similar stretch of the process, a take-home also became a major time sink compared with what was promised—one version was capped at around four hours but took far longer because it effectively required building an app with tests and an API. I never got to a final interview in that scenario because a hiring freeze intervened, and the feedback I did receive on the take-home wasn’t that informative. Altogether, the process felt time-consuming without enough clarity, and my final reflection was that the lack of concrete feedback made it hard to learn from.
> 1 year
Average Positive Tel Aviv-Yafo

My interview journey felt pretty professional and calm overall. It started with recruiter outreach and then moved into a series of technical interviews paired with an HR conversation. The questions I got were fair and grounded in day-to-day engineering work rather than weird puzzles, and the interviewers were clear about what they were looking for and how the team approached problems.

As the process moved forward, the technical rounds didn’t feel like a trap. One part included a take-home problem where a skeleton was provided and the expectation was to implement the missing logic. I went through it, and when I got to the subsequent engineering discussions, they reviewed my approach and walked through it with me instead of jumping straight to gotchas. The atmosphere stayed respectful, and I didn’t get the stressful style where they try to break your confidence. Feedback timing was also pretty reasonable—often within a couple of days, except longer work that could take a week.

Unlock every Backend Engineer interview experience

Real Backend Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.