You get to work with ridiculously intelligent people who are also very creative.
Keep in mind that the engineers who make Apple products are also the users, and they control their entire hardware/software stack, which is very enabling on a company level.
Apple is also a great place to learn about designing products for user benefit, which is not always apparent in other organizations. Designing an experience is of the utmost importance and part of the culture of the company.
One of the hardest parts of working at Apple is how busy everyone is and how hard it can be to get time and resources from people. A lot of times, you have to be very inventive and maybe take a less efficient route if it means not involving other teams that don't have the time to spend on your project. I imagine this gets easier as you advance in rank, but as an intern, it can be hard. You could also look at that as an opportunity for growth.
The other hard part of working there is not having a lot of freedom to actually take your products to market and test them out. There is a lot of filtration of ideas that occurs, even before Steve Jobs can slam an idea.
I cannot speak much about the full-time job opportunities at Apple, but you have one of the best internship programs I have ever seen. I was pushed, I met some great people, and I grew a lot. There is not much more that a student can ask for in an internship, and I will always be grateful for that experience.
I think one of the difficulties at Apple is not being able to explore and learn about other groups, but I know that is part of the culture of secrecy there, and I understand your reasons for preventing such talk between groups. If that culture were to be lifted and interns could talk to each other more about their work, perhaps it would make for an improved experience.
Overall, I had a great time at Apple.
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