Interviews are hard.
Fundamental attribution error. It was luck that they turned out to be a compatible work situation.
Granted, I think it was accidental on their part (ie: the person that interviewed me was newbie at Amazon himself and quite lost, but seemly the person that was going to interview me had a serious problem of sorts and could not do it)
I really don't know where to start with your comment. All I can suggest is that you sit in on about a dozen interviews by someone who actually knows how to interview and learn from that process. The thing about interviewing is that it is really just about due diligence. You are verifying that what someone represents on their resume is likely to be true. I think it's great that you are passionate about algorithms and various Sieves. You are a piece of a puzzle in a team. Someone who loves algorithms will pair well with someone who loves standard CRUD, as well as a UI designer. You are not looking for someone who knows exactly what you do plus more, you are looking for a team member.
Interviewing on "what you'll actually be doing" is also problematic, since most work is simple stuff that won't demonstrate the difficult edge cases.
Why not let your inferior-sounding candidate handle all of the CRUD and you can tackle those fun edge cases? For hacker news, I'm not sensing a lot of hacking going on here.
I am 100% positive that I can ask someone 10 questions that they don't know the answer to, and subsequently make them look like a fool. I can do this to PHD's, it's not hard. Get over yourself and start looking at candidates as potential team members, rather than opponents or competition.
Like, the question itself is boring and cookie cutter. Why not implement a linked list or a tree in SQL (much more interesting for everyone)? Or a simple query language in JavaScript (a bit more practical)? Or tell have them do a code review of a simple webapp, have them critique it, then have them refactor it with you (much higher signal overall question)?
If your goal with an interview is to see how much bureaucratic bullshit a programmer is willing to put up with, by all means have them write linked lists. Have them write 5, one for each person interviewing them. If not, think about what you're trying to figure out about the person and craft the questions to suss out who it is you're talking to. "Program a linked list" is uncreative, and won't let you know very much.
Another YC company:
Stopped reading here.
To reiterate my second sentence: He was looking for a company that was too good to spend interview time on a question containing low signal.
In your case, why not ask about linked lists, and then ask why in a CRUD app the models are ending up in a mixed up state when you add a second application server?
As I mentioned to you in my initial apology, we had a fire drill. That being said, the tardiness was inexcusable, and I talked to the developer about that.
Regarding our interview questions, they were meant as an "initial screen." We do ask more practical questions in person. However, we figure that most smart software engineers can write a linked list or prime number solver.
I had a phone screen with 500friends recently. They were late calling me, and the person I was scheduled to talk with wasn't even on the call. They had pulled some poor engineer off of whatever he was doing, shoved my resume in front of him, and said "go".
The list of things that our "interview" contained:
#6 was what really got me. It was literally, "Hi this is <x>, we're out of time, click."If you advertise a position as requiring a certain set of skills, then ask prospective employees about those skills! Go through their experiences and see if they're a good engineer outside of the narrow scope of "solves logic puzzles well". You might be surprised that someone who doesn't normally write linked lists in javascript or implement 2500 year old prime-solving algorithms on a weekly basis actually has skills and experience to contribute.
My personal recommendation for anyone considering 500friends is to skip over them. There's much better companies more deserving of your time and consideration, and you'll certainly be treated better.
## Just to add on, I don't have a problem with logic problems. But too many people only ask them and don't do real interviews. Yes, I can do linked lists in javascript. Does that tell you anything useful about what kind of engineer I am? No, it doesn't.