Hacker News new | past | comments | ask | show | jobs | submit login

Some really great advice within that forms a foundation for the narrative. I can really appreciate the diligence and apparent 'no hard feelings' kind of pragmatism. I especially liked the closing part:

>If you fail 10 interviews in a row, go for the 11th interview. But take a look at all the variables, and see if there’s anything you can do differently to improve. Take the pressure off, and work through problems routinely to keep your muscle memory in shape.

That reminds me of being in 'game shape' as I call it for playing and soloing - standing around thinking about notes to play doesn't come off nearly as fluid as being so practiced as to get into the groove and run with it. Good parallel. Nicely framed conversation, glad to read it.




Yeah. When I was job hunting ~3 years ago I knew I was going to have to do a lot of whiteboarding problems. I only had two 2 years of coding experience, and for the last six months I had been freelancing, which doesn't often encourage algorithms. I was working through "Cracking the Coding interview" and "programming interview exposed" but I was worried.

So I sent an email to everyone in my coworking space that I'd put a six pack in the community fridge for every person who did a mock whiteboard interview with me. Some of them came with their own problems, some of them picked problems from websites or the books that I hadn't done yet. Some of them were doing it as a favor, and some of them wanted to practice interviewing people. I got five mock interviews over a week, many of them with strangers. Best 40 bucks I ever spent. (I nailed the next real interview I had and got a job offer.)


That's a damn good idea. I completely agree, a job interview is something that you need to practice to be good at. Just doing code exercises isn't enough. Having someone do a real interview is the best way.


This is a brilliant idea




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: