Job Posting Red Flags: 24 Phrases to Clarify Before You Apply
Definition. A red flag in a job posting is not proof that the job is bad. It is a condition the posting leaves unresolved, and the correct response to an unresolved condition is a question — not an automatic rejection and not silent acceptance.
Red-flag lists usually end in rejection: see the phrase, walk away. That advice is expensive to take, because most of these phrases describe a real arrangement that would be acceptable if specified. This list is therefore a question generator: each phrase is paired with what it may hide and the one question that resolves it.
No frequency claim is made here. How often these phrases appear in real postings would require disclosed sampling, window and cleaning rules, which this page does not have.
Compensation
| Phrase | What it may be hiding | Question to ask |
|---|---|---|
| “Competitive salary” | Nothing about level, band or currency | What is the band for this level, and is it fixed or negotiable? |
| “Salary commensurate with experience” | An undefined range that can move after you disclose | What range is budgeted before my experience is discussed? |
| “Unlimited earning potential” | A commission-only or heavily variable structure | What share of on-target earnings is base, and what is the target? |
| “Performance bonus” | An unstated formula and an unstated payout history | What is the formula, and what did the last cycle actually pay? |
Scope
| Phrase | What it may be hiding | Question to ask |
|---|---|---|
| “Wear many hats” | An unfilled role absorbing work from another function | Which functions are currently unstaffed, and for how long? |
| “Fast-paced environment” | Repeated priority changes, or chronic under-staffing | What changed in priorities last quarter, and who decides priorities? |
| “Own it end to end” | Accountability without authority or budget | What decisions can this role make without approval? |
| “Comfortable with ambiguity” | An undefined remit the employer has not resolved | What is decided already, and what is genuinely open? |
Authority
| Phrase | What it may be hiding | Question to ask |
|---|---|---|
| No reporting line stated | A role that reports to several people at once | Who is my manager, and who sets my priorities? |
| “Work directly with leadership” | Access without a defined manager or support layer | Is there a manager between me and leadership? |
| “Dotted-line reporting” | Competing instructions from two functions | Which line sets my objectives and signs off my work? |
| “Newly created role” | No predecessor, no defined success criteria | Why does this role exist now, and what would success look like in six months? |
Workload
| Phrase | What it may be hiding | Question to ask |
|---|---|---|
| “On-call as needed” | An unstated rotation frequency and compensation | What is the rotation, how often is it triggered, and is it compensated? |
| “24/7 mindset” | Expectations of availability outside contracted hours | What response time is expected outside office hours, in writing? |
| “Deadline-driven” | Crunch cycles treated as the normal state | How many deadline crunches happened in the last six months? |
| “Weekend availability around launches” | Unpaid overtime built into the role | Is launch overtime paid, time-off-in-lieu, or expected unpaid? |
Process and legal form
| Phrase | What it may be hiding | Question to ask |
|---|---|---|
| “Unpaid trial project” | Work delivered before any contract exists | Is the trial bounded, scored against published criteria, and contracted? |
| “Commission-only” | Income contingent on pipeline you must build | What is the draw or guarantee during ramp-up, if any? |
| “Must be authorized to work” | Silence on sponsorship for candidates who need it | Does this role sponsor, and if not, is that a hard filter? |
| “Training or equipment deposit” | A cost shifted to the candidate before employment | Is any payment requested from me? |
Role viability
| Phrase | What it may be hiding | Question to ask |
|---|---|---|
| “Rapidly growing team” | Headcount that exists on a plan, not in the room | How many people are in the team today, and how many are hired? |
| Reposted within a few months | A role that keeps failing, or a pipeline-building posting | Was this role filled recently, and who left? |
| No team or product named | A mandate that may be reassigned after hiring | Which team and product would I work on in month one? |
| No interview process described | An open-ended process with no timeline | How many stages, with whom, and over what period? |
How to use the list without over-reading it
Three rules keep this usable. First, a single phrase is a prompt, not a verdict: commission-only is a legitimate structure for some sales roles and a serious problem for others. Second, count the unresolved items rather than collecting them — five clarified items and one open one is a different situation from six open ones. Third, prefer questions over conclusions in writing: a question invites correction.
JOBOK applies the same discipline to a posting: stated requirements, reasonable inferences, and items worth asking are kept in separate layers, and nothing inferred is presented as quoted.
Frequently asked questions
Are these red flags reliable indicators of a bad employer?
No. Each phrase names an information gap, not a proven problem. The value of the list is the question attached to each item, which converts a suspicion into a specific answer you can act on.
Which three flags deserve the most attention?
Compensation with no numbers, an unstated reporting line, and an undefined success metric. These three determine what the job pays, who directs the work, and how you will be judged — and none of them can be resolved by reading the posting twice.
Should I ask these questions before applying or during the interview?
Split them. One message with two or three blocking questions before you invest tailoring time is reasonable; the rest belong in the first conversation, where answers can be followed up.
Does a missing reporting line really matter?
It matters most in newly created roles, where the reporting line decides whether the role has authority or only accountability. If the posting is silent, treat it as unresolved rather than assuming the best case.
Sources
- JOBOK JD Decode (stated / inferred / worth-asking layers): https://jobok.app/jd-decoder (accessed 2026-11-04)
- JOBOK user manual (no-evidence rule): https://jobok.app/manual (accessed 2026-11-04)