Spotting Job Postings That Will Waste Your Time

Ian Klosowicz

Not every job posting is worth applying to. Some are ghost postings that will never produce an interview. Some are real roles that are already internally filled. Some are legitimate openings that you have no realistic shot at given where you are right now. Learning to filter these out before you spend 20 minutes tailoring a resume is one of the fastest ways to make your job search more efficient.

Here's what bad postings look like and how to spot them quickly.

Table of Contents

Ghost postings

A ghost posting is a job listing for a role that either doesn't exist or that the company has no current intention of filling. Companies post them for a few reasons: to build a candidate pipeline for future openings, to comply with requirements that positions be publicly posted before an internal hire, or because the listing was never taken down after the role was filled.

Knowing which postings to skip is only half the equation, and knowing where entry-level analyst roles are actually posted tells you where to direct the time you save.

Ghost postings are more common than most people realize. A 2023 survey of hiring managers found that a significant portion of companies admitted to posting roles they weren't actively trying to fill. For job seekers, this means a real fraction of the postings you see are producing no hires regardless of how good your application is.

Signals that a posting might be a ghost:

  • Posted more than 30 days ago. The longer a listing sits live, the more likely the role is filled, frozen, or never real.
  • The same listing reappears repeatedly. A posting that keeps getting reposted every few weeks is often pipeline-building, not active hiring.
  • No company name. Anonymous listings make it impossible to verify the role exists and often come from aggregators.
  • A vague description with no specifics. No named tools, no team context, no concrete responsibilities usually means no real role behind it.

You can't always identify a ghost posting with certainty before applying. What you can do is deprioritize applications to postings over 30 days old and spend more time on recent listings where active hiring is more likely.

Roles that are already filled internally

Many companies are required by HR policy or legal compliance to post roles externally even when they've already identified an internal candidate. The posting goes live, applications come in, a perfunctory review happens, and the internal person gets the job. Your application went nowhere before it was ever considered.

You can't always tell from the outside when this is happening, but a few signals are worth watching for:

  • Hyper-specific requirements. A list that reads like one exact person's resume often means they already have that person in mind.
  • A very short application window. A role open for only a few days is often a compliance posting around an internal hire.
  • A fast, generic rejection. A rejection within a day or two, before anyone could have reviewed you, suggests the decision was already made.
  • Posted only on the company site. A role never promoted anywhere else may be meeting a posting requirement rather than seeking candidates.

This pattern is frustrating but not a reason to avoid applying entirely. It's a reason to not spend extra time on applications you're uncertain about and to move on quickly from fast rejections rather than trying to figure out what went wrong.

Evergreen postings that collect resumes indefinitely

Evergreen postings are listings for roles that companies hire for repeatedly over time, kept live permanently to maintain a candidate pipeline. Staffing agencies and large enterprise companies use these constantly.

The problem with evergreen postings is that you don't know whether the company is actively hiring right now or just collecting resumes for a future need. Applying to one isn't necessarily wasted time, but your application may sit in a queue for weeks before anyone looks at it.

Identifiers of evergreen postings:

  • A generic title with no team or location specifics. "Data Analyst" with no department or context is often a pipeline listing.
  • A staffing agency as the poster. Agencies keep roles live to collect candidates for whenever a client need appears.
  • A listing that never expires. If the same role has been open for months with no changes, it's likely evergreen.
  • Language about "always looking for talent." Phrasing that invites applications in general rather than for a specific opening.

Apply to evergreen postings with your standard tailored resume, but don't invest extra time in research or a custom cover letter for them. Treat them as low-effort, low-expectation submissions and focus your tailored effort on direct company postings where active hiring is clearer.

Postings at the wrong level

Senior roles, lead roles, and specialist roles with deep experience requirements are not worth your time as an entry-level candidate, regardless of how interesting the company is. You already know this, but it bears stating clearly because a lot of people apply to these anyway and then wonder why they're getting no responses.

The specific signals that a posting is too senior:

  • "Senior," "Lead," or "Principal" in the title. At a company with a real data team, these mean years of experience you don't have yet.
  • 5-plus years of experience required. A hard experience floor well above zero is a clear screen-out for entry-level applicants.
  • Ownership or mentorship language. "Own the analytics roadmap" or "mentor junior analysts" describes a role above the entry level.
  • Deep specialist requirements. Demands for advanced statistics, ML, or a specific niche tech stack signal a specialist hire, not a first analyst job.

