.png)
Why Do US Startups Use Contract-to-Hire in India Before Making Permanent Hires?
Nearly seven out of ten US startup mandates we've run in the last few years start as a contract, not a permanent offer. Founders test an engineer for 60 to 90 days, then convert. We've seen this pattern hold across fintech, SaaS, and healthtech clients funded anywhere from seed to Series B. The reason is simple: setting up an Indian entity costs anywhere from $25,000 to $70,000 in legal, registration, and compliance fees before a single salary is paid. Most seed stage founders don't have that kind of runway to spend on infrastructure instead of product.
US startups use Contract-to-Hire in India before making permanent hires because it gives access to senior engineering talent within two to three weeks, lets them validate fit on a live sprint, and only commits them to payroll, benefits, and Indian labour law obligations once the engineer has proven themselves on real production work.
Why US Startups Use Contract-to-Hire in India Before Making Permanent Hires
US startups don't avoid permanent hiring because they distrust Indian engineers. They avoid it because a permanent hire in India, even through an EOR, locks the founder into notice periods, statutory bonus obligations, and gratuity liability the moment the offer letter is signed. For a startup burning $150,000 to $300,000 a month, a bad senior engineering hire that takes four months to unwind isn't a rounding error. It's a quarter of runway.
We see this most often with YC backed and seed funded companies in the Bay Area, Austin, and increasingly Miami, where founders are hiring their first two or three offshore engineers without an internal HR function. There's no recruiter to vet a resume, no legal counsel on retainer to review an Indian employment contract, and no bandwidth to manage a termination if the hire doesn't work out. Contract-to-hire pushes the hardest decision, permanent commitment, to the point where the founder has evidence, not just a resume and two interviews.
Current hiring data reflects a broader shift too. Demand for AI engineers, cloud specialists, and DevOps professionals in India has grown well ahead of general IT staffing, and a meaningful share of that growth is coming from US companies under 50 employees rather than the large enterprises that used to dominate offshore contracting.
Bengaluru and Pune based engineers who once only considered full time roles at Indian product companies are now actively seeking short term US contract engagements, since dollar denominated contract pay often beats an equivalent Indian permanent salary by 30 to 40%. At AnjuSmriti Global, we've watched this shift make contract-to-hire workable in a way it simply wasn't for founders a few hiring cycles ago, because the supply side wants this model too.
What Contract Hiring Actually Means for a US Startup
Contract hiring, in plain terms, means engaging an Indian engineer for a fixed term, usually 90 days, through a legal employer structure such as an EOR, rather than putting them on your own payroll from day one. The engineer works your sprints, joins your standups, and uses your tools, but the statutory employment relationship sits with the EOR until you decide to convert them.
For founders, this translates into three practical advantages: faster hiring, since you skip entity setup and payroll registration entirely; access to specialized skills without a long term commitment, useful when you need a DevOps lead or an AI engineer for a defined project rather than a permanent seat; and the flexibility to end the engagement cleanly if the fit isn't right.
In the $30 to $50 per hour range, companies can hire almost any type of technology candidate, including DevOps professionals, AI engineers, data scientists, cybersecurity specialists, SAP consultants, and other niche technology experts. That budget band is what makes contract hiring realistic for a startup evaluating a role for the first time, rather than reserved for enterprises with large offshore budgets.
Which Indian Cities Have the Right Talent for This Model
Bengaluru remains the deepest pool for contract-to-hire specifically, not because the raw talent is better than Hyderabad or Pune, but because Bangalore's contract and freelance culture is more mature. Many engineers there have already done short stints with US clients through platforms or direct contracts. That familiarity matters: an engineer who has never worked outside a fixed Indian office schedule often struggles with asynchronous, deliverable based work in the first month.
An engineer who's already billed hourly or by sprint to a US client adapts within days.
Pune is close behind, particularly for full stack and backend roles tied to fintech and healthtech, with a strong base of engineers from mid size product companies who are comfortable with US compliance heavy codebases. Hyderabad is strongest for cloud and data heavy contract roles because of its GCC density, though Hyderabad engineers tend to be slightly more oriented toward permanent employment structures, worth knowing if you're building a GCC rather than a lean contract pod.
What Indian engineers reliably bring: strong fundamentals in React, Node, Python, and increasingly Go; genuine comfort with AWS and GCP at mid to senior level; and real discipline around documentation, a habit carried over from outsourced and GCC environments. What they typically lack, and what we test for specifically, is ownership without a manager in the room. Our technical screening for contract-to-hire roles includes a live, ungoverned build task with no clarifying questions allowed after the first few minutes. It's a blunt but effective filter for who can operate under startup level ambiguity.
Contract Hiring and Indian Labour Law: What US Founders Get Wrong
The biggest compliance mistake we see is founders treating a contract-to-hire engineer as a 1099 style freelancer under US logic, when Indian law doesn't map cleanly onto that category. If an Indian engineer works exclusively for your startup, on your schedule, using your tools, for more than a few months, Indian authorities can reclassify that relationship as employment regardless of the contract's wording, triggering retroactive liability for provident fund contributions, gratuity, and statutory bonus.
The relevant law here is the Contract Labour (Regulation and Abolition) Act, 1970, which governs how contract workers can legally be engaged in India, alongside state level Shops and Establishment Act registrations that apply once you cross certain headcount or duration thresholds. Most US founders have never heard of either until we raise it on the first onboarding call.
The clean way to handle this, and the reason most of our US startup clients don't set up an Indian entity at all, is to run the contract phase through an employer of record structure. The EOR is the legal employer in India during the contract window, handles payroll and statutory withholdings correctly from day one, and executes the permanent conversion or clean exit once the founder decides. This also resolves the IP assignment question that trips up almost every first time founder: without a properly worded EOR or contract hiring agreement, code written by an Indian contractor may not automatically vest IP in the US company, since Indian default copyright rules differ from US work for hire assumptions.
Contract-to-Hire vs Freelance vs Direct Permanent: A Founder's Comparison
Freelance | Contract-to-Hire (EOR) | Direct Permanent Hire | |
Time to start | 3 to 5 days | 2 to 3 weeks | 4 to 6 weeks |
Legal employer | No one, misclassification risk | EOR in India | EOR or your own entity |
IP assignment | Often unclear | Written into EOR contract | Written into employment contract |
Exit if it doesn't work | Immediate, no cost | End of term, minimal cost | Notice period plus gratuity |
Statutory compliance | None, your risk | Handled by EOR | Handled by EOR or entity |
Typical hourly range | $20 to $40 | $30 to $50 | Salary based, higher effective rate |
Best for | One off tasks under 4 weeks | First hire in a new role or market | Proven team, scaling headcount |
The choice most founders wrestle with is between column two and column three. Our rule of thumb: if this is your first hire for a given skill set, your first DevOps engineer, your first AI engineer, start with contract-to-hire. If you're hiring your fourth backend engineer onto a team you already trust, direct permanent hiring is usually faster and cheaper.
Our Process and a Real Client Scenario
Our contract-to-hire timeline runs on a fixed cadence: sourcing and shortlist in 5 to 7 business days, technical screening including the ungoverned build task in days 8 to 10, founder or CTO interview in days 11 to 14, and contract start by week three. The term itself is almost always 90 days, with a conversion clause letting the founder move to permanent at day 60 if they already know, or let the full term run.
One scenario from a recent mandate: a Series A fintech client, roughly 40 employees, needed a senior backend engineer to own their payments reconciliation service, a system where a bug doesn't just create a support ticket, it creates a financial discrepancy. We placed a Pune based engineer on a 90 day contract through our EOR structure. Around week six, it almost went wrong: the engineer, coming from a large GCC background, had never worked without a staging environment gatekeeper, and pushed a schema change directly that briefly broke a downstream reconciliation job.
We flagged it in our biweekly check in, the founder's team caught it within the hour before it hit production numbers, and we used it as a coaching moment rather than a termination trigger. By day 90, the engineer had rebuilt the reconciliation pipeline with proper safeguards, the founder converted him to permanent, and total time from first sourcing call to permanent offer was 94 days, against the 5 to 6 months a direct entity based hire would have taken.
What Contract Hiring Costs in India
For a mid level backend or full stack engineer with 3 to 5 years experience, contract rates typically run $2,800 to $4,200 per month all in, including our agency fee and the EOR's statutory contributions. Senior engineers with 6 to 9 years run $4,500 to $6,800 per month. Lead level engineers or specialists such as DevOps architects and AI leads with 10+ years run $7,000 to $10,500 per month.
Compare that to a US based equivalent: a senior backend engineer in the Bay Area typically costs $170,000 to $210,000 in base salary alone before benefits and payroll tax, working out to roughly $14,000 to $17,500 per month fully loaded.
The all in cost breaks down as base contractor compensation at 70 to 75% of the total, EOR statutory contributions covering provident fund and gratuity accrual at 10 to 12%, and our placement and management fee, typically 15 to 18% of contract value, reducing once the engineer converts to permanent. Founders who run the numbers usually reinvest the savings into one of two places: extending runway by three to four months, or hiring a second Indian engineer instead of a single US based one for the same budget.
Conclusion
Over the next several hiring cycles, we expect more US seed and Series A startups to skip permanent hiring entirely for their first two or three Indian engineers, treating contract-to-hire as the default rather than a cautious first step. In live mandates right now, we're seeing founders ask for shorter screening calls and faster contract starts, especially for AI and cloud roles, than they did even a year ago. Speed has become as important as the hiring decision itself.
The pattern is consistent: US startups use Contract-to-Hire in India before making permanent hires because it converts a hiring decision into a tested outcome, not a bet. If you're evaluating your first India hire and want a walkthrough of what a 90 day contract-to-hire timeline would look like for your specific role, start here.
Interesting Reads:
FAQs
1.Does the Contract Labour Act apply if my startup has no Indian entity?
Yes, indirectly. The Act governs how contract labour is engaged through a principal employer and a contractor, in this case the EOR. Even without your own entity, the EOR must be properly registered and compliant, and your startup is still considered the principal employer for oversight purposes in a dispute.
2.Can I convert a contractor to permanent without restarting the hiring process?
Yes. A well structured contract includes a conversion clause from day one, so moving to permanent status is a documentation exercise, not a fresh recruitment cycle. Most clients convert between day 60 and day 90, with no re-interviewing or re-sourcing required at any point.
3.What happens to IP ownership if I don't convert the contractor?
A properly drafted contract-to-hire agreement assigns IP to your company regardless of conversion. If the contract is silent on this or copied from a generic freelance template, code and architecture created during the contract may sit in a legal grey zone. We insist on explicit IP language upfront.
4.Why do Indian engineers accept 90 day contracts instead of demanding permanent offers?
Compensation drives this. A dollar denominated 90 day contract in the $30 to $50 per hour range often exceeds equivalent Indian permanent pay, even before conversion. The EOR structure also guarantees statutory benefits during the term, which pure freelance arrangements don't offer.
5.How do stock options work for a contractor before conversion?
They generally don't. US equity plans are structured for employees, and issuing equity to a contractor employed through an Indian EOR creates tax and securities complications on both sides. Most clients defer equity conversations until permanent conversion and are transparent about this from the first interview.
6.Is 90 days a standard term, or can it be shorter?
90 days is our standard because it covers at least one full sprint cycle plus a production incident or two, the real tests of independent operation. Shorter terms of 30 to 45 days work for narrowly scoped project tasks, but we advise against them for evaluating a first hire in a new role.
7.What's the most common reason a contract fails to convert?
Timezone friction that wasn't addressed early, more often than skill gaps. Engineers hired without a clear overlap agreement end up working late nights indefinitely, leading to burnout right around conversion time. We now build a mandatory daily overlap window into every contract from day one.
8.Can I run contract-to-hire for a whole small team, not just one engineer?
Yes, and it's increasingly common for founders building their first offshore pod. We stagger start dates by one to two weeks so screening doesn't hit the founder all at once. For teams of five or more, this starts to resemble bulk hiring with improved EOR fee structures at volume.
Comments