Product Manager Jobs at New Relic

New Relic PM interview guide

New Relic's PM loop runs about four stages over roughly two months (candidates report anywhere from three weeks to three months): a recruiter phone screen, a hiring manager phone interview, a take-home assignment, and a final onsite panel with the team. The one thing that defines the loop is the take-home: it pairs product questions with actual SQL, so you are expected to query and reason about data yourself, not just talk about it.

The interview process

1. Recruiter phone screen (about 30 minutes). A talent partner walks through your background, the role, and logistics. Light fit and motivation check, not a deep product round.
2. Hiring manager phone interview (about 45 to 60 minutes). A one-on-one with the PM hiring manager covering your PM experience and how you operate. Expect behavioral prompts about hard product decisions and how you work with engineering.
3. Take-home assignment (SQL plus product questions). A homework exercise that mixes SQL questions with product questions tied to the day-to-day work of a New Relic PM. This is the round that sets New Relic apart: it tests whether you can actually pull and interpret data, fitting a data and observability company.
4. Onsite panel with the team (sometimes a group presentation). A final panel to meet the team, in some cycles including a presentation of your take-home or a product exercise. Candidates describe it as friendly and collaborative; they assess product judgment, cross-functional fit, and how you defend your thinking.
5. What they're really testing. Three signals carry the most weight: data fluency (can you reason in SQL and from metrics, not just words), how you partner with engineering through the build cycle, and product judgment under ambiguity (framing a vague problem fast and defending your call).

Likely PM interview questions

1. How would you monetize dashboard software for the "car of the future"? You get no background information and 20 minutes to come up with something.Product sense
2. What is your favorite product and why, and what would you do to improve it?Product sense
3. Tell me about a time a feature didn't deliver to expectation. What happened?Execution