9 ms·
> Most jobs are now hoops after hoops, not taking into consideration your particular profile or the contributions you can make. I’ve done some mentoring of CS
by Aurornis 2y ago
> Most jobs are now hoops after hoops, not taking into consideration your particular profile or the contributions you can make.
I’ve done some mentoring of CS grads for the past few years. We some times get people with unreasonable interview demands, like companies asking them to make an entire app or website for the interview process. We advise them to decline the really excessive ones. However, it’s rare to see that.
Often we’ll get people complaining about excessive interview loops, but when they describe the process it adds up to around 4-5 hours total. I think the expectations for interviews became really distorted during the period a few years ago when some companies were hiring anyone willing to do a short interview. Many younger engineers entered the workforce when that was normal and now any amount of interviewing feels unreasonable.
I frequently have to convince people to do simple take-home problems (often 60 minutes or less, I see them because they post them into the chat frequently) because Reddit tells them to decline all take homes. Some days I’m pulling my hair out because someone who has been unemployed for months has valiantly refused yet another take home problem that could have moved their application forward with a minimal time investment.
Another problem I’m seeing a lot is people who halt their job search as soon as they receive a response from a company. We have to repeat over and over again that job searches are a parallel process, not a sequential one. It really hurts candidates who interview with one slow company and then wait around for months for a response before they move on to the next application.
While there are definitely some excessive interview loops out there, the average case honestly isn’t as bad as I read about on the internet.
- golergka 2y agoI love long takehomes. They're like pet projects, but with clearly defined goals and with people that might even give you a review if you're lucky. I always use them to try a new library or a framework, and often continue improving on them even after they're submitted and evaluated.
- pants2 2y agoI had a take-home assignment to build a Dropbox competitor around 10 years ago, it was a pretty big project but I actually still use it for sharing files with friends because it's legitimately much easier to use than Dropbox.
- GJim 2y ago> I had a take-home assignment to build a Dropbox competitor around 10 years ago, it was a pretty big project I'm genuinely amused you thought (think?) it acceptable to do such work without payment. Here, any potential employer submitting such a request would be laughed at.
- mrkstu 2y agoWell, technically if he isn't getting paid, it's his copyright, allowing him to use the code and even create a business around it, and the company has no rights to it- so in this case it worked out well for him. But yes, its a pretty crappy idea that people should do 'real' work for free to get hired.
- digging 2y agoSure, but at best that's unrelated to their value as an interview process. At worst, it's actually making things worse for you, because you're distracted and not doing more interviews.
- ninininino 2y agoQuality beats quantity. If you smash the hell out of a take-home project you won't need to do any more interviews. Companies that rely on take-homes usually are the same ones that don't make you go through Leetcode/trivia gauntlets. My biggest advice is if they say to use 4 hours but you need 8 to do an amazingly thorough job then use 8. It's basically cheating but I've always found that it doesn't end up causing any actual problems in terms of being able to deliver at a velocity they needed in actual product work post-hire.
- gopher_space 2y agoMy biggest advice is to assume the reviewer is a bored junior running down a checklist that tests only what was in the spec. They have like five minutes budgeted for getting your project running and a pile of applications to go. > Quality beats quantity. If you smash the hell out of a take-home project you won't need to do any more interviews. This means a decent amount of that time spent on documentation, imho.
- camdenreslink 2y agoI do as you do, but there is a very real risk that nobody will ever look at it. Or it gets assigned to a dev (who has a lot of other real work to do) to look at and the give it a cursory once over and a thumbs up or down.
- jofla_net 2y agoI had one where after weeks of work, tweaking, it received zero time on their eyeballs. And I know because they never went to the link i sent. So ghosting a project is a very huge reality...
- 2y ago
- trallnag 2y agoHow often have you done such tasks?
- dennis_jeeves2 2y agoTroll!
- KaiserPro 2y ago> I love long takehomes. I am happy that you are full of life and joy with programming. I genuinely want you to keep that, it is precious. However, they are getting free labour from you, so just keep that in mind. For me, I can't do that anymore. I just can't muster up the energy to work on problems for something thats not going to be taken seriously by the "client"
- funemployd 2y ago4-5 hours... per job. Do you think most people apply to a single job and just get it?
- pants2 2y agoThat's the whole process if you get hired. In the hiring process at my company we'll maybe give take-home assignments to three candidates for one role. So by the time you're doing our 4-hour assignment, you have about a 1/3 chance of getting the job. Not a bad deal in my opinion.
- atomicnumber3 2y agoIf, given you are at the beginning of the "do onsite interview loop" stage, you have a 30% chance of getting an offer, you will need to do NINE of those to have a 95% chance of having gotten >= 1 offer. So yeah that is kind of a bad deal assuming you already have a full-time job and/or family/kids. I guess if you're single and unemployed then it's not so bad, aside from the fact that being unemployed greatly cuts your bargaining power?
- fasa99 2y agoAs a whole unemployed cuts your bargaining power, it's natural to say "why should I leave my job" as a counterpoint. The flipside game is if you can arrange multiple offers at once (i.e. a high value candidate) while unemployed, it's a fantastic feeling. Then it's more like an auction, and auctions can get irrational. Turnabout is fair play and all that
- zeroonetwothree 2y agoYou are probably more likely to get hired if you are already employed (at least that’s been my experience)
- FireBeyond 2y agoHah. I have had multiple instances lately where I submit an application on LI/Indeed, and minutes later: "[Company] has invited you to work on this take-home assignment." Those just get circular filed. I'm not doing an assignment to get the privilege of a first round interview.
- thayne 2y ago> it adds up to around 4-5 hours total. That's fine if you can get a job after a few interviews, but when a talented job searcher has to go through that dozens of times to get a job offer, and much of the interview is "leetcode" questions that don't evaluate the skills you'll actually use, is it surprising people are frustrated by the hiring process?
- burningChrome 2y agoI got fed up this about 8 years ago when it felt like this approach started. I would go in for a front-end role and people would start asking me about .Net and show me .Net code and ask me see I could figure out why the code didn't work or troubleshoot some Python snippet. I thought I would never walk out of an interview. When I walked out of three of them because of stuff like this, I kept asking myself if I was being unreasonable. I came to find out talking to other dev friends, this was becoming fairly common and I have no idea why. All of the big corporations I worked at always focused on specialization. You a DB gyy? Then that's all you do and you're an expert. Front-end guy? Sure, know some design, but client side stuff you should be an expert. Now? Feels like, "How many roles can I hire one person for?" is the standard bearer.
- mr_toad 2y ago> this was becoming fairly common and I have no idea why. Too many chiefs, not enough braves. The length of the interview process has grown with the proliferation of scrum masters, project managers, project leads, business analysts and seemingly endless other roles. I miss the simple days of direct lines of management and shorter, simpler interviews.
- ericskiff 2y agoFor over 10 years we've had people do a paid ~4 hr take-home which is very similar to the work they'll actually be doing (here's a dummy codebase, add a few features fix a few bugs). If they're not interested in getting paid to do that work now, it's a good signal for us that they won't be happy doing it when they're working with us. It's helped us find really wonderful people to work with.
- saulpw 2y agoDo they get to pair with your team on the take-home or are they doing it solo? I'm not happy working by myself on features/bugs in a codebase that no one will ever. It's meaningless work. If that's the job you're offering, then you're right, great signal. But I imagine at your company that you work together on a codebase that people are using. That the requirements and bug reports are coming from actual users if not customers. If so, then you may be discarding some good talent who might be better for your company. The ones who will push back on bullshit work because they can see it's not doing anything for anyone.
- ahaferburg 2y agoI think that's very fair. Problem is when they expect those 4+ hours of work for free.
- ascendantlogic 2y agoPaid take homes are probably the least worst way to suss out signal in today's hiring market. The only time I had better was when I just set up a nights/weekends arrangement with a company and just started ripping through real tickets. Ended up getting hired on full time and they cut me a check for a few thousand dollars up front. It was very nice.
- notaustinpowers 2y agoI remember I once applied for a job that was entry level mortgage customer service or something like that, paying just $45k/yr, can't remember exactly. I had to go through 5 interviews over the course of 4 weeks, with the final interview being with the VP of Marketing. Got the job offer, was waiting for the paperwork, and was called the next day that they are actually going on a hiring freeze and cannot hire me. It was absolute buffoonery to me. Why on God's green earth is the Vice President of Marketing interviewing the candidate for an entry level customer service position? Especially after I already interviewed with an HR rep, the Head of HR, and the Team Manager before them. Do they not trust their team? It makes me feel like these interviews are just to make management feel important again since it was a WFH role.
- wyclif 2y agoI get your point. But to me it sounds like you dodged a bullet.
- fakedang 2y agoTech companies inflate roles, especially in sales teams, so that enterprises think they're talking to someone important, when in reality it's just a dude with his second job out of college. Same with Investment Banking Vice Presidents (although IB VPs will definitely have the experience to back it up, if not the authority in a deal).
- bfung 2y agoThe job titles in the different industries are pretty interesting, also, that inflate/confuse things. At financials (and sometimes sales departments), you have, from most junior to senior: 1. Associate 2. Analyst 3. Vice Presidents 4. Directors (MD - Managing Director) Whereas in software/tech, it's usually Directors that are subordinate to Vice Presidents.
- dexwiz 2y agoI heard a major US back had something like 9k VPs. Reason is the same as GP. Everyone felt special when they had a VP personally handling their account. I have seen Product Management go this route. Seen Senior Directors with 5 or less, sometimes 0, direct reports.
- viridian 2y agoAre you paying me for that 4-5 hours of my time? If not, you'd better be a damn sight better in terms of what you offer as an employer, versus the rest of the market. I get that it's different for the unemployed, but we shouldn't let people do this to us if we are in a position to help it. I personally have only ever dropped a potential employer mid interview pipeline once, and it was when they sprung one of these on me. Even worse was, I was told it should only take 3-4 hours to do. Just eyeballing it, it seemed like 8 hours of work at least, which made dropping out of my candidacy an even easier decision.
- Aurornis 2y ago4-5 hours was for the whole process, recruiter call, screening call, time for questions from the candidate, negotiation, and others. I was not suggesting every candidate gets a 4-5 screen at the start.
- bluefirebrand 2y ago> when they describe the process it adds up to around 4-5 hours total 4-5 hours is pretty excessive for an interview process actually. A candidate cannot be doing 4-5 hours for an interview process just to hear a no at the end. Successful job hunts need to have many irons in the fire at once and if each one is taking 4-5 hours there's only so much you can realistically take on I know that interview processes generally aren't designed to make things easier on candidates but they probably should be if you want good candidates
- Beijinger 2y ago"4-5 hours is pretty excessive for an interview process actually." I have been asked for basically two weeks of work. I don't think it is unreasonable. You just have to ask "10k okay?"
- darkerside 2y agoThat's a time investment for a serious consideration, and I don't think it's unreasonable at all. Nobody is making you spend that time, but if you choose not to, understand that plenty of qualified people will happily do so and get the job.
- tomduncalf 2y agoExactly, and you can also look at the interview as time for you to vibe check the company. Even in a purely coding interview, I find there’s a noticeable difference in demeanour between interviewers who will probably be empathetic and good people to work with, and people who won’t. And if most of the interviewers fail that vibe check, the job probably wasn’t right for you. I can see how lengthy interview processes are annoying if you’re applying for loads of jobs, but honestly 4-5 hours doesn’t seem unreasonable and I’d actually be a bit concerned about any company that was willing to hire me with substantially less time to see if I was a good fit.
- ipaddr 2y agoIf there are plenty of qualified candidates there must be an over supply of candidates in the market. Too many developers but not enough roles.
- darth_avocado 2y ago> I think the expectations for interviews became really distorted during the period a few years ago when some companies were hiring anyone willing to do a short interview. I find this whole thread really enlightening. As someone who has been trying to move around in tech in the Bay Area, outside of Amazon who hired en masse, most companies have had 6-8 interviews as a standard hiring process for almost the last entire decade. What's really happening is that most of the people who were on the other side, being very selective in who they hire, are now really coming to terms with how bad the process is because they are the ones now trying to find jobs. The problem always existed for someone else, now it exists for you.
- rprospero 2y agoI also find this thread interesting from the opposite direction as someone not in the Bay Area. In the past ten years, the longest job interview I had was two hours long. Honestly, most of the interviews I've been in (on both sides of the table) have been closer to half an hour.
- ipaddr 2y agoI entered the workforce 25 years ago and interviews were less than an hour many times hired by the time you made it home. Somewhere in the last 5 years someone thought I don't want to be on the hook for a bad hire and I will not get in trouble for not hiring so unless someone else recommended a person don't hire until it's not your decision. Get as many people in the loop as possible and make sure they meet with everyone twice. Now no one is responsible. Instead of hiring restart the process. At year's end talk about the amount of people you put in the pipeline and how many interviews you did and put your flag down. A bad hire might cost you 3 months salary 30,000. A bad hiring process costs millions. In the end these companies are not shutting down because of not hiring developers so maybe their process is working as intended. The demand for developers was inflated precovid because manager headcount pride, hiring so other companies wouldn't and company valuations tied to spending. Back in the day you had small teams and little management. Now you have layers of management, and huge teams that use complex tools designed for huge teams that create new work so even bigger teams are needed. They produce the same amount of work the small team does but take much longer. Management is able to measure daily progress in an artificial way through constant status meetings. They get addicted to the constant data stream and think they have a pulse on the team. Meanwhile the amount of important work that gets done hasn't changed just the cost.
- farhanhubble 2y agoYou're almost right, but firing a bad hire in many places is near impossible.
- gen220 2y agoI think this is the root cause of most problems. No hiring process has a zero false positive rate. A company needs to be able to fire people quickly and humanely, otherwise good people will leave and you have a mediocracy / Peter principle problem. If you keep a reasonable hiring bar and enforce a reasonable firing bar, you’ll do fine. Netflix famously did a lot of experiments on this that have been written about in public. Being squeamish about freeing people to find a better mutual fit job is really harmful, to an underrated extent.
- csa 2y ago> Often we’ll get people complaining about excessive interview loops, but when they describe the process it adds up to around 4-5 hours total. I’ve researched and negotiated the terms of buying small businesses in less time. 4-5 hours is excessive for most jobs imho. You might be able to justify up to three or so for a C-suite position, 1-1.5 should be enough for most lower level positions, and anything beyond that is just institutional masturbation. Collect a work sample, talk to them about work to see if they are like-minded in terms of working norms and habits. At that point, if it’s a hell yeah, then go with it. Otherwise it’s a pass. If a new hire significantly underperforms, just help them find a better place inside or outside of your org during the probationary period. If they are just leeches, then fire them mercilessly during the probationary period and revisit your hiring process.
- meroes 2y ago4-5 hours? No assessment should be over 1 hour and 3-4 hours of interviews for most jobs is excessive. I’ve trudged through long assessments. I can’t think of a single one where a better thought out 30 minute one wouldn’t better. No. I’ll tell you EXACTLY what is going on. The long interview and assessments are because jobs don’t train anymore and these unpaid or underpaid hours are the initial training. 3 hours of assessment means 3 hours getting used to their systems and workflows. You’re just reinforcing wage theft and gaslighting, that’s all.
- mind-blight 2y agoI've been on both sides of plenty of multi hour assessments. Unpaid training is absolutely not the reason. As an employer, I don't want to spend time training anyone unless they're actually going to be hired. It's really hard to figure out if someone is going to be a good fit for a job, so the idea is to get as many different perspectives as possible. Hence why you often interview with different people on different roles as part of the process
- bboygravity 2y agoI think fu pay me applies here. If you're going to "assess" me for 5 hours, I'm going to send you an invoice for 4 hours with 1 hour special discount for special fwend.
- mind-blight 2y agoI mean, that's fine if you discuss it up front with the company before heading on site. You severely limit your options, but I know a few companies that have agreed to payment. Though, it's worth noting that the company is already spending a lot of money interviewing you. Especially if they're paying for flights, lodging, and meals for an on site. It's worth figuring out what your goals in demanding compensation for being interviewed are. If it's making sure the company isn't "taking advantage" if your time, then I think that's already covered (interviews are super expensive expensive for companies) so long as 4 of those 5 hours are with actual humans. If it's due to financial hardship, most companies will be sympathetic and work with you. If it's to satisfy a sense of moral righteousness, then I think there are better options than sending and invoice after the fact (which comes across as passive aggressive and would ding you on your communication skills assessment)
- johnnyanmac 2y ago>but when they describe the process it adds up to around 4-5 hours total. 4-5 hours for an entry level role does seem excessive yes (if you're not a top tier tech company). How much do you really need to gleam from a new grad? Why does a new grad need to talk to the CTO to show their eagerness? I've gone through longer hurdles (one interview I did for a potential 2nd job with 2YOE at the time was HR call, 2 stages, and an all day interview with 3 technical stages and 2 "culture fits". So evaluate the stages as you will there), but that doesn't mean I saw it as reasonable. I don't hold the cards in these processes though. >I frequently have to convince people to do simple take-home problems everyone's experience will vary, but I've never had a "simple take home problem". Ironically enough my shortest problems were timed 90 minute leetcode medium-hard questions. most other takehomes are just 4-12+ hour miniprojects or quizzes spanning coding, math, language domain questions, and system design. I did it for my first few jobs, but I really can't these days unless I am already far along. Especially when you get a few from last year that ghost you after you turn it in.
- xienze 2y ago> 4-5 hours for an entry level role does seem excessive yes (if you're not a top tier tech company). Not really? Between a half hour with the recruiter, an hour with the manager, an hour or 90 minutes with the broader team, a little time with HR, you’re bumping right up there on 4 hours. I agree with the parent, people’s expectations have been warped recently.
- johnnyanmac 2y agoI don't really count the recruiter call. This is basically just "tell me about yourself" and "can we align on compensation/localtion"? Not much to study for outside of remembering your resume. I don't count the offer stage with HR for similar reasons (though these days, even the offer stage doesn't guarantee an offer, even if you don't negotiate). So maybe it's a misalignment. that's a 2-3 hour interview gauntlet in my eyes. >I agree with the parent, people’s expectations have been warped recently. I've done much much worse in my experience. Doesn't mean I think it's okay, productive, nor respectful. Recruiter -> manager -> Team is a fine 3 step process process (with a potential take home test. so 4 stages) I agree with responses questining the marginal value of the 5th stage with another team member, the 6th stage with some C class you'll never directly talk to, and beyond. Very few people are are applying for director roles, which is the only place I can see such stages needed.
- FireBeyond 2y ago> unreasonable interview demands, like companies asking them to make an entire app or website for the interview process. "We don't want you to spend more than 3-4 hours on this", where "this" was: Build a log parser for streaming Apache CLF. The parser should: Keep a rolling monitor of the top 10 requests, displaying their velocity in req/sec as a rolling average. Display aggregates of visitor counts over the last hour and day. Have high watermark alerts when ingress traffic as a whole, or to hotspot URLs hit thresholds, and then be able to de-alert when traffic dropped. Scaffolding to deploy same. Unit tests and documentation for same. Ability to ensure URLs were safe, stripped of any GET parameters. > Often we’ll get people complaining about excessive interview loops, but when they describe the process it adds up to around 4-5 hours total. One non-FAANG (not even close) well-known on HN's interview loop: - recruiter screen - 30m - hiring manager screen - 60m - networking meeting - 30m - resume deep dive - 60m - peer interview - 45m - cross-functional team collaboration interview - 60m - leadership interview - 45m - values interview - 30m - department specific interview (picking on 'product') - 60m - discuss take home writing project - 60m - engineering collaboration - 30m Things like that? Ridiculous. Oh, fun fact, they ask you to tell your references to expect a 30 minute call from them.
- camdenreslink 2y agoI’m pretty sure I did that exact take home project. It was interesting and I felt I did a good job, but it was excessive. I really wanted the job though (rejected due to getting vetoed on the last interview I think).
- FireBeyond 2y agoWas it for a company starting with D?
- camdenreslink 2y agoIt was indeed. My interview process took like 6-7 weeks or something by the end. Was quite the disappointment at the time.
- 2y ago
- dennis_jeeves2 2y ago>Some days I’m pulling my hair out because someone who has been unemployed for months has valiantly refused yet another take home problem that could have moved their application forward with a minimal time investment. How would you/candidate know in advance that the current take home problem will lead to a hire, if completed ?
- DrBazza 2y ago> adds up to around 4-5 hours total. > a few years ago when some companies were hiring anyone willing to do a short interview. Many younger engineers entered the workforce when that was normal and now any amount of interviewing feels unreasonable. When I interviewed in the 90s "short interviews" were the norm. 4-5 hours are excessive. Especially if people are interviewing for 10 or more jobs. That's 40-50 hours interviewing. Even if you're single and young, that's onerous. Doubly so if you're senior with a family. I'm not sure many other industries ask people to do tasks like this in their own time as part of the recruitment process. Certainly not one of my friends that's an engineer. He's never been asked to machine something on his lathe or milling machine. Nor one of my friends that is an architect. I can't imagine surgeons get many 'take home' tests either.