16 ms·
Tell candidates what to expect from your job interviews
- catsarebetter 6y agoJust curious, thought of doing something like this for my company too, how long did this take and who did you have to go to to get this approved for public consumption?
- vinaysshenoy 6y agoWe (https://obvious.in https://obvious.in) documented our entire hiring process on our Playbook (https://playbook.obvious.in/hiring/hiring-process/engineering-hiring https://playbook.obvious.in/hiring/hiring-process/engineerin...). Took us about a week to write everything down the first time and then we continuously updated it until it reached the current state. We had the advantage of being a "public by default" company, so there was no need for approvals of any sort.
- catsarebetter 6y agoOh nice, you know it does have an interesting effect on me of making Obvious a more enticing place to apply... Has this improved the quality of interviews and/or applicants?
- vinaysshenoy 6y agoIt's hard for us to tell since this was the first time we were doing an "official" interview for hiring.
- gozzoo 6y ago> We expect you to use git, commit code as you go along, and build the app iteratively -- just as you would during a normal workday. This seems a little bit odd to me. How long do you expect people to work on their home assigments in order for them to commit often? Is it days, or weeks? I don't imagine multiple commits for a 3 hour poject. For a new project there aren't any well defined states of the code that make sense to be persisted. This means the commits will be arbitrary and their messeages not very meaningful.
- jeff_jefferson 6y agoI think you've just failed that part of the test. If you've got more than an extremely simple project there are multiple point s where you should commit. If you implement a piece of logic with passing tests, then commit. It takes seconds to do but makes reviewing so much easier.
- gozzoo 6y agoOr the company failed to attract the most suitable people for the job. As I said - I don't see a reason for multiple commits for a few hours project. It is not how people start a new project. This is an exploratory phase, you check this, test that. Very often it becomes a mess. Eventually your idea of the project gets clearer, then you clean the code, or start again from scratch. I don't see why these steps need to be persisted. This has been my experience each time I've started a new project, unless it is something very trivial, where you just follow the steps from the tutorial. If that's the case though I don't see the value of such assignment. Conversely, if it is a few days or a week project you shouldn't expect experienced developers to take you seriously. This has been discussed multiple times here on HN and most poeple don't like it. People have lives, they probably have applied to multiple companies and it's just not possible for them to invest that much time. In both cases the company misses the chance to meet potentially bright and hard-working people, which should be the purpose of the whole thing. There is something else - what commit messages should look like is a very controversial topic. Introducing a chance for a strong disagreement on such an early stage of getting to know a candidate is not very wise.
- twic 6y agoI get the impression that the project here is not one that calls for exploration - "a simple note-taking app with a couple of screens". You can use a tech stack you already know well, the entity model is pretty obvious, you should be able to sit down and mostly just smash it out. You can make lots of little commits while doing that. I have had interview projects that were much more open-ended and exploratory, and there, i would not expect to be cranking out neat atomic commits. But i don't think that's what they are doing here.
- odshoifsdhfs 6y agoCan I honestly ask what is the point of this question: > Why do you want to be at Obvious? I never understood this. Unless you are Apple or Google or some other big brand, most likely people found your job through a job forum or even HN and never heard of you before. Then most likely the answer is money. So what is the point? I just stopped filling up job applications that have this. Seems so counter productive. Heck, I was approached by a CTO of a Ycombinator company a while ago, he found my resume somewhere, asked me if I would be interested in the position, then redirected me to a form where 2-3 questions was about why I wanted to work with them, and what I would bring to their team. I want money, and in exchange I give you my time and knowledge. Is that so hard to understand?
- Huggernaut 6y agoNo, it's not hard to understand, but that doesn't do you any favours. I'm not saying that someone needs to be so desperate to work somewhere (that would probably be bad), but if a candidate can't express why they have an interest in a particular role then that's of note, especially if I'm comparing to someone who can. Pretty much everyone wants to exchange their time and knowledge for money, but they could do that anywhere, so why here?
- odshoifsdhfs 6y agoI'm not sure what to reply. I was going to be snarky but prefer not to. From their website 'We help people create digital experiences their customers love.' Has anyone been 6, day dreaming in school, 'when I grow up, I want to help people create digital experiences their customers love.'? My interest in the role is it matches my experience and I want money. Again, if you are a FAANG, fine, if you are a startup no one really knows but pretend you are changing the world, you are making yourself a disservice by asking these questions. You can ask 'What are you looking in a new position/What excites you/etc', but to ask specifically why this company is tacky and I know I am not alone with this as I regularly talk with friends that feel the same. Maybe I am jaded as a software developer with more than 20 years professional experience, but job=money so I can money=things/time I want. 99.9% of companies aren't changing the world. They are trying to make money for the owners/shareholders/investors, and employees should think exactly the same, and that is motivation enough. If you paid a million dollars a month for people to dig holes for 8 hours a day, you would see the fastest shortage of shovels ever.
- hardwaregeek 6y agoAlso get feedback from candidates, especially rejected ones. The people who get offers will assume that the process works, since it validates their self-worth. Even if the process is very stupid. I've had processes that were so so bad from top companies. Like "here's a repo, clone it, write a program that will be judged by automated tests that you can't see". I had to basically guess what the tests were going to do, which turns the coding challenge into a game of luck. I'd love to do away with coding screens in general. I glanced at the doc for Stripe and it looks great. I'd have loved to read this doc, but the last time I applied to Stripe I got a HackerRank followed by an auto-rejection. I get why coding screens exist, but it's so annoying to be batted away because I failed blind automated tests.
- xen0 6y agoI think it can only be fair to ask for feedback from a rejected candidate if you (the potential employer) are willing to give feedback yourself, which is rarely the case, especially from larger companies.
- warent 6y agoThis might be what you'd think intuitively. I've conducted ~500 technical interviews, and in my experience candidates who are obvious DNP (do not pursue) often times really do not want your feedback or do not care about it, either because they think they're smarter than the whole process, or they're too busy turning inward to deal with an emotional breakdown. But those very candidates are the ones who are likely to leave the feedback! tl;dr candidates are happy to give feedback whether or not you provide any yourself. EDIT: I agree with you though. An interviewer should be ready and willing to provide feedback if the candidate signals that it would be welcome.
- pdimitar 6y ago> An interviewer should be ready and willing to provide feedback if the candidate signals that it would be welcome. And at which point would this happen, I wonder? All the interviews I went through during the last 4 months didn't have one person sound inviting along the lines of "we won't take you but if you think we can improve our process do let us know". Not one even hinted at that. It's all very... impersonal, cold and often feels like copy-pasted emails are being to sent to the candidate. You are kind of assuming -- way too generously -- that the process and the interviewers are actually open to feedback. Most people, including in tech companies, are happy to tick boxes and check in / check out at given times of the day, and do nothing else more creative or requiring special attention (like recruiting). --- EDIT: I tried giving feedback -- unsolicited -- after the rejection in my first 5-6 interviews. Didn't go well. You could tell people got offended by very simple points like "would have helped if you told me you will measure me with one extremely specific test while I am looking for a generalist role" or "what was the value of imposing a hard deadline on a homework while the candidate is going through several interview processes in parallel? does that tell you anything about their real productivity?", and a few others like "I am not sure that teling me 'I am not like the others in the team' is a valid point in remote working conditions where comms are mostly async and people don't chat that much". Etc. In the end you get tired hitting a brick wall. People are generally not receptive to feedback and even react in a hostile fashion when it is given to them. Plus when you want to go through 35-50 interviews, at some point you really start counting the hours that each company is taking away from you before rejection and you figure it's not worth it to try and present feedback where it's clearly not wanted.
- denzil_correa 6y ago> We will do our best to provide a 15 minute break and/or lunch/coffee break during your interviews, especially if you'll be interviewing for more than 3 hours. That said, we are happy to accommodate additional breaks or fewer breaks, depending on your preferences, just let your recruiter or recruiting coordinator know! I have seen this w/o breaks 5-7 interviews a day, too often. Some candidates suffer from low energy at the (n-1)th interview. The interviewer is baffled and gives a slightly negative feedback. The reason for the interviewee's interaction is not the skill of the interviewer. So, in short - please keep breaks. You should have a 1h (min.) dedicated lunch break if you have a long 1-day interview. In additional, you should schedule 15m breaks in the morning and afternoon session to let the candidate recuperate. Finally, please ask your interviewers to look through the candidate schedule. Take into account that they have had many interviews, do your bit to make them comfortable. Also, please do not spin this as "If you can't go without breaks in a 7h day, you are not good enough to work here". Kindness, empathy helps and makes you a better employer.
- barbegal 6y agoIs there any evidence to suggest that more than 3 hours of interviews is actually beneficial? 7 hours of interview seems like overkill. I've never had more than a couple of hours of interview: an hour with the department head and another hour with my future line manager and/or another senior employee.
- austhrow743 6y agoI can fake who I am for 3 hours. I'm not sure I could do 7.
- deleted 6y ago[deleted]
- ThePadawan 6y agoYour phrasing is such that I can't tell which side you are arguing for. I love it!
- 6y ago
- axegon_ 6y agoPerhaps a bit of an unpopular opinion but as far as interviews go, I think that seeing how someone reacts unprepared is a lot more valuable then seeing their work with them knowing what to expect. You see their ability to adapt and improvise, which is far more valuable then being picky about a particular library or technology. Yes, the quality of their tests will be lower, but that's fine and you can take that into account when you are checking them and you can check the test along with the candidates and ask additional questions which will steer them in the right direction, which ultimately will give you more insights about their thought process. Imo, their thought process is arguably the most valuable factor. Also the most valuable question you can ask as a part of the non-technical interview: "So do you have any questions for us"? If the answer is "no", you are not looking at a good candidate.
- Dayshine 6y agoThat only works if your task is equally unexpected/unusual for all candidates. If it isn't then either you punish them for being familiar with your stack (as you don't get that valuable knowledge) or you punish them for not being familiar (as you reward a good result). > you can take that into account I seriously doubt you can do this in a consistent and fair way. Whether someone does well in a completely unfamiliar stack is fairly random, so you're almost certainly filtering out excellent candidates who just got unlucky with understanding the IDE.
- ConsiderCrying 6y ago> I think that seeing how someone reacts unprepared is a lot more valuable then seeing their work with them knowing what to expect But why? The odds of them facing unexpected tasks on the job aren't that high, they have their job description, they have their set of skills, you delegate tasks based on that. It's not like there are curveballs coming every week where they have to upend their knowledge and strategies. It might be good to see how they act under pressure but seeing the person comfortable and putting in their best work helps evaluate how beneficial they will be to the company.
- brailsafe 6y agoImo, most of most jobs come down to how well you can tolerate doing what is basically intellectual grunt work while people interrupt your attention. As an IC, things are much more boring than ridiculous interview processes would have you believe.
- dilyevsky 6y agoAll of that sounds like you’re just going to favor people who are slacking at their current work, unemployed or have a ton of free time outside of work to prepare. How is that “leveling the playing field”? Obviously if you’re google or whatever your process is going to leak anyway so better to tell candidate upfront what to expect (and they do). If you’re smaller/unknown co may as well get genuine reaction rather than choreographed dance. Ofc that doesn’t mean you should expect candidates to have their env already setup that’s just silly.
- greggyb 6y agoI disagree. I've interviewed an abnormal amount: roughly every 8 months since getting my first job, and for more than one job at a time.[0] Based on my experience, the best interviews have been the ones with the most detail shared up-front. When I say best, I don't just mean my own performance has been best, but I also feel that the interviewer has been most satisfied and that they have learned what they meant to learn. The reasons for this are several-fold. In order to prepare a candidate well, there must be a well-structured interview process. This means that each interview should have some explicit goals - information about the candidate which the interviewer intends to elicit. It is painful for everyone and a waste of time for the goal of an interview to be unclear to one party (and many times so if the goal is unclear to both). My favorite interviews have been at several FAANGs, which were highly structured. I knew up front what the interviewers would be looking for in broad strokes, and how the interviews would be structured to elicit that information. I knew how technical acumen would be ascertained. I much prefer this over walking into a room with no idea what will happen. I do very well in those interviews as well, as I have spent much of my career in professional services, where part of my job description is to be always ready to project competence and to rapidly build rapport with new clients and potential clients. I also have much experience in interviewing to lean upon. Nevertheless, this is still a worse interview process, as I have to spend time figuring out what the interviewer needs to learn. You may object that a good interviewer should be able to guide the interviewee. This is correct on the face of things. However, any people are bad interviewers, because there is rarely much training or prep for them. I have had plenty of successful interviews where I have had to lead the interviewer, rather than the other way around. Additionally, there are very few jobs where job requirements include being quick on your feet and being able to rapidly (aka within an hour or so) ascertain what someone needs and how to give it to them. If you are looking to fill such a position, no-prep "genuine reaction" interviews might be a good fit. If, on the other hand, the position requires analytical thought and deliberation over periods of time greater than an hour (or whatever the length of your interview is), then such a no-prep interview seems a poor method to learn whether the interviewee has the skills you are looking for. All this said, I do not like interview processes that have large homework requirements. It is one thing to inform the candidate of the structure and broad content of the interview, but another thing entirely to request that they do extensive work. My most extensive interview prep (excluding homework assignments) has never been more than a few hours, even for FAANG interviews with much structure and lots of prep materials shared by the company. If you can't find a few hours to prep for interviews, you're probably not taking them very seriously. And if you can't fit two or three hours of prep into a period of one to two weeks, then you've got bigger problems in your life. [0] Note I haven't changed jobs this frequently, but I've always kept an eye out for interesting opportunities. I would interview companies to see if I like them or their job offer. I would frequently bail out early if it didn't seem like a good fit. Some I went for offers and used that to negotiate. Some I went for offers just to learn what comp packages look like. Some I went for offers to get the job.
- incognito_limey 6y agoI think an additional piece to this, is to tell candidates what level they are interviewing for and the possible salary ranges, not total package, but actual base salary ranges. I just went through an interview process with AWS that wasted a lot of time for both sides due to them not being up front about the potential package. I had to push a fair bit to get any info, and finally had to politely tell them if the it's less the X I don't think it makes sense to move forward. Edit: ----- Additionally, they were unable to explain how after two interviews, what an additional 7 interviews in an onsite capacity would add/build on top of the first two. It felt like they were just putting me through a gauntlet without really understanding why. It saves both sides effort if you can make sure you are in general alignment before going too far into the process.
- michaelt 6y agoA lot of people say "never be the first to give a number" (which might be wise if you aren't confident you have a good idea of your market value) but I've always found it useful to just give recruiters a salary requirement figure upfront. After all, I know $X is what it will take for me to move enthusiastically and see it as good for my career trajectory, so if $X is over their salary range being coy about what I want just wastes my time.
- twic 6y agoI think that "never be the first to give a number" advice is good if you want to maximise your income. If you want to minimise your drudgery, name a number as soon as possible.
- collyw 6y agoI agree. I am at the higher end of the payscale where I live (Spain so overall pretty poor salaries). Most jobs will be offering around average salaries, so it's saves me time to state up front what i expect.
- twic 6y ago> not total package, but actual base salary ranges Why base salary rather than total comp?
- jrockway 6y agoMy general thought is that your compensation scale should be proportional to the complexity of the interview process. If you're going to be copying the FAANG interview process, then the candidate should expect an offer similar to what they'd get from FAANG. In general, I haven't been disappointed on this front, but I fear that many people are. If you want to be super transparent about the interview process, you should probably define what compensation range you're going to offer and realize that some candidates will simply never contact you. Saves everyone time.
- pdimitar 6y agoThis is strongly misaligned with many companies' incentives so it will never happen, I am afraid. A lot of interviewing processes are kind of like fishing. They hope that if they wasted you 6-10 hours of your time before an actual offer then you'd make a decision based on the sunk cost fallacy ("not sure how much time the other companies will waste me, let's take this one on their offer, it's not so bad"). I am glad that your experience has been positive but as you correctly intuited yourself, many others' experiences are very far from it. (To clarify, the employer I started onboarding with is nothing like that; I am talking about all the others that I talked with before I stumbled upon them.)
- claudeganon 6y agoThe solution is to make companies pay people for their time during interviews, at an hourly rate equivalent to compensation for the position. Everyone else in the interview is getting paid by the company, after all. Suddenly, managers, hiring committees, and recruiters will stop wasting people’s time and everyone will know what to expect to get paid!
- freedomben 6y agoThat's an interesting idea, tho I expect it would have the unintended consequence of making it really hard to get an interview.
- 6y ago
- swarnie_ 6y agoI've just finished this maddening process for the 4th time in my "career" and it was as frustrating as i remember. To all potential employers and recruiters: When a candidate asks you for the agenda or some indication to the structure a meeting will take its because they want to be prepared. They aren't trying to "cheat", they want to be as productive as possible. Unless your company operates some insane work methodology where preparation for any task is strictly forbidden i don't understand why you wouldn't give them this info. Twice in my last round of interviewing additional people where added to the call with short or no notice. These people where obviously experts in their technical niches so expecting me to preform well in a 30 minute grilling unprepared seemed unreasonable.
- sokoloff 6y agoMy experience is that when obvious experts in niches are added late to an interview loop, that’s almost always a positive sign for the candidate. Those people are generally busy and aren’t on the “everyday candidate” loop typically.
- tumetab1 6y agoFor some reason developers seem to assume that the recruiting process is immune to the regular company dysfunctions. If they scheduled an interview without an agenda is because it's the norm to do that within the company when talking with outsiders. If someone jumps in to a call, it's their practice to have surprise guests within meetings. If someone ask you subject matter expert questions, it's how the company sees developers, as subject matter experts. So, you were interviewing to a company which views, my guess, developers as subject matter experts, has people jump in into calls and doesn't prepare specific calls.
- andrewstuart 6y agoIt's a pity job interviews aren't generally better run. I'm tempted to run the job interview myself and instruct them on how to properly assess and interview developers, and then go ahead and interview myself for the role with them watching on. But of course the outcome of that would be a rejection for insubordination - "not a team player". You can't win so you just have to shut up and hope that some random series of events will get you a job.
- robjan 6y agoI usually ask for feedback on the interview process from the candidate. Not sure how common this is.
- andrewstuart 6y agoThe psychology of recruiting is that once a candidate is rejected, the interviewers and company have lost any sense that the potential employee is competent and their opinions at that point are of little value. I'm yet to encounter a company that thinks their interview process is anything but awesome. Companies really aren't interested in feedback. This is human nature - pretty much anyone, when given "feedback", it is taken as criticism and the status quo is defended and the feedback disregarded. Companies who say they want feedback I think like the idea of asking for feedback but not acting on it or internalising it. If a candidate was not good enough for a job with a company, why would they be qualified to advise that company on how to improve? Don't believe me? Run an experiment - next time a candidate is rejected, ask them to give feedback to other members of your team, and in the unlikely event you get considered feedback, observe what happens to that feedback - don't intervene - just do the experiment to see whether the above assertions are correct or not.
- collyw 6y agoYou are more likely to get ghosted after wasting hours on a technical "challenge" than asked for feedback in my experience.
- davidhyde 6y agoGreat article but I also really liked the website. Fast and simple but still aesthetically pleasing. It's got that charm of being hand written. Love it.
- anjc 6y ago> We used to apply a ‘Sunday Test’: “If this person were alone at the office on a Sunday, would that make us want to come in just to hang out with them?”. However, this was the wrong phrasing for the idea we really cared about (we don’t encourage people to work Sundays, and we want people who would make excellent coworkers rather than be our personal friends). Instead, we now ask: “Is this someone we’d actively seek to work with” I'd love if this requirement were explicable and quantifiable. Two people can each be nice and kind, but not get along for whatever reason. When a hiring process can include face to face meetings with 10+ people, the chances of a suitable candidate being excluded for an arbitrary 'personal' reason seem high. What's the point in many stringent evaluation criteria if, at the end of it, all interviewers then have to agree that they can be besties with a random person. It's too fuzzy.
- kevsim 6y agoWhat I'd like to see is the process documented and actually stuck to. Not the content of the interviews, but the actual composition of the process - how many interviews, timelines, etc. I've been on both ends of terrible recruiting processes. Processes which have gone so slow that good candidates get away, processes with slow follow ups after interviews, processes where candidates are asked to come back in with short notice. I think documenting and sharing how the process is going to run might cause it to actually run that way. That may be wishful thinking.
- azhenley 6y agoA recent research paper looked at traditional coding interviews versus "private" interviews. One of the authors summarized the paper in a blog post [1]. [1] The case for the private technical interview. https://medium.com/@gameweld/the-case-for-the-private-technical-interview-4a92947e1692 https://medium.com/@gameweld/the-case-for-the-private-techni...
- pm24601 6y agoHow about telling candidates why they were rejected?
- stronglikedan 6y agoI presume it's a liability thing. It only takes one candidate to "spin" an otherwise valid reason into something they can sue for. Same reason why companies don't tell employees what they're being let go for in at-will states.
- pm24601 6y agoThat is not true. GDPR specifically requires that interview notes be available to the candidate
- greggyb 6y agoI've had some surprisingly good feedback experiences in recent interviews. One was at a 40,000-employee global tech professional services firm. I got feedback from each interviewer filtered through the recruiter at each step along the way, sharing both positive and negative. This process ended in an offer I didn't accept. Another recent interview process at a FAANG ended in a rejection. The recruiter followed up with me and informed me which interviews were considered a pass and which were a fail. Each interview had several components, and the recruiter was able to tell me which components were the cause of failure in the one interview, and what to focus on in any future applications to the company.
- raghava 6y agoIMO, if a company is very serious about hiring for the role, they must offer a 1 week trial period (PAID!). The candidates get a fair idea about the kinda muck they might be getting themselves into. The team(s) get an idea as to what kinda schmuck they get to deal with over next months. It's too easy to fake "expertise" and "culture fit" over a 2/3/4/5 round interview each lasting an hour or so. Most companies who deem this mode as not an option, simply aren't looking for great experts or engineers, but rather a cog in the grand system of wheels to keep the show running - or what HRs end up calling - a resource! Solution: What can engineers do for this problem? 1. Propose this option (1 week PAID work trial) to HRs 2. Keep a backlog of technically engaging, but smaller work-items which could be taken up with least amount of background-knowledge , or something that has an easy-ramp-up-path for a newbie in the realm 3. Iterate and improve This is just an extremely condensed internship of sorts. And many firms understand the value of intern-to-hire path.
- XargonEnder 6y agoI like it except for one problem. I never leave a job unless I have a job. Seems too risky to jump ship from a good job where you're under paid to get a chance at a little more money.
- raghava 6y ago> I never leave a job unless I have a job. This is actually solved by this approach. Nobody needs to quit, a week's leave/vacation is good enough for the trial period. Or, am I missing anything?