Good benefits and coworkers, but extreme red tape is a risk for burnout
Good benefits and coworkers, but extreme red tape is a risk for burnout
Benefits are good. Coworkers are generally nice.
Information is siloed to an extreme extent, yet cross-functional collaboration is not only a must, but a frontly-touted paramount of company culture. A gigantic amount of red tape is embedded into the corporate infrastructure. When it comes at odds with the breakneck, almost unrealistic speeds at which we are expected to deliver, that's when the burnout happens. And boy, does it happen.
I understand intra-corp secrecy is an important mainstay, but it impacts velocity and puts undue onus on the individual engineer to reverse engineer that which is undocumented, find out requirements way ex post facto, and makes it difficult to spearhead meaningful change in a meaningful amount of time when you're effectively herding cats via teleconference in different timezones, and each cat carries not only its own partial understanding of the end goal or the requirements, but also asserts that it and only its piece of the pie warrants P1.
Additional Ratings
Was this helpful?
Apple Interview Questions
Apple Interview Experiences
Junior Hardware Engineer
It started with a quick phone technical interview, followed by a second, more in-depth technical interview over the phone. Initial questions were more about motivation and background knowledge, and slowly built into more complex technical concepts.
Engineer
The interview was long, but easy. Most of the questions were technically simple, but they tried to confuse you. Three people interviewed me on the same day. The job requirements were different from most of the questions asked.
Senior Software Engineer
All day, groups of 2 or 3 engineers at a time came into a windowless conference room and asked questions. Some of them involved solving logic problems, either by writing code on a whiteboard or creating a flowchart showing how you'd solve the problem
Junior Hardware Engineer
London, England, United KingdomFebruary 1, 2018It started with a quick phone technical interview, followed by a second, more in-depth technical interview over the phone. Initial questions were more about motivation and background knowledge, and slowly built into more complex technical concepts.
Engineer
IrelandNovember 9, 2021The interview was long, but easy. Most of the questions were technically simple, but they tried to confuse you. Three people interviewed me on the same day. The job requirements were different from most of the questions asked.
Senior Software Engineer
Vancouver, Washington, United StatesJanuary 1, 2012All day, groups of 2 or 3 engineers at a time came into a windowless conference room and asked questions. Some of them involved solving logic problems, either by writing code on a whiteboard or creating a flowchart showing how you'd solve the problem
