A screening interview was followed by a panel interview (6 in total).
Each of the panel interviewers would focus on a different area covered in the screening interview.
I was interviewed twice in one month with two different teams. I excelled at both interviews, but I wasn't given an offer, and they didn't share the reason.
How BGP works, controlling upload/download, and why it uses TCP.
Route reflectors (and how they implement loop prevention).
Additional paths feature.
Path hunting.
CLOS networks (and how to prevent microloops within CLOS).
How OSPF works, loop prevention mechanisms, OSPF flags, and scaling OSPF.
Two simple programming tasks (counting things and such).
CI/CD.
Version controlling.
Sed/awk.
Basic bash commands.
How do you meet deadlines?
How BGP timers work and what's the longest it would take for a route to update?
How would you design a site that can connect 100 Tbps worth of customers?
What's the difference between Python data structures?
Why is it faster to iterate through a dictionary compared to a list?
The following metrics were computed from 1 interview experience for the Amazon Network Development Engineer role in Iraq.
Amazon's interview process for their Network Development Engineer roles in Iraq is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Amazon's Network Development Engineer interview process in Iraq.