Cool Project, Limited Impact
Cool Project, Limited Impact
- Very cool, self-led project style.
- Encouraged to explore ideas and develop.
- Limited opportunity for real-world shipping/impact based on leadership.
- More interaction with production code and fixing bugs would be nice.
- Not a lot of structure.
Additional Ratings
Was this helpful?
Apple Interview Questions
Apple Interview Experiences
Software Engineering Intern
There were two screenings and one technical interview that lasted about an hour. The technical interview involved a design question, not a LeetCode-style problem, so I was able to be creative in my approach. The interviewer was friendly. It took a
Software Engineering Intern
Had a LeetCode Easy as a rising sophomore. Was asked about the resume and it was overall just a vibe check. The interviewer was the manager of the team I would be joining. The recruiter called afterwards with details on the offer.
Software Engineering Intern
Technical interview. Lasted about one hour. The interviewer was very nice and supportive. They started by giving their intro and the details of their team and what they're looking for, followed by codepad questions.
Software Engineering Intern
United StatesNovember 16, 2024There were two screenings and one technical interview that lasted about an hour. The technical interview involved a design question, not a LeetCode-style problem, so I was able to be creative in my approach. The interviewer was friendly. It took a
Software Engineering Intern
Cupertino, California, United StatesJuly 20, 2023Had a LeetCode Easy as a rising sophomore. Was asked about the resume and it was overall just a vibe check. The interviewer was the manager of the team I would be joining. The recruiter called afterwards with details on the offer.
Software Engineering Intern
New York, New York, United StatesJanuary 20, 2023Technical interview. Lasted about one hour. The interviewer was very nice and supportive. They started by giving their intro and the details of their team and what they're looking for, followed by codepad questions.
