You can see from the application data that each role that's been reposted already has hundreds of applicants, which implies that it did last month as well.
Why would you repost a role vs just going through the 1000 applications you received last time?
What is the reasoning there?
Not really a new practice, but having job postings and job searching online makes it more obvious. Running ads for jobs the employer may not fill has few downsides and doesn't cost much.
Digging through job postings and applying to them has turned into a numbers game, and an arms race of automation and now AI tools. I suggest a more effective job hunting strategy, because worrying about ghost job postings just wastes your time if you intend to find a job.
It's always been a numbers game, at least over the course of my career.
As a freelancer I do get gigs through an agency, but even that works mainly by word of mouth. I never apply or do anything resembling an interview for those jobs. I keep my freelance customers for a long time -- five years or longer -- so I don't have to churn for new projects all the time. Even a fairly small company can keep a few programmers and system admins busy.
I understand that people early in their career don't have a lot of professional contacts, and that makes it hard to find a job. In that situation perhaps it makes sense to apply for a lot of jobs, but I think targeting a few specific companies and cultivating relationships will get better results, even for someone fresh out of school or laid off from their first job. A person who went to university should have quite a few contacts from school. A person who worked even for a few months has colleagues from that job. When someone posts that they have worked in the business for a while but have no professional network I wonder how that could happen -- take off the headphones, stop shunning every meeting and social interaction, meet more people, and not just other programmers/tech people.
But it's still a numbers game. All that changes is how big those numbers have to be. What I mean by that is when I'm looking for work, I'm not doing it one application at a time. I develop a list of the places that I think would be good, and apply to them all.
What specifically do you suggest?
A more targeted approach as described in books like What Color Is Your Parachute? and Who's Hiring Who? will let you actively target a job, rather than passively sending in hundreds of applications/CVs like everyone else.
Some combo of both could grow your network while opening new areas.
Another difference: focusing on relationships and business domain expertise, versus trying to exactly match a "tech stack" to job listings. No company ever needs another five thousand lines of JavaScript. They need people who can solve business problems and add value.
I live abroad and travel constantly, but only work for US companies. They pay better and I don't have any language or culture mismatches.
This is why I don't look for jobs on LinkedIn, it's the garbage heap of false optimism.
Is this messed up and totally broken? Yes. Is it how many recruiters operate? Unfortunately, yes.
One of the answers was (paraphrased), "because we're constantly recruiting for that title, but maybe not the same team." I'm not sure if that was a good or bad sign. Growth? Or constant turnover? Really makes you wonder.
I manage a highly stable tier 2 software team embedded in enterprise, and only recruit maybe once every ~2 years, if that. Hard to relate to what is going on these days.
> you can't let teams who have not hired for 2 years come up with their own process
Perhaps? We're a 9 person backend department inside a 250 person ISP. Not the typical type of team we talk about here on HN. I doubt small startups need a pipeline either, they just hire on demand.
More likely reasons:
https://en.wikipedia.org/wiki/Ghost_job
https://www.bbc.com/worklife/article/20240315-ghost-jobs-dig...
Note that this is out of the people on the job market applying for these jobs. Most of those people will never be hired for a coding job and so they'll be applying to every job they see on LinkedIn for a year or so.
This is worse for low barrier job portals. 1 out of 2 may be able to pass FizzBuzz out of applicants from HN. There are a lot of people on HN who hate tech and are burnt out. A lot of these guys hate Next.js but will learn it for money. Half your applicants on LinkedIn don't know the difference between Node.js and Next.js and will go into the interviews without checking.
Why not just post the role in the future when its ready and get applicants that way?
https://en.wikipedia.org/wiki/Ghost_job
I think you have an erroneous model of how the job "market" works. Right now employers have the upper hand with tech jobs, at least junior and mid-level jobs. With so many people laid off and coming out of school competition will get most fierce at the low end. Employers don't have to care, they will get piles of applicants regardless, and can pretend to hire with online postings until it suits them to hire.
The people asking about these practices, and getting upset and indignant, either never had to search for a job before, or got their last job back when demand meant anyone who could credibly put "React" on their CV got ten offers right away. Those days have gone.
> "It is possible that state laws have posting requirements for employers awarded state government contracts. "
https://www.shrm.org/topics-tools/tools/hr-answers/regulatio...