5 ms·
To be frank, I have never gotten a job I've really enjoyed which required me to know my algorithms in an interview. Such questions are a negative indicator whic
by falcolas 12y ago
To be frank, I have never gotten a job I've really enjoyed which required me to know my algorithms in an interview. Such questions are a negative indicator which indicate to me that the interviewer is more interested in showing off than getting things done.
The only practice I keep up with is talking to people. Being able to maintain a conversation with a non-technical person for more than a minute will has furthered my career more than any amount of algorithmic knowledge.
- joezydeco 12y agoThis is great advice. One good way to start is to take a project that you've been heavily involved with and create a small presentation out of it. Draw up the architecture in Google Docs, keep any confidential stuff out of it, add some screen captures. Print it out and keep it in a small binder. Practice explaining the project in under 5 minutes. Try it out on some friends that might not understand the tech completely. Rehearse questions and answers that people might ask. Being comfortable speaking like this with management and future coworkers has worked well for me, more so than FizzBuzz on a whiteboard.
- jtheory 12y agoThis is excellent advice specifically because it's not about "prepping for interviews"; honing these skills simply makes you more valuable to any company, and it's an aspect of your capabilities that you can show off in a decent interview process... so take advantage of that.
- joezydeco 12y agoJust to add to my comment above, I recently did a round of hiring for a new embedded engineer. I had a handful make it to the in-person interviews. When asked about previous projects, almost every single one waved their hands and tried to explain how they glued widget A to framework B and <magic> got product C. Exactly one candidate brought materials to show things he had worked on and how the skills he used in those projects applied to the work we were doing. You could see eyes light up when he was asked "so, tell us about <project z>" and he smoothly pulled out some pages to show. He blew everyone else away and got the offer.
- collyw 12y agoDid you ask him to bring stuff in advance?
- joezydeco 12y agoNope. And I always carry materials on my interviews even if I'm not asked to. It's not much more work to carry a small 3-ring binder along with the notepad and resume folder I typically carry to an interview. (Protip: always carry extra copies of your resume to interviews. There's always someone that is missing theirs and it's nice when you hand them an extra copy)
- jhildings 12y agoThis is a good advice, but how about company secrets and things like that? Of course it varies by country, but is it legal in the US for example to create this kind of presentation about a adnetwork with user tailored ads you created for example?
- joezydeco 12y agoLike I said above, showing confidential material is bad form. But in my experience you can show a lot without exposing secret algorithms or formulas.
- hackerboos 12y agoI've flunked almost every interview where I've been asked to solve a fiddly math problem with an algorithm. I've always sucked at these types of questions. I ended up buying Gayle McDowell's book 'Cracking the Coding Interview' to get me through my next career move, but since then, I've taken a job that didn't involve getting through a coding exam. It's these types of questions that would stop me even applying for a job at Amazon or Google. I know they'd come up and I know I'd flunk them, so I don't bother. Funny thing is, nobody has regretted hiring me.
- fweespeech 12y agoYeah, the worst part is companies like Amazon will expect you to eat multiple days of PTO to go through their screening process. Hell, I feel this way even tho they have recruiters trying to fill quotas that contact me about jobs at Amazon :| Why would I bother? It is like they only want to hire unemployed programmers with plenty of time on their hands to prep.
- a3n 12y agoI've noticed a trend over the decades (yep, decades) where people and corporations are moving away from subjective evaluations to safe, who-could-argue-with-that objective evaluations. If someone doesn't know how to evaluate a candidate, or doesn't feel safe or comfortable, well ... nobody gets fired for asking about algorithms.
- eli_gottlieb 12y agoAmazon and Google's hiring processes appear designed to bring in large numbers of very clever undergraduates finishing their bachelor's degree and looking for a first job -- and little else. (For the record, I've gotten an offer from Amazon before, but never from Google, and Google seems to make their interview process noticeably harder in terms of how much of your undergrad algorithms and data-structures curricula you have to remember to do the interview. Strangely, my lack of obsession with these subjects hasn't ever stopped me getting anything done in real life.) Alternative hypothesis: these companies believe that the ability to answer undergrad exam questions about general algoriths-and-data-structures can act as a kind of intelligence quotient for programmers, giving a strong measure of general intelligence with low false-signal rates, and they are hiring for (what they believe to be) raw cleverness because they simply don't believe domain expertise or specialization to be real, exploitable phenomena. This alternative has the advantage of neatly explaining their allocation processes, too. But on the other hand, believing these to be disjoint hypotheses requires me to assume that undergraduates have never actually specialized by the end of their degree.
- soham 12y agoMaking connections and building a hiring network is awesome advice, that many many developers miss. Thank you. I run a company (http://interviewkickstart.com http://interviewkickstart.com) in Sillycon Valley, that helps developers brush-up their data structures, algorithms and system-design skills for interviews. Previous to that, I worked at a very fast growing startup in the valley, where I had joined early and had the privilege to contribute to multiple iterations of their technical interviewing processes. Here is the thing: not a single employer is happy with their interviewing processes. They do it not because it's the best process ever, but it's the least evil for demands on the business, for their size, stage and culture. Every single process has its flaws. The core reason most companies ask data-structures/algorithms and such, is because that's the lowest common denominator of knowledge between the interviewer and the interviewee. How is that? That's because the field of programming is so vast, that candidates apply to ANY available job, whether that fits their experience or not. e.g. If you worked on Payment systems and you apply to a Deployment systems role, what am I, as an interviewer, going to ask you about? I can't ask you about Payment systems and JUDGE you on your knowledge of 5 years in 45 minutes especially when I have not worked in it myself. And I can't ask you about Deployment systems because you haven't worked with them enough in the past. I hence fall back to the lowest common denominator of knowledge between us, which is, most likely, something in the CS programs we attended. Then why ask algorithms, of all the CS that we may know in common? Because that needs the least amount of specific knowledge, compared to things like compilers and systems. Algorithms is a proxy to your problem-solving skills. An unfortunate proxy, but the best available among the things we know in common. If you however end up applying to the exact SAME thing you have been doing, they should not ask you all the algo shit. They should ask you exactly what you've done and how you've done it and judge your experience off of that. After all, interviewing, by definition, is a verification of your experience. But reality is, that you probably don't want to continue working in what you have been working in. Because you want a change and because frankly, CS is just so vast and cool opportunities exist anywhere. Data Structures and Algorithms hence, become the best equalizer/normalizer among anyone who wants to do programming. Also, business pressures are such, that as a company, I just cannot spend more than a day or two evaluating someone's fit. Otherwise I'll take my team's attention off of more important things e.g. the holiday e-commerce season, or I'll be second to the market with a feature or I'll miss that big conference where I wanted to launch that product. I'll much rather hire an okay developer with a short interview process and hit that deadline that's going to keep my business afloat, than wait for a unicorn by a thorough evaluation. And when I can only give a short amount of attention to you, I will fall back to the easiest and most prevalent method of interviewing, which is what you see today. In conclusion, I don't think it helps agonizing over interviewing processes of companies. It's best to remain prepared. Keep solving problems, keep interviewing. And when you need a booster, just come to us ;-) http://InterviewKickstart.com http://InterviewKickstart.com.