
One candidate who applied for a New Relic Solutions Engineer role in 2024 describes a long loop: recruiter, hiring manager, peer and manager interviews, a presentation with group scenario, and an in-person meeting.
$158K
Avg. Base Comp
$200K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The one account available for this guide, from a candidate who applied in October 2024, describes a long, multi-stage loop in which each stage asked for something different. It began with a recruiter screen, then a hiring manager conversation, a peer group interview and a separate manager interview. It ended with a presentation that included a group scenario and an in-person meeting. The candidate was not offered the role, and said the main lesson was to plan preparation across the whole loop instead of only the early rounds.
The one technical question the candidate remembers was about hands-on experience with Kubernetes and OpenTelemetry. Since this is one report, treat it as a hint rather than a pattern. Prepare to describe specific environments you have instrumented, what you observed, and how you explained it to others.
The candidate also said the recruiter was responsive, gave feedback after each stage and suggested a role that fit their background better than the one they applied for. Expect to rehearse the presentation and scenario separately from the conversational rounds, and keep your stories ready for several different interviewers.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the New relic process.
I applied for a Solutions Engineer role at New Relic in October 2024, and the recruiter, Jarvis, was the best part of the whole process. He suggested a different role from the one I had applied for, one he felt matched my skills better, and he kept me updated and gave feedback promptly after each stage.
The process was long and took real preparation. It started with a recruiter screen, then a hiring manager conversation, followed by a peer group interview and a separate interview with a manager. After that came a presentation with a group scenario, and the loop finished with an in-person meeting.
The technical question I remember was about my experience with Kubernetes and OpenTelemetry. I came away feeling that the number of stages mattered as much as any single conversation, since each one asked me to show something different.
I did not receive an offer. Looking back, the biggest lesson is to plan your preparation across the whole loop rather than concentrating on the first few rounds.
Prep tip from this candidate
Be ready to describe your hands-on Kubernetes and OpenTelemetry experience concretely, since that was the technical question raised. Budget preparation time for every stage, including the presentation and group scenario, because the loop runs long.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at New relic
Write a query that returns all neighborhoods that have 0 users.
| Question | |
|---|---|
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Upsell Transactions | |
| Longest Streak Users | |
| Customer Orders | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Merge Sorted Lists | |
| Employee Salaries (ETL Error) | |
| Last Transaction | |
| Random SQL Sample | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Top 3 Users | |
| Download Facts | |
| Paired Products | |
| Find Bigrams | |
| 7 Day Streak | |
| First Touch Attribution | |
| Order Addresses | |
| Manager Team Sizes | |
| N-gram Dictionary | |
| Find the Missing Number | |
| Lowest Paid | |
| Scrambled Tickets | |
| Minimum Change | |
| Payments Received | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports the process started with a recruiter screen. The recruiter was responsive, gave prompt feedback after each stage, and suggested a different role than the one applied for. Applicants may want to be ready to discuss their background and which role fits it best.
After the recruiter screen, the candidate reports a conversation with the hiring manager. The account gives no detail on its content, so applicants should typically expect questions about their experience and fit for the role, and prepare concrete examples of past work.
The candidate describes a peer group interview and a separate interview with a manager. The technical question they remember was about hands-on Kubernetes and OpenTelemetry experience, so applicants may want to prepare specific examples of that work and what they learned from it.
The candidate reports a presentation combined with a group scenario, and says each stage asked them to show something different. Details of the topic and format were not shared, so applicants may want to prepare and rehearse a presentation separately from their interview answers.
The candidate reports the loop finished with an in-person meeting, after which they did not receive an offer. Their advice is to budget preparation time across every stage, since the long loop rewards sustained preparation rather than strength in only the first few conversations.