I just chatted online with someone currently hiring for a mid-level software engineer who received more than 2,000 applications. That’s ridiculous.

So (inspired by actual events), I’m writing a freelanced article, "Upending the hiring process for technical talent.” Although the topic applies to any job search situation, the story is tuned to software developers and other tech fields, and I expect both remote work and AI to be primary factors.

Getting thousands of applications is nuts for both the company and the applicants. My question is, "What — if anything — can be done to make the process more sane for everybody?"

I would love input from the wise people on Tildes. (Formal attribution is not required, but context is helpful for verisimilitude: "...says one program lead from a midwest insurance firm.") I know you have opinions. However, the HIVE MIND responses I care about should come from people who have been affected by this change – primarily HR professionals and tech industry hiring managers. My short (?) list of questions:

• How many job applications do you typically get today for a technical position such as a software engineer? How has that number changed?
• Are there differences in the applications? I’m open to anything from “remote work expanded the number of people who want to work here” to “They are impersonal and seem AI-generated” to… well, what? Tell me.
• How do you triage the applications (no / maybe / worth talking to)? How long does it take? For HR, what percentage of the applications are provided to the hiring managers? For hiring managers, how does that percentage make you feel?
• How have you changed job listings? For instance, are you asking for more information in the application process or including more detail in the job req? Are you employing tools that claim to sort responses? Are you offering salary transparency so that nobody wastes time when the numbers don’t align?
• What changes have you implemented in the job process? (Turning more to recruiters, for instance? Relying more on employee referrals?)
• Is “return to office” an issue here? (I would imagine that “local candidates only” would reduce the number of applications, but I don’t want to assume too much about any HR connection.)
• Regardless of what your company IS doing to deal with the job application deluge, what — if anything — do you think COULD be done to make the process more sane for everybody? What would you do if you could wave a magic wand to address the problem?

I realize that businesses want to draw talent from the largest pool possible, and to do so available positions are often advertised simultaneously across several job market websites with audiences larger than what almost any company could reach on their own. Certainly some steps of the application process must be automated when dealing with, what I can only imagine, is a relatively high number of applicants. Websites like Indeed.com have even automated the phone interview process, having applicants take a robo-call and recording their responses to questions selected by the employer. The result, in my own experience, is an often bleak, one-sided, discouraging and depressing bout of dysfunctional online dating, except the relationship you're looking for is with your future employer.

Are there any HR people on Tildes? If so, I'm curious what this whole process looks like on your side and how it differs from say, twenty years ago. Is the process better? Are the people you hire better? How, on your end, could this process be improved? And most importantly, do you have any advice for getting through this increasingly frustrating first step?

I'm in the midst of an interview process with an employer that insists on an "Introduction to Algorithms"-type test for all of its white-collar workers. Their claim is that it selects for "smart" people. [I'm anxious because my relevant coursework was many years ago, and there's no way I'll have time to master it again before the scheduled test - there's some age bias, noted below.]

Based on review of Glassdoor's comments about this company's interview process and demographics, what they really want is recent college graduates with fresh CIS degrees that they can abuse and use up quickly, giving them no market-relevant skills in the process. The product relies on an obscure, specialized database architecture and elderly front-end code.

However, the company is a market leader in my industry, and I'm interested in working there in a customer-facing technical liaison/project management role because the product is better fitted for task, has better support and customization, and better interoperability than anything else. There's huge R&D reinvestment as well, and the company is just that little bit more ethical in the marketplace than its competitors.

Do you believe that the ability to do sorts and permutations in code genuinely selects for general intelligence, and would you want to work with a population of people who all mastered this subject matter, regardless of their actual job title?

I posted an article yesterday about name-blind hiring processes, and it got me thinking of discrimination slightly differently.

I actually don't feel that we run into outright racial discrimination as much nowadays. Instead it's more subtle. It's not about technical merit, but about cultural fit. Often times, distilling down to one skill - English (both spoken and written).

It brings up questions such as:

• Can a candidate communicate verbally for the job? (Technical, though sometimes this may be judge harder than for a native English speaker that isn't always clear)
• Do they "get" jokes and other subtleties? (Cultural fit)
• Do they have an accent? How heavy is it?

I believe this is for a couple reasons:

• Candidate just can't display enough charm or charisma during the hiring process
• Raise doubts about a candidate's education/upbringing. This in itself is discriminatory (though location is not a protected class), but some regions are though to train their students in more blunt force manners than skills in problem solving

What do you all think?