21 ms·
Granted, there are a lot of bad tech interviews out there (asking about algorithms that nobody ever uses) ... but I do not understand this. Imagine someone's b
by crazygringo 13y ago
Granted, there are a lot of bad tech interviews out there (asking about algorithms that nobody ever uses) ... but I do not understand this.
Imagine someone's being hired for a front-end position, and we don't have months to get them up to speed.
I'm going to ask them to explain how a closure works. How they deal with AJAX. What they think about "!important". Things to be careful about with floats. How CSS precedence/specificity works. Give them an example webapp idea, and ask how they might architect it.
None of these are gotchas. All of them are directly applicable to the work they'll be doing. If you can't explain how closures work, then either you don't understand them (so you shouldn't be hired except for a very junior position), or you're bad at communicating/explaining (which, on teams, can be equally bad).
The author says "Other times I just froze on topics that I know very well." Maybe somebody can explain this better to me -- but if you freeze up in interviews, are you also going to freeze up in developer meetings? During code reviews? When you're in the room with clients?
If you freeze up in interviews, then it doesn't seem like the problem is with interviews -- the problem is with you freezing up, isn't it? I mean, if you can't answer basic questions about your knowledge in a one-on-one conversation, then that's a real problem, and not just in interviewing. (Obviously, some overly aggressive or unfriendly interviewers can be off-putting, but I'm just talking about "normal" friendly interviewers.)
- untog 13y agoMaybe somebody can explain this better to me -- but if you freeze up in interviews, are you also going to freeze up in developer meetings? During code reviews? When you're in the room with clients? Of course not. Interview situations are very, very different than the others. Meetings and code reviews are with co-workers, whom you know and trust. Meetings with clients could be nerve-wracking for other reasons, but they're unlikely to challenge your depth of coding knowledge. For my own personal example, I once interviewed at a place where the interviewer wrote up some HTML on a whiteboard, and then asked me to write out the CSS next to it that would turn it into a horizontal drop down menu. I don't work that way. I sit with my editor in one screen and a browser window in the other, and I piece together the layout as I go along. I assure you, it works just fine. But the interview situation was so far divorced from any every-day working situation that it felt very unnatural. I opted out of returning for the second round of interviews. The next place I interviewed I sat down, in front of a computer, with the interviewer, and we talked through code as I wrote it. I took the job.
- jaegerpicker 13y agoThat's the issue, it's much less important to ask someone to produce the code then it is to ask them how would they produce it. Being a Sr. Developer is less about what you know and more about how you work and think.
- blah32497 13y agoI guess it depends on the industry/clientèle, but meetings are fundamentally very similar. You are worried about what "they" will ask and if you will be able to answer the questions. With a client, it's about the software you're developing, with a interviewer, it's about software architecture or coding principles. In your example about HTML -> CSS I think you missed the point. It wasn't so much to check that you have something memorized, but to check your familiarity with the subject. Everyone sits with a browser while they code - I don't think that's a unique workflow. The thing is, if you've done this HTML -> CSS conversion a hundred times before, you wouldn't need to look it up. They're trying to gauge your experience level and if you've done this stuff hundreds of times before. I bet even a highschool student could find that with Google. EDIT: I think a more relatable example would be if the interview gave you a simple geometrical problem and you were upset you can't look up the Pythagorean theorem. You're not being tested on your ability to memorize the Pythagorean theorem per se - it's just that everyone is expected to know the Pythagorean theorem b/c it's so fundamental to the sciences. Super simple problem with no google are testing if you have domain familiarity and experience and are a metric of whether you will hit the ground running or not. They're not gauging you problem solving ability, or your ability to memorize crap.
- untog 13y agoThe thing is, if you've done this HTML -> CSS conversion a hundred times before, you wouldn't need to look it up. They're trying to gauge your experience level That really doesn't make sense, though. They were gauging my experience level by forcing me into a development process I have never used before? I don't think the best way to test if a person can do X is to take them far, far out of the environment in which they've always done X, and would be doing X if hired by you.
- 13y ago
- concernedctzn 13y ago> if you freeze up in interviews, are you also going to freeze up in developer meetings? No, the examples you listed are very different settings. An interview is far from a casual conversation, no matter the tone of your voice. An outsider is trying to prove themself to the group, they are under direct scrutiny at all times. One mistake can widely swing the interviewer's impression and cost them the job. No matter how many times you tell them to relax, certain people get into a feedback loop and it freezes them into inaction. Once part of the team being criticized for their code from other developers or clients is much less stressful, it's something they're ready to deal with. They are held with a certain level of respect for even being part of the group at all, and much less likely to lose the job/get fired in such a setting so the stakes are nowhere near as high.
- MitziMoto 13y agoNot to mention getting a job or not getting a job has the potential to be life changing. There are very few developer meetings or code reviews that will have such a huge impact on one's quality of life.
- YZF 13y agoI'll try to turn the table on you. Pick some particular technology that you don't hold in your head. three.js, Angular, Bootstrap, canvas, WebRT - whatever. I'm sure among those we'll find some details you don't have in your head right now and you will look up some APIs/details. Now I'll structure my interview around those topics which I happen to hold in my head since we use them all the time. I am not a front-end web developer at all. I play with some front-end stuff occasionally. But if I had to work in that area I'm sure I could pick it up very quickly and become very effective. I think you need to differentiate between things people can read up on a day and catch up and things that are more fundamental to how they think and learn.
- imsofuture 13y agoWhat you just described isn't a 'tech interview' though, it's a 'bad tech interview'.
- walshemj 13y agoI agree a few years ago I had to pick up Pl/1G to look after one of BT's Billing Systems took me all of a week.
- btilly 13y agoThe problem is that interviews are high stress affairs. Stress produces adrenaline. One of adrenaline's known effects is to prepare us for "fight or flight", meaning that higher order logic is shut off, digestion is shut off, our senses sharpen, reactions improve. This is great when you've got to climb a tree to get away from a tiger. This is horrible if you are trying to demonstrate your ability to function mentally. Different people differ in how strong this effect is for them in an interview. I'm unusual - I actually relax. Whereas the author of this article tenses up. And, of course, once you're tense and you notice that you just flubbed something obvious, then you tense up even more. Leading negative reinforcing cycle. And if you experience this in one interview, you'll experience it in the next. It does not matter how reasonable your questions are. If this is what someone faces, you do not get an accurate picture of how good anyone with interview anxiety is. And a lot of people suffer from this. The author of this article to an extreme degree.
- 10098 13y agoWell, jobs are high stress affairs too. We often have to maintain production systems that fail in cryptic ways at the most inconvenient times. I postulate that such situations are more stressful than solving some binary search tree problem on a whiteboard.
- georgemcbay 13y agoMost of my developer jobs haven't been particularly high stress. Perhaps there is some selection bias here in that if you rely on the usual high stress interview process for developers you increase the chance of working with people who create systems that regularly need hot patching in production. Sounds like a dreadful job to me, so I guess that if there is any truth to this speculation that I should be happy about the selection mechanism.
- jaegerpicker 13y agoNot at all. If I fix a production issue it's fixed. Either it is or it isn't. In an interview, I'm trying to impress another human. Who knows if I do a good job at that. Computers and their problems are simple in comparison. Judging a humans reaction, A LOT of developers are seriously bad at that. I'm pretty good at it myself but I hate it. I've had very few interviews that I didn't receive offers from but even I dislike the human part of interviews.
- SonicSoul 13y agoi've forgotten the most elementary stuff in interviews.. half the time if someone asks me what object oriented programming is, i can't remember basic tenets (encapsulation, polymorphism) yet i have no problem coding up a dependency graph pattern. whoever breezes through such technical interview, has either just had 20 interviews with similar questions and it's fresh on their mind, or studied specifically to become good at technical interviewing.. The latter is what i figured out that i had to do to stop being rejected from jobs i was clearly qualified for, just because i couldn't articulate something i never really had to articulate in the past.
- maxk42 13y agoJust replying to state my shock at how many people are defending poor interview performance. If you freeze up during interviews because it's "high stress" then maybe you need to practice going on more interviews until it doesn't bug you any more. When you're a developer -- especially at a senior level -- you need to be able to work well under stress. Hell -- you need to be able to do that for nearly any job in the world.
- j_baker 13y agoTrue. Sr developers need to be able to handle stress. However, I don't think an interview accurately measures a person's ability to handle under stress.
- justincormack 13y agoWhy? Interviews are an unnatural situation. I have hired people who did not interview well but were great at the work.
- thedufer 13y agoBut have you also hired people who did not interview well and weren't great at the work? The goal of interviewing is to avoid false positives, not to avoid false negatives.
- justincormack 13y ago"The goal of interviewing is to avoid false positives, not to avoid false negatives" - why is it? I can rectify a false positive, but if I miss greatness I might fail. If you hire people that others do not look at you can get people who are very loyal too.
- thedufer 13y agoRectifying a false positive is very expensive (cost of time they're not producing but drawing a salary, eating dev time for training, etc. + cost of firing), and firing people is a morale issue as well. Maybe this is from the perspective of a company that has no shortage of applications, but rejecting an applicant that would've been good costs basically nothing (dev time + travel if they got through phone screens). I didn't realize there was dissent on this topic. Care to elaborate? I initially picked this up from http://www.joelonsoftware.com/articles/fog0000000073.html http://www.joelonsoftware.com/articles/fog0000000073.html ("An important thing to remember about interviewing is this: it is much better to reject a good candidate than to accept a bad candidate.")
- MartinCron 13y agoif you freeze up in interviews, are you also going to freeze up in developer meetings? Are you really saying that your developer meetings are as high-stakes as job interviews?
- stephencanon 13y agoI can see it now: second prize is a set of steak knives. Third prize is you’re fired.
- dragonwriter 13y ago> Are you really saying that your developer meetings are as high-stakes as job interviews? Most certainly aren't, but some are potentially higher stakes (especially with smaller companies), since you and coworkers losing jobs you have -- which can be the price of getting things wrong -- is a bigger stake than you not getting a job that you currently don't have.
- ronaldx 13y agoPossibly, a senior front-end developer shouldn't be exclusively responsible for those higher stakes meetings?
- RyanZAG 13y agoWoah hold on - you're firing people for getting things wrong in meetings? Most people would be unemployed. Seriously though - if you're creating a high stress meeting like that in a company where people are at risk of getting fired then your culture is going to be terrible with people backstabbing each other so they look good at the next meeting. A company is a team - it's everyone's job to make sure the team is working by helping to fix any mistakes brought up in meetings, not firing people. You are not in competition with your employees. Your employees are not in competition with anyone either. Employees are hired by a company to work together to create things.
- dragonwriter 13y ago> Woah hold on - you're firing people for getting things wrong in meetings? Wrong outcomes for meetings have business consequences, which can include people losing their jobs. That's not necessarily "people getting fired for getting things wrong in meetings" -- indeed it generally shouldn't be that except in rather extreme cases of "getting things wrong" -- but it still means that people's jobs are on the line in the meeting and that there is extreme pressure not to make mistakes. Not because your boss will fire you because they don't like your answer, but because the market will punish your company -- potentially cost you and your coworkers their jobs -- if the market doesn't like the outcome of the meeting.
- mattmaroon 13y agoThe freezing up is a factor of anxiety, and anxiety can have any combination of triggers. What usually happens in an instance like this (I'm assuming it's similar to test anxiety) is that somewhere along the way, they froze during an interview, and the memory of that compounded the problem for the next interview, and so on and so forth. So the anxiety could be tied solely to tech interviews. There are plenty of students who are very bright, do outstanding jobs on their projects and homework, and otherwise get fantastic grades who then freeze up and get a C (or worse) on every test. Thankfully most real life situations don't mirror test taking, so often they're still high achievers. Most job activity doesn't resemble a tech interview, so it's quite possible for this person to not freeze up ever after you hired him. That said I'd still never hire this guy on the no false positives principle. I have neither the time nor inclination to contract with everyone who gets to that stage. But I rarely have projects for which a short term contractor could make much of a contribution. I suppose that's probably not the case for a lot of startups.
- mikevm 13y agoI also get very anxious during exams and always make silly mistakes. It saddens me to see some some interviewers on this thread that naively believe that the kind of stress a person feels during an exam (especially one where the tester is sitting in front of you and watching your every move) is the same kind of stress you might experience while trying to fix some problem in front of your computer.
- mattmaroon 13y agoWell, the thing about anxiety is that it's very irrational. Unless you've suffered from it or, like me, are very close to someone who does, it's very hard to understand. (I still have only a surface level understanding after a 10 year relationship with a sufferer.) It's easy to look at all of the things taking a test and fixing code in an emergency have in common and make the rational assumption that someone who is bad in one situation would be bad in the other.
- j_baker 13y agoTruthfully, I'm not certain I'd trust someone who can go through an interview without freezing up or having any similar problems. Confidence is a valuable thing, but only in moderation.
- nkuttler 13y agoI find it very bizarre that anybody would say something like this. Are you afraid of people who are more confident than you? Would that deter you even if they demonstrate superior technical skills?
- nknighthb 13y agoI take it you've never heard the word "overconfident"?
- nkuttler 13y agoPeople who don't freeze in interviews are overconfident according to j_baker, I got that, I just don't understand how he came to that conclusion.
- j_baker 13y agoI find it very bizarre that you don't see a need to keep out people who are overconfident. Are you afraid of people less confident than you? Would that deter you even if they demonstrate "superior technical skills" (whatever that means)? Confidence gives you the strength to get up and go to the interview. It tells you you're competent enough to get the job even if you freeze a couple of times. Overconfidence tells you you can't make mistakes. It tells you you have "superior technical skills", and that freezing up is only something that happens to lesser mortals.
- nkuttler 13y agoOh well, if you think that everybody who doesn't freeze up in a job interview is automatically overconfident this discussion can't go anywhere.
- imsofuture 13y agoExactly. I am a very vehement opponent of quizzy, obscure-knowledge or high-pressure tech interviews. That said, I think a good tech interview is irreplaceable. I like to work through a complex problem with the candidate, oftentimes I don't know the answer, nor do I expect them to be able to finish the problem (this is made very clear) -- I do expect them to sink their teeth in and think out loud with me. I would never hire someone who bowed out of a tech interview. If you can't handle thinking through problems in a collaborative, relatively low-stress interview -- you're not the kind of person I want to work with, sorry.
- dgesang 13y ago> relatively low-stress interview Is there such thing? I doubt it, unless you're interviewed by someone you already know well.
- wisty 13y agoThe article doesn't say "interviews don't work". It says "interviews don't work for me, so I get my foot in the door another way". He's not really arguing that they are a bad idea in general, but he simply suggests he'd do better with a test project. I think you're going too far the other way. Your argument basically seems to be "if you can't pass an interview, there's something wrong with you". Which is probably true. On the other hand, there's dozens of personality quirks (some of which are worse than getting nervous in job interviews) which wouldn't show up in an interview.
- ap22213 13y agoThis is weird. I would definitely fail your interview. Yet, at the same time, I've shipped over a dozen products, dozens of releases, consistently, to hundreds of thousands (if not millions) of people. I have a solid track record of clean, bug-free, efficient code. In 14 years of development, I've never had a bad review, and I've consistently ranked on the 'A-track' at all companies that I have worked for. I have low ego, work well with others, am a great teacher. Yet, my top priority is the craftsmanship of software: understanding user requirements and shipping great products that meet those requirements. My priority isn't being able to describe the intricacies of closures.
- bigtunacan 13y agoYou have to look at the candidate's overall performance in the interview; not the answer to a single question. Describing a closure is actually a great example of something many great software developers WON'T know based upon their prior domain experience. A strong Java or old school C/C++ programmer (yes I know C++11 has closures) may actually be an excellent candidate, but have no idea what a closure is. I would expect that a front end JavaScript developer, RoR dev, or anyone else "experienced" in a language with some functional support (Scala, Haskell, F#, etc...) should be able to explain a closure.
- jimmaswell 13y agoI can get anything I need to done in JS and I have no idea what a closure is. I've even written an emulator in it. Took me a little while reading to figure out what it is. Apparently it's just using vatiables in a lambda that are from a scope higher than it. I do that all the time, I just didn't know it had a special name. To be fair, I didn't know JS could do lambdas. I've only used them in C# and possibly Python. Well, I guess it's like a closure when you use functions as methods in objects in JS, since they can be defined with this.MyMethod = function(){...} which can then access the object's stuff.
- tonyarkles 13y agoYou've never passed a callback to a JS function?
- mncolinlee 13y agoNumerous people cannot remember the names of acquaintances they've lived and worked with for years. If you name a concept a programmer works with every day, it's entirely reasonable that that programmer does not remember the name because she knows the concept by its syntax, not its name. A lot of interview questions are also asked using synthetic examples that are not complete solutions. A good programmer will reach out and explore the full technical ramifications of the requirements instead of merely solving the problem. Knowing that complexity adds a whole new level of stress versus simply solving the easy problem the interviewer intended. A lot of people have trouble sleeping the night before an interview. It's more stressful than anything they will likely encounter at your company because it determines a major, unpredictable branch point in their future. Unless informed their continued employment is at risk over the outcome of a meeting, client meetings will not have the same degree of stress.
- dsrguru 13y ago> I'm going to ask them to explain how a closure works. How they deal with AJAX. What they think about "!important". Things to be careful about with floats. How CSS precedence/specificity works. Give them an example webapp idea, and ask how they might architect it. ... None of these are gotchas. You can do those in a half hour initial phone screen. Getting an idea of the applicant's general and/or domain-specific technical competence before you fly them out absolutely makes sense. I think what the author is criticizing, or at least the part of the author's criticism that I agree with, is the typical on-site interview that spends 3+ hours testing one's algorithmic knowledge and whiteboard coding skills. I do think that approach is vastly superior to doing nothing at all, but my personal experience suggests that testing the applicant's skills in a real life situation, after having vetted their technical knowledge/competence over the phone, seems more likely to identify strong engineers.
- lightcatcher 13y agoUnless you're literally looking for someone who can be productive within the first 2 or 3 days of hiring (which means your product/stack is fairly generic and you're hiring some specialist), I don't think this is a great kind of hiring methodology. I recognize you say "we don't have months to get them up to speed", but I think your whole post would be more true if you said "one month" or "2 weeks" rather than "months to get them up to speed". Personal anecdote/case study: I interned on the frontend team at Mixpanel in 2011. I had written about 200 lines of Javascript prior to starting work, not a ton of HTML, and literally no CSS. I had however done quite a bit with Python/Django (which they used). My first month consisted of me "getting up to speed" where I was working at a lower rate than others on the team. By the end of summer, I was a fairly productive member of the (3 person) team, building products with tools I had previously had very little experience in. Fast forward 2+ years: I've now done 2 years of college. I spent one summer writing distributed machine learning tools for fraud detection, and another summer during deep learning research. The majority of my computer science classes are just theory (no programming), but I've done a bit of programming in C/Python/Rust (for a choose your own language thing) for school and also a bit of programming in Python on the side. Now I apply for your frontend job. >I'm going to ask them to explain how a closure works Closes over internal state, talk about read-only (Python)/ read/write (JS) closures and how read/write closures allow you to make basic objects out of functions. >How they deal with AJAX Use a callback? Not sure what this question is really asking. Potentially do some kind of client side queuing for some special cases. How to implement server-side push is more interesting. > What they think about "!important". Overrides all other CSS rules iirc. Not a best practice thing to use, but still a useful hack to keep in the toolbox. > Things to be careful about with floats. I don't remember specifics, but I remember floats can be a bitch. Just Google any problems I'm having. I believe the type of container that floats are in matters. > How CSS precedence/specificity works. Could probably work out an example. In general, element inherits all rules that apply to it, and more specific rules overwrite less specific rules. I don't remember the non-trivial ordering for more specific -> less specific (ie id is more specific than class), but would be very easy to look up. > How to architect a webapp Would be more comfortable talking about the server-side component, but could talk about client-side code design. Summary: I'd probably do alright but not exceptionally on your interview. You might give someone else the job. They would probably be more productive on day 1, but I don't know about by the end of week 1. The twist: If I was interviewing for a frontend job, I'd take a few days to study all of this stuff and significantly increase my interview performance. Would that make me any better at actually doing the job? Probably marginally.
- ronaldx 13y agoWould you be kind enough to explain further why knowledge of closures is a priority...?
- siegecraft 13y agoIMO, it's because they're abstract enough to be completely opaque to someone who doesn't understand the concept of them, but ridiculously simple once you do. Also, if you're doing a lot of front-end/javascript work you're bound to have run into them, even if you don't realize what they actually are at the time. For me it was just one of those "a-ha" moments where you realize there's an easier/better way to do something. And if the interviewee doesn't know about them before the interview, hopefully s/he has learned something from the interview (I learn a lot from interviews just from looking up all the stuff I didn't know).
- _delirium 13y agoIf you're looking for something very specific and the hiring is such that there's no time for a hire to get up to speed, vetting candidates to make sure they already have exactly the knowledge you need makes sense. But a lot of technical interviews are not really doing that. Google does not care about the specific knowledge they ask you about at interviews for the most part; they have so many Google-specific internal systems and processes you couldn't possibly have any experience with, that there is going to be some getting up to speed anyway. Instead, they're using the interview gauntlet as a proxy for something they're actually interested in, something vaguely like "technical skill".
- Ensorceled 13y agoWell, for most positions I don't need somebody who can talk to clients comfortably and I don't care if they are shy or quiet in meetings.
- ngoel36 13y agoI used to work at Google. I saw a lot of good candidates get rejected. I myself was rejected multiple times before I got an offer. I was talking to my manager who was on the Hiring Committee about this dilemma, and at the end of the day the fact is that good companies don't give a shit about their false negative rate - only their net positives. By having an efficient technical interview process, yes, you let good candidates go. Just as you do by only having certain target universities or requiring certain experience. But they don't give a fuck. They get 1000 applications a day. Hundreds of internal referrals. If they were to reject the ~100 candidates/week that get hired based off doing well in their technical interview and take the next 100, Google Engineering would be just as well off. Maybe better. (Harvard says the same thing about its incoming classes). No technical interview will ever be perfect. But if you have a holistic process that is 50% based on past experience, and 50% based on being a top 10% performer in well-designed technical interviews (among other factors), that's usually good enough to take a bet on the candidate.
- mtdewcmu 13y agoI think Google's hiring is less about finding a few good engineers and more about collecting impressive specimens of humanity for a dream team. They're playing a different game than most, and that's their prerogative.
- chetanahuja 13y agoGiven that google has recently publicly denounced their own hiring methodology (that they've been using for years), I wouldn't use them as a shining example. Also consider the fact that most companies are not google and don't have the same unlimited streams of top candidates coming in the door (is that even true for google any longer ?). A smaller operation (ie. the typical hn population) needs to work much harder to avoid false negatives. One way of doing that is to optimize the hiring process to allow a good candidate to shine vs the Google way of putting the candidate through endless abuse (I know what I speak of).
- jmspring 13y agoI interviewed w/ Google a couple of years back, didn't get hired. Interviewing is a two way street, and I won't BS if I don't know something. That said, had one interviewer who had 0 personality, 0 people skills, and didn't introduce himself. He asked one of the typical open ended questions, which was fine, we went through it a bit. At the end, he claimed there was actually a closed answer to the problem, wouldn't actual say what it was and just walked out. The two of the other few people I talked with were interesting and engaging. But it was seriously a mixed bag and didn't present a good face for Google. Recruiter calls again a year or so after the fact. "You did well in your prior interview, but things didn't line up. Interested in coming back in?" Me - "The last impression left a pretty bad taste in my mouth. Not at this time." Note - I was on internal referral as well as had apparently incredibly impressed the "phone screen" person (whatever that means). Of anywhere I have talked with, GOOG has been at the bottom of list in overall experience.
- chrischen 13y agoYes the problem is with freezing up. As a person with ADHD, high pressure situations will cause a lockup if my brain due to the inability to focus.
- wpietri 13y agoGenerally, I'm not hiring people to explain things out of the blue to people who already know the answers. I'm hiring them to build things. So I don't like to spend a lot of interview time on pure quizzing. The primary filter for me these days is the pair programming interview. Can they make something? Do they think clearly about what they're making? Do they ask good questions? Can they explain why they did something, and what other options are?
- cheald 13y agoThe level of position being interviewed for matters a lot, too. When I hire a "senior developer", part of what I'm hiring is someone with the experience and ability to teach junior developers. Someone who is unable to articulate basic concepts in a conversational context is not that developer.
- mrbgty 13y agoWhy do you need them to explain how a closure works when you could do something like the OP suggested and give them some work to do on their own time that allows them to show you how it works? The company he mentioned was able to get 10 hours worth of work info on him this way.
- danjayh 13y agoI think it's important not to get _too_ caught up on terminology, though. Someone who is already familiar with say C, C++, Java, and Perl, HTML, and CSS, but has only done some basic javascript (just to choose a random grab-bag) might look at you with a blank stare if you ask them about a closure. However, they may well be familiar with the concept, as in Java an anonymous class has many of the same properties. And I would argue that such a person would probably be able to pick up javascript and become effective in it in a matter of days, provided that they already have an extensive development background in other languages. If you truly have only a day or two to get somebody up to speed, then sure, you need somebody who is already intimately familiar with every technology that you use ... but if it's a gigantic project, you're probably going to have a bigger learning curve than a couple of days anyway. However, if you're looking for the absolute best person you can get for a job, you shouldn't write them off because they haven't had experience with a specific technology. More important is that they have a solid understanding of algorithms, data structures, and various design architectures, have exposure to a number languages, and are capable of rapidly assimilating new concepts. I'll take the lightening fast learner over somebody who knows a few specific techs _really_ well any time, because the lightening fast learner will _also_ learn the specific quirks of my project quickly, whereas somebody who has a difficult time with new concepts but happens to know the right techs might struggle for a long time just to come up to speed on a large project that somebody else created.
- rralian 13y agoI'm not sure you and OP are talking about the same thing. What you're describing as a a tech interview (as I understand at least) sounds like a delight to me. I enjoy talking tech and am happy to wax poetic on any of those topics. But the tech interviews I've recently done (for web developer positions) have been more focused on com-sci concepts and whiteboarding exercises (sometimes in front of 3-4 people on a video line) on arbitrary things like solving mazes according to special rules or building a donkey kong clone in javascript. Generally nothing that you would do as a web developer. I'm a fairly accomplished developer, but it's easy for me to look stupid in front of even a junior developer when I'm writing code on a whiteboard. I use google a lot while I work (without shame... until I'm at a whiteboard) and I reference other parts of the codebase for context. The best offer I got was from a company that did exactly as OP suggested... gave me a short contract job and evaluated on the code and my interactions during the job. That's also how I've hired developers for my own startups, and the results were excellent... they've all gone on to top-tier companies.
- ikeellis 13y agoFor a well done interview, the problem is definitely mine. I wish I could reliably do the right thing and show a quality thought process as I iterate towards a good answer. However, I need to be away from the pressure to speak in order to solve problems. Sometimes this only takes a few minutes, but that silence in an interview ruins my composure. This problem doesn't happen to me when I'm delivering a product pitch, speaking at a conference, meeting with investors, or any other situation where I'm on equal footing with my audience. Frequently, though, I ask to get back to people later with answers to difficult questions. I also prepare fanatically for those situations, where it's very difficult to prepare for a random tech interview. A huge part of this is simply finding ways to stack the deck in my favor. A great interviewer knows that it's THEIR job to figure out what I can do well. Most people are not great interviewers. This makes a technical interview a total crapshoot that has never worked out for me. My post is definitely suggesting that companies should examine their process to see if they're filtering for the right things. More importantly, I'm explaining how I've solved this problem for myself. Will I miss opportunities with my approach? Absolutely. I just now believe that I find better ones with my new method. One caveat... I mostly consider a question like, "Can you explain what a closure is?" to be conversational. Simple knowledge quizzes are great fodder for a phone screen just to find out if someone even belongs in the room and whether they match the needed skills in general way. Where I get into trouble is with with whiteboard coding, brainteasers, etc. We could have a great chat about async front end dev and then I'd stare blankly at you when you asked about CSS specifics. That's productive and tells you about my experience, though not my aptitude.
- jonotime 13y agoThanks for this blog entry. I happen to be going through this problem right now. I'm a developer who just moved to SF. There are tons of jobs, but I freeze up during tech interviews. In the past I have landed jobs at small companies with a looser interview structure where I can basically distract them with interesting nerdy stuff so the time runs out before they can get to the programming questions. I am wondering 2 things: 1. How do you phrase it to a potential employer that you would prefer a take home project? Do you say you do bad under pressure? Do you say you think your abilities would shine though on a larger thought through assignment instead? 2. Do people have other strategies for dealing with such issues? Perhaps using a head hunter who knows the hiring process of each company, and can pass you along to ones with a less rigerous tech interview component. Maybe I should just find smaller companies that have not figured out their interview process yet and hope they wont drill me.
- joe_the_user 13y agoIf you freeze up in interviews, then it doesn't seem like the problem is with interviews -- the problem is with you freezing up If a person is interviewing for an air traffic controller position or any position with continuous stress and confrontation, well yes. But if the job isn't a constant stress, constant demand affair but rather an affair of creative, constructive activity, then no. Now, I suspect one problem might be that more jobs are becoming constant, chaotic stress affairs. In a large sense, that seems like a problem society has but that's just me.
- mbrock 13y agoThis is also an example of the "extraversion bias" in company culture. http://www.theguardian.com/technology/2012/apr/01/susan-cain-extrovert-introvert-interview http://www.theguardian.com/technology/2012/apr/01/susan-cain...
- subdane 13y agoFWIW, this is exactly how we recruit at my startup. In fact I was a little worried that it might be a turn off, so it's nice to hear that it's actually preferred (at least by some). Things we're looking for are the ability to get shit done and ship. We aren't looking for genius chess players, we're looking for curious problem solvers with a sense of responsibility and accountability.
- a5seo 13y ago"Maybe somebody can explain this better to me -- but if you freeze up in interviews, are you also going to freeze up in developer meetings? During code reviews? When you're in the room with clients?" No because the interview process is designed to uncover where you're weak. It's a systematic way to figure out what you DON'T know. Other situations are not (at least not overtly). For someone with inferiority or self esteem issues, this can be a very threatening situation, and totally artificial and unlike a normal working relationship where your intellect and skills get the benefit of the doubt most of the time. Interviews strip away that easement and raise even the slightest possibility that you might be full of shit. For most people that's easily managed by their ego but for others, not so much.
- phaus 13y agoFreezing up in an interview doesn't necessarily indicate that the person won't be able to communicate in a normal business setting. Imagine you've been applying to jobs for over half a year (180ish days is the average time it takes for someone to find a job these days), maybe you've had a couple of interviews, maybe this one is your first. You have burned through your savings, maxed out your credit cards, and you are less than a month away from missing your rent payment. When you're in such a situation, every interview becomes the single most important event in your life. If you fuck it up, you might not be able to put enough gas into your car, which you very well may be living in, in order to get to the next one. Trust me, if you've ever been in this situation, it's pretty easy to get freaked out and sound like a fucking idiot in the middle of an interview. It doesn't say anything about a person's ability to communicate in a routine business scenario.
- reeses 13y agoWhat many candidates don't realize is that the hiring manager has probably gone through 1,000 or more resumes from recruiters or retained search agencies, phone screened 20-50, and interviewed 5-10 to fill one position. "Pay me to contract on probation," sounds as if it's low risk for everyone, but it has stalled the pipeline for new candidates. It's not a reasonable request. If it were, then it would be a "contract-to-hire" position, and advertised as such. I've walked candidates out because they've refused to whiteboard code. I'm very "hey, let's work out this problem together, and don't worry, I'm not going to compile the whiteboard, ha ha," so most people don't get too stressed out. If they do, that's where I step in and help them along, which is my job once they come on board as well, so they can get a feel for my style. It also helps separate the people with 10+ years of c, java, c#, and syntactically similar languages who can't differentiate between parens and braces, understand pointers, etc. The interview is where you can say,"would you do that differently if..." and see if the person has just had an interview brain fart or if they really don't know what they're talking about. I've had a few candidates over the past 15 years or so that would just refuse to write any code. Certainly, I made the mistake of asking if they wanted to do some problem solving at the whiteboard, but I was flummoxed when the first guy (back at Amazon when interviewing at Amazon was perceived to be like interviewing at Google today) just said,"No." And kept insisting. I'm a big believer in not wasting people's time, so I walked him out before he talked to the more senior people on the team, who were all working 24/7 to bring out (I think) auctions at the time. Looking back, it may not have been that big a waste of time. :-)
- kamaal 13y ago'Do x in y seconds or you die', is totally different than 'Do x and we shall review it later' by your friends. The biggest problem with testing knowledge than checking their work is, you ultimately end up hiring a lots of people who know(or atleast act that way) everything but can do nothing.
- mmorett 13y agoI think part of the problem is the breadth of material for which you can be questioned in. Since I live in the Java world, let me use that as an example. I have heard of anonymous classes. I've never used one on the job. Maybe that's a function of me being more server side and I think anonymous classes are use more heavily in Swing. Ditto for reflection -- aware of it and when to use it, but just never had the need. For better or worse, the pieces of functionality I've had to build out over the years simply did not require me to use those pieces of Java. There are countless of pieces of Java that I simply do not use, even if I'm aware of them. A Java developer (at least in my circles) rarely just codes in Java all day. Often, they're using a framework. It might be Spring. It might be Hibernate. Right there, you have two vertical streams of expertise they could pounce on. Now add SQL. Even if you're using Hibernate, you'll still need some fundamental knowledge of SQL. Likely, they'll hit you with HQL questions. Maybe some lazy loading. Maybe some optimistic locking. Maybe add EJBs. Maybe add JPA. Throw in some jQuery/HTML/CSS (unless they live exclusively in the server tier). Inevitably, some may ask about stored procs/PL-SQL. Oh what the hell...let's add web services, SOAP, REST, Ajax, JMS, transaction isolation levels, clustering, SSL. And so on. Wait...add Linux admin. The disconnect (anxiety?) comes from a developer having to use so many technologies, which is realistic, and the interviewer salivating at the opportunity to go deep in any one of those. "Excuse me...you can't write a static nested inner class? And you call yourself a Java developer?" I once had an interviewer disappointed in not being able to ask me PL/SQL questions, despite me not even having PL/SQL on my resume. He just wanted to go there. The interviews are often based on a notion that a developer does nothing else but use the language to its fullest. All day. Every day. Reality suggests that a developer uses only as much of a language as needed to build out a piece of functionality for a given need. They don't use every data structure available, nor necessarily every major piece of the language. There's seemingly no way around this conflict. The interview is focused on a language. The developer is often focused on putting together solutions. Depth vs. breadth. For the record, I had an interview once for a Grails developer spot and was asked about UDP. Yes, seriously...UDP. We're not God. We're just developers.
- acchow 13y ago"Imagine someone's being hired for a front-end position, and we don't have months to get them up to speed." First, I'll ignore the fact that contributions can be made to any stack far sooner than "months". It's uncommon for companies to be so incredibly short-sighted. In tech, the hiring goal is for talented people who will contribute for a long time (1 year+).
- krfsm 13y agoMaybe somebody can explain this better to me -- but if you freeze up in interviews, are you also going to freeze up in developer meetings? During code reviews? When you're in the room with clients? Developer meetings are about the issues at hand. Code reviews are about the code. Client meetings are about their problems and ways to solve them. Presentations are about the topic you're presenting. Selling your teammates on an idea is about the idea and its merits. Interviews are about you. (Incidentally, getting a person to go out with you, as some other poster mentioned, is about you. It is also a well known source of major brain freeze.)
- Tyrannosaurs 13y agoAs someone who recruits I'd say that I don't think the point is that there are parallels between interviews and other situations and the candidate is being rejected because of that, it's that I just didn't get enough information to make a decision. Any part way competent interviewer knows the difference between a bad interview and nerves getting the better someone. When it's nerves we're not thinking "they're awful", we're thinking "i don't know how good they are". At that point I'm generally too busy to try and come up with a bunch of other things myself on the off chance the person will respond better to a different situation BUT if the person were proactive and came back and said "I know I screwed that up, would it be possible to try X instead", I think I'd be open to that. (That said obviously giving small paid projects work to all potential interviewees doesn't scale particularly well.)
- GhotiFish 13y agoThe author says "Other times I just froze on topics that I know very well." Maybe somebody can explain this better to me Personally I find that when I meet new people, I have an instinctual assumption that they are more knowledgeable and better than me in every measurable way, I am intimidated. It's only when I see peoples flaws that I can operate around them. Only when I know they are not perfect. (By the way I realize this is illogical behavior, I really can't help it, I'm ascared T.T) I don't think this is anything new, I'm timid around new people. That doesn't impair my productivity, it just impairs how attractive I look as a hire.