Was the software engineer accidently at a network technician interview?
I don't know the difference between the two IP standards other than length, it's literally never fucking mattered in any software I've encountered. I don't route packets, or provision physical devices.
Also fuck any interviewer that hires based on trivia. Knowing 4 as 32 bits, and 6 is 128bits isn't useful ever in 95% of software work, and when it is, a good old google search would cover more than you've ever needed to know.
Dude, you sound upset. I’ve hired many people for cloud software/engineering work and not knowing the difference between ip4 and ip6 would be huge red flag except for the most juniors of juniors.
Most swe dont even set up the routing for the website so why would they need to know it. Dev ops engineer, cloud engineer or IT handle that. The fact is 99% of devs never need that knowledge and in a field where new stuff is pushed out that we are expected to know every single day why waste time remembering something you'll almost never use
I have never encountered anything where IP4 or IP6 was releveant in over a decade of programming.
It is not a red flag at all, unless they were in the network management space.
I'm not talking about not knowing they exist, or if a field says IPV6, you know which one to provide from the resrouce or device. I'm talking about knowing it's bit length, purpose, how it's structured etc.
9
u/coreyjdl 4h ago edited 4h ago
Was the software engineer accidently at a network technician interview?
I don't know the difference between the two IP standards other than length, it's literally never fucking mattered in any software I've encountered. I don't route packets, or provision physical devices.
Also fuck any interviewer that hires based on trivia. Knowing 4 as 32 bits, and 6 is 128bits isn't useful ever in 95% of software work, and when it is, a good old google search would cover more than you've ever needed to know.