.png)
What is C2H (Contract-to-Hire) in US IT Staffing?
- Saransh Garg
- 18 hours ago
- 13 min read
Updated: 3 hours ago
When a mid-sized SaaS company in Austin told us they needed a Senior DevOps Engineer but were not ready to commit to a full-time headcount, we placed a C2H engineer from Bengaluru within 19 days. The engineer was on a 6-month contract. At month four, the client converted him to permanent. Total hiring cost: under $28,000, against a US market average of $42,000 to $55,000 for a direct permanent hire at that level. That is what C2H (Contract-to-Hire) US IT staffing actually looks like in practice.
It is a model where the company hires a tech professional on a fixed-term contract, retains the right to convert them to full-time employment at the end of the contract period, and pays a conversion fee only if they choose to make that transition. For companies hiring from India, this model carries specific legal, payroll, and compliance mechanics that most HR managers do not fully understand until they are already mid-engagement.
What Is Driving C2H Demand in US IT Staffing Right Now?
The US IT talent market has been operating under intense pressure since 2022. Engineering salaries spiked, then tech layoffs created a complicated middle ground where companies needed skills but could not justify headcount approvals. By 2024, C2H arrangements made up roughly 35 to 40% of all IT staffing placements in markets like Austin, Dallas, Atlanta, and Raleigh, cities that saw explosive GCC growth and startup scaling without proportional local talent supply.
What we see in live mandates across our US client base: hiring managers get budget for contractors far faster than they get headcount approval for permanent roles. A CTO at a 200-person fintech firm in Chicago told us bluntly: "I can spin up a contractor in two weeks. A perm hire takes three months of internal approvals." C2H sits exactly in that space.
The roles most commonly placed through C2H (Contract-to-Hire) US IT staffing are:
DevOps and platform engineers (Kubernetes, Terraform, AWS)
Full-stack engineers (React + Node, Java Spring Boot)
Data engineers (Spark, Airflow, Snowflake, dbt)
QA automation engineers (Selenium, Cypress, Playwright)
Cloud architects (AWS, Azure, GCP)
For companies exploring international hiring from India, C2H is often the first model they try, partly because it lowers commitment risk and partly because it creates a natural trial period before full payroll integration.
The talent shortage is acute in specific stacks. Kubernetes-certified engineers in Chicago or Denver command $160,000 to $190,000 in annual salary. The same engineer hired from Hyderabad or Pune on a contract-to-hire arrangement costs the US company $38,000 to $52,000 per year in total, depending on EOR structure.
Which Indian Cities and Roles Are Best Suited for C2H IT Hiring?
India produces approximately 1.5 million engineering graduates annually. The cities with the deepest bench for US C2H IT roles are Bengaluru, Hyderabad, Pune, and Chennai, in that order for pure volume. Noida and Gurgaon lead for certain enterprise stack roles including SAP, Oracle, and legacy Java.
For DevOps and cloud roles, Bengaluru is our first call. The density of engineers who have worked with US-headquartered product companies is highest here, which matters for C2H because US clients need engineers who can hit the ground running, not spend three weeks learning Jira workflows and async communication norms.
Hyderabad is our go-to for data engineering and QA automation. The GCC ecosystem there, with companies like Apple, Google, Microsoft, and ICICI running large tech centres, has produced engineers who understand delivery timelines, sprint cadence, and stakeholder management in ways that align well with US client expectations.
What Indian engineers on C2H placements typically lack, and this is something only a recruiter who has managed 500+ cross-border mandates would tell you honestly:
1. On-call culture alignment: US product companies often expect engineers to be reachable outside sprint hours. Indian engineers are excellent within structured hours but frequently underestimate what getting a Slack message at 10 PM IST on a P1 incident actually means operationally.
2. Client-facing communication in async environments: Writing a Confluence update that a US stakeholder can read at 8 AM their time and act on immediately, without a call, is a skill gap we test for explicitly.
3. DevOps ownership vs. execution mindset: Many Indian engineers are trained to build what is scoped. US contract-to-hire clients, especially startups, want engineers who also flag what should be built. We use scenario-based panels to test this.
For cloud engineering roles, we run a live AWS architecture review where the candidate must both propose and defend a design, not just implement a given one. This filters out the top 30% from the top 10% very quickly.
Is C2H Legal for Indian Engineers Working Remotely for US Companies?
This is where most companies make costly mistakes, and where our team adds the most value beyond sourcing.The governing law in the US context is the Internal Revenue Code (IRC) Section 1706 and related IRS worker classification rules, specifically the 20-factor common law test.
Misclassifying a worker as an independent contractor when they function as an employee is the single most common legal error in C2H (Contract-to-Hire) IT staffing arrangements. The penalties include back taxes, interest, and in some states, statutory damages.
For Indian engineers working remotely from India on a C2H arrangement for a US company, the legal and tax structure is more nuanced:
1.If the engineer is on the payroll of an Indian EOR:
The Indian company is the legal employer. The US company pays the EOR a service fee. The engineer receives Indian-compliant payroll. No US payroll tax liability arises for the engineer. The US company has no W-2, W-8BEN, or 1099 obligation in this structure, but must ensure the EOR agreement is correctly drafted to avoid a permanent establishment risk under the US-India tax treaty.
2.If the engineer is paid as an independent contractor:
This triggers the IRS behavioral control and financial control tests immediately. If the engineer works exclusively for one US client, follows client-directed work hours, uses client tools, and is integrated into client sprints, the IRS will reclassify them as an employee. This is the most common mistake we see with US startups who try to manage India contracts without an EOR intermediary.
3.State-level rules add another layer.
California's AB5 law imposes one of the most stringent ABC tests for contractor classification in the country. If the US company is registered in California and the Indian engineer is performing work within the usual course of the hiring entity's business, the contractor classification fails under AB5, regardless of where the engineer sits physically.
When our clients ask about contract hiring from India, the first question we ask is: what state is your entity registered in, and do you have an EOR relationship already? If neither is in place, we recommend using our EOR service before the first engagement letter is signed.
The conversion fee, which is what the US company pays the staffing agency when they convert a C2H engineer to permanent, is typically 10 to 15% of the engineer's first-year annual base salary in Indian rupees, or a flat fee agreed at contract initiation. This must be spelled out in the Master Services Agreement (MSA) before placement begins. We have seen clients attempt to convert engineers six months in and then dispute the fee because it was not in writing. That dispute never goes well.
C2H vs. Direct Hire vs. EOR: Which Model Works Best for Hiring Indian IT Engineers?
This is the table we share with every new US client at the first discovery call. It is built from 200+ real mandates, not industry surveys.
Parameter | C2H (Contract-to-Hire) | Direct Permanent Hire | EOR Permanent Hire |
Time to first working day | 15 to 25 days | 45 to 90 days | 20 to 35 days |
Upfront commitment | None (trial period) | Full headcount approval | Full headcount approval |
Employer payroll liability (US) | No (if Indian EOR used) | No (if Indian EOR used) | No |
Conversion fee | 10 to 15% of annual base | N/A (direct hire fee paid upfront) | N/A |
IP ownership | Requires explicit assignment clause in contract | Standard employment agreement | Covered by EOR template |
IRS misclassification risk | High if no EOR structure | Low | Low |
Best for | Uncertain headcount, skill validation | Long-term critical roles | Scaling GCC or offshore team |
India talent cost (mid-level) | $28,000 to $42,000/year total | $35,000 to $50,000/year total | $33,000 to $48,000/year total |
US equivalent salary (mid-level) | $120,000 to $145,000/year | $120,000 to $145,000/year | $120,000 to $145,000/year |
One thing not on this table that only a recruiter knows: C2H engineers from India tend to perform better in the first 90 days than permanent hires at the same level, because they are aware they are being evaluated for conversion. We have tracked this pattern across 40+ US mandates over three years.
When conversion happens, the transition to remote contract hiring structures or full EOR permanent employment is handled by our compliance team, not left to the client to navigate alone.
How Does the C2H Hiring Process Work When Placing Engineers from India?
Our process for C2H (Contract-to-Hire) US IT staffing engagements runs in four structured phases. At AnjuSmriti Global Recruitment Solutions, we have refined this process across 200+ cross-border mandates to reduce time-to-hire and prevent the compliance gaps that derail most India-to-US contract placements.
Phase 1: Mandate Qualification (Days 1 to 3)
We document the role, stack, seniority level, client timezone expectations, and the conversion intent. If a client says they might convert but probably will not, we flag this as a potential IR35-adjacent risk and structure the contract accordingly. We also confirm the MSA conversion clause before sourcing begins.
Phase 2: Sourcing and Screening (Days 4 to 12)
For most US C2H roles, we shortlist from Bengaluru and Hyderabad first. We run an internal technical screen of 1 hour practical testing, a communication assessment using an async written response to a real scenario, and an IST-to-ET timezone simulation to confirm the engineer can maintain a 5-hour overlap window reliably.
Phase 3: Client Interviews and Offer (Days 13 to 18)
We schedule two rounds: a technical panel that is client-led and a culture and working-style call. We brief the engineer on US async norms before each round. The offer letter and contract are executed simultaneously with the EOR engagement letter.
Phase 4: Onboarding and 30-Day Check-In (Days 19 to 49)
We stay in the loop for the first 30 days. We have a weekly 15-minute check-in with both the engineer and the client-side manager. This prevents the silent misalignment that kills contract-to-hire arrangements at the 60-day mark.
The real engagement that tested us: A 150-person healthcare IT company in Nashville needed two Senior QA Automation Engineers for a C2H role covering Selenium, Java, API testing, and HIPAA-compliant environments. We placed both within 22 days. At day 45, one engineer disclosed that he had a competing offer from a Bengaluru-based company at a 30% salary premium. We had not built a competitive hold-back clause into the contract because the client had resisted it at signing.
We escalated immediately. The client agreed to an early conversion at month three instead of month six, with a revised compensation structure. The engineer stayed. The second engineer converted at month six as originally planned. Combined, the client saved approximately $67,000 against what two direct US hires would have cost. The QA hiring from India pipeline we built for that client is now a standing arrangement and they come back to us every quarter.
What Does C2H (Contract-to-Hire) Hiring from India Actually Cost a US IT Staffing?
Here are real cost figures for C2H (Contract-to-Hire) US IT staffing of Indian engineers:
Mid-Level Engineer (4 to 6 years experience)
India contract rate (all-in, EOR included): $28,000 to $38,000/year
Agency placement fee: $3,500 to $5,000 (one-time)
Conversion fee (if converted at 6 months): 12% of first-year Indian salary, approximately $3,360 to $4,560
Total Year 1 cost if converted: $34,860 to $47,560
US equivalent permanent hire: $130,000 to $145,000/year
Senior Engineer (7 to 10 years experience)
India contract rate (all-in, EOR included): $42,000 to $55,000/year
Agency placement fee: $5,000 to $7,500 (one-time)
Conversion fee (if converted): 12%, approximately $5,040 to $6,600
Total Year 1 cost if converted: $52,040 to $69,100
US equivalent permanent hire: $160,000 to $185,000/year
Lead / Architect (10+ years experience)
India contract rate (all-in, EOR included): $60,000 to $80,000/year
Agency placement fee: $8,000 to $12,000 (one-time)
Conversion fee (if converted): 12 to 15%, approximately $7,200 to $12,000
Total Year 1 cost if converted: $75,200 to $104,000
US equivalent permanent hire: $190,000 to $230,000/year
The savings US companies typically reinvest go most often into tooling such as Datadog, Snyk, and Grafana licenses, additional headcount at the junior level, or accelerating cloud migration timelines. We have seen clients use the savings to fund a second C2H position within the same fiscal quarter.
For companies managing global payroll outsourcing across multiple geographies, the predictability of a contract-to-hire model is an underrated advantage. The cost per engineer-month is fixed for the contract duration, with no variable benefits liability on the US side.
Conclusion
Over the next 12 to 18 months, we expect C2H (Contract-to-Hire) US IT staffing to grow as the dominant model for companies building distributed product teams with Indian engineers, particularly as more states outside California adopt contractor classification reforms modelled on AB5. The cost arbitrage remains significant, but the compliance complexity is growing in parallel. Companies that get this right are the ones who set up the EOR relationship and the MSA conversion clause before the first engineer joins, not after.
In our live mandates right now, we are seeing a sharp increase in contract-to-hire requests from US healthtech, fintech, and climate tech firms in roles covering data engineering, DevOps, and backend development that were previously perm-only. The shift is real and accelerating.
If your company is evaluating this model for scaling your India engineering team, start with a conversation before you start with a contract. We structure engagements differently depending on your entity setup, conversion intent, and the specific role, and getting that foundation right at the start is what prevents the expensive corrections later.
Interesting Reads:
FAQs
1. What is the difference between C2H and a standard contract role in US IT staffing?
A standard contract ends on the agreed date with no conversion option. C2H begins the same way, but both the company and the engineer enter with the shared understanding that a permanent offer may follow. The MSA spells out the contract duration, usually 3 to 12 months, the conversion fee, and the notice period. It gives the US company a structured trial window to assess technical fit and working style before committing to headcount, which is particularly useful when internal approvals are slow or the role scope is still evolving.
2. Does the IRS treat Indian engineers on C2H arrangements as US employees?
Not automatically, but the risk is real if the structure is wrong. The IRS applies a 20-factor common law test regardless of where the engineer is located. If the engineer works exclusively for one US client, follows client hours, uses client tools, and joins their sprints, the IRS will likely classify them as an employee. Without an Indian EOR acting as the legal employer, the US company could face back taxes and penalties. The correct structure is: Indian EOR as employer, US company as client, staffing agency managing the MSA and conversion terms.
3. How does California's AB5 law affect C2H hiring of Indian engineers for a California-registered company?
AB5 uses the ABC test for contractor classification. Under Prong B, the contractor must perform work outside the hiring company's core business to remain a contractor. A software engineer hired by a software company fails this test immediately. Without an EOR structure, California will treat that Indian engineer as a de facto employee of the California entity, triggering state payroll tax and workers' compensation obligations. The EOR structure resolves this because the legal employer is the Indian entity, not the California company.
4. What conversion fee should a US company expect to pay when converting a C2H engineer from India to permanent?
Conversion fees typically range from 10% to 15% of the engineer's first-year base salary, calculated on the Indian salary. For a mid-level engineer earning approximately $34,000 to $42,000 per year, the fee comes to roughly $3,400 to $6,300 paid once to the staffing agency. This must be documented in the MSA before the engagement begins. Our standard rate is a flat 12% with a 30-day conversion notice. Agencies sometimes reduce the fee for early conversions within the first 90 days.
5. Which US IT roles are most commonly filled through C2H hiring from India right now?
Based on our active mandates in mid-2025, the highest-demand C2H roles are Senior DevOps Engineers working with Kubernetes and Terraform, Data Engineers on Snowflake and dbt stacks, Backend Engineers in Java Spring Boot and Python FastAPI, QA Automation Engineers using Playwright and Selenium, and Cloud Architects across AWS and Azure. These roles suit C2H well because the skills are objectively testable during the contract window, and the cost of a permanent-hire mismatch at this seniority level is high enough to justify a structured trial period.
6. What timezone overlap can US companies realistically expect from Indian C2H engineers?
For US Eastern Time clients, Indian engineers can maintain a 5 to 6 hour overlap window by starting their day at 1:00 PM IST. For Pacific Time clients, this reduces to 3 to 4 hours. The rhythm we recommend is a standup call in the IST afternoon, focused async delivery during the overlap window, and an EOD update posted before the engineer signs off. Every C2H engineer we place is briefed on this structure before day one, and the timezone expectations are written into the statement of work.
7. How long does it typically take to place a C2H engineer from India for a US company?
Our standard timeline is 15 to 25 days end to end. Sourcing and internal screening takes 3 days. Client interviews across two rounds take 5 to 7 days. Offer and contract execution takes 2 to 3 days. EOR onboarding and IT access provisioning takes 5 to 7 days. The most common delay is client-side scheduling. US healthcare and fintech clients requiring India-specific background verification add another 5 to 7 days. When clients move quickly on the first shortlist, we have completed placements in under 14 days.
8. Can a C2H engineer from India travel to the US client's office during the contract period?
Yes, using a B-1 business visitor visa. Under B-1 status, the engineer can attend onboarding sessions, training, and collaborative meetings for up to 6 months per visit. They cannot perform independent productive work or receive US-source income. If the client wants the engineer to work from the US office on an ongoing basis, that requires an H-1B or L-1 visa, which is not practical for a short-term C2H arrangement. Most of our placements are fully remote, with travel used only for initial onboarding visits of 1 to 2 weeks.
9. What happens if the US company decides not to convert at the end of the C2H term?
The contract ends on the agreed date and no conversion fee is owed. The engineer returns to our active roster and is typically re-placed within 30 to 45 days, as US client experience makes them more competitive in the market. We build a 30-day end-of-contract notice clause into every C2H agreement so neither side is caught off guard. Non-conversion is not a failed placement. The trial period served its purpose, and the client avoided a permanent hire that was not the right fit.
10. Is C2H the right model if the US company already knows they want a permanent hire?
Not always. If headcount approval and budget are confirmed, going straight to a permanent EOR hire is faster and avoids the conversion fee entirely. C2H works best when approval is pending, the role is new with evolving scope, the company wants to validate the engineer before committing, or they are building a capability for the first time and need to test the model before scaling. If you already know you want permanent, we will tell you that upfront and recommend the more direct path.
Comments