Product leadership clearly is out of touch with how the product is used, probably because they've never used it in any meaningful way. Most of leadership seems to come from a non-technical background, and it shows in their lack of cohesive or realistic vision. New Relic is a product for engineers, and the product leadership clearly has no, or very stale, engineering perspective.
Engineering leadership is designing top-down without understanding how the product works at all, which is doomed to fail. The name of the game is to cut costs and consolidate. Slideware is repeatedly presented that shows some magical simplified product architecture without any idea of how to get there.
ICs are being moved overseas for cheap labor, but they aren't being trained up at all, leaving everyone to deal with massive confusion.
Private equity definitely played out as one might imagine. The culture has all but disappeared, and everything is grinding to a halt while they lower the bottom line with layoffs and cost cutting.
Replace product managers and C-suite with people that have a deep engineering background, as the product is literally for engineers.
Remove some layers from the engineering management hierarchy and teach them how to enable their ICs, not dictate to them what to build based on incomplete information.
Figure out how to get out of PEs hands ASAP else you will lose all your talent.
You are contacted by the recruiter for a first conversation. Then, you need to submit a technical exercise, and if you pass this test, you get an interview with the manager and with several engineers.
The interview process was fairly to the point. We went over role expectations as well as diving into my experience and some soft skills questions. This was broken up by some small talk, and the overall interview was about 45 minutes.
The first round was a recruiter screening. Then, the second round, I had a meeting with the hiring manager to discuss my background and experience. The last round was a technical interview which involved some multithreading. Unfortunately, I didn't g
You are contacted by the recruiter for a first conversation. Then, you need to submit a technical exercise, and if you pass this test, you get an interview with the manager and with several engineers.
The interview process was fairly to the point. We went over role expectations as well as diving into my experience and some soft skills questions. This was broken up by some small talk, and the overall interview was about 45 minutes.
The first round was a recruiter screening. Then, the second round, I had a meeting with the hiring manager to discuss my background and experience. The last round was a technical interview which involved some multithreading. Unfortunately, I didn't g