11 ms·
As someone with 20+ years in the experience, red flag #1 for me is being expected to go through a skill-testing technical whiteboard (or similar) coding exercis
by cmrdporcupine 6y ago
As someone with 20+ years in the experience, red flag #1 for me is being expected to go through a skill-testing technical whiteboard (or similar) coding exercise before even having a deeper discussion about the role and whether there's a fit, etc.
I've seen this many times and I find it baffling: I already have a very high paying high quality job, I want you to sell _me_ on the position before demanding I do stressful work to prove myself to you.
The vibe I get from that is: they're not interested in senior or experienced talent. What they want is new grads. So I just tell them I am not interested. Either that or the hiring market isn't nearly as tight as people claim. There must be a surplus of talent if companies can get away with this.
I don't like whiteboard coding exercises, but would be willing to do them for the right position. We need to see if this is the right position for me/them before we proceed to that phase. That means that that process comes as one of the last steps, before an offer. If they're not willing to do that, I just politely decline.
- skohan 6y agoI get the feeling a lot of this is cargo-cultism: I.e. people want to work at the kind of place which only hires geniuses who can dazzle with their real-time problem solving, but they don’t actually get the reasoning behind such an interview
- baron_harkonnen 6y agoThe funniest part of this I've found is that in the rush to replicate FAANG white board interviews most companies end up with poorly thought out questions, with interviewers who are rushed to prep meaning that the question often contain technical errors and the interviewers can barely solve the problem themselves. I've been on the other side of this process where the "solution" to a technical case study is flat out wrong, but most of the people training to do the interview didn't realize this to the point where the most skilled candidates would likely (and luckily for them) fail the interview by giving the correct answer! This means that for many interviews at these wannabe-FAANG companies, if you really know your shit, you often have to proactively guess what the interviewer thinks is the correct answer.
- svachalek 6y agoIt's largely a symptom of having mostly new grads do the interviewing, and favors new grads getting the positions, so around it goes. After a while you can get a feel for whether you're going to get anything out of the interview process other than a black hole (and probably lowball) offer and just abort the whole process before it starts. There's no point jumping blind from a good position into the unknown, especially given all the ??? are a bad omen.
- megiddo 6y agoI'm with you on this. 20+ years. My usual MO is to walk away from interviews that have jump-scare whiteboarding or require a quiz prior to an actual interview. I recently broke my own code at an interview and was rewarded with complete nonsense. Never again.
- Zippogriff 6y agoMy new rule after my last job search is that I don't interview if I don't know enough about the interview process to be more than 50% certain I'll come off OK in it. Not that I'll get the job, but more than 50% certain I'll at least look alright. The FAANGs practically (sometimes, actually) give you a study guide, at least. Lots of smaller places act like knowing anything more than the names and titles of the people you'll be talking to would be cheating or something. I'm not gonna burn half a day or more just to bomb a question about graph traversal I haven't brushed up on lately, and I'm not gonna study everything unless I'm shooting for FAANG. Tell me what to expect, a few days out, with decent detail, or I'm not interviewing. I don't need to know exact questions but "first thing in the morning we'll ask you to do something with very basic data structures, like one of [short list of possibilities], and it will be on a whiteboard". Then if you tell me the day is packed with 6+ hours of whiteboard problems I know not to bother, because I'll definitely be tired AF and bombing them after hour 3 no matter how much I study, because I'm not built to literally perform in front of people for hours on end. It saves us both some time.
- thaumasiotes 6y ago> The FAANGs practically (sometimes, actually) give you a study guide, at least. The study guide is hundreds (thousands?) of pages. How is that helpful?
- WC3w6pXxgGd 6y agoWhy study everything for FAANG specifically?
- cmrdporcupine 6y agoYep, I agree with you 100% and as I said before I think companies looking to hire are doing themselves a disservice by not paying attention to this more. A grueling day long interview to get into Google is/was worth it at least from a monetary compensation POV. But frankly most shops out there are not worth it, but if they are, let's talk about how. Many very smart people I know would willingly leave their high-salaried FAANG job for a more rewarding or interesting job even with a steep compensation cut -- and there are many places that would benefit from that talent -- they just need to learn how to recruit it.
- jarjoura 6y agoMost companies I've interviewed at allow me to chat with the hiring manager first to get a sense of the role. If they're looking for someone super senior like us, you just need to be upfront about what it would take for them to hire you. I agree though, if the company isn't willing to let you talk to them about the role and requirements upfront, then I don't think you're being actively recruited for your talent and background, and the recruiter is just looking to meet quotas.
- mywittyname 6y agoThis could be a side-effect of how separations of concerns are handled vis-a-vis interviews at the company. I do technical interviews for other teams within my company. I may not know much detail about the role, beyond just generally knowing with the team in question is responsible for and the topics they asked me to cover during the interview. I wouldn't ever think to ask for more details about the role because I assume that's a question for the manager or internal recruiter. I honestly see it as a way to streamline the interview process and make it more fair. My role in the process is to determine how well you understand the core concepts of a handful of technologies, not to necessarily to sell you on the position or evaluate "culture fit." Of course, I try to be pleasant and want you to come away with a good experience. But sticking to the script is largely me being mindful of everyone's time; interviews are time-consuming and you probably don't want to be answering / asking the same questions to four different people.
- cmrdporcupine 6y agoIf companies want to hire experienced senior talent, then streamlining isn't going to be a good idea. They need to recruit them, and that means not alienating them right away. The process for new grads and interns should be different from senior talent. I don't care about the division of labour. Want to hire people away from Google? Don't be a pain in the ass. People expect pain in the interview process, but not before they are sold on the company. So like I said, what I get from this is on the whole there's an aggregate trend away from wanting experience. I think it's a worrying sign that the market may be either saturated with talent, and/or that companies are totally fine hiring only junior/mid-level "framework" developers.
- mywittyname 6y agoI get it. We all want to be shown respect and courtesy. And how we and our team treat candidates is a reflection on the company; regardless of how accurate it is. But I see recruiting as a team effort. The recruiter should sell you on the company, the manager should sell you on the job, and I should sell you on the quality of the team. If companies aren't meeting your expectations, you should let everyone in the process know. I'm sure lots of technical employees have no idea what the recruitment process is like at a company, especially if they've been there for a long time.
- redisman 6y agoOne thing that's funny is when the internal recruiter for company X (that I had to google) reaches out to me and sets up a call. Then their question is why did you choose this company specifically? And I'm like dude, you called me!
- jacquesm 6y agoClassic. I had a similar thing happen a while ago. US based company - not named to protect the guilty - wanted me to move to the United States to do some pretty specific work for them. I'm not open to such offers but they went out of their way to make the invitation, offered to fly me out there and a whole pile of other buttering up bits and pieces. So I said if they wanted me that badly, could we do this remote? You can guess where that ended. In case you can't: "Who did I think I was to refuse their offer to come to America to partake in this great opportunity?". Interesting attitude change, turning on a dime they went from all smooth and friendly to outright hostile, and that on a track that they initiated. Very weird.
- WrtCdEvrydy 6y agoI always love getting a question about "Why are you interviewing for this position?" and replying "I got an email from your internal recruiter". The follow up is usually "Why do you want to leave your current company?" replying with "I'm not, your recruiter said this was a cool place".
- seattletech 6y agoYeah that just drives me nuts. If you're recruiting, you're trying to sell me on the position.
- Zippogriff 6y agoImagine if we did this for other things. "Why do you want to sell me this apple?" "Be... cause... I grow apples? To sell? And you said you want one, and are holding money?"
- Throysksk282 6y agoOn the flip side, I've been interviewing people with supposedly 15+ years of experience using simple whiteboard questions for a while and I've seen too many people fail miserably at writing basic for loops (a very slightly more involved problem than fizzbuzz, really) for me to simply trust that spending time selling you on the company is useful. Lying on a resume is easy, and even truthful resumes can be misleading. Screening candidates with a half hour of simple coding gets rid of a lot of people who seem to be making money without actually knowing how to write code, which is a problem when you're hiring people to write code and help others write code.
- cmrdporcupine 6y agoI'd fail fizzbuzz on your whiteboard. And I'd be proud of it. Working in this industry for 25 years and almost 10 at Google has not trained me to write fizzbuzz.
- monocasa 6y agoWhich part of fizzbuzz would be an issue for you?
- cmrdporcupine 6y agoWriting code on a whiteboard like it's a test or a competition, without being able to sit down in my editor of choice and calmly think it through and trial and error. Programming is not sports. I'm not a coding athlete. Maybe it is for some people, but not for me. That's not what the job I've held for all this time has ever been about. Plus you get to a certain age and experience and the thought of "proving myself" to some 25 year old is just... Really?
- Throysksk282 6y agoIf you have to sit down and deeply think about a question like fizzbuzz then as an interviewer I'd be a bit concerned - this is a quick check to make sure you're basically competent, not architecture of a critical piece of infrastructure. If you just don't like hand writing and prefer typing, then that's cool with me and you can just do that during the interview (the content of interview is important, not the medium you write with). If you're mentoring a 25 year old you'll have to prove yourself to them every day.
- Galanwe 6y agoAfter being on both sides of the interview situation for quite a while now, my feeling on this is more nuanced. The thing is, when you look for a job, you will often go for 5 to 10 interviews. On the other end, when I'm looking for someone to fill a position in my team, I will interview at the very least 50 candidates. That is to say, all things equal, the interviewer has most likely more incentive than the interviewee to go straight to the point, and thus perform a technical check early in the process. Also, you have to realize than the vast majority of candidates applying for a position are highly unfit for it. Seriously, even for very senior positions, you would be amazed at the sheer amount of people applying with grossly pumped resumes, and overall low skill level once tested. Even after careful picking of resumes, I would estimate that 80% of candidates end up being obviously unfit after the first 10 minutes of a technical interview. That's why, as an interviewer, I'm not very inclined to have a long open discussion about the job until I have at least some degree of confidence that the candidate is worth it. Of course that process is unfair for the "good" candidates. Those who apply to positions fitting their skill set. But when you have more than 50 interviews ahead of you, and an actual job to do, you have to make compromises and tailor your process for efficiency.
- cmrdporcupine 6y agoHonestly, I question most interviewers ability to evaluate someone as low or high skill. I honestly don't think the testing works most of the time.
- AshamedCaptain 6y agoIf you really believe so, then I think you are failing to grasp how low "low skill" truly happens to be.
- cmrdporcupine 6y agoNope, I think lots of people perform 'low skill' in a whiteboard scenario that are not. And the arrogance of their interviewers gets them on HN making very bold claims about other people's skill levels without consideration for the scenarios involved. Don't get me wrong-- I've worked with very incompetent people. Many of them would have passed a coding interview though.
- gedy 6y ago"But! But! Our 24yo interviewer has gotta check if you know the _fundamentals_ ... You might have been coasting for 20 years." Agreed, I'm totally confused and put off by this as well.
- monocasa 6y agoA lot of people do in fact manage to coast for 20 years.
- Throysksk282 6y agoI've seen too many people who clearly have been coasting for 20 years (or people who are simply applying to a position that's not actually aligned with those 20 years of experience). Those 24 year old interviewers are the ones you'll have to train, so you need to, at minimum, be able to do their jobs.
- Jach 6y agoI suspect the reason they get away with it is because for most of us it's not that stressful, especially if we already have a reasonable job. For some it can even be fun, a diversion from the usual day to day. The companies that want you to spend 8 hours doing a side project for them, though, yeah that's going to be a no for a lot of non-desperate people...
- chris_va 6y agoI think this viewpoint is common from senior engineers but not entirely merited. (FWIW, I am also a senior engineer, and I have seen this play out from both sides of the table.) Sometimes folks overestimate their value as senior engineer for certain types of companies, and under-appreciate the risk companies take in hiring an employee. Large companies, for example, generally do not need yet another L6+ that cannot get their hands dirty. They usually have plenty of folks that fit that role already. Additionally, senior engineers are expected to mentor junior engineers, and doing so often requires whiteboard technical skills. I cannot tell you the number of L6/L7/L8 interviews I've done where it was clear the person had no idea how to write simple algorithms, or put together a basic design. They may be great (or not) at the job they have been doing for years, but that sort of information is not accessible to the interviewing company. If the skills existed, it is a red flag if the candidate let them languish. Or perhaps those skills never existed, and that's a very large risk the company ($100,000s/year) is taking, especially for companies (cough FANG cough) that have a "you must be smart if you made it here" attitude around letting people go. If one agrees to interview somewhere, it should come with the understanding that it is a mutual exchange. The company is not doing the interviewee a favor, and the interviewee is are not doing the company a favor. Both sides are expending work, which involves some tradeoffs and annoyances. As an interviewer, throwing in a technical question early is an easy sorting check to make early in the interview process before it gets into the nuanced details around role fit.
- cmrdporcupine 6y agoI have to head out for a bit, so can't write much, but I don't think we actually disagree. The point I was making is that in this organizing of the interview process we need to put figuring out whether there's a potential match before proceeding to the confrontational 'testing your skillz' phase. Otherwise we're just wasting time. And, to be honest, as a well paid senior engineer my time is pretty valuable. Doing a skills test and then finding that the job is not of interest to me is pretty frustrating.
- user5994461 6y agoL7/L8 positions are comparable to the director of a department with 100+ people underneath in a large company or the owners/executives at a smaller company. Of course people in these positions don't code, they couldn't be further away from developers. It's fine that FAANG want heads who can code AND run a department but it shouldn't come as a surprise that candidates don't match that.
- ufmace 6y agoI have a feeling that most positions like that are filled through networking and word-of-mouth if not from internal promotion. Not many companies who want somebody like that are confident that they can determine if they really are that skilled in an interview. And not many people who have jobs at that level already have much interest in the usual rigamarole of most technical interviews.
- binarytox1n 6y agoI'm a hiring manager and I start our technical interviews with coding problems. I have seen too many candidates who can't write code to ever be ok hiring someone who I haven't seen write code with their own hands. I understand that you are highly compensated and may not want to spend time trying out for a new job when you already make so much money, but from my perspective: I have a team of highly compensated individuals who are evaluating a candidate for potential hire and I don't want to waste all of their time if the candidate can't even write a simple algorithm to rearrange the characters in a string. Since it sounds like you're pretty happy where you're at you have the freedom to choose to participate or not. I am guessing that the only way to pull away a candidate like you is by referral anyway, so I am guessing there's not actually a problem here. If I am getting someone via referral, then interviews can focus on what you find valuable - I can sell you on the role, I can ask you personality questions and make sure there is goal alignment. If I have someone to vouch for you. If you're a stranger? You better believe you gotta write some code. I think that if you take a step back and ask yourself if you'd really like to work at a place where they hire people who they haven't seen code, you'd probably rather choose to just write some code for 30 minutes in an interview.
- cmrdporcupine 6y agoYou have set up a strawman -- I didn't say go hire people who haven't seen code, I didn't even say don't do skill testing questions. The question is: at what point in the interview process do you start dumping skill testing questions at them? And I think as the first gate to pass, this is just awful. Further there's also a question of what kinds of questions, and how the question is asked, but that is a separate topic. In any case, as a tangent: Most of the questions asked in these interviews have little to do with the day to day tasks of software engineers. So I'm not sure they give much insight into the performance of software engineers doing software engineering. But they do give preference to the skills obtained in CS algorithms courses, so there is an intrinsic bias towards hiring new grads.
- binarytox1n 6y agoI did address your question - I ask them to write code first. It may waste your time, but it saves time for my team. You can't code? Ok, the interview is over. Thanks for your time. There's lots of debate on what kind of coding questions to ask. My questions are more fizz-buzz and less CS textbook. You'd be amazed how many people apply for senior level software engineer roles who can't demonstrate basic programming skills.
- 88840-8855 6y agoI think you are arrogant.
- cmrdporcupine 6y agoIt's possible. I try not to be. Arrogant people piss me off.
- chipuni 6y agoPeople lie on their resumes. There's a huge surplus of people claiming skills they don't have. You'd be shocked at how many people who claim to be strong data scientists don't know SQL. When I last hired for a technical position, I had half an hour for each candidate to decide whether to move forward with them. I wrote up seven questions that took fifteen minutes to answer. I also spent fifteen minutes talking about the job, the co-workers, and answering questions about the fit of the position.
- Reedx 6y agoWhiteboard coding in an interview is a performance anxiety test and hazing ritual as much as anything.
- EVdotIO 6y agoNothing like the emotional appeal of invoking Godwin, but here we go. Wernher von Braun was a literal Nazi of the brutal kind, but when you are in a race to develop ICBMs, things like "culture fit" are suddenly irreverent. There is no shortage of labor in the market, and I would say that has been the case for the past 10 years and it has been progressively accumulating a glut. I can ask a senior programmer to complete a multi hour at home task after a brief call, and they will expect nothing in return. When I DJed at strip clubs, I would be payed to try out. Both have similar situations of a position staying open for months on end, large pools of people applying, and the need for selecting a candidate based on skill. The difference is incentive from the other DJs to fill in a Tuesday shift is way higher than a team to sign off on a DevOps engineer. Other people just aren't directly impacted by your marginal value and the selection process is going be for other qualities that are. As for the company's perspective, these engineers still cumulatively provide tremendous value and everything is stilling humming along more or less fine.
- cloverich 6y agoOffices that lead with (or even only use) algorithmic questions are either places you know the name of, or they aren't high quality places. That's my rubric.