You get Apple on your resume. Engineers are nice for the most part.
Apple IS&T is the worst, most toxic environment at Apple.
When you work here, you do not really work for Apple; you are like an outsider. It is truly scary that a place like this can exist at a company like Apple.
You should not join. Good people cannot fix broken environments. The place is broken because of legacy culture from the top.
They will make it sound nice and paint a nice picture with words, but once you get there, you will realize you are trapped in a bait and switch, career suicide. They could get sued for this.
Many managers are mean, incompetent, or aggressive slave drivers. Stay away.
You at least need to overhaul/modernize IS&T and put in real technical leadership. Imagine if this were a place that naturally attracted top infra talent, like Google, Facebook, or Netflix.
The whole "business partner" vs. "IS&T partner" dynamic creates never-ending division, attracts mean/micromanagers, and results in a diversity and inclusion issue. Imagine, for a moment, if the business partners actually hired the engineers they depend on. Or do they not have the technical acumen? Or is the work too unattractive/dirty? Do you really need 30 contractors when 2 FTE engineers would get the job done?
You can do better than this.
Overall smooth. Had 3 interviews: one behavioral and 2 technical. Heavy system design and debugging. Interviewers were nice, standard interview format with an introduction and then mostly technical questions. Some OOP concepts needed as well.
It was a pretty standard big tech interview process. At a high level, it had the following steps: * Recruiter call * Hiring Manager screen * Technical phone screen * Onsite
One interview, supposed to be with the hiring manager, was followed by a group of three interviews. These interviews were primarily focused on computer architecture and verification concepts. There was also some coding related to these computer archi
Overall smooth. Had 3 interviews: one behavioral and 2 technical. Heavy system design and debugging. Interviewers were nice, standard interview format with an introduction and then mostly technical questions. Some OOP concepts needed as well.
It was a pretty standard big tech interview process. At a high level, it had the following steps: * Recruiter call * Hiring Manager screen * Technical phone screen * Onsite
One interview, supposed to be with the hiring manager, was followed by a group of three interviews. These interviews were primarily focused on computer architecture and verification concepts. There was also some coding related to these computer archi