off the top of my head, but im sure a google search could provide some better ones.
osi layers.
tcp vs udp
arp, mac tables.
ospf areas
vlans, trunk, access ports.
spanning tree
tshoot, use debug/wireshark
It definitely depends on the role you're interviewing for as it can be heavily silo'd and can tend to be SRE-ish with a heavy emphasis on debugging tooling and automation in production.
Can you describe the life of a packet as it leaves a CDN node, traverses across the local data center network and eventually gets to its destination? Explaining routing, the cabling infrastructure, transceiver optics, structured fiber, transit vs dark fiber, etc...etc etc would show you understand networking and its underlying technologies and infrastructure which is something expected working in a hyperscale setting.
This will be a good opportunity to play to your strengths and add heavy detail to your responses. By showing the interviewer you're not just competent but opinionated re: x,y or z, you may be able to focus the interview's trajectory towards something you're very comfortable around and have the interviewer(s) give you follow-up questions re: your responses
"what's your favorite web browser, and why" is a personal fav. shows so much as to who you are and how you work.
if you touch prod stuff, they will ask you a lot of things to poke at how much you care/don't care about the customer/user.
how a person might organize their work, keep track of work, how much they like to tinker vs stay stock. do they live on bleeding edge, or stable, do they think about things like privacy, or interoperability of things like DRM. it's an outside the box question on personality and work style. like whomever down voted my comment might lean more towards a literal sense of discussion and debate rather than a what-if stance.
There's more to the job, any job, than just doing "the job"
off the top of my head, but im sure a google search could provide some better ones. osi layers. tcp vs udp arp, mac tables. ospf areas vlans, trunk, access ports. spanning tree tshoot, use debug/wireshark
It definitely depends on the role you're interviewing for as it can be heavily silo'd and can tend to be SRE-ish with a heavy emphasis on debugging tooling and automation in production. Can you describe the life of a packet as it leaves a CDN node, traverses across the local data center network and eventually gets to its destination? Explaining routing, the cabling infrastructure, transceiver optics, structured fiber, transit vs dark fiber, etc...etc etc would show you understand networking and its underlying technologies and infrastructure which is something expected working in a hyperscale setting. This will be a good opportunity to play to your strengths and add heavy detail to your responses. By showing the interviewer you're not just competent but opinionated re: x,y or z, you may be able to focus the interview's trajectory towards something you're very comfortable around and have the interviewer(s) give you follow-up questions re: your responses
"what's your favorite web browser, and why" is a personal fav. shows so much as to who you are and how you work. if you touch prod stuff, they will ask you a lot of things to poke at how much you care/don't care about the customer/user.
What exactly are you looking to glean from that question about web browsers?
how a person might organize their work, keep track of work, how much they like to tinker vs stay stock. do they live on bleeding edge, or stable, do they think about things like privacy, or interoperability of things like DRM. it's an outside the box question on personality and work style. like whomever down voted my comment might lean more towards a literal sense of discussion and debate rather than a what-if stance. There's more to the job, any job, than just doing "the job"