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.
Applied online through the website. Two interviews, mostly focusing on research, projects, and some easy coding topics like Applied ML and linked lists. Fairly fast process, took about 3 weeks in total. I got a project that was a good match.
I submitted my resume online, and the recruiter contacted me within one week. A talk with the hiring manager was then scheduled. Once the result was positive, a one-hour technical phone screen was done. Then came the onsite interview, which consisted
The interview process was pretty quick and easy. I reached out to a team manager who posted on my university job board. The first interview was with a first-year SWE, and it was a standard LC easy. The second interview was a day or two later with the
Applied online through the website. Two interviews, mostly focusing on research, projects, and some easy coding topics like Applied ML and linked lists. Fairly fast process, took about 3 weeks in total. I got a project that was a good match.
I submitted my resume online, and the recruiter contacted me within one week. A talk with the hiring manager was then scheduled. Once the result was positive, a one-hour technical phone screen was done. Then came the onsite interview, which consisted
The interview process was pretty quick and easy. I reached out to a team manager who posted on my university job board. The first interview was with a first-year SWE, and it was a standard LC easy. The second interview was a day or two later with the