That doesn't really match my experience. Usually if my problem is not unique it's already documented somewhere and I've solved it that way (And support generally puts some effort into documenting the non-unique problems to reduce their workload). If I'm calling support, it's because I've exhausted all other options and I've either concluded I need them to do something I can't do with an online form or the information is not at all accessible elsewhere, in which case first line support is nothing but an obstacle.

Sure, because you've already lived with 10+ years of enshittification in the process. Customer support used to be an in-house team that was actually trained on providing relevant support, not an outsourced call-center that's as (or more) useless than a chatbot.

In some ways it's not that different with hiring. I used to work with HR teams that knew the roles they were hiring for extremely well and could make reliable calls on whether or not to pass a candidate to a hiring manager. More recently I've seen HR get outsourced entirely, or staffed with cheaper employees that just shuffle documents through systems.

The AI and the human are both programmed to avoid helping you.

At this point I find the humans know so little that an LLM referencing documentation or past support answers is superior.

Certainly, because not deviating from the scripts also cuts off the infinite range of made up nonsense a bot can hallucinate. And it's not like the bot will have magic authority to fix the real issue it can't be bound by the script, so in this regard there is no upside.

> The last mid-level Python dev job I posted had 300 applicants in the first hour, with 1/4 of them being from acupuncturists and restaurant servers who have never written a line of code.

That has to be due to policy failure of forcing people on benefits to apply for jobs to get benefits, even if they already have applied to all suitable jobs there are right now?

> candidate time is free and manager time is massively expensive

This is a naive view of the proceedings. Why not hire literally the first person that applies? That would reduce your cost even further.

The point is to figure out who would be good at making you money. The question is, does an ai chatbot wasting your prospective candidates time make you more, or less, likely to find people good at that? Perhaps it reduces the amount of cost reviewing applications, but I imagine it also drives away a good number of the better candidates, those that have more options, away. If you're cutting corners and cost this much, why are you even hiring? surely the point of the exercise is looking towards future growth.

Naturally, there is also a limit to that line of thinking also - spending weeks reviewing each one of the ten thousand applications to your junior developer role wouldn't be the most efficient way to grow. But surely there are better filtering methods you can think of than this, which is imo the equivalent of planning on reducing the number of candidates by lining them up in a room for hours in sweltering heat and hurling verbal abuse at them until only a couple of the wretched ones without a shred of dignity are left

[dead]