Integrating Contract Engineers Without Creating a Two-Tier Culture

Last updated: October 4, 2026

By Kris Drouet, Engineering Executive, in partnership with KORE1

#lending-core had nineteen people in it. #lending-core-ext had seven.

I approved the second channel. It took me about four seconds. Security wanted contractors out of the incident channel until their background checks cleared, somebody suggested a separate room “just for now,” and I typed yes between two other meetings. Eleven months later it was still there. Every one of the seven was a contract engineer.

One of them, two months into a year-long engagement on our loan origination platform, found a retry bug in the credit-report integration. On a timeout, the client could fire the request twice. Two requests meant two hard inquiries on a borrower’s credit file. She posted it in #lending-core-ext on a Tuesday with a log excerpt and a one-line fix. Two other contractors reacted with the eyes emoji. No employee was in the channel to see it. Nobody was going to be.

Three weeks later a borrower disputed a second hard pull. The fix took an afternoon. It was hers, almost line for line.

Nobody on that team would have told you we had a two-tier culture. We had good people, decent rates, a staffing partner who sent strong engineers, and a team lunch every other Friday that everyone was invited to. What we also had was a structure that quietly sorted information, decisions, and credit by employment status, and a VP who had signed off on it without noticing. That is how it usually happens. Nobody designs a second tier. It accretes. Slowly.

The fix sits in a framework I’ve already written up. The decision ownership diagram plots every call on two axes, reversibility and blast radius, and hands the owner to whoever the grid says. It’s the third layer of the Clarity Stack. What I didn’t say in that piece is what happens when half the names on the grid belong to people on a contract staffing agreement. The grid still works. I’ve checked. You just have to stop it from silently checking the badge first. It’s also a team design question, the same one behind team topologies in practice, because contractors tend to get dropped into whichever boundary is already weakest.

What a Two-Tier Engineering Culture Looks Like From the Inside

A two-tier culture is a mixed team where employment status, not the work, decides who gets information, who makes decisions, and who gets credit. You can usually see it in artifacts before anyone feels it, in channel lists, retro invites, and who is allowed to approve a pull request.

The vocabulary gives it away first. At Microsoft in the late 1990s, permanent staff were “Blue Badges,” after the color of their passes, and agency temps were “A-dashes,” after the prefix on their email addresses, as the history of the permatemp fight records it. Thousands of those workers sued over being shut out of the employee stock purchase plan. Microsoft settled for $97 million. KORE1’s piece on contractor tenure limits covers the legal side of that case and why it still shapes how long assignments run, so I won’t relitigate it here. The part that interests me is the email prefix. Every message an A-dash sent announced which tier it came from before anyone read a word of it. Think about that.

Twenty years later the scale got bigger. A New York Times report in May 2019 put Google at about 121,000 contract workers against 102,000 full-time employees, and by August a group of U.S. senators was demanding that Google convert contractors to full-time after six months of work, as CNBC reported. Some of the separation inside a company that size has a legal rationale. Plenty of it is just habit wearing a policy badge.

Your team isn’t Google. The pattern scales down fine, though.

The Research Says the Whole Team Pays for It

The obvious cost lands on the contractors. They get less context, so they make worse calls, so they get trusted with fewer calls, and the loop tightens until the engagement ends and everyone agrees the contractor was “fine.” Less obvious is what it does to everyone else on the team. It isn’t small.

Joseph Broschak and Alison Davis-Blake studied exactly this in the Academy of Management Journal in 2006, looking at what happens to work groups as the mix of standard and nonstandard arrangements shifts. Groups with a higher share of nonstandard workers reported less favorable relationships with supervisors and peers, less willingness to help one another, and stronger intentions to leave. Read that list again. Every item on it is a team behavior. The mix exposes a team problem, and it reaches your retention numbers before it reaches anywhere you’d think to look.

Then there’s speaking up. Amy Edmondson’s 1999 study of 51 work teams in a manufacturing company, published in Administrative Science Quarterly, found that team psychological safety, the shared belief that the team is safe for interpersonal risk, was associated with learning behavior, and learning behavior predicted performance. Somebody who thinks they’re a guest doesn’t take interpersonal risks. They post the credit-pull bug in the side channel. Or they don’t post it at all, because the last time a contractor questioned a design the room went quiet, and quiet in that room means something different when your contract renews in March.

