13

The worst question was asked by me once. At least I guess it must have been the worst question for an applicant. She applied for a job as Ruby dev and gave her knowledge of the language a solid 5 Star rating. Something I wouldn't give myself unless my name is Mats. So I prepared some really nice questions about metaprogramming and the object model and stuff. As a warm-up I decided to go easy on her and asked her something simple: "how do you define getters and setters in Ruby?" Which is like one of the first things you learn but not too simple. She got a really red face and told me she didn't know. In the end I had to learn that she never even really programmed Ruby but only wrote some method calls in a file she named .rb and she didn't even know what an object was m(

Comments
  • 0
    ouch. I always start by asking a few simple questions, to get a feel for the technical knowledge of the dev.
  • 2
    @magicMirror too bad, when the simple questions already ruin the party. And I was really looking forward to this interview, too. Ruby devs don't grow on trees here in Germany.
  • 0
    They don't grow on trees anywhere. from my close encounter with ruby, and the ruby devs I worked with.
    Most big corp backend is java, and startups choose ruby, node.js, or python. I wonder if there are stats for that?
  • 3
    Ruby is 💖
  • 0
    @magicMirror I think that u forgot PHP. Atleast in Central Europe I've seen it in like 90% of job advertisements for web developer position in startups. Remaining 10% were server-side js.
Add Comment