The engineers are typically top-notch. If you can deal with the culture, politics, gatekeeping, and empire building, you can learn a lot and earn a lot.
The engineering culture has changed from a mostly bottom-up approach (engineers identify and fix things that need work) to a mostly top-down org.
Lots of tracking, OKRs, status meetings, and critical reviews.
Review season is brutal for managers and ICs alike.
Keeping your engineers happy will help them be productive in the long run. A Darwinian struggle every day at work is a bad, short-term solution to getting things done.
The interview process was a five-stage process. These stages included: * Technical * Behavioral * Architectural * Meeting the team * Overall review and feedback The hands-on coding assignment was a little contrived and very similar to th
The interview process consisted of one telephonic round, which covered questions similar to those mentioned by others. The onsite portion included four rounds focused on SQL, coding, and product sense. Had I received an offer, I would have declined.
The standard interview process began when a recruiter reached out to me and explained the interview stages. It included: * An initial phone screen with two coding questions. * An onsite loop consisting of two coding rounds, one system design ro
The interview process was a five-stage process. These stages included: * Technical * Behavioral * Architectural * Meeting the team * Overall review and feedback The hands-on coding assignment was a little contrived and very similar to th
The interview process consisted of one telephonic round, which covered questions similar to those mentioned by others. The onsite portion included four rounds focused on SQL, coding, and product sense. Had I received an offer, I would have declined.
The standard interview process began when a recruiter reached out to me and explained the interview stages. It included: * An initial phone screen with two coding questions. * An onsite loop consisting of two coding rounds, one system design ro