Apple can be exciting to work for, but it's a rough ride. Not for the faint-hearted
Apple can be exciting to work for, but it's a rough ride. Not for the faint-hearted
Everyone knows where you work, and they think it's awesome. You get to play with all of the latest software and toys, and work for one of the most profitable companies in the world.
Apple is very secretive. It can be difficult to know what's going on ahead of time, and then all of a sudden, you need to shift and adapt. Schedules are very rough and change a lot. Releases and crunch time seem omnipresent. It can be overwhelming.
If your strengths do not include constant adaptation to continuous change, then Apple will frustrate you.
Trust your employees more than you do with company secret information. Things would run a lot smoother.
Was this helpful?
Apple Interview Questions
Apple Interview Experiences
Senior Software Engineer
I was contacted by the recruiter via email, followed by two separate phone calls with someone from engineering. Both conversations involved writing quite a bit of code for most of the hour. After that, I was invited on-site for a full day of "fun an
Senior Software Engineer
Team-specific interview process. This team focused on OOP principles. The phone screen involved OOP with a bit of system design. The onsite included another OOP section and a peculiar tree/node question where the task was to serialize and deserializ
Senior Software Engineer
It was good, tough, and long. 1. Prescreen interview with overall questions to estimate my technology knowledge and experience. It took a 15-minute talk. 2. Test task: write a project. It took 2 hours. 3. Tech interview: 3 sessions, 1 hour each.
Senior Software Engineer
Cupertino, California, United StatesMarch 1, 2016I was contacted by the recruiter via email, followed by two separate phone calls with someone from engineering. Both conversations involved writing quite a bit of code for most of the hour. After that, I was invited on-site for a full day of "fun an
Senior Software Engineer
Cupertino, California, United StatesOctober 22, 2024Team-specific interview process. This team focused on OOP principles. The phone screen involved OOP with a bit of system design. The onsite included another OOP section and a peculiar tree/node question where the task was to serialize and deserializ
Senior Software Engineer
Cupertino, California, United StatesFebruary 1, 2024It was good, tough, and long. 1. Prescreen interview with overall questions to estimate my technology knowledge and experience. It took a 15-minute talk. 2. Test task: write a project. It took 2 hours. 3. Tech interview: 3 sessions, 1 hour each.
