9 ms·
What I'd love tips for, is how to politely and professionally protest certain interview styles. I want to know how to say, "sure here's how to implement foo but
by Waterluvian 9y ago
What I'd love tips for, is how to politely and professionally protest certain interview styles. I want to know how to say, "sure here's how to implement foo but I also want to express that a focus on this coding trivia is distracting from the skills I feel make me an asset..."
Maybe what I'm asking is tips on how to steer an interview. One of the reasons I wouldn't even consider a tech giant interview is that I feel like I'm just one of many cattle being processed through a long gauntlet of nonsense that distils me down to quantifiable traits rather than who I am.
- SomeStupidPoint 9y agoAn approach is to proactively bring up interesting aspects of the problem yourself -- eg, the last time I was writing example code on the board, I spent most of the time talking about where hooks to add more features would go or algorithmic complexity/edge cases I encounter as I try to implement a solution. If you're focusing on the trivia, you're probably too focused on the code and not on solving the problem -- my experience tends to be that there's at least one or two interesting edge cases you encounter if you try the naive approach, and those are generally what the interviewer wants to discuss. The reason is that discovering edge cases in requirements and solving them is what a lot of the job is, and so how you approach that matters (and to an extent, more than if your code on the board is "correct"). Another approach is to extend the problem by asking clarifying questions -- if there's something unspecified that might influence your design, ask about it and tell the interviewer why it matters. Again, this generally is more what they care about than the details of the coding. Finally, if those skills make you an asset -- why not apply them to the question? Even tangentially by talking about how you would (if you had more time/were doing a real assignment). Coding on the white board is more about the journey than the coding, assuming you can write vaguely correct code. (Though writing on a whiteboard is definitely a skill you have to practice.)
- ebiester 9y agoIn our interview, we have people from 4 different departments who will talk with the candidate, as well as the team (who is there for the coding portion.) I honestly don't want to have to test if someone can handle a simple algorithm. (I'm not talking about anything crazy here, mind you.) Can they read code? Can they think about how to test? I've seen faked code samples, and our test has a half dozen answers on github. I want to just assume that anybody with five years of programming experience can code, but I've worked alongside enough counterexamples that I know I can't assume that. That said, I'd really rather not have to deal with it as a candidate or as an interviewer.
- kuro68k 9y agoThese tests favour people who are good at tests. I know people who test will, crank out code fast, but I'm the long run they suck because they didn't think about it enough. I'll point a company at my sample code. They can ask me about it too make sure it's really mine. When interviewing people I'd much rather have someone who knows how to find the best solution, not the person who has read a list of questions like this.
- misanthropic 9y agoWell you can always say that you're not comfortable coding during interview, and propose to look at your github instead...
- pklausler 9y agoWhen I ask a straightforward problem during a technical interview, I'm trying to ensure that the human before me is actually capable of solving the straightforward problem. You're free to respond any way that you like, but if your response doesn't actually include a solution that demonstrates the capability I'm testing for, I'm not sure that I'm going to be able to distinguish you from the ~50% of interview subjects that HR puts before me that have no idea whatsoever how to program a computer. I don't even ask softball questions. Mine are more like tee-ball questions. Too often, the tee pitches a perfect game.
- rurounijones 9y agoOut of curiosity. Would you still ask these questions if the candidate has a github/gotlab/whatever profile with X repositories where they are the main / only contributor? Could you explain why yes / no and what the specifics would be? (Volume? Complexity? Commit history? )
- pklausler 9y agoI absolutely do. I can't assume that the person before me is the person who actually wrote the code on github.
- deleted 9y ago[deleted]
- Vendan 9y agoI think you'd get more value out of talking with them about those repos, and the process of building them, design choices, then any silly question like "how would you design a database". Of course, that would also mean you'd have to actually put more then a few minutes into prep for the candidate's interview...
- rabidrat 9y agoWhile I agree with you for the most part, many companies want a "standardized" interview process, for both diversity and CYA reasons. Tailoring the interview to the candidate is actually illegal in certain organizations (like government), as it has large potential for abuse.
- tytytytytytytyt 9y agoImplementing things isn't trivia, it's an integral part of being a software engineer.
- sabman83 9y agoA somewhat related experience I had with a company that advertised proudly that they don't do live coding tests. They had a take-home exercise which I did very well and I was scheduled for a phone interview later. I was expecting it to be more around system design, behavioral questions but to my surprise it was a live coding test. After the interview was done I questioned the person why have another coding test. He said it was to test on different areas of programming. I later messaged the VP/CTO who wrote the blog post on not having live coding test. The person apologized for the experience and said that the team I interviewed for did not come under engineering org. It was a frustrating experience but at least the person responded positively.
- thesmallestcat 9y agoA warning: If you take this approach, you'd better be a programming god, because you're going to be the guy who was too good to knock out a simple coding problem. Every off-by-one error you commit on the job will raise an eyebrow. People will wonder, does this guy want to be an engineer or something else? Why couldn't he rip through that problem and teach _us_ a thing or two on the way? Another thing is you're basically coming in and saying "your interview process is wrong". If you're being interviewed as a manager or a lead, you can afford that risk. If not, be careful, because many people, myself included, don't want to work with somebody who cannot focus on the task at hand and feels the need to question things that have clearly been thought out ahead of time.
- programmarchy 9y ago> don't want to work with somebody who cannot focus on the task at hand and feels the need to question things that have clearly been thought out ahead of time This seems a little too general to me. Many things are not clearly thought out, and I'd rather work with people who can recognize when that is the case and communicate well enough to correct the course. A big part of successful development in my experience is knowing when not to implement things, or having foresight to implement things in a better way. Working with people who just do what they're told is often a huge waste of time.
- majormajor 9y agoI think it's fair for non-simple coding problems. If someone asked me a problem that basically reduced to a textbook case of something in the middle, difficulty wise, like reservoir sampling, and I said "oh, nifty, resevoir sampling, what do you use that for in your stack?" and they said "nothing, I just want to make sure you can code," then depending on how my experience to that point in the process had been going I might challenge them on that to some extent, a la "do you find this more useful than questions that are more representative of the work you're expecting me to do?" If the loop had been going particularly robotically, this might find stronger forms - I've walked out on a mismanaged interview before, though it was way worse than this (and way worse in a very different way - they just weren't at all prepared and the tooling they wanted me to use wasn't actually functional). Or they might answer something more like "we use it to select test cases from our logs to ensure that we're adequately testing against real behavior with proper weights" (or whatever—it's been a while since I actually did this in a past job :) ) in which case I'd still try to have what I consider a more "real" conversation ("what primary problem are we trying to solve, and what else might be options to consider"), but in that case at least they had a good answer to the question and I'd be happy to write the code too. But lastly, frankly, as a hiring manager I absolutely want to hire people who are willing to "not focus on the task at hand" and question things. I don't want people who just blindly do what I tell them to, I want people I can trust to disagree with me and be able to make a case for why they disagree. Being a manager doesn't mean my instincts are 100% and theirs are 0%.
- watwut 9y agoIt is only after you worked with someone lazy or barely capable of foo who charizma-around-company-pong-table his way to staying in company and being treated as genius by those who don't work directly with him that you appreciate those simple exercises.
- mylons 9y agosteering an interview is all about steering the human(s) giving the interview. real life example: an MIT PhD in distributed computing walks into the room, looking extremely tired from interviewing people like me. I can tell this is going to be rough unless I'm controlling the conversation and we have a good rapport. He's wearing a Fender shirt. I have played guitar a bit. After he introduces himself and I myself I open with, "Oh nice shirt. I assume you play some guitar?" and there goes 20 minutes of the interview talking about guitars. So long as I don't completely bomb the technical aspect I've left this person with a positive and relatable experience.
- UncleMeat 9y agoThis is the kind of thing that people want to avoid. Hiring a person because they share a hobby is ridiculous. If a candidate tried to steer the interview to non-technical questions I'd point that out to the relevant people and make sure it was highlighted in my feedback.
- bsder 9y agoIf you let the candidate steer the interview in the wrong direction, the fault is in the interviewer, not the candidate. I have been on both sides of the equation. My stories: 1) Brain teaser questions sometimes aren't as easy or as straightforward as everybody thinks--don't ask them as an interviewer unless you genuinely KNOW the question. Digital VLSI design loops almost always have a question that makes you use a state machine--this is actually a decent question for a whiteboard as long as you don't do something stupid like use J-K flip flops in CMOS. There are a host of basic questions you can use ... but beware of traps. I was once asked the following question: "You have a serial bitstream that represents a binary number. Keep track of the value of that number modulo 3." This is a decent question ... Or a really hard question ... depending upon whether the number is being clocked in MSB first or LSB first. Unfortunately, when I wrote the numbers down on the whiteboard, I chose the "hard" direction. And had to really think ... and the interviewer kept getting more and more agitated and finally complained "Look, this is easy, just do 3 states like this". To which my response was "But clock in any of the numbers in that I wrote on the board. Your machine fails at the second clock." His machine, of course, works just fine for one direction. But that wasn't the direction I picked and documented picking by writing it on the whiteboard. And his machine didn't work with the bitstreams I chose. And 20 minutes wasn't enough for me to see what he got wrong and demonstrate it back. And he didn't understand his question well enough to flag the reverse order. Exercise for the reader: There are two answers to the question depending upon MSB-first or LSB-first. One answer only requires 3 states. The other answer requires 6 states, but it is NOT clear that 6 states are enough without some serious thought (you can prove 6 are enough inductively if you are clever). 2) I used to always bring to electrical engineering interviews 2 printouts with the same program--one in Python and one in Perl. This meant that when I was asked "Do you know Perl?" I could force the interviewer into MY subset of Perl--and I could explain why I avoided Perl nowadays with a compare and contrast. This simply steamrolled all but one interviewer. 3) I was interviewing with an RF company who was needing VLSI digital designers. A poor slob of an analog engineer drew the short straw for handling the digital questions and was so completely out of his depth that I felt sorry for him. After about half the interview of glazing his eyes with advanced digital architecture, I threw him a bone. I made an off-handed comment about digital really not being digital and how the old audio guys used to use the 4000-series CMOS inverters as audio amplifiers. Baited and hooked. We spent the rest of the interview discussing that as an audio amp (of course, I knew the answers to that question cold--that's why I mentioned it). 4) As an interviewer, I used to run a really difficult section of the VLSI design loop which used to intimidate candidates horribly. I had very stern words with HR that my section was supposed to always be at the end (we almost lost a REALLY excellent candidate because he hit me first, did excellently but THOUGHT he bombed, and then flubbed everybody else afterward). I only had a couple of questions, but they were bottomless. If I had a PhD in front of me, I could make him explain complicated things. If I had a newbie in font of me, I would take him one step further than he was comfortable with and see how he reacted. The candidate steered the interview, but within the bounds I set. 5) My favorite interview was when an interviewer asked me my own difficult question back. It took a moment until I realized exactly what he did, and then I launched 30 minutes into the bottomless pit until I was sure that everybody had glazed eyes and then some. We all had a good laugh afterwards.
- IncRnd 9y agoHow to steer the interview is to be honest and to talk. "That's a cool problem. I'm curious though - I didn't see that on the job description. I'm not expert on that, and I didn't bone up on that last night. (ha ha everyone laughs) I can step through it if you want, but it would help me if I knew why you asked about this. If you're looking to understand how I solve problems, that's okay, I'll muddle my way through it and ask if I need any clarifications." They'll tell you. Interviewers often hold similar views to the candidates, but may be asking for a different reason than you think.