One nuance: some companies use "Senior" in a way that doesn't mean much (a small startup calling its first analyst hire "Senior Analyst" because it sounds good on a job board). When a senior title appears at a small company with few employees and the requirements are otherwise entry-level, apply. When a senior title appears at a company with a real data team and specific requirements, skip it.

Misleading titles that aren't analyst roles

A few title patterns appear in data analyst job searches but describe something different:

  • "Data Entry" roles. These are manual input jobs with no analysis, despite sometimes showing up under analyst searches.
  • "Data Analyst" that's really a sales or ops role. Some listings use the title but the responsibilities are account management or reporting administration, not analysis.
  • "Business Analyst" in a requirements-gathering sense. Many business analyst roles are about process and documentation, not SQL and data work.
  • "Data Scientist" at the entry level that wants an analyst. Occasionally the reverse: a science title on work that's actually analyst-level, which can be worth a closer read.

The fix: read the full responsibilities section before deciding to apply, not just the title and the requirements list. The responsibilities tell you what the person in this role will actually do every day. If that doesn't match what you're building toward, skip it regardless of the title.

Red flags inside the job description

A few patterns inside the posting itself signal the role or company may not be worth your time:

  • A dozen tools in the requirements. A list demanding SQL, Python, R, Tableau, Power BI, and more for one entry-level role usually means the team doesn't know what it needs.
  • "Wear many hats" at a company with no data team. This often means you'd be the lone data person with no support, which is a hard first job.
  • Unpaid "assessments" that look like real work. A take-home that resembles an actual business deliverable can be free labor rather than a fair test.
  • No mention of what the team or data looks like. A description that never says who you'd work with or what you'd work on is often hiding a messy situation.

How to vet a posting in under 2 minutes

You don't need to spend 20 minutes vetting every posting. A 2-minute check before deciding to apply covers most of the major issues:

  1. Check the post date. Under 7 days is a priority; over 30 days gets deprioritized.
  2. Confirm the company is named and real. A quick look at the company and its data team tells you the role probably exists.
  3. Read the responsibilities, not just the title. Make sure the day-to-day is actual analyst work.
  4. Check the level. Confirm the experience requirement and title match where you are.
  5. Scan for red flags. A dozen required tools, lone-analyst framing, or an all-caps wall should give you pause.

If the posting passes those 5 checks, it goes in your tracker and gets a tailored application. If it fails any of them, the time you save goes to an application that's more likely to produce something.

The targeting and vetting system that goes with this is part of Month 3 in the program at Analyst Hive, the full job search workflow that covers how to source, filter, and apply at a volume and quality that actually moves the pipeline.

Once you're consistently applying to real roles that match your profile, the next thing that matters is how your resume reads to those companies. Both are covered inside the program. Join Analyst Hive on Skool.

FAQ

How do I know if a posting is a ghost before applying?

You often can't know for certain. The most reliable signals are: posted more than 30 days ago, no company name listed, vague description with no specifics, and the same posting appearing repeatedly. If a listing hits 2 or more of those signals, treat it as low-priority and apply quickly with minimal tailoring rather than skipping it entirely.

Is it worth applying to postings from staffing agencies?

Sometimes. Staffing agencies fill real contract and full-time roles at real companies. The issue is transparency: you often don't know which company you'd actually be working for, what the team is like, or whether the role is active. Apply if the description matches your target role and the agency has a real online presence. Skip anonymous or very vague agency postings.

How old is too old for a job posting?

30 days is the threshold for deprioritizing. Over 60 days is the threshold for skipping unless you have a specific reason to believe the role is still active (a recruiter mentioned it, the company just announced expansion, etc.). Postings under 7 days old are the priority; apply to those first.

Should I apply to a role if Glassdoor reviews are bad?

Depends on the nature of the reviews. Generic complaints about company culture are common and not necessarily deal-breakers. Specific patterns like "analytics team has no resources," "high turnover in data roles," or "data work is all manual Excel" are more directly relevant to your experience in the role. Read critically and use it as one signal, not the only one.

What if the posting is vague but the company seems good?

Apply with a standard tailored resume and low additional time investment. If you make it to a phone screen, use the first conversation to ask what the role actually involves day-to-day. "Can you tell me more about what a typical week looks like for someone in this role?" is a reasonable early question that surfaces the information the posting didn't give you.

Is applying to a role that's already internally filled ever worth it?

Sometimes. Companies occasionally find an external candidate compelling enough to reconsider the internal hire, or the internal candidate turns down the offer. More practically, applying to a company even when the specific role is filled gets your resume into their system for future openings. If the company is one you want to work for, the application is worth the 20 minutes even if this particular role goes nowhere.