Most hiring managers use “contract-to-hire” as a loose synonym for “trial period” or “temp-to-hire.” It is a specific arrangement with real mechanics: a defined trial length, a conversion path both sides agree to up front, and a pay structure that changes the moment the engineer converts.
When the term stays loose, the arrangement breaks at the worst possible moment. A team brings on a backend engineer on a “contract-to-hire” basis with no written conversion criteria. At day 90, the engineer expects an automatic offer. The manager expects to start a fresh evaluation. Both feel misled, and the team either loses a good engineer or converts someone it doubts.
A contract-to-hire is a fixed-term contract, usually one to three months, with a pre-agreed path to a full-time offer based on written criteria. It works best when you trust the role’s scope but still need proof of long-term fit.
In this guide:
- What does contract-to-hire mean for an engineering team?
- How does an engineering trial work?
- When does this hiring model make sense?
- What should you agree on before the trial starts?
- What will the arrangement cost, and what changes at conversion?
- What should engineers ask before accepting a contract-to-hire role?
- Frequently asked questions
- Make the hiring decision with evidence from real work
What Does Contract-to-Hire Mean for an Engineering Team?
Contract-to-hire is an arrangement where an engineer works on a fixed-term contract with a pre-agreed path to a full-time offer. The offer depends on specific criteria that you write down before the contract starts. It sits between an open-ended freelance engagement and an immediate permanent hire.
In practice, the engineer joins your team, ships real code, and attends your standups for a set window. At an agreed date, you decide whether to make a full-time offer on terms you already outlined. The engineer decides whether to accept.
Two terms get confused with it:
- A straight contract or freelance engagement. The work has an end date or a project scope, and there is no conversion path. Nobody expects a full-time offer.
- Temp-to-hire. This term is more common in non-technical staffing, such as warehouse, admin, or call center roles. The mechanic is similar, but temp-to-hire often implies less integration during the trial. The worker fills a seat while the permanent team works around them. An engineering contract-to-hire should put the engineer inside your real workflows from week one.
How Does It Differ From Direct Hire and Project-Based Contracting?
The three models differ in two ways: when you commit, and what you are trying to learn.
- Direct hire: You make a full-time offer after interviews. You commit on day one, based on interview signals alone.
- Project-based contracting: You pay for a scoped piece of work, often hourly. You commit to the project, not the person. When the project ships, the contract ends.
- Contract-to-hire: You commit to a defined trial. You learn how the engineer performs on your codebase, in your reviews, and with your people. Then you commit to the person.
Interviews show you how someone solves problems in a 45-minute window, while a trial shows you how they handle a messy pull request review on a Thursday in week six. The second signal predicts long-term fit far better.
Who Engages and Pays the Engineer During the Contract Phase?
During the contract phase, the engineer is engaged and paid by whoever holds the contract. That is usually one of three parties:
- Your company directly. You sign an independent contractor agreement and pay invoices. You carry the classification risk, covered below.
- A staffing agency. In traditional contract-to-hire staffing, the agency is often the employer of record. It runs payroll and bills you a marked-up hourly rate.
- A hiring platform. Platforms such as Arc handle matching and payments during the contract. On Arc, freelancer payments run securely through the platform, and compliant global hires go through trusted EOR (employer of record) partners.
Whichever path you use, get one answer in writing before day one: who pays the engineer, and who becomes the employer at conversion.
Read more: Staff Augmentation vs Outsourcing vs Managed Services: Choosing an Engineering Delivery Model
How Does an Engineering Trial Work?
An engineering trial treats the engineer as a team member from day one, with a clear end date and written success criteria.
Run it in this order:
- Set the trial length. One to three months is common. Senior or specialized roles can run up to six months. Past that point, move the engineer onto a W-2 or EOR payroll (step 5) instead of stretching a contractor arrangement.
- Pay close to the standard rate for the role. Skip the “trial discount.” Below-market pay attracts weaker candidates and signals to strong ones that the offer isn’t serious.
- Write the conversion terms. Put the compensation band, target full-time start date, and notice period in writing before work begins.
- Integrate fully. Give the engineer access to your repos, Slack channels, standups, sprint planning, and code reviews. An engineer kept at arm’s length can’t show you whether they fit the team.
- Put the trial on a W-2 or EOR payroll. Step 4 is the part that makes a contract-to-hire engineer look like your employee: you set their hours, direct their work, and fold them into your team, which are the facts the IRS and the Department of Labor weigh in a classification review (see worker classification below). Resolve it before day one by having someone employ the engineer for the trial: a staffing agency that puts them on its own W-2 payroll, an employer of record if they live outside the US, or your own payroll as a fixed-term employee. Keep 1099 contracts for engineers who run their own business and decide how the work gets done.
- Define 30/60/90-day outcomes. Name specific deliverables and collaboration behaviors for each checkpoint.
- Hold checkpoint reviews. Share honest feedback at each mark so the final decision surprises no one.
- Decide on the scheduled date. Convert, extend once with a stated reason, or end the contract cleanly.
How Long Should the Contract Phase Last?
For most engineering roles, 60 to 90 days gives you enough signal. Use role seniority and system complexity to set the number.
| Role type | Suggested trial | Why |
| Mid-level web or mobile developer | 1 to 2 months | Enough time to ship several features and go through multiple review cycles |
| Senior backend or full-stack engineer | 2 to 3 months | Architecture decisions and cross-team work take longer to show up |
| Staff-level, DevOps, or AI specialist | 3 to 6 months; past 6, move to W-2 or EOR payroll | Impact appears in system design, reliability, and mentoring over time |
Shorter is better for the candidate. A strong engineer with other offers won’t wait six months for a decision on a mid-level role. If you can’t judge a mid-level developer in 90 days, the problem is usually your success criteria, not the trial length.
How Do You Decide to Convert?
You decide by scoring the engineer against the written 30/60/90-day criteria you set on day one. Don’t rely on a gut read in the final week.
A practical decision meeting looks like this:
- Who attends: The hiring manager, one peer engineer who reviewed their code, and one cross-functional partner such as a product manager or designer.
- What you review: Shipped work against the 90-day outcomes, code review quality, how they handled feedback, and how clearly they communicated blockers.
- What you decide: Convert, extend once for a named reason (such as “we need to see them own an on-call rotation”), or end.
If you convert, send the offer using the band you already agreed on. The engineer should be able to predict the number within a few percent. When they can’t, trust breaks right when you need it most.
When Does This Hiring Model Make Sense?
Contract-to-hire makes sense when you are confident in the role’s scope but less sure about long-term fit. Use a straight contract when the work is temporary. Use a direct hire when you already have a strong signal on the person.
Pick contract-to-hire when:
- You are building a new team and have no existing culture to hire against.
- The role uses a tech stack your team doesn’t know well, so your interviewers can’t judge depth.
- The role is new to your company, such as your first platform engineer or first ML engineer.
Pick a straight contract when:
- The work has a clear end, such as a migration, an MVP, or a security audit.
- You have no budget or headcount approval for a full-time seat.
- You need a narrow specialist for weeks, not years.
Pick a direct full-time hire when:
- A trusted colleague refers someone they have worked with directly.
- You have worked with the person as a freelancer for months already.
- The role matches ones you have hired for successfully several times.
| Arrangement | Best-fit scenario | Typical trial or ramp length | If it doesn’t work out |
| Contract-to-hire | Clear role, uncertain fit (new team, new stack, new role) | 1 to 3 months, up to 6 for senior roles | Contract ends on the agreed date or after written notice; access revoked, code ownership already assigned |
| Straight contract | Temporary or project-bound work, no intent to convert | Days to weeks to ramp; ends at project close | Contract ends per its terms; you re-scope or find a new contractor |
| Direct full-time hire | Strong prior signal on fit | 60 to 90 day onboarding ramp | Performance plan, then termination, severance, and a new search |
Which Engineering Roles Benefit From a Working Trial?
Roles where interviews give weak signal benefit most from a working trial.
- Senior and staff engineers. Their value lies in design choices and influence, which a coding test barely touches.
- Founding or first engineers in a function. Nobody on your team can judge the work yet, so real output is the best judge.
- Remote engineers in new time zones. A trial shows whether async handoffs work across, say, a US and LATAM team.
- DevOps and AI developers. The stacks vary so widely that “Kubernetes experience” can mean very different things. Our comparison of platforms to hire DevOps engineers sets out the trial and replacement terms each one offers.
Roles like a mid-level React developer on a well-known stack usually do fine as direct hires, especially with a strong vetting process in front.
A vetting step in front of the trial shortens it, since week one starts with an engineer whose fundamentals are already checked. Arc’s vetting process screens engineers for domain expertise and English fluency before you interview them.
What Are the Trade-Offs for You and the Engineer?
Contract-to-hire lowers your risk and raises the engineer’s. Be honest about that balance, and price it in.
For you:
- Upside: You judge fit on real work before committing to salary and benefits.
- Cost: You spend 60 to 90 days onboarding someone who may leave. The trial rate also runs higher per hour than salary.
For the engineer:
- Upside: They see your codebase, your managers, and your on-call reality before signing up.
- Cost: They go without full benefits and job security for the trial. Strong engineers with competing full-time offers will often pass.
Close that gap with fair pay, a short trial, and conversion terms written up front. Those three moves keep strong candidates in your pipeline.
What Should You Agree on Before the Trial Starts?
Agree on scope, pay, conversion terms, success criteria, and the off-ramp in writing before day one. Every one of those left for “later” turns into a hard talk at day 90.
How Do You Set Scope, Pay, and Conversion Terms?
Put these items in a one-page term sheet and have both sides sign it:
- Role scope: The team, the systems they will own, and who they report to.
- Trial rate: An hourly or monthly rate close to the role’s standard contract rate.
- Trial length and decision date: For example, “90 days, decision by June 30.” Put that date on both calendars on day one so it can’t slip.
- Full-time compensation band: A salary range, such as $140,000 to $155,000, plus any equity or bonus range.
- Target full-time start date: The day payroll and benefits begin if you convert.
- Notice period: How many days each side gives to end the trial early. Two weeks is a common, fair number.
- Agency restrictions and buyout terms: If an agency or platform holds the contract, read its conversion clause before day one. Agency contracts often include a no-hire clause that stops you hiring the engineer directly for a set period, plus a buyout fee if you convert. Get the fee, how it changes over time, and the length of any no-hire period in writing.
Writing the band down early does two things. It proves the full-time path is real. It also stops a competing offer from beating you in the final week, since the engineer already knows your number.
What Does the Trial Count Toward?
Decide whether the trial months count once the engineer converts, and write the answer into the term sheet. Each of these is your call, and each one changes what the offer is worth:
- PTO accrual: whether the engineer starts the full-time year with leave already accrued or at zero.
- Tenure: whether the trial counts toward promotion timelines, severance formulas, and service-based awards.
- Equity vesting cliff: whether a one-year cliff starts on the trial start date or the full-time start date. Starting it at conversion pushes the first vesting date back by the length of the trial.
- Benefits waiting periods: the Affordable Care Act caps a group health plan’s waiting period at 90 days, and the IRS lets a 401(k) plan require up to one year of service before an employee joins. Ask your benefits provider whether trial time on an agency or EOR payroll counts toward either.
Engineers with competing offers will ask about all four, so have the answers ready before the offer conversation.
What Should a 30/60/90-Day Scorecard Measure?
A 30/60/90-day scorecard should measure both output and collaboration on the same written rubric. Engineers who ship fast but block their teammates are a common mis-hire. Ground the output column in delivery signals your team already tracks; Arc’s guide to measuring developer productivity explains why raw PR counts mislead and which team-level signals, such as review turnaround, hold up.
| Checkpoint | Output examples | Collaboration examples |
| Day 30 | Local environment running; first 3 to 5 PRs merged; one small bug fix in production | Asks clear questions in public channels; responds to review comments within a day |
| Day 60 | Owns one feature end to end; writes tests to team standards | Gives useful code reviews to others; flags blockers early in standup |
| Day 90 | Ships a medium-sized project with little guidance; handles one incident or on-call shift | Explains trade-offs to product or design; peers want them on their next project |
Score each row 1 to 4 with a short written note. “Good communicator” is useless in a decision meeting. “Wrote the rollout plan for the billing migration and got sign-off from two teams” is evidence.
How Do You Handle Notice, Intellectual Property, and a Decision Not to Convert?
Handle all three in the contract itself, before any code gets written.
- Notice: State the notice period for early exit by either side. Say whether you pay through the notice period if you end it.
- Intellectual property: Include a clause that assigns all work product to your company upon creation. That keeps you from needing to chase an assignment later if the engagement ends badly.
- A decision not to convert: Write down what happens. Does the contract end on the decision date? Is there a final handoff week? When is access to repos, cloud accounts, and Slack revoked?
A clean off-ramp protects the engineer too. They know the worst case up front and can plan their search around it.
What Will the Arrangement Cost, and What Changes at Conversion?
The arrangement costs you in two phases: an hourly trial rate, then a full-time salary plus any conversion fee. At conversion, you also pick up payroll taxes and benefits.
How Do Hourly Rates and Conversion Fees Work?
Trial phase
You’ll pay close to the standard contract rate for the role. On Arc, freelance rates run from $15 to $110+ per hour according to its pricing page, with region and seniority setting where an engineer lands. Engineers in LATAM or APAC often cost less than US-based engineers with similar skills.
Conversion phase
Full-time salary is your highest cost. For a benchmark, the U.S. Bureau of Labor Statistics lists a median annual wage of $135,980 for Software Developers (occupation code 15-1252) as of May 2025. That is the closest official proxy for US engineering salaries. Check the latest release before you set a band, since BLS updates it every year.
Conversion fees
Agencies and platforms often charge a fee when you move a contractor onto your payroll, and the structure matters as much as the headline number. You will usually see one of three:
- Flat conversion fee: a percentage of the engineer’s first-year salary, charged at conversion, much like a direct-hire placement fee.
- Sliding scale: the fee drops the longer the engineer has billed through the agency, sometimes reaching zero after a set number of hours or months.
- Built-in conversion: no separate fee after a minimum billing period, because the agency’s margin is already in the hourly markup you paid during the trial.
Ask which one applies, what the fee will be on your planned decision date, and whether the clock resets if you extend. Arc doesn’t publish a fee for converting a freelancer to full-time, so get that number in writing before the trial starts. For engineers you hire as full-time from the outset, Arc’s published fee is 20% of annual salary.
What Should You Check About Worker Classification and Global Hiring?
Check that your trial engineer is classified correctly for their location. The rules change depending on who controls the work.
In the US, the IRS applies a common-law test that looks at the whole relationship and the extent of your right to direct and control the worker, grouped into behavioral control, financial control, and the type of relationship. The Department of Labor uses an economic reality test under the Fair Labor Standards Act, which asks whether the worker is in business for themselves or economically dependent on you; its February 2026 proposed rule names the worker’s control over the work and their opportunity for profit or loss as the two core factors. A contract-to-hire engineer who attends your standups on your schedule looks a lot like an employee under both tests, which is why the trial belongs on a W-2 or EOR payroll. Talk to employment counsel if you pay a US contractor directly for months.
For engineers outside the US, use an employer of record. An EOR employs the engineer legally in their country and handles local payroll, taxes, and required benefits. Arc pays freelancers through the platform and routes compliant global hires through trusted EOR partners, so confirm which of the two your engineer will be on before the trial starts. That choice decides who carries the classification risk.
Check work authorization before day one as well. Every US employer completes Form I-9 to verify a new hire’s identity and right to work, so expect to run it yourself at conversion even if an agency employed the engineer during the trial. If the engineer holds an H-1B through another employer, the new employer files its own petition, and under DHS’s 2016 portability rule they can start once a non-frivolous petition is filed. Build that filing time into your target start date, and check with immigration counsel before you promise one.
When Do Payroll Taxes and Employee Benefits Become Your Responsibility?
Payroll taxes and benefits become your responsibility at conversion, on the full-time start date you wrote into the term sheet.
- During the contract phase: The contractor, agency, or EOR handles tax withholding. You avoid the full permanent benefits package, such as health insurance, 401(k) matching, and paid leave.
- At conversion: You start withholding income tax and paying the employer share of Social Security, Medicare, and unemployment taxes. Your benefits package kicks in per your plan’s waiting period.
Budget for this jump. The full cost of a US employee runs well above base salary once you add taxes and benefits, so build that into your band before you share it.
What Should Engineers Ask Before Accepting a Contract-to-Hire Role?
If you’re the engineer, a contract-to-hire offer asks you to carry risk the company is shedding. Five questions before you sign tell you whether the full-time role is real:
- Who employs me during the trial? On an agency or EOR payroll, tax is withheld and benefits may start sooner. On a 1099 contract you owe self-employment tax of 15.3% (12.4% Social Security plus 2.9% Medicare) on top of income tax, so set your rate with that in mind.
- What is the full-time salary band? A company that won’t put a number in writing before day one hasn’t committed to converting you.
- What are the conversion criteria and the decision date? Ask to see the 30/60/90-day scorecard you’ll be measured against.
- Is there a buyout fee or no-hire clause? If an agency holds your contract, a buyout fee can make you cost more to convert than an outside candidate. Ask whether the hiring manager has budgeted for it.
- What does the trial count toward? Ask when health coverage starts and whether trial months count toward PTO, tenure, and equity vesting.
One more question tells you a lot: how many of the last few contract-to-hire engineers on this team converted? A manager who can answer with names and dates has run the process before.
Frequently Asked Questions
What Does Contract-to-Hire Mean?
Contract-to-hire means an engineer works on a fixed-term contract with a pre-agreed path to a full-time offer, evaluated against written criteria you set before the contract starts. It sits between an open-ended freelance engagement, which has no conversion path, and an immediate permanent hire, which commits on interview signal alone.
What Is the Difference Between Contract-to-Hire and Temp-to-Hire?
The mechanic is similar, but the terms come from different corners of staffing. Temp-to-hire is more common in non-technical roles and often implies less integration during the trial; the worker fills a seat while the permanent team works around them. An engineering contract-to-hire should put the engineer inside your real workflows, standups, and code reviews from week one, since that is where fit shows up.
How Long Does a Contract-to-Hire Trial Typically Last?
Most engineering trials run one to three months. Senior, staff-level, or specialized roles (DevOps, AI, architecture-heavy work) can run up to six months, since the impact of those roles shows up more slowly, in system design decisions and mentoring rather than in shipped features alone. If you need longer than that, put the engineer on a W-2 or EOR payroll for the rest of the evaluation.
What Happens if You Don’t Convert a Contract-to-Hire Engineer to Full-Time?
It depends on what you wrote into the contract before day one. At minimum, define whether the contract ends on the decision date or after a notice period, what a final handoff week looks like, and when access to repos, cloud accounts, and communication tools gets revoked. A clean, pre-agreed off-ramp protects both sides.
Is Contract-to-Hire Staffing More Expensive Than a Direct Hire?
It costs more per hour during the trial, since you should pay close to the standard rate rather than a discount, and you carry that cost for one to three months (up to six for senior roles) before any full-time salary begins. In exchange, you get real evidence of fit before committing to salary and benefits, which lowers the cost of a bad full-time hire. Whether it nets out cheaper depends on how often your direct hires would otherwise not work out.
Make the Hiring Decision With Evidence From Real Work
Contract-to-hire gives you the best hiring evidence: weeks of real work inside your real team. It only pays off when you define the model tightly.
Keep these points in front of you:
- Contract-to-hire means a fixed-term contract with a written path to a full-time offer. It differs from a straight contract (no conversion path) and from temp-to-hire (less team integration).
- Run trials of one to three months for most roles and up to six months for senior or specialized ones, at close to the standard rate and on a W-2 or EOR payroll.
- Use it when the role is clear but fit is uncertain. Use contracts for temporary work and direct hires when you already have a strong signal.
- Write the compensation band, target start date, notice period, and decision date before day one.
- Score output and collaboration on the same 30/60/90-day rubric.
- Plan for payroll taxes, benefits, and any conversion fee at the switch to full-time.
When you’re ready to fill the trial seat, Arc matches you with engineers from the top 2% of its vetted talent pool, with freelance hires in as little as 72 hours. You pay $0 until you hire.
