Live data from Hacker News

Not only coders are hard to recruit

blog.sysadminsarena.com

11–20 of 73 posts

Re: Not only coders are hard to recruit

#11

There's been a lot of criticism of hackerrank.[1][2] Are you doing anything to make sure your service gets more respect? [1] - https://news.ycombinator.com/item?id=12825953 [2] - https://news.ycombinator.com/item?id=12667174&source=techsto...

I don't think I would enjoy HackerRank as an interview, but as a user I do enjoy being able to practice computer science problems.

Just wrote an answer above which i think is good for your concerns. What'do you think?

Re: Not only coders are hard to recruit

#12

Earlier quoted context omitted.

We are going to give real life scenarios based on the various roles you are testing with.(basicly a ssh login to the test machine) And we plan to asses the candidates way of solving the problems based on what commands and what process it uses to identify and solve the problem.

Please allow me my honesty but that's a stupid way of thinking about candidates and the roles. Or I do not get it. So you are basically going to judge the candidate based on what criteria ? If they use vi instead of cat to append to a file ? So decide what is the best way of solving the problem ? Or you give +1pt for using tail instead of opening the whole file in VI ? Are you aware of the fact that there are many ty…

When I used to work in OS support my actions were optimized for the assumptions of a default minimal install and being able to describe actions to a person of questionable knowledge over the phone and interpret what they would most likely try to read back at me. The certifications were along those lines too.. While the exact nature of the certifications was ridiculous and would be even more ridiculous in terms of judging a general user's skills, dropping an administrator on minimal installs with broken ttys, etc makes a lot of sense. If you can't recover a system when vi is not an option then you have a problem, if you spend a lot of time recovering a good term when you could have used tail, then you are also not ideal.

The only suggestion I would make is that a good tool is present and working then I don't expect a penalty. I expect tools to not be present accordance with standard minimalist setups and to pay extreme penalties if I need to call a package manager or move to a less minimalist install to complete the task.

Re: Not only coders are hard to recruit

#13
So this is to have a test VM they have to fix? Excellent! I heartily approve of this method for finding a sysadmin.

This is a thread where I talk about how we did this: https://news.ycombinator.com/item?id=8332104

We used to use it a lot - a trivial Java webapp running in a slightly misconfigured Tomcat with a slightly misconfigured Apache in front on a slightly misconfigured Unix box - though it's fallen by the wayside because we never quite get around to the faff of setting up a slightly broken test system for them. So having that as a service would be pretty good.

If this is what you're doing: I suggest not just keystrokes, but that they keep a log of what they're doing and thinking. Because we never expect them to fix everything wrong with the box, but we do want to know how they approach it.

Re: Not only coders are hard to recruit

#14

Earlier quoted context omitted.

I don't think I would enjoy HackerRank as an interview, but as a user I do enjoy being able to practice computer science problems.

Just wrote an answer above which i think is good for your concerns. What'do you think?

