However I would not ask a candidate or more specifically I would not show him the code for fork bomb. I would ask him what fork bomb is or demonstrate it on some demo VM and ask him how would he prevent himself..
There's too many technologies already. I would not ask specific questions about the staff we use but instead a very generic ones.
Like really it's almost impossible to be a specialist these days and you can pretend your company is full of rockstars and works on the next big thing but in fact you are just bunch of posers.
Nobody really knows everything to the detail. I really hated when my colleague asked new people really deep stuff about Puppet and then we have switched to Ansible and half of the team was clueless and had to learn along the way. That's what good engineers do. They adapt. They learn the concepts and focus on delivering a good service. They do not memorize man pages.
When it comes to scripting / programming do not print scripts on paper and make the candidate to describe you what is it for or find a bug / mistake just by reviewing the paper. It's insulting. Especially if you do not follow any conventions or your code is not idiomatic.
Also I would never ask a question "What does the following command / parameter do". These are not good questions. Ofc they are asked often during interviews but are just plain stupid.
How would you display last / first 10 lines of a file ?
How would you remove an X string from a line / row of text ?
However I would not ask a candidate or more specifically I would not show him the code for fork bomb. I would ask him what fork bomb is or demonstrate it on some demo VM and ask him how would he prevent himself..
There's too many technologies already. I would not ask specific questions about the staff we use but instead a very generic ones.
Like really it's almost impossible to be a specialist these days and you can pretend your company is full of rockstars and works on the next big thing but in fact you are just bunch of posers.
Nobody really knows everything to the detail. I really hated when my colleague asked new people really deep stuff about Puppet and then we have switched to Ansible and half of the team was clueless and had to learn along the way. That's what good engineers do. They adapt. They learn the concepts and focus on delivering a good service. They do not memorize man pages.
When it comes to scripting / programming do not print scripts on paper and make the candidate to describe you what is it for or find a bug / mistake just by reviewing the paper. It's insulting. Especially if you do not follow any conventions or your code is not idiomatic.
Also I would never ask a question "What does the following command / parameter do". These are not good questions. Ofc they are asked often during interviews but are just plain stupid.
How would you display last / first 10 lines of a file ? How would you remove an X string from a line / row of text ?
and so on...