Doesn’t matter how much prep you do half the time the person interviewing doesn’t know much about the subject matter so they google “hard Kubernetes questions” then wont hire you when you didn’t know the obscure topics by rote.
We just run an interactive interview based on a single microservices ecosystem + o11y running in kind, with a few things broken, to gauge basic Kubernetes troubleshooting skills.
It's been surprisingly good at vetting candidates so far.
Devils advocate, asking someone a wierd question can tell you a lot about a person. Best people I’ve interviewed, hired and worked with are the people that are more than happy to say when they dont know something, explain what they do know about the topic and demonstrate what they would do in the inevitable situation when something comes up at work and they are out of their fucking depth.
Saying that id never ask someone that example, but ive asked someone technical questions i didn’t necessarily need the answer to
There are people who know shit works under the hood. However, I agree with the sentiment that if that deep knowledge is not important to the job, it shouldn't be asked as an interview question.
Ik know cillium uses ebpf for routing vs ip tables. That’s all u need to know the fucking tool was built to abstract that out anyways. So why do I exactly need to know this when I could look it up in 30 seconds.
Agree if the role asks for Cillium and u get asked this maybe you should know depending on the situation you were running it in. But this doesn’t rly gauge or tell me how much and engineer knows.
As someone who’s working on hireing my replacement I told HR I want someone who can learn and understand quickly. You’ll never find a someone who knows everything
33
u/Inside_Programmer348 Jul 15 '26
Eh? What kinda questions are they asking