Friendly Culture, High Stress
Friendly Culture, High Stress
Friendly people, friendly managers.
Amazing company and products.
Excited to be part of such an amazing organization.
Friendly work culture and collaboration environment.
Very good infrastructure and tooling.
Great perks.
Good upper management.
Competitive, stressful, and high-pressure working environment.
Subpar communication.
Bottom-up management is challenging.
Middle-level program and project management is totally lacking.
Communication in a COVID-19 WFH environment is challenging when the work culture historically was office-based.
Instability is normal: releasing to production and taking risks is actively encouraged.
The codebase is, in places, low quality.
The majority of the documentation is outdated and therefore unusable.
High turnover of staff means little continuity; the only people who stay long enough usually end up so stressed that you have to deal with people barely being able to function due to burnout.
Was this helpful?
Meta Interview Questions
Meta Interview Experiences
Production Engineer
I was contacted by the recruiter cold. He asked several technical questions to see if my experience matched the job requirements. After that, there were two scheduled phone interviews: one for programming and another for Unix system internals. The
Production Engineer
The first round was a coding interview, and the second round was a systems interview (not system design, but rather Unix-based operating systems). The coding round was quite basic, similar to LeetCode Easy, and included a question on manipulating fi
Production Engineer
Contacted on LinkedIn based on Google experience. The interview process was fairly long, including: * A phone screen * Two technical phone interviews * A full-day interview in Menlo Park It took several weeks for them to get back, but they ultimat
Production Engineer
United StatesMarch 5, 2018I was contacted by the recruiter cold. He asked several technical questions to see if my experience matched the job requirements. After that, there were two scheduled phone interviews: one for programming and another for Unix system internals. The
Production Engineer
Ann Arbor, Michigan, United StatesJanuary 1, 2022The first round was a coding interview, and the second round was a systems interview (not system design, but rather Unix-based operating systems). The coding round was quite basic, similar to LeetCode Easy, and included a question on manipulating fi
Production Engineer
United StatesJuly 1, 2014Contacted on LinkedIn based on Google experience. The interview process was fairly long, including: * A phone screen * Two technical phone interviews * A full-day interview in Menlo Park It took several weeks for them to get back, but they ultimat
