Job Posting Red Flags: 15 Phrases and What They Usually Mean

The short answer: no single phrase proves a posting is bad. "Fast-paced environment" is in half the listings you'll ever read, including good ones. What matters is the pattern. A posting with no salary, no named team, a job description that could belong to any company, and three or four of the phrases below is asking you to trust it without giving you a reason. Spend your applications on postings that give you one.

This is the list we built the job posting roast around. Paste a listing there and it scores the whole thing. Read on if you'd rather learn to see it yourself.

How to read this list

Every phrase below has an innocent version. Recruiters copy templates, small companies write postings in a hurry, and some of the worst phrases are just habits. So each entry has two lines: what it usually means, and when it's harmless. Count the flags, weigh them against the specifics the posting does give you, and decide. One flag is noise. Three is a pattern.

The 15 phrases

1. "Fast-paced environment"

Usually means: understaffed. The pace is set by how much work there is divided by how many people there are, and this phrase is how a posting says the second number is small.

Harmless when: the posting also describes what the work actually is, names a team, and lists a salary. Then it's a template line, not a confession.

2. "Wear many hats"

Usually means: the role hasn't been defined, or it's two or three roles paid as one. The hats are jobs someone else used to have.

Harmless when: it's a genuinely small company and the posting is honest about that. A 12-person startup saying it is being accurate. A 4,000-person company saying it is telling you the team is short.

3. "We're like a family here"

Usually means: boundaries will be fuzzy. Families don't have working hours, and they take it personally when you leave.

Harmless when: it's a family business that says so plainly. Otherwise treat it as a description of the exit, not the welcome.

4. "Work hard, play hard"

Usually means: long hours, with events you're expected to attend afterwards. The "play" is scheduled and the "hard" is not.

Harmless when: you already know the company's hours from someone who works there. Nobody puts this in a posting for a 40-hour week.

5. "Competitive salary"

Usually means: they'd rather not say. If the number were competitive, the posting would use it, because a real number is the strongest recruiting line there is.

Harmless when: the posting is in a place where ranges aren't customary and everything else is specific. Even then, ask for the range on the first call. Our salary expectations guide has the wording.

6. "Salary: DOE" (depends on experience)

Usually means: the range is wide and the low end is where they'd like to start. Same as above, one step more evasive, because it names the reason without naming the number.

Harmless when: it never is, exactly, but a posting that says DOE and then lists a range is fine. The flag is DOE on its own.

7. "Rockstar," "ninja," "guru," "wizard"

Usually means: the writer doesn't know what the job is well enough to describe it, so they've described the person they imagine doing it. Also a reliable sign the posting was written by someone who won't be your manager.

Harmless when: the rest of the posting is specific and the word is clearly a joke. Rarely.

8. "Unlimited PTO"

Usually means: no PTO is tracked, so none is paid out when you leave, and the amount you actually take is set by what your manager and your peers take. Often less than a stated allowance.

Harmless when: the company also states a minimum they expect people to take, or a current employee tells you the real number. Ask in the interview: "What did the team actually take last year?"

9. "Other duties as assigned"

Usually means: the list above it isn't the whole job. Standard in a lot of HR templates.

Harmless when: it's the last bullet under a specific list. It's a flag when the list above it is already vague, because then the whole job is "as assigned."

10. "Self-starter who thrives in ambiguity"

Usually means: no onboarding, no process, and possibly no manager with time for you. "Ambiguity" is a polite word for nobody having decided what the role is.

Harmless when: it's a senior role where defining the work is the work. For a junior or mid-level role, it's a warning.

11. "Must be willing to work evenings and weekends when needed"

Usually means: evenings and weekends will be needed. Postings don't include this line for something that happens twice a year.

Harmless when: the role is genuinely shift-based or event-based and the posting says so. For an office role, it's the most honest red flag on this list.

12. "Always accepting applications" or "urgently hiring"

Usually means: the first one is a pipeline posting: they collect resumes for roles that may open later, and there's no seat to fill today. The second is either real (someone left suddenly) or permanent (someone leaves regularly).

Harmless when: "urgently hiring" on a role with a start date and a named manager is probably real. "Always accepting" is the closest thing to a ghost job label a posting can carry.

13. "Ground floor of something huge" and "equity potential"

Usually means: the salary is below market and the difference is being paid in a story. "Potential" means no equity has been offered yet.

Harmless when: the posting states the equity, the vesting, and a salary you could live on without it. Then it's an offer, not a story.

14. Eight years of experience for a junior role (or a senior title with an entry-level list)

Usually means: the title and the pay were set separately from the requirements. Either the pay is junior and they want a senior for it, or the title is inflated to attract applicants for a job that doesn't need it. Both cost you.

Harmless when: it doesn't happen by accident often. Read the whole requirements list against the title and trust the mismatch.

15. "Due to the volume of applications, only successful candidates will be contacted"

Usually means: you won't hear back, and they've told you in advance so it doesn't count as ghosting. On its own it's just honesty. Combined with everything above, it's the posting explaining that the silence you're about to get isn't personal.

Harmless when: the posting is otherwise specific. Large employers include this line by default.

The two checks that beat any phrase

Wording is a hint. These two are evidence, and neither takes more than a minute.

Is the role on the company's own careers page? Real openings almost always live at the source, because that's where the applicant tracking system feeds from. A role that exists on job boards but not on the company's site is often a listing nobody took down.

When was it posted? Check the date on every board you can find it on and trust the oldest one. A posting that's been up for months, or that vanishes and reappears, is being used to collect resumes, not to fill a seat.

The full checklist, with the reasons companies post jobs they won't fill, is in the ghost jobs guide.

“No single phrase proves a job posting is bad. A posting with no salary, no named team, responsibilities that could belong to any company, and three of the usual phrases is asking you to trust it without giving you a reason.”

Share on X→

What a good posting looks like

It's worth knowing the other end of the scale, because a boring posting can be an excellent one.

• A salary range, even a wide one.
• A named team, manager, or reporting line.
• Responsibilities specific enough that you could picture a Tuesday.
• Requirements that match the title and the pay.
• One job, not three.

A posting that hits all five and says "fast-paced environment" is fine. It's the phrase without the specifics that should slow you down.

If you're going to apply anyway

Sometimes the posting is bad and the job is still worth a shot. Two things help.

First, ask the questions the posting dodged, early, on the recruiter call: the range, who the role reports to, and what the first 90 days look like. A recruiter who can't answer any of the three has told you something.

Second, make sure your resume can survive the posting before you spend the time. Job Match scores your resume against the exact listing and names the missing keywords. And if you want the posting itself scored, the job posting roast reads it the way this article does, quotes the lines that earned the score, and never names the company.

The short version

• No single phrase is proof. Count them, and weigh them against what the posting actually tells you.
• The worst signs are missing information: no salary, no team, no real description of the work.
• "Competitive salary," "wear many hats," "like a family," and "evenings and weekends when needed" are the four to take most seriously.
• Two checks beat any wording: is it on the company's site, and how old is it?
• A good posting can be dull. Specific beats exciting.