Had a good coding conversation; the thought process was clearly articulated and penned down clearly. In this age, if someone is still looking for syntax and semantics, it shows a lack of technology adoption in their mindset, and they are stuck in the old school. It didn't move forward, but sure, there are no red flags. I'm not sure why there was a rejection; the interviewer doesn't seem to have any clue why he rejected. I have been an interviewer, and I know how it bites back. Be careful, interviewers: look for clarity in thinking, and avoid mindsets not needed in this advanced tech era. If I remember too much syntax and semantics, I can jump boats continuously and won't be loyal anywhere.
Given the API and its response time, just return the max, min, average, and mode of the API.
The following metrics were computed from 2 interview experiences for the New Relic Principal Software Engineer role in India.
New Relic's interview process for their Principal Software Engineer roles in India is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for New Relic's Principal Software Engineer interview process in India.