[truetuna]

I've had my fair share of bad interviews too. Just recently I was interviewing for a full stack position with a company that tried to get me to recite "what happens when I type google.com into my browser". I asked them where they had gotten idea from and showed them this: https://github.com/alex/what-happens-when. They decided ask me another question soon after.

Sometimes the questions aren't even related to data structures or algorithms. I'm OK with those because at least you can somewhat prepare for them. I've once had an interviewer ask me obscure questions about Netscape 6 (this was 2016 btw).

> I much prefer “homework” projects, even if they involve me working “for free”, because I feel like they ask for actual programming skills rather than the “guess the algorithm” lottery of phone screens and whiteboard coding.

Me too but when you're interviewing with 3+ companies at the same time while working at your current job, it gets difficult. There was one time where I had spend my Saturday afternoon maybe 6-8 hours completing their "homework" project. I got a call back from them a few days later for a follow up interview and they flat out didn't even bother to ask about the project I had completed for them. What was the point?

Tech interviews suck.

[odonnellryan]

> I got a call back from them a few days later for a follow up interview and they flat out didn't even bother to ask about the project I had completed for them. What was the point?

It's worse when they give you an easy project that takes you ~30 hrs to complete, they state it "doesn't have to be finished," then disqualify you because "why didn't you use a graph database for this problem?"

Oh well. Same company was using Mongo+Node on a new startup from when they were still in year one. Wish them the best..