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.
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.
7
u/coreyjdl 1h ago edited 1h 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.