BelVisgarra
BelVisgarra on Hacker News
Posted by
BelVisgarra on Sunday March 08, 2026 @10:15PM
from the ask-hn dept.
The scale is probably the bigger challenge now. When a role gets hundreds or thousands of applications, even distinguishing small differences between candidates becomes hard in practice.
At that point the process starts to look a lot like the secretary problem you mentioned — you’re trying to make a decision with incomplete information and limited time to evaluate each candidate.
Transparency around application volume would already help a lot. Knowing whether a role has 50 applicants or 1500 changes how people decide to spend their time applying.
Surfacing more of that kind of signal — instead of just the listing itself — seems like a step in the right direction.
1800 applications for a small team sounds brutal. At that scale the problem becomes less about finding candidates and more about filtering signal from noise.
Verification alone wouldn’t solve that, but one of the things we’re exploring is helping employers surface stronger matches earlier instead of forcing them to manually sift through hundreds or thousands of applications.
That makes sense. Once a role receives hundreds of applications, the main challenge becomes signal vs noise for the hiring side.
The idea behind verified listings targets a slightly different problem — reducing scams, fake postings, or roles that were never actually open.
The volume issue you describe is real as well. We’re exploring an additional feature intended to ease that situation by surfacing stronger matches instead of turning every posting into a flood of applications.
Verification alone wouldn’t solve the competition problem, but it could make the job board itself more trustworthy.
Large platforms like AWS tend to develop niches naturally. Once a service becomes complex enough, people who work with it for years accumulate a lot of practical knowledge that isn’t obvious from the documentation alone.
It’s less about closed code and more about experience with real deployments, edge cases, and integration patterns that only appear at scale.
That’s a good example of how niche expertise can make someone stand out in the job market.
In many cases the challenge isn’t just finding a job posting, but finding one where that specific experience is actually valued or understood by the hiring side.
Requiring deposits from both sides could reduce a lot of spam and ghost listings.
My concern would be the friction for applicants. Many people already apply to dozens of roles during a job search, so even a small deposit might discourage legitimate candidates.
The broader idea of aligning incentives between employers and applicants is worth exploring.
Ghost jobs are definitely a real problem.
Verification wouldn't solve all of that, but even confirming that a role is currently open and tied to a real employer could reduce some of the noise applicants face today.
The goal wouldn't be filtering candidates, just verifying that the job posting itself is legitimate.
A lot of job boards currently have fake listings, resume farming, or outright scams.
That’s true. Platforms like Upwork use paid connections to create some friction and reduce spam applications.
The downside is that it can also discourage legitimate candidates or favor those who are simply willing to spend more. It solves part of the noise problem, but it doesn’t necessarily guarantee better matches.
There are tools for that. Many companies already use applicant tracking systems to filter applications automatically.
LLMs may improve this by understanding context instead of just keywords, but the real issue often isn’t filtering itself — it’s the volume and quality of applications.
There’s definitely risk on both sides. Companies want to find viable candidates, but candidates also need to know the company and the role are legitimate.
Situations like the one you described are exactly what make trust around job listings important. Even basic signals about the company, funding, or compensation expectations could help candidates avoid wasting time.
That’s fair. Recruiters do provide value, especially when they help candidates navigate the early stages of the process.
The idea I mentioned about verifying listings is only one part of it. The broader goal is to increase trust around the listings themselves and the people behind them, so candidates can spend less time filtering noise and more time engaging with real opportunities.
Good recruiters can add a lot of value. When they’re good, they filter opportunities, provide context, and connect the right people.
The challenge is that not everyone has access to that kind of recruiter, so many candidates still end up relying on job boards.
That’s true — a legitimate company can still post ghost jobs.
Verification probably can’t eliminate that entirely, but it might still help if it focuses on the listing itself (for example confirming the role is active, recently updated, or tied to a real hiring process).
Matching seems to be a big part of the problem. A lot of hiring still feels like timing and luck, like in the situation you described.
Improving the signal around listings could still help that process though. If candidates know a role is real, active, and owned by a responsive team, it becomes easier for the right people to engage with it.
The market definitely feels tighter than it did a few years ago.
That’s actually part of why the quality of listings matters — when there are fewer real opportunities, ghost jobs or low-signal postings become even more frustrating for candidates.
A strong vetting process during company onboarding probably does a lot to improve trust on both sides.
The point about recruiters being active on the platform also seems important — being able to reach a real person quickly likely makes listings feel much more credible.
That’s true — verification alone wouldn’t necessarily solve ghost jobs.
A company can be real and still leave outdated or speculative postings up.
The harder problem might be verifying that the position itself is actually active and being hired for.
That makes sense if jobs already reach you through your network or other hiring channels.
There’s definitely some truth to that. Many of the best opportunities do move through relationships.
At the same time, job boards still handle a huge portion of the market — especially for people outside strong networks, early-career candidates, or remote roles.
I’m curious whether better verification or signal on the job side could at least reduce the “lemons” effect a bit, even if it can’t replace relationships.
The volume of applications — especially AI-generated ones — does seem to be becoming a real issue for companies.
Things like verified accounts or some form of rate limiting could potentially reduce that noise.
Do you think companies would actually prefer fewer applications if they were more relevant, instead of maximizing the total number?
That's the tricky part. Verifying that a company exists is relatively easy, but verifying that a role is genuinely open and accurately described is much harder.
I wonder if it would require a combination of signals — for example confirming the recruiter identity, requiring periodic confirmation that the role is still open, or feedback from applicants about whether the process actually happened.
I'm not sure how far that could go in practice, though.
That's useful to hear from someone who has actually posted jobs.
From your experience, do candidates ever worry about scams or fake listings, or is the main challenge on your side just the sheer number of applications?
It sounds like there might be different problems on the candidate side vs the employer side.
I see what you mean about it being a coordination problem.
Do you think the main issue is that job boards create too much noise — hundreds of applications — instead of helping companies and candidates find better matches?
If that's the case, what kind of system do you think would improve that coordination?
That definitely makes things harder. Roles posted for internal transfers or compliance reasons are tricky because they may never have been intended for external candidates.
Maybe verification would need signals showing that the role is actually open to external applicants.
I wonder if something like an “externally open role” label would help.
That’s an interesting point. Transparency about things like salary, tech stack, and engineering practices would probably make job boards much more useful. It sounds like verification alone might not be enough without better information about the role.
That’s true, platforms like LinkedIn try to verify companies.
What I’m more curious about is whether people would value deeper verification of the actual job posting itself, not just the company.
Good point. Verifying that a company exists is relatively easy, but confirming that the role is actually open and actively being hired for is definitely harder.
I was thinking verification could include confirming the recruiter’s identity and requiring employers to periodically confirm that the position is still active. Ghost jobs are definitely an important challenge.