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
Tree question. Couldn't give tips at all. Interviewer was disconnected and condescending for each reject in 45 minutes. Really terrible candidate experience. There have been few good experiences with Meta.
First is the recruiter round, then a one-hour technical interview which included questions around SQL and Python. After that would be behavioural and other technical rounds. Other technical rounds would cover system design, etc.
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
Tree question. Couldn't give tips at all. Interviewer was disconnected and condescending for each reject in 45 minutes. Really terrible candidate experience. There have been few good experiences with Meta.
First is the recruiter round, then a one-hour technical interview which included questions around SQL and Python. After that would be behavioural and other technical rounds. Other technical rounds would cover system design, etc.