I describe the contractor-to-FTE transition to clients like this: contracting is dating, full-time is marriage. Both are valid. But if you're dating someone great and you wait too long to have the conversation about commitment, don't be surprised when they find someone who's ready.

This is the single most common talent mistake I see in scaling companies. They find a great contractor, they keep renewing the contract quarter after quarter, and then one day the contractor gives two weeks notice because someone else offered them stability.

The Signal That It's Time

You should start the FTE conversation when three things are true simultaneously:

The role is clearly ongoing. If you're backfilling a specific project need that has an end date, keep it as a contract. If the contractor has been on your team for 6 months and you can't imagine not having them, the role is permanent — your staffing model just hasn't caught up yet.

They've demonstrated judgment, not just output. Plenty of contractors can write code to spec. The ones worth converting are the ones who push back on specs that don't make sense, who flag technical debt before it becomes a crisis, who mentor junior team members without being asked. They're acting like an employee already — make it official.

The cost of losing them exceeds the employment overhead. Contractors are typically 20-40% more expensive per hour than equivalent FTEs, but they don't come with benefits costs, PTO, or employment liability. Run the actual math: fully loaded FTE cost vs. contractor rate vs. cost of recruitment, onboarding, and ramp-up time if they leave. For most positions, the break-even is around month 4-5.

The 90-Day Conversation

Don't wait for the contractor to bring it up. At the 90-day mark, have a direct conversation: "Here's what we're seeing, here's what we value about your contribution, and here's what the path to full-time looks like if that's something you're interested in."

Some contractors prefer contracting — higher rates, more flexibility, variety of work. That's fine. But you need to know where they stand so you can plan accordingly. The worst outcome is assuming they'll stick around indefinitely when they're quietly interviewing.

What Changes (and What Shouldn't)

The biggest risk in the transition is bureaucracy shock. A contractor who was shipping code autonomously suddenly has to sit through mandatory compliance training, wait for IT to provision a company laptop, and navigate a PTO request system. Some of this is unavoidable, but minimize the friction.

Keep the same: their team, their projects, their autonomy, their daily rhythm. The work shouldn't feel different on day one as an FTE.

Add gradually: benefits enrollment, company culture events, longer-term project ownership, mentoring responsibilities. Don't dump everything on them in week one.

Watch for: the conversion sometimes changes the power dynamic in ways nobody expects. A contractor who felt empowered to push back may suddenly feel like they need to be more compliant as an employee. Explicitly tell them: "We're converting you because of how you work, not despite it. Keep doing what you're doing."

Security and Access Considerations

One thing that changes immediately: risk profile. Contractors with production access represent a specific security posture — most companies have immediate termination and access revocation policies for contractors, which is appropriate. FTEs typically have more graduated offboarding.

During the transition, audit their access. They may have accumulated permissions over months that should be rationalized. Convert their contractor accounts to employee accounts rather than running both in parallel. Update your access control lists.

The International Contractor Question

This gets more complex with international contractors, which is increasingly common. I've seen strong contributions from international talent — including engineers in Ethiopia and Brazil who've been exceptional contributors on recent engagements.

Converting international contractors to FTEs means either setting up a legal entity in their country, using an Employer of Record (EOR) service like Deel or Remote, or relocating them. Each has tradeoffs:

EOR services cost $300-600/month per employee on top of salary, but they handle compliance, payroll, and benefits. For 1-5 international employees, this is almost always the right answer. For 10+, start evaluating whether a local entity makes financial sense.

When to Keep It as a Contract

Not every good contractor should be converted. Keep the relationship as-is when:

The work is genuinely project-based with a defined end. Converting someone to FTE and then laying them off 6 months later is worse for everyone than a clean contract completion.

The contractor is running their own business and has multiple clients. They may value the independence more than the stability, and forcing the choice may cost you the relationship entirely.

Your company isn't ready for the overhead. If you don't have HR, payroll, and benefits infrastructure, converting contractors creates administrative burden that can distract from the actual work. Get the infrastructure in place first.

The Timing Trap

The most expensive version of this mistake: you know at month 3 that you want to convert them, but you wait until month 8 because "budget isn't approved yet" or "we want to wait until the next fiscal year." During those five months, the contractor is fielding other offers and you're paying a premium rate for someone you've already decided is permanent.

If the decision is obvious, make it. Budget cycles shouldn't override talent decisions that are clearly net positive. The CFO will understand when you explain that the alternative is paying a recruiter $40K to replace someone you already have.


Related: Hiring Your First Engineering Leader, How to Interview Engineers Without Wasting Everyone's Time, Scaling Engineering Teams from 1 to 20