3 ms·

Similar thing here. The more candidates we reject the more scrutiny we get and management starts hinting we should take what we can get. The latest few hires we

• flagrant_taco 3y ago
  > The latest few hires we’ve been told to just ask basic questions and not do any coding stuff. Oh this is one that would definitely get me in trouble. I'd rather just not hire someone than make a bad hire, and I expect I'd be pretty ticked off myself if management was telling my team to dumb down our interview process and make it easy for most anyone to fill the seat
• jjav 3y ago
  > The more candidates we reject the more scrutiny we get and management starts hinting we should take what we can get. This is actually quite rational. Does the team actually need the help? If yes, just hire someone already who is adequately qualified and has a good attitude. These people are super easy to find. But lots of teams like to have a req open forever while they keep looking for that absolutely perfect candidate on a hundred arbitrary scales who has spent a lifetime working the exact tech stack they have, is totally willing to spend a year crunching leetcode and doesn't ask for much pay. So it's more of a game, like a cat toying with a mouse instead of actually needing to eat. In that case it is the best decision to close that req and reallocate the funding to some other team who actually needs help right now.