
One candidate for a New Relic Senior Product Manager role reports a recruiter call, a product-philosophy interview focused on observability, extra unplanned rounds, and no feedback afterward. Here is how to prepare.
$173K
Avg. Base Comp
$205K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
One Senior Product Manager candidate describes New Relic's Product Manager interviews as a recruiter call followed by an interview centered on product philosophy and best practices. The conversation also covered how the candidate would learn the nuances of observability and application monitoring, which the candidate described as a core part of the role.
For preparation, expect to talk about how you learn an unfamiliar technical domain. Be ready to explain how you would get up to speed on monitoring concepts, who you would learn from, and how you would turn that into product decisions. You should also be ready to describe your product principles with concrete examples, since that was the substance of the conversation.
The same candidate found the structure unclear. They were told further rounds were needed after thinking the process was ending, and a new interviewer was added later. The hiring manager's notice period also stretched the timeline. This is a single account, so treat it as a sign to ask questions rather than a rule. Ask the recruiter early who you will meet, how many rounds to expect, and when you should hear back, then confirm the answers in writing. The candidate did not receive an offer and heard nothing after repeated follow-ups.
Synthesized from 2 candidate reports 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.
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 | |
| Experiment Validity | |
| Top 3 Users | |
| Button AB Test | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Manager Team Sizes | |
| Upsell Transactions | |
| Longest Streak Users | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Customer Orders | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Employee Salaries (ETL Error) | |
| Last Transaction | |
| Testing Price Increase | |
| Random SQL Sample | |
| Subscription Overlap | |
| Google Maps Improvement | |
| Monthly Customer Report | |
| Hurdles In Data Projects | |
| Download Facts | |
| Group Success | |
| Pre-Launching Shows | |
| Paired Products | |
| 7 Day Streak | |
| First Touch Attribution | |
| Order Addresses |
Synthesized from candidate reports. Individual experiences may vary.
The candidate describes the recruiter call as fairly standard. It is a sensible place to ask about the interview stages, who will be involved, and the expected timeline, since this candidate later found the structure unclear. Details beyond that were not reported.
The candidate reports an interview with a Senior Project Manager that focused on product philosophy and best practices. It included how they would learn the nuances of observability and application monitoring. Candidates may want to prepare examples of ramping up quickly in a new technical area.
The candidate reports that extra rounds were added after they expected the process to wrap up, including a new interviewer. The timeline was also affected by the hiring manager giving notice. After the interviews, repeated recruiter follow-ups reportedly went unanswered, and the outcome was no offer.