Why Companies Post JavaScript Jobs They Never Fill and How I Spot Ghost Listings on My Board

A company posted a senior React position on my board four months ago. I noticed it because the listing stayed active longer than anything else on the platform. Most postings get taken down after 30 to 60 days, either because the role is filled or because the company gives up and rewrites the description. This one just sat there. Same text. Same requirements. Same salary range. Four months.

I sent them an email asking if they needed help with the listing. Maybe the description needed updating. Maybe the salary was off. Maybe I could help them reach a different pool of candidates. They replied the next day. The position had been filled three months ago. The person they hired had already completed onboarding, passed probation, and shipped their first feature. Nobody had bothered to take down the posting. It was still collecting applications from developers who thought the job was real.

I wish I could tell you this was unusual. It is not. I run a JavaScript job board with over 400 active listings, and ghost jobs are something I think about more than almost any other problem in the hiring market right now. Not because they are new. They have existed for as long as job boards have existed. But because in 2026, with over 80,000 tech layoffs in Q1 alone and hundreds of developers applying to every single role, ghost jobs are doing more psychological damage than at any point I can remember. A developer who sends 200 applications and gets 3 replies does not know that 40 or 50 of those applications went to jobs that did not exist. They blame themselves. They rewrite their resume for the fifth time. They question whether they chose the wrong framework. The real problem was never them. The real problem was that the job was not there.

Why Ghost JavaScript Job Postings Exist on Every Platform Including Mine

I have been watching this pattern on my own board for over a year, and I have identified three reasons that companies post jobs they are not actually trying to fill. None of them are malicious in the way developers assume. Most developers think ghost jobs are a conspiracy to collect resumes. The reality is more boring and more frustrating.

The first reason is simple neglect. A company opens a role, starts interviewing, hires someone, and nobody remembers to close the listing. This happens constantly at companies where HR and engineering are not well coordinated, which is most companies. The hiring manager knows the role is filled. The recruiter moved on to the next search. The job board listing is orphaned. It keeps collecting applications that go into an inbox nobody checks. I see this pattern most often at mid-size companies with 200 to 500 employees. They are big enough to have multiple open roles at once and small enough that there is no dedicated person managing the job board pipeline.

The second reason is pipeline building. Some companies post roles not because they have budget to hire right now, but because they want to build a pool of candidates for when budget becomes available. This is especially common after layoffs. A company lays off 15 engineers in January, knows they will need to hire 5 back by Q3, and posts the roles in February to start collecting resumes. The posting is technically real in the sense that the role will eventually exist, but right now there is no hiring manager, no interview loop, and no offer authority. Developers who apply get silence for months and then either a sudden interview request or a quiet rejection when the company decides to go in a different direction.

The third reason is the one that frustrates me the most. Some companies are required by internal policy or by investors to maintain an "active hiring pipeline" even when they are not hiring. I have seen this at venture-backed startups where the board wants to see that the company is growing. Posting jobs signals growth. It looks good in board decks. It looks good on LinkedIn when the company page shows 20 open positions. Whether anyone is actually reviewing those applications is a different question, and the answer is often no.

I wrote about the broader pattern of why most JavaScript job applications fail in 2026, and ghost jobs are the invisible layer underneath all of it. You can have the perfect resume and the perfect cover letter, and if the job does not exist, none of it matters.

The Red Flags I Use to Identify Fake Listings Before Wasting Time

After reading thousands of job postings on my board, I have developed a set of patterns that reliably indicate a listing is either dead, fake, or functionally useless. None of these are guaranteed indicators on their own, but when two or three appear together, the probability that you are looking at a ghost job is very high.

The most reliable signal is age. A JavaScript job posting that has been active for more than 90 days without being updated or reposted is almost certainly dead. The hiring cycle for most JavaScript roles is 30 to 60 days. If a company has not filled the role in 90 days, either the role is not real, the hiring process is broken, or the requirements are so unrealistic that nobody qualifies. In all three cases, applying is a waste of your time.

The second signal is requirement inflation. When a posting asks for expert-level experience in React, Vue, Angular, Node, Python, .NET, and AWS simultaneously, the company does not know what they need. I see these postings weekly and I have talked about this before in my observations from 14 months of running a job board. A real hiring manager with a real team and a real project knows their stack. They do not ask for everything. When they ask for everything, it usually means nobody with actual technical authority wrote the requirements, and that often means nobody with actual hiring authority is behind the listing.

The third signal is the ratio of company description to job description. I covered this recently, but it bears repeating in this context. When 50 percent of the posting is about the company mission and values and the actual role description is compressed into a few vague sentences, I read that as a branding exercise, not a hiring exercise. The company wants to look like it is hiring. Whether it actually is hiring is secondary.

The fourth signal is posting volume versus company size. A 30-person startup posting 15 open positions is almost certainly not filling all of them. They might be filling two or three and using the rest to project growth. I check company size on LinkedIn before taking listings at face value, and I recommend you do the same.

The fifth signal is the absence of a named hiring manager or team. Postings that say "you will join a dynamic team" without naming the team, the manager, or the product are often generated by HR without engineering input. When engineering is actually trying to hire, they put specifics in the posting because they want to attract the right person. When HR is posting for optics, they keep it vague because there is no "right person" to attract. There is no person at all.

Why "Apply Anyway" Is the Worst Advice You Can Follow With Ghost Jobs

Most career advice blogs will tell you to apply to every job that roughly matches your skills. The logic is that job searching is a numbers game and the more applications you send, the better your odds. I think this advice is actively harmful when a significant portion of the jobs you are applying to do not exist.

