8 ms·
Notes from an Interviewer
- sharas- 3y agoSOLID, TDD, etc is a noise from simpleton uncle. I tried hard to see if he has anything of value to say. He doesn't really. That doesn't stop him from selling simplistic slogans to get attention.
- mooreds 3y agoI'd add: * Do some research on the company and ask a question showing you did so * prep your coding skills with koans or similar, depending on the job and your recency of coding experience * Have a good reason why you are looking at this company, instead of any other
- uraniumjelly 3y ago> * Have a good reason why you are looking at this company, instead of any other I don't like this sentiment. Are people not allowed to be looking at other companies at the same time? Your company is probably not so unique that people will have legitimate reasons to have a significant preference for your company over other ones (sans the salary). I feel that it's out of the interviewer's line to expect interviewees to have an answer for that, when it's not like the interviewer is looking at a specific interviewee instead of any other.
- igetspam 3y agoI didn't read it that way. You could absolutely be interested in other companies but you should be interested in this one as well. Don't show up not knowing what the company does or the basics of the product. We hire people we want to work with, that want to work with us. Knowing who we are shows you want to work with us.
- quesera 3y agoThis is canonical advice, but I think it's often taken too far, or over-interpreted. The vast majority of companies are not special or interesting. And the vast majority of candidates are the same. Making the candidate pretend to think there's something special about your company makes you look foolish. If you water it down to "You need someone with my skills, you're located conveniently (or remote), you pay reasonably well, and (so far at least) I don't hate you.", then sure. That's fine, but wanting more is often self-deluding. OTOH, showing some initiative and a vague understanding of what the company does? OK sure. Candidate should have read the home page and maybe About Us. If only to establish that they have determined the company passes the first couple stages of their filter and that the conversation is not a total waste of time. Addendum: The above is for staff positions, where I interview most candidates. I also do peer interviews at the leadership level, and expectations at that level are definitely higher and include the desire to help set the tone for the organization -- which should trend toward specialness, but presuming that you've succeeded in the eyes of a candidate is, well, presumptuous. :-)
- mooreds 3y ago> Are people not allowed to be looking at other companies at the same time? Of course. But I think if you can think of some reason that you are interested in this company (beyond "I need a job") that is going to help you stand out. You don't need to pretend that working for this company is your life's dream, but a reason will show you have done some work and are excited to be a team member. Examples include: * I like the variety of consulting (for a consulting company) * I really want to work more with Ruby on rails, because I have done so in the past and enjoyed it. * What you are doing in the industry is exciting because I think webhooks are foundational and undifferentiated, but hard to get right (for a webhooks company) Etc etc. Don't gush, just show a modicum of interest and research.
- runamuck 3y agoFollow instructions. I like to say "please respond with short, focused answers. Two or three sentences per question max." The interviewer will inevitably ramble on with unfocused stream of conscious word vomit until I have to cut him/ her off.
- jacamera 3y agoThank you for sharing this and for providing explicit instructions during your interviews. It's confusing and awkward when the interviewers set it up as a casual conversation. There are no natural conversational cues when you're talking to muted participants who are looking down writing notes and continue to do so for a few seconds even after you stop talking. It feels rude and uncomfortable to just deliver a short statement and stop but I suppose that's probably always going to be the best strategy. I'm new to interviewing and suspect I just failed a final round due to word vomit. I would have much preferred to be working through a coding problem instead of having a "conversation".
- angarg12 3y agoOne big point I'm missing from this post is "work on your communication skills". People shit on STAR method or variants, but the fact is that unless you are a great communicator (and most engineers I interview aren't), you will do better by adding some structure to your answers. And then there is people who just ignore your questions and ramble on and on. Listen to your interviewer and directly answer their questions.
- andrewstuart 3y agoI’ve written a lot of software without knowing SOLID. Maybe I did it all wrong.
- ninkendo 3y agoIME, SOLID is only an important idea because there are so many ways to do OOP poorly and you need a set of guidelines to help you not turn your OOP codebase into a mess. You get most of SOLID automatically if you just don’t do implementation inheritance. Many great languages don’t even support it in the first place, and that’s a good thing as it’s a massive footgun. That obviates 3 of the 5 SOLID principles right there: just don’t do implementation inheritance. (Interfaces are ok, just not base classes, ie. Use “implements” but not “extends” in Java, etc.) The other two principles are mostly just common sense anyway. Or heck, maybe just don’t do OOP, as it’s not clear to me that it’s the right approach in the vast majority of circumstances. Make your data first class and design algorithms that work on it, keeping your logic and data firmly separated, and you sidestep the whole issue.
- nomemory 3y agoDon't worry!
- sys_64738 3y agoI've found that interviewers who often give expert advice are the problem, not the interviewed.
- koliber 3y agoCan you elaborate?
- Joeboy 3y agoMy #1 interview tip would be, have a decent mic / internet setup so I have a shot at understanding what you're saying.
- epalm 3y agoYes, this! In this day and age, if you’re applying for a remote position but you’re still fumbling around, unable to smoothly join a zoom meeting with a working microphone, it doesn’t bode well.
- hajile 3y agoI’ve never understood this issue. We get paid well. A $400-450 Shure sm7b or Electrovoice re20 will last you decades and is an incredible return on investment — way better than your electronics and monitor investments and probably better than your chair and desk investments for most people. Even a $30-50 USB mic will last a few years and blow away your laptop or built-in camera mic (though the dynamic Shure/EV mics don’t pick up everything like capacitive mics).
- jacamera 3y agoFor me at least it's about the ergonomics of the microphone form factor. I'm not comfortable with a standalone mic in front of my face. I don't like having to remember to keep the proper distance. I got a nice high quality broadcast headset that sounded amazing but then I couldn't get the monitoring levels to work well with any combination of audio interfaces. On any given call I might have to boost my headphone volume considerably depending on the other person's audio quality but that would invariably throw off my own monitoring levels. In the end I got a high quality gaming headset that doesn't require monitoring due to the open-back design. The microphone sounds fine but not nearly as good as the other options unfortunately. All that to say I spent a few thousand dollars over a few months trying to solve this problem and couldn't find a great solution!
- hajile 3y agoElectroVoice re20. The "variable-D" design helps you sound decent if you're not keeping exact distance from the mic. The builtin pop blocker is also quite effective. It was designed so that if your interview target didn't have good mic discipline (most people don't have any), you'd still get a usable recording. As long as you're in a roughly 12" cube in front of the mic, you'll basically be fine. If you're spending that much money and really want a headset mic, get a countryman and wireless set. You only need to reach a few feet, so a cheap analog system should work perfectly and provide way better sound quality.
- nomemory 3y agoI am also doing lots of interviews, and I try to stay away from theoretical questions about SOLID, OOP , the difference between a GET and a POST, what is an inner join, or similar. Most of the seniors I interviewed were acing questions like this (they probably answered them tens of times before), and there's no way to differentiate them, once you get perfect answers. As the author of blog post mentioned, some of them don't even listen the question till the end before reciting manual phrases about Single Responsibility. Some people would disagree but for us there are a few factors that predict if the candidate would be a good fit: * The ability to solve easy and medium leetcode-like challenges and explain his choices. Nothing fancy, no dynamic programming or graph theory. This tells us if the candidate knows how to write code, which in most cases is at least 50% of the job. * His academical record. It's a good predictor, because people who actually did good in school and finished their homeworks have a good work ethic. Of course, we are not recruiting PHDs to do backend work, but people who did decently well in school are usually nice to work with. There are brilliant dropouts, of course, but they are not the norm. * We test how opiniated the candidate is when it comes to technology by asking outrageous questions (relative to the Status Quo): Why dependency injection is bad. We like people with opinions, but we find difficult to work with "evangelists". The rest is commentary (at least in our case).
- DinaCoder99 3y ago> It's a good predictor, because people who actually did good in school and finished their homeworks have a good work ethic. Wow, you actually ask for their transcript? I don't think I've run across this after my first job (an internship), thank god. The main issue with this, of course, is that people are generally much more motivated by pay than by grades and foisted requirements, so you're going to get a very noisy signal from this.
- michaelrpeskin 3y agoI’d rather have people who are internally motivated to do good work. I don’t look for people who get good grades for the sake of getting good grades. But people who have good grades as a byproduct of just wanting to do well. I think it’s a pretty good signal for me.
- decafninja 3y agoMy experience with tech interviews is that the number one most important thing by far is to be an leetcode master while being friendly and personable. Everything else is secondary or tertiary to the ability to regurgitate perfect hyperoptimal solutions to leetcode mediums and hards in twenty minutes. This won’t cover every single company as there are edge cases, but it’s the most scalable approach covering a huge swathe of companies, including many of the most competitive ones.
- deleted 3y ago[deleted]
- t8sr 3y agoI had to look up what SOLID is, and it kinda goes against most of what we’ve learned about software development since the 90s. When people say they don’t want algorithmic “leetcode” interviews, I wonder if this is the alternative they want? 1999 style OOP Java trivia? Is the idea that you’re supposed to provide good discussion of the pros and cons, and so show some experience? That sounds like you’ll just hire people who had similar experience to you.
- mytailorisrich 3y agoHmm, SOLID is very well-known and the principles are ubiquitous good practices for object-oriented programming and also useful for software dev in general. Certainly, asking about them and , especially, asking the candidate to critique them is a very good question.
- diarrhea 3y agoOnly ones I ever found worthwhile are D and maybe I.
- mytailorisrich 3y agoS (Single responsibility principle) is very important, not only for OOP but for good, maintainable software design in general (yes, even if you do firmware stuff).
- diarrhea 3y agoAbsolutely. I just find it rather inactionable, as it can be subjective.
- mytailorisrich 3y agoOdd because that's arguably the easiest to apply when designing software.
- 3y ago
- deleted 3y ago[deleted]
- ryukoposting 3y ago> I used to ask ‘tell me one of the SOLID principle you strongly agree or disagree with’ but I had to stop because it ended up with the interviewee listing/describing the SOLID principles rather than critiquing them. It sounds to me like this is a good question that you should keep asking. You're typically hiring one person out of a large pool. If only one out of 15 interviewees does well on a question, that's a helpful signal.
- Fuzzwah 3y agoAs a good test for how important a signal this is, the interviewer should ask it to a few of their top performers.
- lubujackson 3y agoThis is the gem comment in this thread. If all these interviewers are such well-rounded and knowledgeable engineers, how much testing and effort do they put into their questions? Or is this just "cowboy interviewing" based on pet questions that scratch their own itch?
- mytailorisrich 3y agoAgreed. Anyone can learn acronyms, principles, etc by heart and repeat in an interview. The real useful questions are about reasons for them, purposes, limitations, etc. I.e. to test the candidate's critical thinking and experience.
- dan-robertson 3y agoJust because a fraction of people can answer something to your satisfaction, it doesn’t mean it’s a good signal. Eg I don’t think baseball trivia would be a great way to narrow down candidates. That said, if you need to narrow down the pool and you like the question then go for it. I think it’s important to keep your ultimate goal in mind, which is probably: - find the desired number of acceptably competent candidates - who are likely to accept your offers - without needing to make very large offers - or spending a lot on finding and interviewing unsuitable candidates - while complying with any local laws These can lead to a bunch of different things you see in hiring processes (eg you prefer referrals because of 2 and 4, and candidates may be rejected for being overqualified for reasons 2, 3, and 4) As a candidate, this often feels very frustrating: you would rather companies follow processes that are maximally fair where so long as you demonstrate sufficient merit, you get an offer. Or even better, processes that do a good job of uncovering the value you bring. I guess one can try to look at the hiring process through this lens to not take rejections so personally, and one can hope that different companies will have different processes (to hopefully reduce how much they compete with each other for the same subset of candidates) though I don’t think they end up being very different in practice.
- thih9 3y agoOverly rigorous interviews are a problem in the IT industry, articles like this are a proof. > If you google ‘top 10 X interview questions’ where X is your technology, and a question is on that list you should probably know the answer. Even if the company is not using that aspect of the technology in their work? What if the candidate has referrals and experience that already presents them as proficient?
- sharas- 3y agoOn interviewers who are asking about "recommended practices", SOLID, etc...: Had an interview while back with a hiring manager for "Agile Coach" position. - He couldn't answer basic questions about what goal he wants to achieve. That was a weird question for him. - He was grilling me on SAFE processes. This is a "normal" case.
- sokoloff 3y agoI suppose that not knowing what goal they want to achieve could reasonably lead to them wanting to really scale up agility.
- jacamera 3y agoThere's some good advice here but I take issue with this statement: > I used to ask ‘tell me one of the SOLID principle you strongly agree or disagree with’ but I had to stop because it ended up with the interviewee listing/describing the SOLID principles rather than critiquing them. How many people have internalized every part of SOLID such that they can immediately start critiquing one of the items? I learned about SOLID in some book 10+ years ago and I'm going to need a minute to remind myself what the acronym stands for. It's a sign that I'm taking your question seriously rather than just giving pros and cons of the first random thing that pops into my head. I think this is just a bad question and that it reflects poorly on the author that they automatically assumed the fault lies with the majority of interviewees.
- hitchstory 3y agoIt's become almost a cliche as an interview question. That's the main reason I've thought about it enough to be able to critique it. I think it's not necessarily a bad question assuming that the candidate can recite it. If they can, they probably should have thought about what it means. I've met plenty of devs who can't recite it but who do it all instinctively though. That's why I'd rather see people demonstrate these principles while coding without using the term at all. But, coding interviews are expensive and you need some way of sorting the 100 applicants into the 90 who can be ignored and the 10 who are worth an interview. This is a hard problem I've never found a really good answer to. OP's question isn't worse than most of the attempts I've seen.
- gopher_space 3y ago> you need some way of sorting the 100 applicants into the 90 who can be ignored and the 10 who are worth an interview. This is a hard problem I've never found a really good answer to. It's a solved problem but you need to take your engineers offline during the hiring process. This looks expensive if you're trying to increase headcount rather than fill actual positions.
- jupp0r 3y agoI've also seen plenty of devs who can recite them and then blatantly ignore them when writing code.
- xandrius 3y agoMaybe I don't know enough but I believe having any person talk about a few random projects from their CV and me asking them questions relevant to their position would give me a pretty good understanding of how much someone is knowledgeable in their field, as well as their confidence and general curiosity (it's ok if they just know their bit but plus points if they can also talk about design, business and/or other parts outside of their role.) Of course one could learn that by heart and fool me but I'm also pretty sure people are currently wasting/spending their time memorising acronyms and leetcode just to get someone to give them a chance, so I'd rather have both enjoy the process.
- tekkk 3y agoSounds like the author really likes their OOP. Nothing wrong with that but I hope the trivia is reflective of the job. I find programming to be mostly manual labor where common sense trumps many clever paradigms.
- jeffrallen 3y ago> I’m sometimes in a practical part of the interview where a certain part isn’t going well. ... At this point I’ll try to offer the interviewee some hints or maybe even just tell them what to move them along. However, on quite a number of occasions this advice has been flat out ignored and the candidates have kept ploughing on with whatever failing approach they were using. To put it bluntly, the initial inability may not have been a deal-breaker but ignoring advice is. Yes! If I set it a problem for you, and you're not getting it, it turns into a new interview challenge: can you work with me to get back in track? I'm not a ghoul looking for any chance to hang you. I'm your potential future colleague, and I'm looking to see if we can work together. Not knowing something is fine. Not listening to me as I try to get you unstuck and work with you too get moving again is unforgivable.
- ccvannorman 3y ago"Study basic interview questions, listen actively, and have a good attitude." Why is this on the frontpage.. ?
- pyb 3y agoSerious suggestion: If interviewers want thoughtful answers, they should try sending the questions in advance.
- icapybara 3y agoThey don’t necessarily want thoughtful answers, they want answers that provide them information about the candidate. Sending the questions in advance would ruin that.
- justina20 3y ago[dead]
- deleted 3y ago[deleted]
- mathattack 3y ago“Listen to the interviewer” should also be read as “don’t talk over the interviewer.” I used to chalk that up to nervousness of the candidate. I’ve since learned it’s a very bad sign.
- nyrikki 3y agoMy big problem with 'Know why not (just) what' is that, as demonstrated in the responses here, the interviewers typically don't, and if you try it will sometimes result in them failing you. At a Google interview I tried to explain that in big-O notation the sequence can only exceed the bound in a finite prefix of the sequence. Formally: O(g(n)) = { f(n): there exist positive constants c and n_0 such that 0 ≤ f(n) ≤ cg(n) for all n ≥ n_0 } I was actually made the interviewer mad with that when he asked if there was any reason to use non-recursive search algorithms and I was providing justification. I still got an offer but turned it down because I need an environment where I can learn where my blind spots are and return in kind with the team.
- Hunpeter 3y agoAre you SimonDev? ;) https://youtube.com/watch?v=gCzOhZ_LUps https://youtube.com/watch?v=gCzOhZ_LUps
- nyrikki 3y agoNo, never seen that channel before but if he interviewed at the Fremont campus in Seattle we probably had the same interviewer or same internal guidelines? It looks like he took that job, I didn't.
- nyrikki 3y agoOn reflection I am sure the fact that both he and I had backgrounds with solving performance problems, forcing us to dig into the details of big-O is why we had similar experiences. Mix with what is probably some standard questions inside Google and it illustrates the problem I was thinking about. That is one of the better videos I have seen on the topic, so thanks for sharing it.
- layer8 3y agoYou describe how it successfully prevented you ending up in the wrong environment, so I don’t understand why you have a problem with it.
- Scubabear68 3y agoI have been interviewing technical candidates for decades. I have found the most effective approach is to deep dive into systems the interviewee has built. This puts them comfortably in areas they should know, and very quickly how shallow or deep their knowledge is. Asking random questions about technology mostly tests their ability to memorize facts. I want people who know how to build things in the real world, not those who excel at adding certifications to their LinkedIn. A parting word - if you are leaning towards Uncle Bob for wisdom, you are heading in the wrong direction.
- mtriassi 3y agoI'd love to know a little bit more about how you do that. I'd typically feel wrong asking a candidate to show code they've written at a previous employer. Do you just ask them to walk you through the architecture by memory? If so what how do you come up with questions about their choices without the specificities of the actual way they wrote their code?
- mixmastamyk 3y agoDon’t believe GP was talking about previous code, rather previous design. Perhaps diagraming on a whiteboard.
- EchoChamberMan 3y agoYou don't need a whiteboard to talk.
- jareklupinski 3y ago> Do you just ask them to walk you through the architecture by memory? depends on the role, e.g. for infra work i can ask "if you had complete autonomy to stand up this project again, what would be your first step" and then we go from there
- Scubabear68 3y agoNo, I don’t ask them to show me any code or artifacts, but to simply describe the architecture, how it’s put together. Any novel code or algorithms they are proud of. Areas of the code that were problematic, and how they would fix them if they had the chance. Talk about non functional requirements and if the architecture addressed them or not. Basically see if they could communicate how the system worked, it’s good points and bad points, and how deep they could go. This quickly separates the good developers from the cargo culters and pretenders. It also is a good gauge of how much real experience they have had. Generally, if someone can’t describe at least the rough outline of the architecture of an application they have worked on, that’s a strong signal they are going to struggle as a developer
- jl2718 3y agoYou should always understand that the reason they are interviewing you is because they are unable to solve their own problem.
- neilv 3y agoThe most useful thing about skimming articles and HN comments about interviewing is: Some people think X about interviews, so I need to be prepared for X. As you pour your energy into simply getting past the ridiculous nonsense gatekeeping. Once that misdirected energy gets you that job, you're now safe to pour your energy into the real business... of resume-driven development. In 12-18 months, repeat. It gets easier each time.
- daniel_iversen 3y agoAnother one or two that I feel are very important; 1. Be invested and show you give a damn, 2. (Related to 1) ask good questions that show you care and are invested
- tptacek 3y agoInterviewing is a terrible way to screen candidates, but if you're literally asking questions that appear on "top 10 interview questions" pages, you're not even trying. This whole thing really comes across as an interview process that is about soothing the interviewer more than it is about collecting empirical data that can be used (and iterated on) to qualify candidates. Be upbeat! Show that you've read the same Uncle Bob posts I have! Question me when it's important that something I said be questioned, but listen carefully and do what I tell you to in other cases!
- angarg12 3y ago> Interviewing is a terrible way to screen candidates so.... how do you suggest companies hire candidates? purely through referrals, without any further screening?
- kasey_junk 3y agoThomas is a long time and outspoken proponent of work sample hiring. Here is his current companies process https://fly.io/docs/hiring/hiring/ https://fly.io/docs/hiring/hiring/
- dilyevsky 3y agoThis is not work sample - Oxide do work sample where they can take work you already completed. This is take-home test as described at least
- tptacek 3y agoUsing OPM.gov's definition: Work sample tests require applicants to perform tasks or work activities that mirror the tasks employees perform on the job. You can call them "take-home tests" if you want, but that term is more general; lots of take-homes aren't work samples (they're not work samples if they're abstract coding puzzles that have nothing to do with the real work, for instance).
- opmelogy 3y ago> If I disagree with you, that’s not an issue. Just like the songs Lennon and McCartney wrote together were better than the ones they wrote after, contrasting opinions on a team bring new insights and better decisions. This is great but please tell people this upfront. Not everyone has an over abundance of confidence - especially candidates that come from traditionally marginalized communities.