9 ms·
Job interviews go both ways (2011)
- ranman 12y agoSometimes. The potential employee is not always in a privileged position. I think with most new grads this is the case (some with significant relevant experience are excepted). If I were interviewing a new grad or someone that didn't have a recommendation (basically someone I didn't have any context for) and they asked me to solve a technical problem, I don't think I would do it. I would not want to waste what little time we had allotted trying to solve that. If we did want to make a good technical match I think it would be great to sit down and work on a low hanging fruit bug together.
- HarryHirsch 12y agoDid I ever mention that interview with a whizzo East Coast startup where the interviewer couldn't answer where the company was planning to be in five years time? It's one of those questions where they will squirm like eels, but you have to know, because you are committing your time and future earnings to them. Squirming is fine, but being struck dumb is not acceptable. The experience was epic, it ended with a greybeard apologizing for the HR lady.
- ctide 12y agoI don't think I could have answered that question at any startup I've ever worked at. And, certainly if I had, I would have been wrong in every case.
- clevep 12y agoRight vs. wrong isn't what he's concerned about, I think. Every company/organization/person should have a long term strategy. That way you can weigh potential actions to see if they are moving you toward or away from your goal. If you don't have that goal, or it isn't well communicated, everyone scrambles to optimize for different things, which frequently leads to people pulling against each other. It's totally acceptable to update the long term goal as you go along, but it's very helpful to always keep one in focus.
- ctide 12y agoSure, but long term strategy at a 6 month old company is a year out. 2 years at best. 5 years is multiple lifetimes for most startups.
- clevep 12y agoI think that's becoming an increasingly popular opinion, but I really don't buy into it. If you have one year of runway, certainly you should have a one year plan, but I like to see something longer term as well.
- dethstar 12y agoA plan can fail or go right. Parent asked for where were they planning to be, a plan is important.
- jlarocco 12y agoHow did you spend your time at work when nobody knew what the company was trying to do? And where are those companies now?
- bryanh 12y agoKnowing where you'll be in 5 years != knowing where you'll be in 3-6 months. For most earlier startups, that is near the optimum lookahead algorithm.
- nevster 12y agoI always ask "Do you enjoy working here?" Their instant response is usually telling.
- aurelianito 12y agoWow! I all ask this on my next interview.
- Dragonai 12y agoNever thought of this! Great question, I'm gonna keep that in mind.
- potatolicious 12y agoThat's pretty direct, I like it. I try to ask "what is the worst thing about X right now?" where X is the project/product/thing being worked on. Caginess and dodginess in this answer is a flag. Of course, different interviewers will be more or less forthcoming and straight with you, but if the entire slate of interviewers hem and haw around the question, I take it as a bad sign. An organization where people are afraid to be frank and call a spade a spade is hiding a lot of systemic problems.
- typingduck 12y agoI always ask this. Doesn't even require an honest answer, the length of pause is sufficient. (although now it's been on HN interviewers will probably be better prepared)
- nevster 12y agoAt a guess, I'd put the chance that the person interviewing you has seen this at about 0.1%
- Zelphyr 12y agoThis is why I hate those services that have an automated pre-screen process. The ones where you visit a specific URL and after reading the questions you record a 30 second video with your answer. The massive hole there is that I don't get to interview anyone the company to see if I feel like its a good fit. I'm sure its saves them time but it wastes mine.
- rlu 12y agoWell to be fair, they likely get many more applicants than you have interviews scheduled. And it's just a pre-screen, right? It's not like you have to make your decision right there and then if you do well in it.
- Zelphyr 12y agoI don't disagree but it seems impersonal at best, rude at worst.
- fphhotchips 12y agoI agree with you. If you can't be bothered asking me the questions in person, I can't be bothered answering them. That's the social contract. I've already written a cover letter that responds to the points in the ad; if they can't prescreen sufficiently using that then they need to work on their ad.
- r00fus 12y agoEven worse (for the hiring team) - it's probably not that effective a filter. You might as well use the "I only hire lucky people" filter [1]. Interviewing needs to be interactive because any decent job requires interaction. [1] http://cream.hr/blog/why-the-hiring-system-is-failing/ http://cream.hr/blog/why-the-hiring-system-is-failing/
- chavesn 12y agoI haven't even heard of such a thing. I've done a couple written Q&As, but those I think are fair, since I have time to prepare a thoughtful response and don't have to worry about communicating body language to a faceless camera at the same time. To be honest, it sounds like a net lose -- it's a definite negative for a candidate, with perhaps not much benefit for the company (high noise, high false negatives due to the awkward environment). My gut feeling is that I would immediately reject any company that asked me to do that, if I had the choice.
- Hamatti 12y agoI think one reason for this (not asking enough questions) is that usually early on your career, you don't really have that many options or you are in a situation where you need to get your bills paid with any means necessary. I have really never (yet) been in a situation where I would have really had enough options to say no to any company offering a job after an interview. In those cases, your full focus is getting them interested - not really about knowing what kind of extra activities they do or what they are planning to be in say 5 or 10 years.
- 7Figures2Commas 12y ago> It turns out, the majority of the people don’t do this. They simply put on their best face, answer every question and try to sell themselves. Some ask questions everyone should ask, such as the financial situation of the company. Very rarely someone probes me to see if they would like to have me as their boss. It's funny. Lots of companies are going to increasingly great lengths to filter candidates based on inane tests that supposedly measure technical competence, but many if not most of them do little to filter candidates based on their apparent interest in the job opportunity as a whole. Obviously, there are reasons candidates shy away from asking "tough" questions other than "I don't really care", but startups in particular should be wary of candidates who don't demonstrate a certain level of curiosity beyond the day-to-day technical rigmarole. Put simply, look to hire people who understand that interviews go both ways.
- ChuckMcM 12y agoThis is a really relevant piece, if I'm interviewing you I'm going to wonder if you're not asking any questions about the company. I get that its hard to ask challenging questions in a situation where you want to get hired, but you will need to ask challenging questions when you don't want to get fired too, and if you can do that you are more valuable than someone who can't. That bit about everyone focused on the stock price also really resonated. Back in the late 90's "everyone" was a millionaire, at least after all their stock vested be that in 1, 4, and sometimes 5 years. Way more people than I expected couldn't really handle that. The most common failure mode I saw was that suddenly the person would do no productive work at all, and instead start shopping airplane or yacht catalogs, or talking about where the best islands to buy were with their co-workers. I once pointed out to a person that if they did no more work, then the company's value would go to zero and knowing the best islands would be a useless fact to know. But I had grown up in Las Vegas (well spent my teen years there) and that was a town that taught people that money is fleeting in a very brutal and efficient way.
- rlu 12y agoI've never interviewed anyone, but also, if they don't ask me any questions about the company then I'm gonna think they simply don't care and they applied for the role "just for a job". I don't want to work with people who don't care.
- Iftheshoefits 12y agoWell, define "care" and "just for a job." My view is that it very rarely happens that a candidate has sufficient information to know whether the job he's applying for is one he can "care" about as more than just a method of obtaining a paycheck. In fact, I submit that such information isn't possible to obtain, outside fringe cases (e.g. knowing people on the inside already), without actually working at a place for a time.
- potatolicious 12y agoEh, I have two rebuttals against that: - Is your job worth caring about? Let's be honest, not everyone is working on putting people on Mars or pushing the boundaries of machine learning, etc. A lot of programming jobs are just spitting out code for a paycheck. When I was a tad younger, with less experience under my belt, and fewer choices in employers, I interviewed at many a job where I was expected to act like I'm deeply enthusiastic about jobs of little import to anyone and technically amounted to not much more than flailing my arms at a keyboard for 8 hours a day. That expectation is ridiculous. The mudane, boring jobs need to be done. Hire people who are capable and willing. This is a job, not a church. - One thing I've experienced are the grueling full-day interview process that certain companies are a fan of (one such company rhymes with Blamazon). Literally 7-8 hours straight of interviewing, even your lunch hour is yet another interview. I don't think I've ever had intelligent questions by the end of those. The questions I did have were answered by interviewers before you, and at this point I've been thinking about manhole cover sizes, jelly bean estimations, families crossing bridges, and regurgitating CLRS algorithms solutions for so long I can't possibly come up with anything more. Full-day cycles are grueling, and to expect candidates to be chipper and operating at 100% (or even 80%) is unrealistic.
- incision 12y agoThe author advocates questioning the interviewer directly, but he doesn't mention questioning anyone in his Netscape interview, only making mental notes of various red flags. In practice, I think that's the way 'both way' interviews generally have to go - you don't interview your interviewer, but you do evaluate and judge your potential employer critically. Personally, my attempts at interviewing an interviewer have served to inform my decision, but not at all due to the face-value of the responses as they're generally going to be hard if not impossible to validate. >'Very rarely someone probes me to see if they would like to have me as their boss.' I'd like to try that someday... Who's the weakest person on your team? What do you mean to do about that? When's the last time you lied to someone here? How did you rationalize it? Are you on any medications? Do you cheat on your spouse? What are you most insecure about? The type of questions I'd really like to know the answers to - the sort that you learn the answers to within the first few months of any new job aren't the sort that I'm likely to get answers to much less completely honest ones.
- bobbles 12y agoI think a better way to ask your first question would be: "What would you say separates the strongest and the weakest members of your team?" It allows you to get a sense of what they value in the team without needing to make them get defensive over staff they probably worked hard to acquire.
- leorocky 12y ago> "What would you say separates the strongest and the weakest members of your team?" It's easy to reply to this phrasing with a canned answer and very little though. "Experience, skill, and a positive attitude." If someone gave this answer to you and you're the candidate asking the question it is basically 0 information. I think the better way to ask this question is to ask "Has anyone been recently let go and why? Has anyone been let go or put on a performance improvement plan for not being a good enough engineer? What are specific reasons why you think they were maybe not good enough? What is your policy when programmers make big mistakes?" I'm not sure I would ask these questions, but I still think it's a better form of phrasing. You want to know what they think makes a bad engineer.
- par 12y agoI like this idea but usually interviewers leave me with such little time that it would be unreasonable or impossible to do such a dive with the interviewer.
- sgwizdak 12y agoHuh, I was asked that very same tree traversal question at an interview recently.
- brianwillis 12y agoCan anyone outline a solution? The only ones I can come up with off the top of my head involve using a stack.
- presty 12y agothe blog post links to a solution https://web.archive.org/web/20110504151340/http://sites.google.com/site/debforit/efficient-binary-tree-traversal-with-two-pointers https://web.archive.org/web/20110504151340/http://sites.goog...
- Yen 12y agoIn my opinion, it's a somewhat misleading question (or the answer is creative to the point of stretching definitions). In-order traversal is pretty easy without a stack, if every node keeps track of its parent. 1. go down left branches until you get to a leaf. 2. visit leaf, and go up. 3a. if, in going up, you were at a left child, visit this node, then go right. loop to 1. 3b. if, in going up, you were at a right child, go up again. loop to 3. 3c. if you can't go up, you're done. The trick comes from not really storing the parent pointer at each node, but instead doing trickery with xor-ing various addresses together so that you can store 3 pointers in the space of 2 (plus possibly an extra bit). Of course, if you do so, you've constructed something that's not exactly a binary tree, and can only be traversed in certain fashions where you'll always have the necessary information to xor.
- chrismaeda 12y agoYears ago, I was asked the C++ virtual destructor question (eg http://www.programmerinterview.com/index.php/c-cplusplus/virtual-destructors/ http://www.programmerinterview.com/index.php/c-cplusplus/vir...) in an interview. My answer was, "I don't know; I would look it up in a book. Is this really relevant for an architect position?" I got the offer anyway and turned it down. I think these technical interview questions are a silly way to evaluate developers. You almost never have to write low-level sort routines because you just call them in runtime libraries. But it's harder to evaluate the more important ability to modularize code and manage complexity.
- asuffield 12y agoI always do this, but I play it subtle. My primary test of your ability as a manager is your hiring process, because if you get hiring right then all other problems are solvable. The question I am always asking myself is: do I want to work with the worst person who can pass this interview?
- pyfish 12y agoI always interview the company interviewing me. The closer I've mimicked Peter Gibbons from Office Space the quicker the job offer arrived, provided I passed their tech tests.
- mycodebreaks 12y agoThe way interviews are conducted, mostly, you are left with a little time at the end. Interviewer will ask you to solve a problem, write code for it. Either the time is just enough for you to solve it, or if you finish too fast, there will be a next question thrown at you.In either case, not enough to have a meaningful short conversation followed by a question, which is sad.
- js2 12y agoI guess I've interviewed over a hundred candidates over the years. I always end with: is there anything you'd like to ask me? I can't recall a single meaningful conversation that ensued as a result.
- carrotleads 12y agoDuring my noob days my questions were always about 1. Work times 2. Dress code 3. Questions of growth in company As I got exposure it moved on to 1. Specific question on potential growth 2. Companies market position risks/challenges and their actions/plans But I have not asked hard questions that a few have outlined here. Hopefully I don't have to :)
- adrianb 12y agoSo why is EOF in C defined as -1 (when it is)?
- Estragon 12y agoNot sure why this was downvoted. I'm curious too.
- berdario 12y agoIf I had to guess: prematurely ending a stream is a problem for the current stream, and for the next stream as well, and thus is more desiderable to avoid corruption in bytes signaling an EOF than other bytes. corrupting an EOF in something else is probably not as bad, and/or maybe a corruption 1->0 is more likely than a bit flip 0->1 (maybe when stored/transmitted as 1==higher voltage) and thus 01111111 10111111 11011111 11101111 11110111 11111011 11111101 11111110 are less likely to be corrupted into a EOF, if 11111111 is the least likely state for a byte to be in. Also, not one of these bytes is a printable ASCII character, which might thus possibly be/have been much less frequent in data streams, and thus further reducing the likelihood the probability of such a corruption happening.
- jerf 12y agoWhile a nifty idea, corruption of this sort is so rare and so unbounded (that is, there's no reason to believe it'll strike in your incoming data, it could well strike at the CPU instructions itself or whoknows) that there's not much you can do about it from inside the code. It's all but impossible to deal with corruption rates on the order of 1 in 10^18 (or better! properly functioning hardware is obscenely reliable at doing what it was designed to do [1]) instructions on properly functioning hardware, and all but impossible to deal with failing instructions at a much higher rate on nonfunctioning hardware, except to replace it with functioning hardware. [1]: If anyone wants to pop up with complaints about that statement, remember that properly functioning hardware is also doing a lot of things very quickly, so it has a lot of chances to fail. ECC RAM is important, for instance, because something that only happens every few billion accesses may still happen several times a day. But this is still an absolutely obscene degree of reliability. Most disciplines would laugh at worrying about something at that rate of occurrence... they wouldn't even be able to detect it.
- pawelkomarnicki 12y agoHuh I remember 2 interviews that I was sure I am never ever going to work at the company :-) At one well-known-company interviewer literally treated me like garbage from the very first minute (including waiting for the scheduled meeting in the building corridor), I didn't even try to do say anything then. Another one started pretty well, but then I saw the team (super demotivated) and they asked me to do some shady test-stuff (HTTP referer header spoofing), but the nail to the coffin was the manager telling me that I have to disregard notice time and instantly jump ships for them, because they won't wait for me ;-) So yeah, the interview works both ways, there were jobs (like my current one) that I felt that the fit is strong and the final negotiation effects are not so important.
- dmitri1981 12y agoOne question I always ask my interviewers is "What is the best thing about working here?". You can tell a lot by their immediate response and whether their face lights up with excitement. One answer I will never forget is a developer responding with "We have a Dyson hand dryer".
- _mulder_ 12y agoAn equally interesting, and perhaps more useful, question I always follow that with is "What's the worst thing about workign here"... The cop out answer is usually 'it's a big company so you get some politics and inefficiencies'.. I suppose a good follow up would be; "how does the company intend to change this going forward?" or even "how does it compare to other places you've worked"
- underwater 12y agoAs an interviewer I loath that question. Why would I invest my time interviewing you only to turn around and tell you something that might make you decide not to work here.
- fredophile 12y agoIt depends on your priorities. Do you just need someone to come and fill a spot or would you prefer someone that's actually a good mutual fit for the role?
- herghost 12y agoI interviewed for a dev job a good many years ago. I hadn't heard of the company at the time (they were pretty small so there was no reason that I should have) so I did a lot of research. I remember that their financials were looking decidedly bumpy, but almost always in the black. I asked about this at the interview. The lady interviewing me looked offended that I would ask about their financial situation as it was "not really something [I] should be worrying about". I didn't get the job, and their feedback was that they wanted a dev, not an accountant.
- nmcfarl 12y agoBullet dodged. Not assessing the financial situation of small employers pretty much has always lead to them going bankrupt in my limited experience. And employers unwilling to give any indications are the ones that leave paychecks un-funded when they do (that was an SOs employer).
- braydenjw 12y agoIt's funny that this article states that it originally came from the IndexTank blog, and the creator of IndexTank just responded to an AskHN questions a few hours ago. https://news.ycombinator.com/item?id=7977188 https://news.ycombinator.com/item?id=7977188
- spopejoy 12y agoOne aspect of "selling the candidates" that can be overlooked is the tech interview. There's a big opportunity to demonstrate your own/your team's technical excellence as a selling point. What this is not, is skewering someone on "j=j++ in a loop" trick questions, or dryly sacrificing them on the algorithmic altar. Programming is supposed to be interesting, so it should be interesting to dive into fundamentals, language issues, library specifics or whatever, and keep drilling to the edge of the candidate's knowledge, and beyond. The hope is, the good candidates get grilled a little, and walk out thinking "I could learn something here."
- dllthomas 12y agoYeah, 'cause language issues and library specifics are far more interesting than dry algorithms. This seems bass-ackwards. Library specifics, and to a certain degree language issues, are exceedingly amenable to recourse to documentation. An understanding of algorithms, less so.
- spopejoy 12y agoI don't mean to knock algo questions, especially not complexity and data structures. I do think language and library fundamentals get overlooked, for the very reasons you mention: yes you can google pass-by-value and consult docs about a TreeSet ... but the good programmers don't, they already know when/how/why and don't forget it after a year of doing something else.
- dllthomas 12y agoFor sufficiently fundamental fundamentals, I'd agree. I'd certainly include pass-by-value vs. -reference vs. -name in that. I strongly dispute the notion that good programmers don't consult library docs. Library surface area is huge, particularly in batteries-included languages. One should know well the areas they use, but there will be plenty outside that, especially if they're moving between many languages.