I have been working in IS&T for just over a year. When I joined the company, I was pretty skeptical about this Apple wing, following the reviews about it before. But after the first year, I am pretty darn proud to have actually joined it.
The people I work with are top performers and all engineers. We have the highest engineering strength in the IS&T Org., which was not the case a few years back. This has improved both employee motivation and deliverables. IS&T is now more engineering-focused than ever, which is evident from the number of Apple employees in the team now.
And the compensation is one thing at the start that you expect good from a company like Apple. But to get a year-end stock bonus, cash bonus, and salary increase all together is just top-notch. Also, earlier in the year, all employees got BEATS headphones in the annual.
Working hours are fine too, yes! You work hard at times, but that's just part of the dev cycle. Nothing out of the ordinary.
No freebies, no free food. Yes, we do get small parties here and there, but I think Apple expects you to spend out of your pocket to cover for them. They have stopped giving apples in the cafeteria. (Well, that one is just due to drought.)
Keep IS&T Engineering focused, and it will be the best at Apple in no time.
This was probably one of the best and fastest-moving interviews I've done. Everyone I met with was tack sharp, and the questions were relevant and fun. These included questions about my research background, as well as a few whiteboard coding proble
Lots of questions that looked like they belonged in a lower-division CS final.
I re-contacted an Apple recruiter who had contacted me in the past because I was looking for new opportunities. After sorting out the location, I had two phone interviews. The questions were quite basic C++ and algorithm questions. After those two i
This was probably one of the best and fastest-moving interviews I've done. Everyone I met with was tack sharp, and the questions were relevant and fun. These included questions about my research background, as well as a few whiteboard coding proble
Lots of questions that looked like they belonged in a lower-division CS final.
I re-contacted an Apple recruiter who had contacted me in the past because I was looking for new opportunities. After sorting out the location, I had two phone interviews. The questions were quite basic C++ and algorithm questions. After those two i