.png)
How to Hire for Contract/C2H roles all over the market?
- Saransh Garg
- May 20
- 13 min read
A mid-level software engineer in the US costs between $110,000 and $140,000 per year in base salary alone, before you add employer FICA contributions (7.65%), health benefits ($6,000 to $12,000 annually), PTO liability, and recruiter fees that typically run 18 to 22% of first-year compensation. A bad permanent hire at that level costs US companies an average of $30,000 to $50,000 in lost productivity, re-hiring costs, and onboarding time, according to SHRM benchmarks our clients regularly cite in intake calls.
This is exactly why more companies are choosing to hire for Contract/C2H roles developers India USA, not as a cost play alone, but as a risk-reduction strategy. The C2H model lets you evaluate an engineer across two to three months of real sprint work before committing to a permanent offer. When that engineer is based in India and placed through an Employer of Record, the financial exposure during the trial period drops by 60 to 70% compared to a direct US hire.
When companies hire contract to hire developers India USA for the first time, the most common question we hear is not about cost. It is about quality control and legal exposure. Both are solvable, and this article walks through exactly how.
Why US Tech Teams Are Exhausted by Direct Permanent Hiring
The US tech hiring market has been volatile. After the mass layoffs at large tech firms, mid-size product companies and GCC-style captive units found themselves in a paradox: budgets were tighter, but engineering backlogs had not shrunk. Headcount approvals for permanent roles were slower, sometimes requiring two rounds of board sign-off, while project timelines did not move.
We saw this pattern repeatedly in our mandates. A 200-person SaaS company in Austin would come to us needing three senior backend engineers. Their internal HR had the permanent headcount frozen for Q1 but had budget for contractors. The C2H model became the bridge: bring engineers in on contract, run them through real delivery cycles, convert the performers to full-time once headcount opened up.
The demand is concentrated in specific stacks. Across our US client base, the highest C2H demand currently sits in:
Java/Spring Boot and microservices, especially for fintech and insurtech platforms
DevOps and Kubernetes, for companies scaling cloud infrastructure without committing to senior SRE salaries immediately
React/Node full-stack, for product companies building new modules with uncertain long-term roadmaps
Data engineering (Spark, Airflow, dbt), for analytics teams that need short bursts of pipeline build work
The cities driving this demand on the client side are Austin, Seattle, Atlanta, and the New York metro, all of which have high permanent engineering salaries that make the C2H model from India especially attractive from a budget perspective. Our offshore staffing practice sees the highest inbound volume from these four metros.
Which Indian Cities Produce to Hire for Contract/C2H roles
Not every Indian city is equally suited for every US client's C2H need. Here is what our sourcing data shows across four years of US mandates.
Bengaluru remains the deepest pool for product-company stacks, including React, Node, Python, and cloud-native engineering. Engineers here are accustomed to agile sprint culture and have often worked directly with US product managers in previous roles, which reduces the onboarding friction significantly. The Bengaluru talent market for mid-to-senior engineers is competitive, but our embedded sourcing team gives us access to passive candidates who are not on Naukri or LinkedIn.
Hyderabad is the strongest city for Java enterprise, SAP-adjacent engineering, and data engineering profiles. Several large GCCs in Hyderabad have trained engineers in US-aligned delivery models, which means C2H candidates from this city tend to need less process onboarding.
Pune is underrated for DevOps and QA automation profiles. The city has a high concentration of engineers who have worked with European and US clients in time-and-material models, which maps naturally to C2H contract structures. Our Pune hiring network regularly surfaces strong Terraform, Ansible, and GitHub Actions profiles that are not visible on public job boards.
What Indian engineers typically lack for US C2H roles, and how we test for it:
The gap we see most often is not technical. Indian engineers coming into US C2H roles frequently underestimate the expectation around proactive communication, specifically flagging blockers before they become delays, writing detailed async updates, and pushing back on ambiguous requirements. US product managers expect engineers to behave like owners of a feature, not executors of a ticket.
Our vetting process includes a 45-minute behavioural scenario round specifically designed around this. We present candidates with three realistic situations: a broken CI pipeline two days before a release, a conflicting requirement from two stakeholders, and a missed sprint commitment. We evaluate how they communicate, not just what they would technically do. Engineers who cannot narrate their decision-making in plain English, regardless of technical strength, do not pass our shortlist.
The Legal and Compliance Reality When You Hire Contract to Hire Developers India USA
The primary US law governing worker classification is IRS Revenue Ruling 87-41, which sets out 20 factors used to determine whether a worker is an independent contractor or an employee. For C2H arrangements where an Indian engineer is working full-time on your product, embedded in your sprint cycles, using your tools, and reporting to your engineering manager, the IRS classification risk of treating that person as a pure independent contractor is real.
The cleaner legal path, which we always recommend to our US clients, is to place the Indian engineer through an Employer of Record (EOR) in India. Under this structure, the engineer is legally employed by the EOR entity in India, which handles Indian payroll, PF contributions (12% of basic salary), professional tax, and statutory compliance under the Indian Contract Labour (Regulation and Abolition) Act, 1970. The US company receives the engineer's services through a B2B services agreement with the EOR, which keeps the worker firmly outside the scope of IRS 87-41 misclassification risk.
The mistake we see most often: US companies try to pay Indian C2H contractors directly as "foreign freelancers" via Wise or PayPal, without an EOR or local employment structure. This creates dual exposure, potential misclassification liability in the US and non-compliance with Indian labour law, specifically the requirement that contractors working more than 240 days in a year must be treated as permanent employees under Indian statute.
Our EOR service covers the full India-side employment structure, and our team advises US clients on the B2B services agreement language that protects them on the US side.
One more compliance point specific to C2H: when the conversion from contract to permanent happens, the US company must decide whether to hire the engineer into a US W-2 role (requiring visa sponsorship or remote permanent employment) or keep them permanently employed in India through the EOR on a full-time basis. The conversion structure needs to be agreed before the contract starts, not after the engineer has delivered for three months and both sides want to move quickly.
C2H Hiring Checklist for US Companies Bringing On Indian Engineers
This checklist covers the complete process from mandate to conversion.
Stage | Action | Owner | Timeline |
1. Role Definition | Finalise JD with stack, seniority, and US timezone overlap requirement (IST+10.5hrs to EST) | Hiring Manager | Week 1 |
2. Legal Structure | Decide: EOR-in-India vs direct contractor. Confirm IRS classification posture with legal counsel | HR + Legal | Week 1 |
3. Contract Terms | Set C2H duration (typically 3 to 6 months), conversion trigger, notice period, IP assignment clause | HR | Week 1 |
4. Agency Brief | Share full JD, tech stack, behavioural expectations, and conversion intent with recruitment partner | HR | Week 1 to 2 |
5. Sourcing | Recruitment partner sources, screens, and presents 4 to 6 profiles with technical vetting notes | Recruiter | Week 2 to 3 |
6. Client Interviews | 2-round interview: technical (CTO/tech lead) and cultural fit (HR/engineering manager) | Client + Recruiter | Week 3 to 4 |
7. Offer and Onboarding | EOR issues employment contract in India; US company signs B2B services agreement | EOR + HR | Week 4 to 5 |
8. Ramp Period | Engineer joins sprint, completes onboarding, IST to EST overlap agreed (typically 6 to 8 hrs/day) | Engineering Manager | Week 5 to 8 |
9. Mid-Contract Review | Formal performance check at 45 days. Flag conversion intent or extend contract | HR + Manager | Day 45 |
10. Conversion Decision | Convert to India-based permanent EOR employee or initiate US visa/remote permanent employment | HR + Legal | End of C2H term |
The IST-to-EST timezone overlap deserves a specific note. Eastern Standard Time is 10.5 hours behind IST. A US team working 9am to 6pm EST overlaps with an India engineer working 7:30pm to 12:30am IST, which is unsustainable long-term. Our clients who have the best retention on converted C2H engineers set a working window of 12pm to 9pm IST, which gives 4.5 hours of live overlap with the US east coast morning. Engineers who agree to this window upfront have a 3x higher conversion acceptance rate in our data.
A Real C2H Mandate: What Happened, What Almost Broke, and the Outcome
This is where we want to share how AnjuSmriti Global has handled a real US C2H engagement from start to conversion, including the part that almost derailed it.
Client: A 150-person insurtech platform company headquartered in Atlanta, Georgia. Series B funded, building a claims automation product on Java/Spring Boot and AWS.
The problem: They needed three senior Java engineers urgently. Permanent headcount was frozen pending a Series C close. Their internal recruiter had been running the search for 11 weeks with zero hires. US-based Java engineers at senior level were quoting $135,000 to $145,000 base, and the client's band was $120,000. The gap was unbridgeable without board approval.
What we did: We proposed a C2H structure with engineers based in Hyderabad, employed through our EOR, at a total delivered cost of $38,000 to $42,000 per engineer annually, inclusive of EOR fee and our placement fee. The client's legal team reviewed the B2B services agreement and approved it within five days.
We ran a targeted search across Hyderabad's Java developer network and presented six profiles within nine days. All six had prior US client-facing experience. Three were selected after two interview rounds.
What almost went wrong: During onboarding, the client's engineering manager assumed the Indian engineers would work US hours (9am to 5pm EST) full-time, which would have meant 10:30pm to 6:30am IST. Two of the three engineers raised this in week one. We intervened immediately, proposed the 12pm to 9pm IST window, and renegotiated the daily standup to 8:30pm IST (10am EST). The manager initially pushed back but agreed after we shared retention data from previous mandates.
Outcome: All three engineers completed their 4-month C2H term. Two were converted to permanent India-based EOR employees. The third declined conversion after receiving a local Hyderabad offer, but by that point the client had already built enough pipeline of profiles that they replaced her within three weeks. Total saving versus hiring three US-based engineers at market rate: approximately $267,000 in year-one compensation costs alone.
The ability to hire contract to hire developers India USA through a structured EOR process, rather than a direct contractor arrangement, was what made this engagement legally clean and repeatable for the client.
What It Actually Costs: Salary Figures and Total Employer Cost
All figures below are in USD, reflecting the total cost to a US company engaging Indian engineers through an EOR on a C2H basis. Indian engineer compensation is in INR converted at prevailing rates and structured as CTC (Cost to Company).
Seniority | Indian Engineer CTC (INR/year) | Equivalent USD | EOR Fee (est.) | Agency Fee (one-time) | Total Year-1 Cost (USD) | Comparable US Hire (USD) |
Mid-level (3 to 5 yrs) | Rs.18 to 22 LPA | $21,500 to $26,500 | $4,800 | $5,000 | $31,300 to $36,300 | $110,000 to $125,000 |
Senior (6 to 9 yrs) | Rs.28 to 36 LPA | $33,500 to $43,000 | $5,500 | $7,000 | $46,000 to $55,500 | $130,000 to $150,000 |
Lead/Architect (10+ yrs) | Rs.42 to 55 LPA | $50,000 to $65,500 | $6,500 | $9,000 | $65,500 to $81,000 | $155,000 to $185,000 |
EOR fee is an estimate based on standard India EOR pricing. Agency fee is a one-time placement fee, not recurring. US hire figures include base salary, FICA, and average benefits with no bonus.
What do our clients typically reinvest these savings into? The most common answer we hear: additional engineering headcount, expanding from 3 C2H engineers to 5 within 12 months, product infrastructure spend on AWS or Azure, and QA automation capacity, specifically certified QA engineers from India who run parallel test cycles during the US team's off-hours.
For any US company looking to hire contract to hire developers India USA at scale, the total year-one cost difference between the India C2H model and direct US hiring is not marginal. At senior level, you are looking at a saving of $75,000 to $95,000 per engineer in year one alone.
Conclusion
The C2H model for US companies hiring Indian engineers is maturing fast. What started as a cost workaround is now a deliberate talent strategy for Series B and Series C companies that need engineering capacity without the permanent headcount risk. Over the next 12 to 18 months, we expect C2H-to-permanent conversion rates to increase as more US companies build India-based permanent engineering teams following successful contract engagements, essentially using C2H as a structured trial before a GCC-style setup.
In our live mandates right now, we are seeing a sharp increase in US fintech and healthtech clients asking specifically to hire contract to hire developers India USA with a built-in 6-month conversion window and a pre-agreed permanent salary band, which tells us the market is getting more deliberate and less reactive about this model.
If you are an HR manager at a US tech company evaluating this model for the first time, start with one role. One engineer, one sprint cycle, one honest performance review at 45 days. That is all it takes to know whether this works for your team.
Interesting Reads:
FAQs
1. Does IRS Revenue Ruling 87-41 apply to Indian engineers working remotely for a US company on a C2H basis?
Yes. IRS Revenue Ruling 87-41 is highly relevant when US companies engage Indian engineers under a contract-to-hire structure. The ruling outlines 20 behavioural and financial control factors used to determine whether a worker should legally be classified as an employee or an independent contractor. If an Indian engineer follows fixed working hours, uses company systems, participates in internal sprint planning, and reports directly to US managers, the arrangement may resemble employment rather than independent contracting. To reduce compliance and misclassification risk, many US companies engage engineers through an Indian Employer of Record (EOR) structure supported by a formal business-to-business services agreement.
2. What is a realistic C2H contract duration for Indian engineers hired by US companies?
A practical C2H engagement for Indian engineers typically ranges between three and six months. Three months generally allows enough time for the client to evaluate technical delivery, communication habits, and team collaboration across multiple sprint cycles. Six-month contracts are more suitable for senior engineers, architects, or lead-level hires where leadership and long-term contribution need deeper assessment. Extending a contract indefinitely without a defined conversion discussion can create uncertainty and increase the likelihood of attrition. Many companies include a formal conversion checkpoint midway through the engagement so both the client and engineer have clarity regarding long-term employment expectations and transition timelines.
3. How does the IST to US Eastern Time timezone gap affect C2H productivity, and how do companies manage it?
The timezone difference between India Standard Time and US Eastern Time creates operational challenges if schedules are not planned carefully. A traditional US workday overlaps with late evening and overnight hours in India, which can become unsustainable over long periods. Successful remote teams typically establish structured overlap windows that allow four to five hours of live collaboration daily. Indian engineers may work shifted schedules that align with US morning meetings while preserving flexibility for asynchronous development work. Companies usually define timezone expectations during hiring to ensure candidates are comfortable with the required overlap before the engagement officially begins.
4. What happens to IP ownership during a C2H engagement with an Indian engineer?
Intellectual property ownership during a C2H engagement is usually governed through two separate agreements. The first is the services agreement between the US company and the Indian EOR or staffing partner. The second is the employment agreement signed by the engineer locally in India. These agreements typically contain aligned IP assignment and confidentiality clauses stating that all work products, code, documentation, and deliverables created during the engagement belong to the client company. Proper alignment between both contracts is important because unclear wording can create disputes regarding ownership rights, especially when software products or proprietary systems are involved across international jurisdictions.
5. Which Indian cities have the strongest talent pool for Java and cloud engineering roles?
Bengaluru, Hyderabad, Pune, and Chennai are among the strongest Indian cities for sourcing Java and cloud engineering talent for US companies. Hyderabad has a particularly strong ecosystem for Java microservices and Spring Boot development due to the concentration of global capability centers and enterprise technology firms. Bengaluru remains the largest overall technology market with deep expertise across AWS, Azure, GCP, DevOps, and platform engineering. Pune offers strong senior engineering talent with comparatively lower compensation bands in some cases. Chennai also provides quality Java talent, although engineers there may sometimes prefer clients operating within European-friendly timezone overlaps.
6. Can a US company convert an Indian C2H engineer to permanent employment without opening an India entity?
Yes. Many US companies convert Indian C2H engineers into permanent remote employees without establishing a legal entity in India. This is commonly done through an Employer of Record (EOR) arrangement, where the EOR becomes the official local employer responsible for payroll, tax deductions, statutory compliance, provident fund contributions, and employment documentation. The US company continues managing the engineer operationally while paying the EOR a monthly fee covering salary and compliance costs. This structure allows companies to maintain a compliant long-term employment setup in India without handling local registrations, labor law administration, or direct employer obligations themselves.
7. What technical vetting is typically conducted before presenting C2H candidates to US clients?
Technical vetting for C2H engineering roles usually involves multiple evaluation stages before a candidate reaches the client interview process. Initial recruiter screenings focus on employment history, remote work experience, communication skills, and familiarity with US-based collaboration environments. Technical interviews are then conducted by experienced engineers who assess stack-specific expertise, coding ability, architecture knowledge, debugging skills, and system design understanding. Many agencies also conduct behavioural and communication assessments to evaluate async collaboration habits and problem escalation practices. This layered approach helps ensure that shortlisted engineers can meet both the technical and communication standards expected by US companies.
8. How does the C2H model compare to a full RPO engagement for hiring Indian engineers?
C2H and RPO models serve different hiring objectives for US companies building teams in India. Contract-to-hire works best when hiring volume is relatively low and companies want flexibility to evaluate engineers before making permanent commitments. Recruitment Process Outsourcing (RPO), by contrast, is designed for larger-scale hiring where a dedicated recruitment function supports ongoing growth. RPO engagements often become cost-efficient once hiring volumes increase significantly across multiple engineering roles. Many companies begin with C2H to validate hiring quality and operational workflows before transitioning to an RPO structure as their India-based engineering organization expands over time.
9. What notice periods should US companies expect from Indian C2H engineers?
Indian engineers commonly serve notice periods ranging from 30 days at mid-level positions to 60 or 90 days for senior and leadership roles. These timelines can significantly affect hiring schedules for US companies expecting immediate onboarding. Notice periods are especially important in competitive markets such as Bengaluru and Hyderabad, where experienced engineers often work for established product or enterprise companies with strict exit policies. Some employers allow partial or full notice period buyouts, enabling faster joining timelines if the hiring company is willing to cover the associated cost. Clear discussion of notice obligations early in the hiring process helps avoid timeline mismatches later.
10. Is there a risk that a high-performing C2H engineer may decline permanent conversion?
Yes. Some high-performing engineers choose not to convert into permanent roles after a C2H engagement concludes. Common reasons include receiving competing offers, dissatisfaction with the proposed compensation package, or preference for the flexibility associated with contract-based work. Companies can reduce this risk by communicating conversion intent early, maintaining regular engagement throughout the contract period, and offering a competitive salary increase at the time of conversion. Even when a conversion does not happen, the C2H model can still provide significant value by allowing companies to complete critical project work while assessing long-term fit before making permanent hiring decisions.
Comments