hiring-without-whiteboards

This is a useful list https://github.com/poteto/hiring-without-whiteboards

Some permutation of this comment is made litterally everytime any coding interview resource is posted. I'm sorry man no cares that you and everyone who upvoted this comment are Super God programmers with 30 offers everytime they say they are looking who can afford to tell every company where they can stuff their interview. Us mere mortals are willing to do whatever it takes to get our dream gigs. These guides are largely targeted are getting into the some of the best, thus pickiest and most selective, companies in the world. And if getting on means being a dsalgo monkey in front of a whiteboard for a few hours so be it. Let us share interview tips in peace please. This "hurr durr technical interviews suck" but I have no real alternative and have never built a company nor seen any really flourish at the top without this is monotonous. Put

Wrong question - the right question is "which companies don't have the typical whiteboard interview". Mine didn't, and it's a regular software engineer job. Here's a list of some - never used it but was on here a while back: https://github.com/poteto/hiring-without-whiteboards

There's this list: https://github.com/poteto/hiring-without-whiteboards

Here's a list of companies that don't do this https://github.com/poteto/hiring-without-whiteboards I hope it's the beginning of an industry wide trend away from these types of interviews.

https://github.com/poteto/hiring-without-whiteboards/blob/ma... Hiring Without Whiteboards

If whiteboarding is not for you, this list was on HN few weeks back. https://github.com/poteto/hiring-without-whiteboards CircleCI is in there too.

Check out some of the companies here. They hire based on trial projects (mostly unpaid). https://github.com/poteto/hiring-without-whiteboards

I think the tide is turning against this type of interview. The industry is starting to notice how ineffective and stupid it is. The big tech companies don't care and will continue doing it because success hides all failures. When there's an endless flood of new college graduate applicants and near-monopoly positions bringing in billions of revenue, nobody cares if the hiring process is bad. They will care someday if those conditions change, but that's in the distant future. Most companies, especially small companies, are not in this position and should have a different process. It's becoming a competitive advantage, especially if a company is looking for senior engineers, to not have this interview process. For example, this list of companies was in a HN story a while ago: https://github.com/poteto/hiring-without-whiteboards The t

It seems many acknowledge that the Google process (and other similar ones) is very flawed with a high false negative rate, but it's considered ok because there's a flood of talent always applying to Google. Maybe this used to be true, but I don't think it's true anymore. It's very likely still true in the fresh graduate to early 20's age range of candidates. But at this point, senior engineers know what this process is about. And I think many are deciding to just avoid this process since it's very biased against senior engineers (who are rusty on DS and algorithms and don't have time to study it like a second job). So the flood of senior talent is probably less now than it used to be. But Google doesn't care. The main reason is, success hides all failures. They're still generating billions in revenue every quarter. Until those num

I'd rather work with the ones who actually care about the people they're solving problems for vs the ones who can write bubble sort with no reference material, which happens in the real world precisely never. Employers pay developers to solve problems, not necessarily to write the most efficient code possible. I get that it's a craft and it's good to understand what happens under the hood, but you can get pretty damn far solving actual business problems for people without having to care which brand of sort ES2016 uses. These skills in micro-optimizations / textbook CS don't help much with understanding customers and solving their problems at the end of the day, so they're really not that valuable for many business scenarios. I think that a lot of engineers in this industry forget that they're not generally paid to write the most efficient

also https://github.com/poteto/hiring-without-whiteboards

not saying these companies[0] wont ask these types of questions, but at least they wont ask you to answer them on a whiteboard [0] https://github.com/poteto/hiring-without-whiteboards related HN discussion thread[1] [1] https://news.ycombinator.com/item?id=13874026