The Edition
How sub-vendor staffing actually works (and why you might be in it without knowing)
If you’ve ever taken a contract engineering role and wondered why the recruiter who reached out to you was different from the one who managed your engagement, who was different from the company on your W-2, who was different from the company you actually worked at — you weren’t imagining it. You were probably in a sub-vendor staffing arrangement, and nobody told you because the industry has decided not to.
This piece explains how the model works, why the layers exist, what each layer takes from the gross bill rate, and what to ask if you want to know where you actually fit in the chain.
We’ll be direct about something up front: Edition Technologies operates as a sub-vendor. That’s part of why we’re writing this. Engineers deserve a clear picture of the model they’re working in, even when the firm explaining it is a participant.
The structure: end client, prime vendor, sub-vendor, candidate
For a typical mid-sized to enterprise contract engineering engagement, the chain looks like this:
End client (the company actually paying)
↓ pays bill rate to
Prime vendor (Tier-1 staffing firm)
↓ pays subcontract rate to
Sub-vendor (Tier-2 staffing firm — Edition is here)
↓ pays the engineer
Engineer
There are sometimes more layers. Three-tier and even four-tier chains exist, especially for federal-government and large-enterprise engagements. But two or three tiers is typical.
Why the layers exist
The end client doesn’t want to manage relationships with 200 different staffing firms. They want one (or a small handful) of “prime” or “Tier-1” vendors who hold the master contract — usually called a Master Services Agreement (MSA) — and are responsible for delivering candidates against any open requisition.
The prime vendor’s job is to filter, manage compliance, handle paperwork, and guarantee delivery. They charge the client a bill rate. They pocket a margin. They pass the rest down.
But the prime vendor often can’t fill every requisition with their own bench. They might have a Java specialist on staff but no Rust engineer. Or their bench is busy. Or the role is in a city where they don’t have a local recruiter. Or the role is too niche for their volume-driven model.
So they have a network of sub-vendors — smaller staffing firms that they trust to source and submit candidates. The sub-vendor doesn’t have a direct contract with the end client; they have a contract with the prime. The candidate goes on the sub-vendor’s payroll (or the prime’s, depending on the deal). Everyone splits the gross bill rate.
The MSP / VMS layer
For larger enterprises, there’s often another wrinkle: a Managed Service Provider (MSP) or Vendor Management System (VMS) sits between the end client and the staffing vendors.
- An MSP is a company that manages the end client’s contingent workforce program for them — they decide which staffing vendors are approved, set rate caps, audit compliance, and run the day-to-day. Examples: Allegis Global Solutions, Magnit (formerly IQN), KellyOCG, Pontoon Solutions.
- A VMS is the software that automates the requisition flow — reqs come in from hiring managers, get distributed to approved staffing vendors, candidate submissions are routed through, timesheets and invoices flow through. Examples: SAP Fieldglass, Beeline, Workday VNDLY, Magnit (the same name covers both their MSP service and their VMS platform).
In an MSP/VMS environment, “prime vendor” might mean the MSP itself, or one of a small set of approved primes that the MSP works with. Sub-vendors apply to be on the approved list.
The result: an engineer’s resume can pass through multiple firms before a hiring manager ever sees it
If a sub-vendor’s recruiter reaches out to you for a contract, your resume usually:
- Lives in the sub-vendor’s database (this is where you “applied” originally)
- Gets submitted by the sub-vendor to the prime vendor
- Gets reviewed and re-submitted by the prime to the MSP/VMS
- Lands in the hiring manager’s queue alongside submissions from other sub-vendors
By the time the hiring manager opens your resume, three or four firms have touched it.
Where the money goes: a worked example
Let’s say a Senior Backend Engineer is being placed at a Fortune 500 company through a typical chain. The end client is paying $160/hr.
| Layer | Takes from $160 bill rate | What’s left |
|---|---|---|
| End client → MSP/VMS administrative fee | ~$3-5 (2-3% of bill rate) | $155-157 |
| MSP/VMS → Prime vendor | Prime pays MSP a fee or gets a discounted bill rate; either way, prime sees ~$140-150 | $140-150 |
| Prime vendor margin | Prime keeps ~$25-35 (gross margin ~18-25%) | $105-125 |
| Prime → Sub-vendor (Edition tier) | Sub-vendor invoices prime at this rate | $105-125 |
| Sub-vendor margin | Sub keeps ~$15-25 (gross margin ~12-20%) | $80-110 |
| What hits the engineer | $80-110/hr depending on engagement model | — |
The engineer’s $80-110/hr take, expressed as a percentage of the $160 the client paid: 50% to 69%.
This is industry standard. It’s not unique to one firm. The exact percentages shift by engagement (high-volume IT staff aug compresses margins; specialized search expands them), by classification (W-2 has more burden in the firm’s margin than C2C), and by relationship (longer-tenure sub-vendors get better splits from primes).
The two layers are not arbitrary overhead. The prime is providing the client relationship, the MSA, the insurance, the compliance, and a guarantee of delivery. The sub-vendor is providing the actual sourcing, candidate vetting, and (often) the payroll. Each layer earns its margin by doing real work.
But each layer also takes a cut, and engineers are the only party in the chain who often don’t know the chain exists.
What this means for you as an engineer
A few practical implications:
1. The recruiter you’re talking to may not have direct contact with the hiring manager
If you’re being submitted through a sub-vendor, your recruiter usually can’t talk to the hiring manager directly. They have to route everything through the prime. This is why questions like “what’s the team structure?” or “who would I be reporting to?” can take 48 hours to get answered, and why interview scheduling sometimes feels like a game of telephone.
A good sub-vendor will tell you upfront how the chain works on a given engagement. Less-good ones will pretend they have a direct relationship that they don’t.
2. Counter-offers and salary negotiations are constrained by the rate cap
The MSP often caps the bill rate for a given role at a level the prime can’t exceed without escalation. The prime sets a minimum margin they need. The sub-vendor has their own minimum margin. By the time the engineer’s rate is being negotiated, there’s often $5-15/hr of flex at most — even if your skills warrant more.
This is why “I can’t get above $X/hr” sometimes feels arbitrary. It is, in a sense, but the constraint is real on the firm’s side. A good sub-vendor will tell you “the cap on this role is Y; I can get you to Y minus my minimum margin; that’s the math.” A less-good one will haggle without explaining.
3. The same role may get submitted to you by multiple firms
If a sub-vendor isn’t the only sub on a particular req, you might see the same job from two different firms. Don’t apply through both. Pick one, and tell any second recruiter you’ve already been submitted. Multiple submissions for the same candidate to the same client through different firms get the candidate eliminated by the client’s HR — they don’t want to deal with the duplicate-attribution mess.
If you’ve already applied directly to the company through their careers page in the past 6 months, tell the recruiter. The client may treat you as already-on-file, which can disqualify the staffing firm from earning a fee. A recruiter who ignores this risks burning the relationship for no good reason.
4. Your reference checks happen at the sub-vendor level, but your data flows up the chain
When you’re at the talent-pool / pre-submission stage, your data lives with the sub-vendor. Once you’re submitted, your name + summary + rate + availability flow up to the prime and the MSP. By the time you’re interviewed, several firms have your information. This is normal but worth knowing — your “private” job search is often less private than you think.
5. The model has compounding consequences for repeat placements
If you do a 6-month engagement through a sub-vendor and they place you well, the obvious question becomes: for the next role, do I go back to the same sub-vendor, or apply directly to the next prime, or go to the end client?
There’s usually a non-circumvention clause in the agreements that prevents the end client from poaching you directly from the staffing chain for some period (commonly 6-12 months). The sub-vendor and prime have similar clauses with each other. If you switch, the legal trigger usually depends on whether you initiated the switch or were poached.
Practically: if you had a good experience, the easiest path forward is the same firm. If you had a bad experience and the firm is the bottleneck, the contractual landscape gets more complicated than most engineers realize. A non-circumvention clause won’t legally bind you (you can quit and apply anywhere), but it can bind the firm or the client from working with you in a way that costs the original chain a fee.
How to ask the right questions
If you’re talking to a recruiter and you suspect you’re in a sub-vendor situation, here are five questions that will tell you almost everything:
**1. “Do you have a direct contract with this end client, or is this through a prime vendor or MSP?” **
Direct → it’s a one-tier engagement. They handle everything. Through a prime → ask who the prime is. Through an MSP/VMS → ask which one (Fieldglass, Beeline, Magnit, etc.).
A recruiter who can’t answer this clearly probably hasn’t done this before, or is hiding something.
**2. “What’s the bill rate cap on this role, and what’s your firm’s gross margin?”
You may not get a numerical answer. But the quality of the response is informative. A firm that says “the cap is $130, our margin is around 18%” is being transparent. A firm that says “we can’t share that information” is signaling that they don’t want you to do the math.
**3. “Who runs payroll, and which entity is on my W-2 (or which entity am I C2C-ing with)?”
This tells you who the actual employing or contracting entity is — which is who you’ll be calling if your timesheet is wrong, your invoice is unpaid, or your benefits don’t activate.
**4. “How long has your firm been on this client / prime’s approved-vendor list?”
A firm that’s been on the list for 5 years has stronger insight into the client’s culture, hiring patterns, and what closes. A firm that’s been there for 3 months is still figuring it out. Both can be fine; you just want to know which you’re dealing with.
**5. “If this engagement converts to full-time, who pays the conversion fee, and how is it calculated?”
Standard answer: client pays a conversion fee to the prime, who passes some to the sub-vendor. Calculated as a percentage of first-year salary (typically 20-30%) and reduced over the contract length. If the firm fumbles this question, they may not have negotiated the conversion language in their agreement, which can leave you stuck mid-conversion.
Why we tell candidates this
The honest reason: most engineers find out how this model works the hard way, after a confusing engagement, and conclude that staffing firms are opaque on purpose.
Most of us are. The information asymmetry is profitable in the short term — easier to compress your rate when you don’t know the bill rate; easier to defer questions when you don’t know who the prime is; easier to keep you on the bench between engagements when you can’t easily go to the next firm in the chain.
The argument we’d make is that the asymmetry isn’t profitable in the long term. Engineers talk. The good ones swap notes. A firm that explains the model gets better candidates because the candidates self-select — the ones who appreciate transparency stick around. The ones who don’t, leave. We’d rather work with the first group.
If you’re talking to any staffing firm — including us — and they refuse to answer the five questions above, that’s the answer to your question about whether to work with them.
This piece is part of The Edition, a monthly newsletter on engineering hiring from Edition Technologies — a US-wide engineering placement firm based in Austin. We operate as a sub-vendor for Tier-1 staffing partners and direct with end clients. If you’d like to be on our talent roster, join here. If you’re hiring engineers and want a different kind of conversation, start one.
Got feedback or a question we got wrong? Email info@editiontechnologies.com — we read every reply.