There’s a fair objection here. Harvard Business Review argued in 2021 that contractors and full-time employees have different motivations and expectations, and that managing contractors exactly like employees is its own mistake. I agree with that. Mostly. Different needs are real. The trouble is that “different” becomes the excuse for every difference, including the ones nobody can defend. So treat them differently. Just be ready to explain each difference to the person on the wrong side of it.

Draw the Decision Map on the Work, Then Check the Badge

Start with the map you already have. If you don’t have one, the two-axis version takes an hour. Reversibility on one axis, blast radius on the other, a named owner in each quadrant. Now do the one thing most leaders skip with a mixed team. Fill it in without looking at anyone’s employment status, then go back and check where status changed the answer.

When I ran this on the lending team, the badge had moved four of the eleven decision types. Three of them shouldn’t have moved. I was embarrassed.

Look at the last row. It’s the only one where a difference survived, and the reason it survived isn’t status.

The End-Date Rule

A one-way door has consequences that outlive the person who opened it. That’s what makes it one-way. Ask any migration team. A data model, a vendor contract with a lock-in clause, a public API field. Somebody will be living with the choice in eighteen months, answering for it, migrating off it. Maybe you.

So here’s the rule I use. A one-way door goes to someone whose time on the team runs past the point where the consequences show up. If a contract ends in five months and the data model won’t hurt anybody until month nine, the contractor writes the decision record, argues the tradeoffs, and probably knows more about the problem than anyone else in the room. A permanent engineer who will still be around signs it and owns the follow-through.

Here’s what makes it fair. The rule applies to employees too. The senior engineer who gave notice two weeks ago doesn’t get to pick the database either, and nobody calls that a second tier. Neither does the engineer who’s moving to another team next quarter. When the rule is about the end date, people accept it. When the rule is about the badge, they notice the difference immediately, and the good contractors start counting days.

Most decisions on any team are two-way doors. Most. That’s the whole point of drawing the map. The end-date rule touches maybe one decision in ten, and for the other nine the contractor’s badge should be invisible.

Differences You Have to Keep, and the Ones You Made Up

Some lines between employees and contractors are real. If a contract engineer is a W-2 employee of a staffing firm, the firm is the employer of record. It pays them, it runs their benefits, and it handles their performance management. Blur that and you’re inviting the same kind of co-employment question the Microsoft case turned on. I’m an engineering leader, not your lawyer, so for the legal side read the co-employment section of the contractor onboarding checklist and the breakdown of contractor misclassification risk, then ask your own counsel.

What I can tell you is which differences I’ve watched teams keep for no reason anyone could articulate. There are a lot.

Notice the pattern in the “Keep” rows. Every one of them is about the employment relationship. Not one is about the engineering. Look again. The moment a difference touches how work gets done, who knows what, or who gets heard, you need a reason that isn’t the badge, and in my experience you won’t find one.

Where the Second Tier Shows Up First

You can audit this in about fifteen minutes. You don’t need a survey. Surveys of contractors about inclusion produce exactly the polite answers you’d expect from people whose renewal depends on your goodwill.

• Open your chat tool and sort channels by member list. Any channel whose membership tracks employer instead of system access is a finding.
• The last five incident reviews. Who was invited, and who wrote it up?
• Check the author field on your architecture decision records for the past two quarters. On one team I reviewed, contractors had written 40 percent of the code in that window and zero ADRs. Zero. Not because they had no opinions. Because nobody had told them the ADRs were theirs to write, so they assumed they weren’t.
• Listen to how people talk in standup. “They” is the tell. “Can we get the contractors to pick that up” means the team has already split, at least in its own head, and the work is being routed by tier.
• Who demos? If contractors build it and employees present it, you’re quietly moving credit up the badge line, and the contractors will notice long before you do.

One finding is a Tuesday. Three is a structure.

When the Contractor Is the Best Engineer in the Room

This happens. More than people admit. You bring in a contract architect because nobody on staff has done a Kafka migration under real transaction volume, and within a month it’s obvious they’re the strongest engineer on the floor. Then the team does one of two things. It treats them like a ticket-taker, which wastes the rate you’re paying. Or it lets them become the single point of knowledge, which is fine right up until the engagement ends and the knowledge walks out with them.

Neither is necessary. Both are common. Give them a real quadrant on the map, the same as you would a staff engineer. Pair them with a permanent engineer from week one, not week twenty, and make the pairing a named responsibility on both sides rather than a vague hope about knowledge transfer. On the decoupling work that took our downstream processing latency down 45 percent, the calls that mattered came from whoever understood the coupling under the hood. Nobody checked a title before listening. That’s the standard. The badge shouldn’t get a vote either.

