New Relic Interview Questions
& Process

The whole interview process at New Relic was pretty good. It started with an online test at our college with MCQs on technical stuff, some aptitude questions, and three DSA problems. Then, the students who passed that got invited for Technical Interview 1. The first technical interview was chill, the interviewer was super friendly and nice, making me feel really comfortable. It was mostly about Data Structures and Algorithms (DSA). They asked me about stack implementation, a dynamic programming problem like Longest Common Subsequence, and also some questions on Operating Systems (OS), Object-Oriented Programming (OOPS), and Computer Networks (CN). The interviewer also asked follow-up questions which made it engaging. After clearing that, I got to Technical Interview 2. The second interviewer was also really kind and encouraging, helping me stay calm. This one was all about my resume – we went deep into my projects, certifications, and previous internship. After I passed that, I had the HR interview. The HR round was mainly about my communication skills and personality, asking casual questions about my life and interests. It was a friendly chat. Finally, they told me I got selected. All four rounds (Online Test, Tech 1, Tech 2, and HR) happened on the same day, and the whole thing was smooth, organized, and felt supportive. The interviewers made it enjoyable and not stressful at all.

The application process felt welcoming, structured, transparent, and respectful of my time. It started with a recruiter call, then a meeting with the Hiring Manager. The third round involved a Manager from a different department, followed by a presentation, a meeting with the VP, and finally, an offer. Although there were quite a few rounds, it was a good opportunity to meet many relevant people and understand their market perspective. Special thanks to the recruiter, Jarvis James, who provided constant updates, feedback, and support throughout the journey, building trust and partnership. The interviews were well-planned, giving me a good chance to learn about the company, its culture, and its people. It was a challenging process that required significant research and pitch preparation, which I found fair given the offered salary. I'm excited to join New Relic and recommend their application experience.

So I initially had a recruiter call and then a hiring manager call. Then things got a little strange. After the hiring manager call, I was given a take-home assignment that didn't seem to relate to the job and required building an application. Even though I'm technical, I'm not a developer, so it was a bit out of my comfort zone. I thought maybe it was a test to see how I'd adapt. I finished it, which cost me about $130 in AWS fees, and submitted it. About two weeks later, I got rejected, with the reason being I wasn't technical enough. What was weird is that the job posting disappeared for a month and then reappeared. I also heard that take-home assignments are usually later in the process. Since the assignment involved evaluating their product, comparing it to competitors, and suggesting AI/ML applications, I suspect they were using applicants for free consulting to get product ideas, with no real intention of hiring. I could be wrong, but I think potential applicants should be aware of this, as it's pretty unethical if true.

I got this job through a referral and the whole thing took about 2 weeks. The first step was a technical interview that covered technical stuff and some behavioral questions about the TSE job. Then, I had a meeting with the Hiring Manager where they asked some basic behavioral questions. After that, there was a take-home assignment where I had to set up a New Relic agent in a demo project. Next up was another technical interview, again with some basic technical and behavioral questions. The final stage was with HR, where we talked more about the job and salary. The whole process was pretty fast and clear.