Software Engineer Interview Experience - Seattle, Washington
Process
An engineer called me for a 1-hour coding round for a Java position.
The interview started with some basic questions.
Then, the interviewer kept asking about:
- Networking internals
- File system internals
- Network packet details
- Protocol details
This was especially confusing since the position requirements did not list these topics.
The interview ended with no coding and in 30 minutes.
Questions
Unix internals Networking internals Packets Protocols Threading internals
Was this helpful?
Interview Statistics
The following metrics were computed from 21 interview experiences for the Apple Software Engineer role in Seattle, Washington.
Success Rate
Apple's interview process for their Software Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Apple's Software Engineer interview process in Seattle, Washington.
Apple Work Experiences
- 5.0World-class Products, Unique CultureSoftware Engineer • Current EmployeeSeattle, Washington, United StatesMarch 20, 2024Pros: Working on first-in-class products loved worldwide.Cons: Strong company culture that might not work for everyone.
- 4.0Food Good, Then BadSoftware Engineer • Current EmployeeSeattle, Washington, United StatesMay 8, 2024Pros: Nice food, and I liked the food.Cons: I didn't really like the food.
- 4.0Good if you can find the right teamSoftware Engineer • Current EmployeeSeattle, Washington, United StatesJune 9, 2024Pros: Good pay. Friendly, respectful culture. Good work-life balance. It's Apple!Cons: It's easy to get stuck in a role, and hard to move teams. Internal tools are garbage, with multiple overlapping systems and slow, unreliable builds. Nothing is written down; everything is tribal knowledge.
Apple Interview Questions
