5 Red Flags Hiding in a Staffing Requisition (Before You Submit)

You open the req. Six-month contract, familiar tech stack, rate 'open.' Your recruiter calls it hot. You're tempted to fire off your resume in the next ten minutes.

Hold on. The posting itself is already telling you things, you just have to read it the way an underwriter reads a loan application: looking for what's missing, not just what's there.

Here are five patterns that show up constantly in requisition language, what they usually mean, and the one question that forces a real answer before you let anyone submit you.

Flag 1: No rate range anywhere

'Rate: open' or 'rate: DOE' (depending on experience) is not flexibility. It's a vendor keeping room to negotiate margin after they already have your resume in hand. A posted range, even a wide one, tells you the client or prime vendor has a budget and is willing to say it out loud.

When a req has no range at all, the silence usually means one of two things: the bill rate hasn't been confirmed with the end client yet, or there are so many vendor layers above the one contacting you that nobody wants to commit until they know their own cut.

The question to ask: 'What is the client's approved bill rate for this role, and what pay rate does that translate to for W-2, corp-to-corp, and 1099?' If the recruiter can't answer within a business day, the req isn't as hot as advertised.

Flag 2: Client name withheld until submission

Some vendors anonymize postings to stop candidates from going direct or through a competing vendor. That's a legitimate business reason. But 'confidential client' combined with vague industry language ('major financial services firm,' 'Fortune 500 healthcare company') makes it impossible for you to check your own exposure: current non-competes, prior bad experiences, or conflicts with another active engagement.

You are also being asked to let a vendor submit your resume into a client's applicant tracking system before you know who that client is. Once submitted, you may be locked out of applying through any other channel for months, sometimes permanently, under that vendor's standard terms.

The question to ask: 'Will you confirm the end client by name before you submit my resume, not after?' A vendor confident in the opportunity will tell you under a verbal understanding of confidentiality. One that won't is asking you to sign blind.

Flag 3: Four vendor layers between you and the client

This is the one posting language almost never admits to directly, but you can usually smell it. Clues: the recruiter's email domain doesn't match the staffing brand on the req, the rate conversation feels unusually cagey, or the recruiter mentions 'our partner' or 'the prime' when describing who actually holds the contract.

Every layer between you and the end client takes a cut of the bill rate before it reaches you. Three or four layers deep is common in large public-sector and healthcare programs, and it can quietly erode your take-home by 15 to 30 percent compared to a direct or single-layer arrangement, even on an identical client bill rate.

The question to ask: 'Are you the prime vendor on this contract, or are you subcontracting from another vendor? How many layers total sit between you and the client?' A straight answer here tells you more about your real take-home than the stated rate ever will.

Flag 4: A six-round interview loop for a six-month contract

Match the interview process length against the contract length. A req asking for a technical screen, a panel, a client culture-fit round, a leadership round, a coding exercise, and a final sign-off, for a role ending in six months, is a mismatch worth questioning out loud.

Long loops on short contracts usually mean one of three things: the hiring manager is risk-averse and may be equally slow to make decisions once you're on the team, the role is actually being used to pipeline for a future permanent hire and the contract framing is secondary, or the vendor stack is so deep that each layer insists on its own screening pass before forwarding you.

• Count the total rounds before you agree to the first one.
• Ask how long the full process typically takes, start to offer.
• Weigh that timeline against your current bench status and any other active submissions.

The question to ask: 'What's driving a process this long for a contract this short, and what's the typical timeline from first interview to start date?'

Flag 5: 'Ongoing' duration with no stated end date

'Contract, ongoing' sounds appealing, like stability. In practice it often means the client hasn't committed to a funded period, the role is tied to a project without a defined close date, or the staffing vendor hasn't negotiated contract terms with the client yet and is posting speculatively.

An open-ended duration isn't automatically bad. Plenty of strong long-term engagements start this way. The problem is going in blind about renewal cadence, notice periods, and what happens to your rate at renewal time.

The question to ask: 'Is this tied to a funded project with a defined budget cycle, and what's the typical renewal cadence and notice period if the engagement ends?'

Scorecard: what good posting language looks like

The one takeaway worth remembering

A requisition is a sales document written by someone trying to fill a seat. Read it the way you'd read a contract, because it's about to become one. If a posting won't answer a plain question about rate, client, vendor layers, process length, or duration before you submit, that's your answer about what submitting will feel like.

If you want a second set of eyes on a req before you say yes to submission, the Josh Pros LLC team looks at this stuff daily across W-2, corp-to-corp, and 1099 placements. Email contact@joshpros.com or visit https://joshpros.com and we'll give you a straight read.

#StaffingRequisitionRedFlags #ContractJobPostingWarningSigns #VendorSubmissionQuestions #ITContracting #CorpToCorp #W2Contracts #TechConsultants #BenchTime #StaffingVendors #ContractRates #ITStaffing #ConsultantLife

Back to all insights