.png)
Why Employers are Choosing the C2H (Contract to Hire) Route?
- Saransh Garg
- 22 hours ago
- 12 min read
A bad permanent hire in a mid-senior tech role costs between ₹8 lakh and ₹22 lakh when you account for the recruitment fee, the notice period served, the salary paid during underperformance, and the cost of restarting the search. We know this number because we have been called in to fix these situations repeatedly, across sectors, at companies ranging from 40-person startups to 4,000-person GCCs.
The C2H (Contract to Hire) model exists as a structured answer to this problem. An employer brings a professional on a fixed-term contract, typically three to twelve months, evaluates real delivery in a real work environment, and then converts to permanent employment with genuine evidence rather than interview-room impressions. Employers choosing the C2H contract to hire route are not cutting corners on hiring.
What Is Driving Employers to Choose the C2H Contract to Hire Route Over Permanent Hiring?
Permanent hiring works well when the role is stable, the skills are easy to verify, and the market moves slowly.
Consider what a typical IT hiring cycle looks like in practice. A company raises a requisition. HR writes a job description that is either too broad to attract more candidates or too narrow because it was copied from a previous hire who no longer represents the role. The position sits open for 45 to 90 days. Three to five interviews happen, most of which test how well someone presents rather than how well they build. An offer is made. The candidate negotiates, accepts, and joins, only for the engineering manager to discover in week six that the candidate's hands-on Kubernetes experience was actually supervisory, not operational.
This is not a hypothetical. It is the single most common technical mismatch pattern we see across IT hiring mandates: candidates who have managed teams doing the work rather than doing the work themselves, and interview processes that never surfaced the gap. The C2H structure eliminates this problem structurally. The engineer is on a sprint. The manager sees actual pull requests, actual incident responses, actual architecture decisions. By month three, the hiring manager has more reliable information about the candidate's ability than twelve rounds of interviews could produce.
There is also a market-side pressure driving this shift. In high-demand tech markets such as Bengaluru, Hyderabad, Pune, and increasingly Noida, strong senior engineers receive multiple permanent offers simultaneously. Many of them are open to contract roles precisely because a C2H arrangement gives them a trial period too. They are evaluating the company's engineering culture, management quality, and growth path before they commit. C2H has become a two-way due diligence mechanism, and companies that understand this use it as a talent attraction tool, not just a risk management tool.
Global companies building teams through offshore recruitment find C2H especially valuable because the cost of a wrong permanent hire is amplified by cross-border complexity. Termination procedures, notice periods, and rehiring timelines all take longer when the engineer is in a different country.
Which Tech Roles and Indian Cities Are Best Suited for C2H Contract to Hire Hiring?
Not every role is equally suited to C2H. The model works best where performance is objectively observable within three to six months and where the cost of a wrong permanent hire is high relative to the contract premium.
Best-fit roles for C2H:
Full Stack engineers, DevOps and cloud engineers, data scientists and ML engineers, QA automation engineers, and technical leads where the gap between a strong and a weak hire is extremely visible in delivery outcomes.
Roles where C2H is less effective:
Engineering managers, architects whose value is strategic and long-cycle, and roles where onboarding itself takes more than three months to complete. In these cases, you are evaluating ramp-up performance rather than steady-state performance, which is a different and less reliable signal.
City-level talent depth for C2H sourcing:
Bengaluru has the deepest pool for product-focused Full Stack, DevOps, and AI/ML roles. Engineers here are accustomed to fast-release environments and contract engagements are culturally normalised.
Hyderabad is strongest for enterprise IT including SAP, Java, Azure, and cloud migration roles. The GCC ecosystem here means engineers often have prior experience with global clients, which shortens onboarding time considerably.
Pune is the most reliable source for engineers with European client exposure, which is useful when the C2H role involves working directly with European stakeholders. Communication quality and time-zone adaptability are consistently higher here for cross-border roles.
What Indian engineers across all cities typically need for C2H roles going to global clients is explicit preparation on direct communication, client-facing status reporting, and pushing back on requirements. These behaviours are often trained out of engineers in traditional IT services delivery models. We address this in candidate preparation before every contract start.
What Indian Employment Laws Apply When Employers Choose the C2H Contract to Hire Route?
The employment law framework governing C2H in India sits primarily under the Contract Labour (Regulation and Abolition) Act, 1970 and, for companies with contractual arrangements, under the Code on Social Security, 2020, which is one of four labour codes consolidating India's previous 44 central labour laws.
For employers choosing the C2H contract to hire route with Indian talent, the critical legal distinction is between a fixed-term employment contract and a contract labour arrangement. Under the Industrial Relations Code, 2020, fixed-term employment is explicitly recognised as a legitimate employment category. A fixed-term employee is entitled to all statutory benefits including PF, ESIC, and gratuity proportional to tenure from Day 1, not from the conversion date.
The most common mistake we see is companies treating C2H engineers as independent contractors or freelancers to avoid statutory contributions. This creates two problems. First, if the engineer works exclusively for one company, follows a defined schedule, and uses company tools, the arrangement can be reclassified as employment by a labour tribunal, exposing the company to backdated PF and ESIC liability. Second, good engineers refuse these arrangements. Senior Full Stack and DevOps engineers in Bengaluru and Hyderabad know their rights, and a contract that withholds PF contributions signals a company that cuts corners on compliance.
The clean structure is a fixed-term employment contract, either directly with the hiring company or through an Employer of Record (EOR), with all statutory contributions paid from Day 1. When the conversion to permanent employment occurs, the fixed-term contract transitions to a permanent contract, typically with a two to four week notice period gap during which the new permanent terms are documented.
For global companies hiring Indian engineers on C2H through our contractual hiring model, the EOR handles all statutory compliance, leaving the client company to focus entirely on delivery and the conversion decision.
What Should Employers Verify Before Starting a C2H Contract to Hire Engagement?
This checklist is what we share with every new client before sourcing begins for a C2H mandate. HR managers should be able to answer yes to all ten items before a contract is signed.
# | Checkpoint | Why It Matters |
1 | Fixed-term employment contract drafted, not a freelance agreement | Avoids misclassification under Industrial Relations Code 2020 |
2 | Statutory contributions (PF, ESIC) confirmed from Day 1 | Legal requirement for fixed-term employees, non-negotiable |
3 | Contract duration defined: 3, 6, 9, or 12 months | Determines performance evaluation milestone and conversion trigger |
4 | Conversion criteria documented in writing | Defines what "pass" looks like, including delivery metrics and manager sign-off |
5 | Conversion salary band pre-agreed | Prevents renegotiation at conversion point from derailing a good hire |
6 | IP assignment clause included | All code and work product must be explicitly assigned to the company |
7 | Notice period for non-conversion agreed | Protects both parties if the conversion decision is negative |
8 | Performance review checkpoint at midpoint of contract | Enables early intervention if trajectory is wrong |
9 | Engineering manager briefed and owns the evaluation | HR administers; engineering manager decides. This boundary must be clear |
10 | Competing offer risk assessed at offer stage | Senior engineers on C2H contracts receive counter-offers. Pre-empt this early |
Items 4 and 5, which are the documented conversion criteria and the pre-agreed salary band, are the ones most often skipped. Both create expensive disputes at the back end. We have seen companies lose strong C2H engineers at the conversion point because the salary band discussion started from scratch at month nine, creating a perception of bad faith in the engineer's mind.
How Does AnjuSmriti Global Manage C2H Mandates and What Can Go Wrong?
Our company Anjusmriti Global manage C2H process runs in four stages with defined timelines.
Stage 1: Role Architecture (Days 1 to 3)
We do not take a job description at face value. We run a structured brief with the engineering manager to understand the actual delivery problem the hire needs to solve, the current team's gap, and what the performance evaluation criteria will be at month three and month six. For one recent mandate, this brief revealed the client needed a DevOps engineer who could own incident response independently. The job description had said "support the DevOps team," which would have attracted a completely different profile.
Stage 2: Sourcing and Screening (Days 4 to 14)
We draw from our internal database first, then run targeted outreach. For C2H roles, we specifically target engineers who have successfully converted from contract to permanent in a previous engagement. This is a strong predictor of C2H success. We screen 35 to 50 profiles to present four to six shortlisted candidates.
Stage 3: Client Interviews and Offer (Days 15 to 20)
Two rounds maximum. We facilitate both and coach candidates explicitly on what the client's engineering culture looks like so that the first two weeks on the job are not wasted on cultural calibration.
Stage 4: Onboarding and Contract Start (Days 21 to 28)
EOR documentation, statutory setup, system access, and sprint integration. The engineer is delivering by Day 28.
A Real Engagement from Bengaluru
A 150-person B2B SaaS company needed a senior software engineer with Python-Django backend experience for a nine-month C2H role. We placed a Bengaluru-based engineer within 22 days. What almost went wrong: at week seven, the engineer's manager gave feedback in a way that the engineer interpreted as a signal that conversion was unlikely, despite strong delivery. The engineer started a quiet job search. We caught this during our standard mid-contract check-in call, which is something we run with every placed candidate, not just with the client.
We facilitated a direct conversation between the manager and the engineer, clarified that the feedback was stylistic rather than performance-based, and the engineer withdrew from the competing process. He converted at month nine. The client saved approximately ₹6.8 lakh compared to the cost of restarting the search.This is the kind of thing that does not appear in any SLA but determines whether a C2H placement actually delivers. We run mid-contract check-ins as standard practice because losing a strong hire at month seven is a failure regardless of whose fault it is.
For companies exploring remote hiring of Indian engineers on C2H structures, this mid-contract support layer is what separates a well-run placement from a contract that quietly falls apart before conversion.
What Does a C2H Contract to Hire Engagement Actually Cost Compared to Permanent Hiring in India?
Here is the cost comparison between a permanent hire and a C2H engagement for three seniority levels of Full Stack and Backend engineers in India.
Seniority | Permanent Hire: Total Year 1 Cost (INR) | C2H Contract: Total Cost for 9 Months (INR) | Saving on 9-Month Comparison |
Mid (3 to 5 yrs) | ₹18 to 22 lakh | ₹10 to 13 lakh | ₹6 to 9 lakh |
Senior (6 to 9 yrs) | ₹28 to 38 lakh | ₹16 to 21 lakh | ₹10 to 17 lakh |
Lead (10 plus yrs) | ₹45 to 60 lakh | ₹26 to 34 lakh | ₹16 to 26 lakh |
What the permanent hire cost includes: Gross CTC, employer PF contribution, recruitment agency fee typically 8 to 12% of CTC, onboarding overhead, and a provision for the cost of a wrong hire, which we estimate conservatively at 25% of annual CTC.
What the C2H cost includes: Contract salary typically 10 to 15% above the equivalent permanent monthly salary to compensate for contract risk, EOR or staffing fee, and our placement fee.
For global companies engaging Indian engineers on C2H through contractual remote hiring models, the cost comparison against local market hiring in the destination country is significantly wider, typically €40,000 to €65,000 per year for senior roles in Western Europe.
What companies typically reinvest the savings into: a second open role that had been on hold, a QA or automation layer that was being deferred, or infrastructure upgrades the engineering team had been requesting for two quarters. All three are patterns we have seen consistently in repeat mandates.
What Is the Future of C2H Contract to Hire Hiring in India?
The trend toward employers choosing the C2H contract to hire route is accelerating, not plateauing. Three forces are driving this: tighter permanent headcount approval processes in companies managing cost discipline, increasing availability of strong senior engineers who are open to and actively prefer contract-first engagements, and the growing adoption of EOR infrastructure in India that makes C2H legally clean and administratively simple.
In live mandates right now, we are seeing C2H requests from clients who previously only did permanent hiring, particularly in the 100 to 500-person scale-up segment, where engineering headcount decisions have board-level visibility and HR teams need a lower-risk path to get roles approved. The pattern is clear: employers choosing the C2H contract to hire route are not doing so because it is cheaper in the short term. They are doing it because it is more reliable, more defensible internally, and increasingly the standard that strong engineers expect before committing to a company long-term.
If your company is evaluating C2H as a hiring model and you want a no-obligation discussion about structure, timelines, and cost, we are ready to help.
Interesting Reads:
FAQs
1.What is the difference between C2H (Contract to Hire) and a standard fixed-term contract in India?
A standard fixed-term contract ends on a set date with no conversion expectation. A C2H contract is also fixed-term but includes a pre-agreed intention to evaluate the candidate for permanent employment. Under India's Industrial Relations Code 2020, both are valid employment categories. The difference is intent and documentation. A proper C2H contract must include conversion criteria, evaluation timeline, and permanent salary band in writing before the engagement begins.
2.Does a C2H engineer in India receive PF, ESIC, and gratuity from Day 1?
Yes, without exception. Under the Industrial Relations Code 2020, fixed-term employees receive all statutory benefits from their first working day, including PF at 12% from both sides, ESIC where applicable, and pro-rata gratuity. Companies that structure C2H as freelance arrangements to avoid these contributions face two consequences: tribunal reclassification risk and rejection by strong candidates. Experienced engineers in Bengaluru and Hyderabad identify non-compliant contracts immediately and withdraw from the process.
3.How do employers set fair performance criteria for the C2H evaluation period?
Criteria must be defined and shared before the contract starts, not applied at the end. We recommend three categories: delivery metrics such as features shipped and sprint contribution, quality metrics such as code review scores, and collaboration metrics covering communication and stakeholder feedback. Each needs a specific measurable threshold, not a vague label like "good performance." Criteria should be reviewed at a midpoint check-in and used as the formal basis for the conversion decision.
4.What is the typical contract duration for a C2H role in IT and what affects the decision?
Nine months is the most common duration in our IT placements, followed by six and twelve months. Six months works for mid-level engineers joining teams with clear processes. Senior and lead roles need nine to twelve months because meaningful work such as architecture decisions and cross-team collaboration often does not surface until month four or five. We advise against three-month contracts for senior roles as they measure ramp-up performance rather than steady-state capability, which is an unreliable signal.
5.Can a company decide not to convert at the end of a C2H contract and what are the obligations?
Yes. Non-conversion is a legitimate outcome. Under India's Industrial Relations Code 2020, the fixed-term contract ends on the agreed date. The company must provide notice or pay in lieu, typically 15 to 30 days for IT roles. No additional severance applies when the contract reaches its natural end date. The decision must be communicated well before the end date so the engineer has adequate time to plan. Late communication damages employer reputation in engineering communities, which are closely networked.
6.How do we handle a situation where a strong C2H engineer receives a competing offer mid-contract?
Three practices reduce this risk significantly. First, document the conversion intention clearly so the engineer is not left guessing. Second, conduct a midpoint review that acknowledges strong performance. Engineers who receive no positive signal during the contract are most likely to accept competing offers. Third, pre-agree the permanent salary band so the engineer has no reason to benchmark externally. We run mid-contract check-in calls with every placed candidate as standard practice to surface warning signs before they become resignations.
7.What is the right way to handle intellectual property and code ownership during a C2H contract?
All code, documentation, and work product must be explicitly assigned to the hiring company through a written IP clause. Indian courts have not consistently ruled that work created during employment belongs to the employer without express contractual language, particularly for fixed-term roles. The clause should cover source code, test scripts, documentation, and any derivative works including tools built outside official hours using company resources. We include a standard IP assignment clause in every contract template and flag its absence when clients submit their own drafts.
8.Is the C2H model suitable for bulk or volume hiring or is it primarily for individual roles?
C2H works well at volume when the evaluation process is standardised before hiring begins. We have run bulk C2H mandates of 10 to 25 engineers for GCC build-outs and product team expansions. Volume C2H requires a shared performance rubric, a cohort review at midpoint, and an organisation resourced to make conversion decisions at scale. For companies considering bulk hiring through C2H, start with a pilot cohort of four to six engineers, validate the process, and then scale. Rushing to 20 engineers without a tested framework consistently produces poor conversion rates.
Comments