A practical note. If you need several senior people at once, hiring them as individual contractors from different sources is how you end up with strangers learning each other’s habits on your clock. KORE1, the staffing firm I write with, assembles contract engineering teams that have already shipped together for exactly that situation. They benefit when you hire that way, and you should know that. Their numbers are worth knowing too. A 17-day average time-to-hire on IT roles and 92 percent twelve-month retention across placements in 30+ U.S. metros. Retention is the one that matters here. A contractor who stays the full engagement and hands off cleanly is worth more than a faster start.

The Pushback I Get on Mixed Teams

Can Contractors Approve Pull Requests From Full-Time Engineers?

Yes, if they know the code, because review rights should follow code ownership and knowledge rather than employment status.

The exception is a regulated control. If you’re running segregation of duties for SOX or a lending audit, write that rule by role. “The person who wrote the change can’t approve it” applies to everybody. “Contractors can’t approve” is a status rule pretending to be a control, and an auditor will eventually ask you to explain it.

Should Contract Engineers Sit in Retros and Incident Reviews?

Always, for any work they touched, since the person closest to a failure usually holds the detail that makes the review worth running.

If a review covers something sensitive, like a personnel issue or an employee comp discussion that drifted in, that part belongs in a different meeting anyway. Don’t solve it by trimming the invite list. I’ve written about running an incident review that actually changes behavior, and leaving out the engineer who saw it happen is the fastest way to get the other kind.

Doesn’t Treating Contractors Like Teammates Create Co-Employment Risk?

Including contractors in engineering work is different from acting as their employer, and the legal exposure sits mainly in the second one, meaning pay, benefits, hiring, firing, and formal discipline.

That’s the short version. The real version depends on your state, the contract with the staffing firm, and facts I can’t see from here, so take it to counsel. What I’ll say from the engineering side is that every lawyer I’ve worked with drew the line around the employment relationship, never around whether the contract engineer was allowed into the architecture review.

So Should a Contractor Ever Own a One-Way-Door Decision?

Own the analysis, yes. Own the final signature, only when their engagement runs past the point where the decision’s consequences show up.

Sometimes it does. An eighteen-month contract on a twelve-month migration, or a contractor everyone already knows is converting to full-time. In those cases, let them sign. The end-date rule is about who will be there when the bill comes due. If that’s the contractor, the badge is irrelevant.

Our Employees Resent What Contractors Earn. What Do I Do With That?

Explain the trade once, in plain numbers. Contractors usually earn a higher hourly rate because they carry the benefits gap, the bench time between engagements, and the end date.

Most engineers get it once they see the whole package side by side. Some won’t. The resentment that doesn’t fade usually isn’t about rate at all. It’s about the contractor getting the interesting work while employees get the maintenance queue, and that’s a work-allocation problem you created and can fix. KORE1’s breakdown of how to budget a blended workforce has the cost comparison if you want to put real figures in front of the team.

How Will I Know the Second Tier Is Gone?

The fastest test is to ask a new hire, after a month, which engineers are contractors. If they have to look it up, you’re most of the way there.

The quantitative version is the audit above, rerun every quarter. ADR authorship roughly tracking who’s doing the work. Incident reviews written by whoever was closest. No channel whose member list maps to an employer. Show me the data on those three and I’ll believe the culture changed. The team lunch roster tells you nothing.

Close the Side Channel

We archived #lending-core-ext on a Monday. It took less time than approving it had. Maybe two seconds. The security concern that started it was real, and it got solved the right way, by scoping the incident channel’s sensitive integrations by role instead of by employer, which is what we should have done in the first place.

The contract engineer who found the credit-pull bug renewed for a second year. She wrote three ADRs in the first quarter after the channel closed. One of them redesigned the retry handling across every bureau integration we had, and the duplicate-inquiry disputes stopped. Same engineer. Same rate. Different room. Better code.

If you want to argue with the end-date rule, or tell me about a difference I said to drop that you think you have to keep, connect with me on LinkedIn or DM me there. And if the real gap turns out to be that you need senior contract engineers who can own a quadrant from week one, talk to KORE1’s engineering recruiters.

Related reading: Decision Ownership: The Single Diagram That Stops Hallway Decisions, The Clarity Stack: 3 Reasons Engineering Velocity Stalls, Scaling an Engineering Team with Contractors, and The Coordination Tax: Brooks’s Law and Why Adding Engineers Made Your Team Slower.