(Speaking as a coder here, although I've also done sysadmin through most of my 20 years of working in the industry).

This would be quite nice. Going through the job searching process at the moment, the "aptitude tests" etc that I've seen are very good at blowing cobwebs off my obscure analytical skills, which I rarely if ever use, yet fail completely at getting any gauge of my ability to get every day stuff done in a clean, smell-free way.

As a result I'm now doing kata training on Coderwars and am getting more used to this style of testing. It's actually good fun, and I think it'll help increasing my ability to just spit out code. In real life scenarios though, most of the time is spent analysing a problem or process flow.

Re: Not only coders are hard to recruit

#15

So this is to have a test VM they have to fix? Excellent! I heartily approve of this method for finding a sysadmin. This is a thread where I talk about how we did this: https://news.ycombinator.com/item?id=8332104 We used to use it a lot - a trivial Java webapp running in a slightly misconfigured Tomcat with a slightly misconfigured Apache in front on a slightly misconfigured Unix box - though it's fallen by the ways…

Hi David, thanks for your thoughts. Very useful the thread provided. And YES, this is what we are doing.

Keystrokes is just one of the metrics we are about to collect and analyze. We are also thinking about number of commands wrote, how many were correct, how many wrong, also a log of the entire test. In future phases, we may take into consideration pair working or capturing a movie of the test.

What other ideas of relevant metrics do you have?

Re: Not only coders are hard to recruit

#16

Earlier quoted context omitted.

We are going to give real life scenarios based on the various roles you are testing with.(basicly a ssh login to the test machine) And we plan to asses the candidates way of solving the problems based on what commands and what process it uses to identify and solve the problem.

Please allow me my honesty but that's a stupid way of thinking about candidates and the roles. Or I do not get it. So you are basically going to judge the candidate based on what criteria ? If they use vi instead of cat to append to a file ? So decide what is the best way of solving the problem ? Or you give +1pt for using tail instead of opening the whole file in VI ? Are you aware of the fact that there are many ty…

We are aware that there are more ways to skin a cat. I think it's fair to evaluate a candidate based on wether if he can solve an issue or not and the amount of time it took. I agree it would be stupid to score based on individual commands and we didn't plan to go that low level. But we plan to count the number of commands with typos or wrong parameters. Don't you agree this would be a way to differentiate between 2 people that solved the same problems in the same amount of time?

Re: Not only coders are hard to recruit

#17

There's been a lot of criticism of hackerrank.[1][2] Are you doing anything to make sure your service gets more respect? [1] - https://news.ycombinator.com/item?id=12825953 [2] - https://news.ycombinator.com/item?id=12667174&source=techsto...

Glad you asked that. As i saw in the treads mentioned by you, the common problem is that the tests are more about theory, and less about practice. Which is true. Sometimes, in interviews, you are asked about algorithms that you studied in college and never used before. It's very difficult to score high in this tests. We propose to eliminate this gap by having real job, day to day, scenarios like: install apache, mysq…

Those are pretty baseline things that get automated away pretty quickly. More useful to me (as both a practicing devops type and a manager in that capacity) would be tests gauging ability to write bash scripts to do various things, or simulated problems that need to be diagnosed/fixed using command line tools (e.g., strace, netstat, etc.).

Re: Not only coders are hard to recruit

#18

Earlier quoted context omitted.

Please allow me my honesty but that's a stupid way of thinking about candidates and the roles. Or I do not get it. So you are basically going to judge the candidate based on what criteria ? If they use vi instead of cat to append to a file ? So decide what is the best way of solving the problem ? Or you give +1pt for using tail instead of opening the whole file in VI ? Are you aware of the fact that there are many ty…

When I used to work in OS support my actions were optimized for the assumptions of a default minimal install and being able to describe actions to a person of questionable knowledge over the phone and interpret what they would most likely try to read back at me. The certifications were along those lines too.. While the exact nature of the certifications was ridiculous and would be even more ridiculous in terms of jud…

I strongly disagree. We should not test edge cases and specific scenarios. We are trying to test the candidate and his abilities in daily tasks. If I say I use vi instead of "commands" I will probably solve most of the "text" editing tasks faster than an admin that only knows how to get around using commands.

I can come up with tons of scenarios when where you do not really know the internals you can get stuck easily. Like if I do chmod -x on the chmod binary. Does it prove anything if the candidate is not able to solve such task ?

Re: Not only coders are hard to recruit

#19

Earlier quoted context omitted.

I am not sure you can do this I believe sysadmin/sre/devops person wears too many hats. What are you going to test ?

We are going to give real life scenarios based on the various roles you are testing with.(basicly a ssh login to the test machine) And we plan to asses the candidates way of solving the problems based on what commands and what process it uses to identify and solve the problem.

1. How exactly are the sysadmins graded? (because in the end, let's be real...this tool will most probably be used by HR folks to filter out candidates and they'd not care too much if you send over a screencast/replay of what the candidate did)

1.1) Sys admins generally have their own set of tools (which would be customized per company I guess)...would these be installed by default? (I'm assuming you are provisioning docker containers / candidate / test and then destroying them after use).

1.2) I've used the ones that are sent for developers and it's been a pretty terrible experience at best (it's buggy, won't accept valid code etc.). If this is the case for sysadmins, it's even more worse (but then again, I guess you can put a spin on it and claim it's for the best as they'd have to deal with unpredictiability).

2. How will different technologies be integrated to test candidates on? (for example, testing knowledge on multi node kubernetes cluster and so on).

Re: Not only coders are hard to recruit

#20

Earlier quoted context omitted.

Please allow me my honesty but that's a stupid way of thinking about candidates and the roles. Or I do not get it. So you are basically going to judge the candidate based on what criteria ? If they use vi instead of cat to append to a file ? So decide what is the best way of solving the problem ? Or you give +1pt for using tail instead of opening the whole file in VI ? Are you aware of the fact that there are many ty…

When I used to work in OS support my actions were optimized for the assumptions of a default minimal install and being able to describe actions to a person of questionable knowledge over the phone and interpret what they would most likely try to read back at me. The certifications were along those lines too.. While the exact nature of the certifications was ridiculous and would be even more ridiculous in terms of jud…

Thank you for your input and suggestions, highly appreciated.
Post reply on HN