81–83 of 83 posts
Earlier quoted context omitted.
Yes, and I am surprised that this wasn't at the start of the article instead. Very few companies have interview processes that test for the actual skills required on the job. Certainly not any of the big 4.
what are the big 4 - amazon, facebook, google and microsoft? apple doesn't qualify?
>Cramming may get a candidate a job. But they won’t succeed at the job if they don’t have the skills and experience needed. Nothing any of us can do about it. It would mean avoiding all mid size/larger tech companies. I am looking for a change, and I am preparing heavily. Algos, data structures, design stuff. >Granted, all of this implies that companies have actually created an interview that actually tests the skill…
Can I ask you to share info on what you're using to study for the design stuff?
The only other resource is questions from actual interviews that people put up. To be honest, I find it hard to prepare for this part too. Algos are easy, once you do crack the coding interview and a few online questions.
Quite simply it is because performers: sports stars, musicians don't have the time to think about how to perform - it has to be "muscle memory".
In an interview, a candidate needs to have the muscle memory to do the work in a timed manner. I have had candidates say they know Java and then not demonstrate their knowledge. (They might indeed know Java well - but have been out of practice!)
I suspect the OP is a very smart person, who can "muscle" his way through most interviews. Most developers are mere mortals and can not pull it off. This is the danger of listening to exceptional people - their techniques do not apply.
----
As for preparing the candidates by letting them know the questions, as an interviewer, I want to judge the candidates based on their best performance. At my company we have a very practical approach to interviewing - it starts with no brainteasers.
And yes we are hiring for all levels! (reply if in the bay area)