DEV Community

Discussion on: I failed an interview because of an algorithm

View post
Collapse
 
leastbad profile image
leastbad •

Worth pointing out that in Ruby,

["1.3.0.9",
 "0.2.0",
 "3.1.2",
 "0.1.6",
 "5.0.0",
 "3.3.3.3",
 "3.3.3.3.3",
 "3.10",
 "0.2.0"].sort
Enter fullscreen mode Exit fullscreen mode

returns

["0.1.6",
 "0.2.0",
 "0.2.0",
 "1.3.0.9",
 "3.1.2",
 "3.10",
 "3.3.3.3",
 "3.3.3.3.3",
 "5.0.0"]
Enter fullscreen mode Exit fullscreen mode

I'm sorry that you had a frustrating experience with your interview process, but my overwhelming gut reaction is that you don't actually want to be working for a company that thinks high-pressure algo regurgitation is a reliable litmus for quality dev team candidates.

Collapse
 
leastbad profile image
leastbad •

BTW, I pointed out the Ruby example not to be an ass but to make the specific point that it's a stupid interview question. Unless they are hiring you to live code language-level algos on Twitch, why not spend the interview time talking with you about how you solve problems?

Their loss.