Earlier quoted context omitted.
The idea of screening for a software engineering gene is patently absurd. In an ideal scenario, we screen for the ability to do the work the job requires. In the normal scenario, we screen for some mix of that and the ability to apply cookie-cutter techniques to (hopefully) novel problems in the space of ~45 minutes. Some companies also ask you to do a sample practical problem either on site or on your own time. None…
To imagine that genetics do not play a role in intelligence (or any talent) is horribly naive, otherwise we could teach our dogs to program.
Stanford CS9: Problem-Solving for the CS Technical Interview
141–150 of 292 posts
Re: Stanford CS9: Problem-Solving for the CS Technical Interview
#142This is what I was afraid of. I always thought interviews were something where you present your abilities, experience and knowledge. It should not be something you "prepare" for because then you're not showing off your skills, instead you're just regurgitating what you are trained to do. I do somewhat blame the whiteboard culture, but I guess that's the one that has given the best results so far. I've no doubt that i…
The idea of having a whole class on how to solve interview whiteboard problems (a skill that is, at least where I work, not very relevant to doing your job) is terrifying.
https://www.edx.org/course/how-win-coding-competitions-secre...
Re: Stanford CS9: Problem-Solving for the CS Technical Interview
#143While the system is admittedly problematic, does it really come as a surprise that for extremely competitive jobs at the entry level, such artificial hurdles need to be used to filter the plethora of black-box applicants? I can't speak to more senior roles, but for entry-level, this only seems like a natural (and practical) response. It happens everywhere, not just CS:
For any competitive school admissions, SAT/LSAT/MCAT what-have-you are all poor indicators of student performance, and boil down to trainable tests.
In finance (both quant finance/and positions like sell side banking, private equity), people constantly practice math/financial modeling/accounting, for interviews. Many of the more selective quant shops (for undergrad hiring, I should mention) have much more difficult problems than MS/GOOG/AMZN technical interviews, and I would argue the type of competition level math/probability are just as unrelated to their jobs.
In management consulting, people spend hundreds of hours practicing for case study interviews. Just search consulting interview prep, and you'll find an egregious number of prep companies.
Some people brought up law and medicine. First, I don't think the grueling nature of the medicine certification is even close to what it takes to be an entry level developer. In law, while "technical" interviews are rare, often times employers filter you by much cruder means: pedigree (both the school you attend, and at top echelon law firms, clerkship status, and top-top grades within those schools). Is that any better?
The common denominator here is the high demand for all of these schools/jobs, and the problem always seems to come down to, how to optimally recruit -given- resource constraints. Maybe I'm cynical but almost any reasonable entry-level interview can be "gamed" or trained for, and most firms are either small and lack resources to extensively evaluate their applicants holistically, especially if they're only in undergrad, or they are large and get way too many applicants, so some proxy is necessary.
Re: Stanford CS9: Problem-Solving for the CS Technical Interview
#144Earlier quoted context omitted.
Indeed. If it was illegal to work as a programmer without a Master’s degree in Computer Science with a GPA above 3.0 the interview process would not look like the current one.
The industry wouldn't look the same, either: it wouldn't be nearly as profitable or widespread as it has become, and nobody but CS academics would care about it.
Re: Stanford CS9: Problem-Solving for the CS Technical Interview
#145I think this is terrible. I feel there are many good engineers that can't possibly compete for decent jobs in tech companies because they haven't spent 6-12 months reading cracking the code interview, doing this Stanford course, practicing mock interviews in crowdsourced websites, getting their leetcode rank up, attending bootcamps where they pad their githubs and practicing any single interview question they can scr…
Re: Stanford CS9: Problem-Solving for the CS Technical Interview
#146This is what I was afraid of. I always thought interviews were something where you present your abilities, experience and knowledge. It should not be something you "prepare" for because then you're not showing off your skills, instead you're just regurgitating what you are trained to do. I do somewhat blame the whiteboard culture, but I guess that's the one that has given the best results so far. I've no doubt that i…
I’m also working on the space with www.onsites.co to solve how broken the interview experience is.
Re: Stanford CS9: Problem-Solving for the CS Technical Interview
#147Earlier quoted context omitted.
FWIW, preparing for interviews is standard practice irrespective of the industry.
Sister is a travel nurse. She does not prepare for interviews and typically has several a year. Her entire interview process goes: call the agency and tell them she is looking for a new position, have one to several 30-45minute phone calls with hiring managers at the hospitals she is interested in (she actually took one once in the middle of a wine tasting - and got the job), then wait to hear back. That's what it's…
Re: Stanford CS9: Problem-Solving for the CS Technical Interview
#148Off-topic probably: This timing! I'm going to interview on Tuesday with a startup in SF. I've spent better part of last 3 weekends studying and solving DS&A. Any advice from HN on what could I do in ~14 hours of prep time?
Re: Stanford CS9: Problem-Solving for the CS Technical Interview
#149Earlier quoted context omitted.
This kind of prep has been common place in other desirable fields for many years. Law, medicine, finance. They all have books, classes, etc. that you can take to prepare for interviewing, taking the bar, mcat, etc. Compared to college admissions, the CS interview process looks downright sane.
They all have prep for everything but interviewing. An interview to get a residency or a junior assistant position will be much more about your credentials and a history of your performance.
Re: Stanford CS9: Problem-Solving for the CS Technical Interview
#150Earlier quoted context omitted.
It’s 1 pass/fail credit out of 180 to graduate. The course looks as much like how to job hunt as anything else. (Resume writing, etc)
In design school, we had one class which involved things like developing your portfolio, learning how to present yourselves to companies, interviews with Creative Directors, etc. Given that technical interviews a common method of partially evaluating engineers/developers, it doesn't strike me as particularly odd for a practical course to exist that helps students maximize their ability to get a job. As you mentioned,…
To take an absurd example, imagine if for some reason Law firms started requiring an Irish Stepdancing component to their hiring process. I'm sure broadly speaking, you'll see the most dedicated lawyers practicing away on nights and weekends, and the best Law Schools with the best students will hire the best Irish Stepdancing teachers. But at the end of the day, Irish Stepdancing has very little to do with practicing Law. Similarly, if solving stupid whiteboard problems has so little to do with being a Software Engineer, that they can't be learned in the 40+ other courses or internships/PT work, that a student will have to do in their time at University, then the question is why are they even done?