Here is the math. If 20 to 30 percent of the remote JavaScript roles you see on any given platform are ghost jobs (and from what I observe on my own board, that is a conservative estimate), then out of 100 applications, you are sending 20 to 30 into a void. Each application takes somewhere between 20 minutes (for a quick apply) and 90 minutes (for a tailored cover letter and resume). That is 7 to 45 hours of your life going nowhere. Not going to a rejection. Going to literally nothing. No human will ever see your application.

But the real cost is not the hours. The real cost is what those 20 to 30 silences do to your motivation. Every application without a response makes you doubt yourself a little more. After 50 silences you start wondering if your resume is broken. After 100 you start wondering if you chose the wrong career. I get emails from developers in this exact state every week, and the hardest part of my response is telling them that the silence was probably not about them at all. It was about a job that was not real.

The alternative approach is slower but psychologically healthier and produces better results. Spend 30 seconds on each listing checking for the red flags I described. If the posting triggers two or more flags, skip it. Do not apply. Do not save it for later. Close the tab and move on. You will apply to fewer jobs per day, but every application you send will go to a role that actually has someone on the other side reading it. Your response rate will be higher. Your motivation will be more sustainable. And you will not spend your evenings wondering what is wrong with you because a ghost did not write back.

This connects directly to what I see working for developers who actually get hired. I described this pattern in my article about the 5 types of remote job restrictions. The developers who get hired are not the ones who apply the most. They are the ones who filter the hardest. Fewer applications to real jobs beats hundreds of applications to a mix of real and imaginary ones.

What I Think Nobody in This Industry Has the Courage to Say About Ghost Jobs

I want to say something that might sound strange coming from someone who runs a job board. Ghost jobs are partly my fault. Not mine personally, but the fault of every job board and every hiring platform that allows listings to stay active indefinitely without verification. LinkedIn does not verify that a job is real before showing it to millions of people. Indeed does not verify. My board does not verify, at least not yet. We all publish what companies send us and we all benefit from having more listings because more listings means more traffic.

I think this is a problem that the industry is choosing not to solve because solving it would reduce the number of listings on every platform, and every platform's business model depends on having a lot of listings. Saying "we have 10 million active jobs" is a marketing claim that works better when you do not check how many of those 10 million are actually active. I think this is wrong, and I think the platforms that figure out how to verify listing freshness first will win long-term trust from developers who are exhausted by the current system.

On my own board, I have started manually removing listings that are older than 90 days without updates. It makes my total count smaller. It makes my board look less impressive in raw numbers. But I would rather have 350 real listings than 500 listings where 150 are ghosts. I do not have this fully automated yet and I am not going to pretend I have solved this problem. But I am thinking about it every day because I read the emails from the developers who are applying to my listings and getting silence, and I know some of that silence is because the job was never there.

I am not the only person thinking about this. But I am probably one of the few people willing to say it out loud while running a job board. Most platform operators stay quiet because admitting the problem exists makes their product look worse. I think staying quiet makes the problem worse.

How to Build Your Own Ghost Job Filter Starting This Week

The developers on my board who consistently get responses have all independently arrived at the same workflow, and it is not complicated. Before applying to any role, they spend two minutes doing three checks.

First, they check the posting date. If it is older than 60 days, they skip it. This one filter alone eliminates a huge number of ghost listings. Most applicant tracking systems show a "posted on" date. If the posting does not show a date at all, that itself is a yellow flag.

Second, they check the company's LinkedIn page for recent hiring activity. If the company has posted about new hires, onboarding announcements, or team growth photos in the last 30 days, the company is actually hiring. If the last update is from 6 months ago and all the open positions are still listed, the company is in maintenance mode and probably not reviewing applications.

Third, they look for the hiring manager on LinkedIn. If they can find a real person with the title "Engineering Manager" or "VP of Engineering" at the company, and that person has posted or commented on LinkedIn in the last month, the role is probably real. If no one at the company with a technical leadership title has any recent activity, the team may not exist in its current form.

These three checks take two minutes. They eliminate 30 to 40 percent of listings from your apply queue. The remaining 60 to 70 percent are real roles with real humans behind them, and your applications to those roles will get a dramatically higher response rate than if you had applied to everything blindly.

The job market is not as broken as it feels. It is polluted. Ghost jobs are the pollution. Once you learn to filter them out, the actual market underneath is smaller but real, and real is what gets you hired.

The worst part about ghost jobs is not that they waste your time. It is that they make you believe something is wrong with you when the problem was never you. The job simply did not exist. Learn to see the ghosts, and the real opportunities become visible.

FAQ

How common are ghost JavaScript job postings in 2026?

From what I observe on my own board, somewhere between 20 and 30 percent of remote JavaScript listings at any given time are either filled, frozen, or posted for pipeline purposes without active hiring behind them. This is a conservative estimate. Some platforms with less curation likely have higher rates.

Can I get a company to confirm whether a job posting is real before I apply?

You can try emailing the hiring manager directly on LinkedIn, but most will not respond to cold messages about posting status. A faster approach is to check whether the company has made any recent hires (LinkedIn announcements), whether the posting has been refreshed recently, and whether anyone with a technical leadership title at the company is publicly active.

Why do job boards allow ghost listings to stay active?

Because more listings mean more traffic, and more traffic means more revenue from job posting fees, advertising, or premium subscriptions. Removing stale listings reduces the total count, which most platforms consider a competitive disadvantage. Some boards are starting to address this, but the industry has not solved it yet.