Good Pay, Legacy Code
Good Pay, Legacy Code
Good pay. Good management. Work on major, influential products. Excellent on a resume. Great work-life balance (varies by team).
Significant amount of legacy code and infra.
Secrecy and divisions are siloed.
Pay not the best (possibly due to brand).
Mediocre benefits.
Top-down management.
Additional Ratings
Was this helpful?
Apple Interview Questions
Apple Interview Experiences
Machine Learning Engineer
First, an initial conversation with the recruiter. Then, two technical interviews. First one was about ML fundamentals. The second one was a general coding interview. Each interview lasted 45 minutes.
Machine Learning Engineer
6 rounds of interviews. * One round for algorithm coding problems for 1 hour. * One round for machine learning coding problems for 1 hour. * One round for system design. * One round for behavioral questions. * Two rounds for past projects
Machine Learning Engineer
The interview consisted of two phone screens. It started with a Data Structures and Algorithms (DSA) evaluation through a shared CoderPad screen. The questions were LeetCode medium level in difficulty. I was also asked about the implementation of so
Machine Learning Engineer
Cupertino, California, United StatesJuly 7, 2023First, an initial conversation with the recruiter. Then, two technical interviews. First one was about ML fundamentals. The second one was a general coding interview. Each interview lasted 45 minutes.
Machine Learning Engineer
Cupertino, California, United StatesSeptember 1, 20236 rounds of interviews. * One round for algorithm coding problems for 1 hour. * One round for machine learning coding problems for 1 hour. * One round for system design. * One round for behavioral questions. * Two rounds for past projects
Machine Learning Engineer
Cupertino, California, United StatesApril 1, 2020The interview consisted of two phone screens. It started with a Data Structures and Algorithms (DSA) evaluation through a shared CoderPad screen. The questions were LeetCode medium level in difficulty. I was also asked about the implementation of so
