How Is Contract Hiring in India Different from Full-Time?

The fixed-term contract rate for a mid-level software engineer in India runs between Rs. 60,000 and Rs. 90,000 per month on a contractor invoice, with no PF, no gratuity, and no notice period beyond what the contract specifies. A permanent hire at the same level costs an employer 20 to 30% more in total when you factor in statutory contributions: 12% Provident Fund (employer share), 3.25% ESIC where applicable, gratuity accrual after five years, and paid leave encashment. That gap is real and it compounds fast when you are placing 10 or 20 engineers simultaneously. Contract hiring in India different from full-time is not just a matter of paperwork.

It changes the legal relationship, the tax structure, the notice risk, and how the engineer thinks about their own career trajectory. If you are an HR manager at a global company running India operations, getting this distinction wrong costs you money on one side and compliance exposure on the other.

Why Do Global Companies Keep Misclassifying Contract Workers in India?

Most international clients who come to us have already made one mistake before we speak: they tried to hire a contractor in India and put them on the same process they use for a permanent employee. JD, multi-round interviews, offer letter, then onboarding into their HRIS as headcount. That does not work here, and it creates problems quickly.

India's labour law framework distinguishes between workers and contractors at the level of the Contract Labour (Regulation and Abolition) Act, 1970 (CLRA). Under CLRA, if a contractor is working continuously on your premises or under your direct supervision for more than a threshold period, and courts have interpreted this as low as 120 days in some rulings, there is a risk of deemed employment. That means the principal employer (your entity or your EOR) can be asked to absorb the worker as a permanent employee with full benefits.

We see this pattern repeatedly in mid-sized European companies that set up an India arm and immediately start pulling in contractors through informal referrals. By month six, they have eight people working full-time schedules, attending all internal meetings, using company email IDs, reporting to internal managers, and zero contracts reviewed by Indian counsel. That is a CLRA exposure, not just an HR oversight.

The second common mistake is conflating a fixed-term employee (FTE) under the Industrial Relations Code, 2020 with a freelance contractor. Fixed-term employees under the IR Code are permanent employees for the duration of the contract. They get proportional gratuity, PF, and all statutory benefits from day one. They are not contractors. The distinction matters enormously for your compliance calendar.

For companies managing remote contract roles across India, getting this classification right before you place the first engineer is non-negotiable.

Which Indian Cities Have the Strongest Contract Tech Talent Pool?

The depth of contract talent in India varies significantly by city and role. For tech hiring specifically:

Bengaluru has the densest pool of engineers comfortable with contract engagements, particularly for DevOps, cloud, and product engineering roles. The culture of project-based work is normalised here, and engineers often prefer a 12-month contract with a global company over a permanent role with a domestic firm.

Hyderabad has strong supply in SAP, data engineering, and enterprise software. Contract roles here often run 18 to 24 months because the skill specificity takes time to ramp. Clients who try to hire these profiles on 3-month contracts usually fail retention within 60 days because a permanent offer pulls the engineer away. If you are building data infrastructure, our Hyderabad desk handles specialist contract placements regularly.

Pune has mature contract talent in QA automation, Java backend, and middleware, particularly for BFSI and manufacturing GCCs. Engineers here are generally more stable on 6 to 12 month contracts if the role is structured well.

Chennai supplies strong embedded systems, infrastructure, and networking contractors. Less volume than Bengaluru, but higher retention on contract because the market is slightly less aggressive.

What Indian engineers on contract consistently bring: strong technical execution speed, comfort with agile sprint structures, and the ability to onboard to existing codebases quickly. What they often lack for global mandates: documentation discipline, async communication habits especially for European time zones, and the instinct to flag blockers early rather than solve silently for three days and miss a sprint commitment.

At AnjuSmriti Global, we test for this through a structured async simulation. We send candidates a mock Slack thread with three technical ambiguities and measure response time, clarity, and whether they ask the right follow-up questions before they code. Most strong engineers fail the first attempt. The ones who adapt on retry are the ones we put forward.

What Does Indian Law Actually Say About Contract Hiring in India Different from Full-Time?

Three laws every HR manager needs to understand before signing a contract:

1. Contract Labour (Regulation and Abolition) Act, 1970 (CLRA)

Governs the use of contract workers. If you engage contractors through a third-party agency, which is the right structure, the agency is the principal employer for statutory purposes. Your entity remains the principal employer for worksite obligations including basic amenities and minimum wages. License thresholds apply: contractors deploying 20 or more workers need a CLRA license.

2. Industrial Relations Code, 2020

Introduced the fixed-term employment category at national level. A fixed-term employee is legally distinct from a contractor. They are on your rolls, not the agency's. They get all benefits on a pro-rata basis. Companies sometimes use this structure thinking it gives them flexibility; it gives them some, but not the same flexibility as a genuine third-party contract arrangement.

3. Code on Wages, 2019

Applies to all workers, including contractors. Minimum wage floors apply. If your contractor rate is below the applicable scheduled rate for the category and skill level, the agency or EOR carrying the engineer is non-compliant, and you share that liability as the principal.

The most common mistake: a foreign company directly contracts with an Indian freelancer with no agency, no EOR, pays them in USD to a personal account, and books it as a vendor payment. This creates a permanent establishment (PE) risk under Indian tax law, and the engineer has no social security coverage. If the engagement exceeds 183 days, Indian tax authorities can assess the foreign company for local PE obligations.

If you are building a structured contract hiring model, running it through a proper Employer of Record (EOR) structure or a registered Indian entity with proper CLRA registration is the only clean path.

Contract vs Full-Time Hiring in India: The Comparison Table

Understanding contract hiring in India different from full-time requires you to compare the two models across every operational dimension, not just cost. Here is the complete side-by-side breakdown our HR clients use when making the engagement decision:

Factor	Contract Hiring	Full-Time (Permanent)
Legal framework	CLRA 1970, third-party agency	IR Code 2020, direct employment
PF contribution (employer)	Agency bears if structured correctly	You bear at 12% of basic
Gratuity obligation	None for true contractor	Accrues after 5 years
Notice period	As per contract, often 15 to 30 days	1 to 3 months typically
ESIC liability	Agency or EOR for eligible wage bands	Your entity
Fixed-term employee variant	Not applicable	Proportional benefits from Day 1
PE risk for foreign entity	High if direct engagement	Managed via India entity or EOR
Hiring speed (our median)	18 to 22 days from JD to onboarding	35 to 50 days from JD to joining
Cost at mid-level (monthly)	Rs. 75,000 to Rs. 90,000 all-in	Rs. 95,000 to Rs. 1,15,000 all-in
Right to terminate	Contract clause governs	Notice plus severance norms apply
Suitable for	Project-based, surge, specialist roles	Core team, long-term functions

Map each role you are hiring against the "Suitable for" row first. If the work is ongoing, repetitive, and tied to your core product, permanent is almost always cleaner legally. If it is a 9-month cloud migration, a QA automation build-out, or a short-term platform upgrade, structured contract hiring through an agency is the correct model.

How We Run a Contract Mandate and the Placement That Nearly Went Wrong

Our contract hiring process runs on a 22-day median from signed JD to engineer at desk. Here is the actual sequence:

Days 1 to 3: Role scoping call covering stack, sprint structure, timezone overlap requirement, contract duration, and renewal likelihood. We push back hard on vague JDs. A "DevOps engineer" with no cloud specified is not a hireable brief.

Days 4 to 10: Active sourcing across our network in Bengaluru, Pune, and Hyderabad. For niche roles, we run parallel sourcing in Chennai. We do not post on Naukri for contract roles. The signal-to-noise ratio is too low. Our network is 80% referral-based for contract mandates.

Days 11 to 15: Technical screening. For cloud and engineering roles, we use a two-stage process: an automated async test that is stack-specific and runs 45 minutes, followed by a live architecture discussion with one of our senior technical evaluators. We reject roughly 60% of candidates who pass stage one.

Days 16 to 20: Client interviews (maximum two rounds for contract). We refuse mandates requiring five rounds for a 6-month contract. Background and document verification runs in parallel.

Days 21 to 22: Contract issued, onboarding paperwork with EOR or agency payroll, access provisioned.

The mandate that nearly went wrong: A 140-person European logistics technology company hired us to place six cloud infrastructure engineers across three locations on 12-month contracts for a warehouse management system migration. We placed four within 22 days. The fifth offer was accepted and then rescinded by the engineer on Day 19 because a domestic company matched his contract rate and offered a permanent role. We had not flagged that this particular profile, GCP-certified with Kubernetes orchestration experience, was in a counter-offer zone in Bengaluru at that point in the market cycle. We replaced the engineer in 11 days by pulling from an alternate shortlist we keep active for exactly this reason.

Final outcome: all six engineers placed, migration went live 3 weeks behind original schedule due to a client-side scope change, and four of the six contracts were renewed at the 12-month mark.

This is why AnjuSmriti Global never presents a shortlist of exactly the number you need. We always run two extra candidates through final technical rounds and hold them in a warm pipeline.

What Does Contract vs Full-Time Hiring Actually Cost in India?

For an IT or software engineering profile, here is what our clients actually pay at current market rates:

Mid-Level Engineer (4 to 6 years experience)

	Contract (Agency or EOR all-in)	Full-Time (CTC plus employer statutory)
Monthly cost to company	Rs. 75,000 to Rs. 90,000	Rs. 95,000 to Rs. 1,10,000
Annual cost	Rs. 9 lakh to Rs. 10.8 lakh	Rs. 11.4 lakh to Rs. 13.2 lakh

Senior Engineer (7 to 10 years)

	Contract	Full-Time
Monthly cost	Rs. 1,10,000 to Rs. 1,50,000	Rs. 1,40,000 to Rs. 1,85,000
Annual cost	Rs. 13.2 lakh to Rs. 18 lakh	Rs. 16.8 lakh to Rs. 22.2 lakh

Lead or Architect (10 plus years)

	Contract	Full-Time
Monthly cost	Rs. 1,80,000 to Rs. 2,50,000	Rs. 2,20,000 to Rs. 3,00,000
Annual cost	Rs. 21.6 lakh to Rs. 30 lakh	Rs. 26.4 lakh to Rs. 36 lakh

Contract all-in rate includes: agency margin typically at 12 to 18% on gross, EOR fee if applicable at Rs. 8,000 to Rs. 15,000 per month per head, and all statutory contributions managed by the agency. What you do not pay for: gratuity, earned leave encashment, or severance beyond contract notice.

Most clients reinvest the delta, typically Rs. 2 to 4 lakh per head per year, into tooling, additional contract headcount for surge periods, or the global payroll infrastructure that makes managing a distributed India team operationally clean.

Conclusion

Fixed-term employment under the IR Code 2020 is becoming the dominant engagement model for global companies building India delivery centres, particularly as more states operationalise the Code's provisions and the compliance line between contractor and fixed-term employee gets sharper. The PE risk of direct freelancer engagement is also attracting more scrutiny from Indian tax authorities, which is pushing more international companies toward structured EOR or agency payroll models.

In our live mandates right now, we are seeing a marked uptick in requests from European and US companies wanting to convert existing informal contractor relationships into properly structured contract hiring in India different from full-time employment, cleaning up what they built ad hoc over the past few years. If that is where you are, the earlier you move, the lower the retroactive exposure.

To discuss your India contract hiring structure, reach out to our team here

---

Interesting Reads:

How Boutique SAP Firms Can Scale with Contract Consultants from India How Much Does Salesforce Contract Hiring Cost in India What AWS Certifications Are Most Valued by GCCs in India?

FAQs

1. Does the CLRA 1970 apply if my company has no registered entity in India?

Yes. If your supervisory control over the contractor is direct, meaning they report to your managers, use your tools, and follow your schedules, the CLRA can still apply to you as the de facto principal employer even without an India entity. What actually protects you is ensuring that a registered Indian agency or EOR is the employer of record under CLRA, holds the required license where applicable, and that your contract clearly places all statutory obligations on them. Without proper Indian legal review of the engagement structure, foreign companies carry hidden compliance risk that surfaces only when a dispute arises or a labour audit is triggered.

2. What is the actual legal difference between a fixed-term employee and a contractor under Indian law?

A fixed-term employee under the Industrial Relations Code, 2020 is on your payroll, entitled to proportional PF, ESIC, gratuity, and paid leave from Day 1. A contractor is on the agency's payroll, not yours, and your statutory obligations toward them are indirect. The fixed-term model gives you a defined end date but not freedom from benefits. The contractor model through a registered agency gives you that freedom, provided the engagement is genuinely arms-length. Misusing the fixed-term label to avoid benefits while treating the person as a contractor is a classification error that Indian labour authorities are increasingly flagging during audits.

3. How does the Code on Wages 2019 affect what I pay an Indian contract engineer?

The Code on Wages sets minimum wage floors that apply to all workers regardless of engagement type, including contractors. For tech roles in metro cities, market rates sit well above statutory floors. However, for support or operations roles where rates are closer to the floor, your agency must certify compliance. The Code also mandates timely wage payment. If your agency runs payroll two months late, you carry shared liability as principal. Reviewing your agency's payment track record and asking for sample compliance certificates before signing any contract staffing agreement is not optional; it is basic due diligence.

4. Can a contract engineer in India work exclusively for my company for two years without triggering deemed employment?

Yes, but only if the engagement is genuinely structured as arms-length. Duration alone does not trigger deemed employment risk. The trigger is the nature of the relationship: direct supervision, integration into internal operations, use of company email or systems, and attendance at all internal meetings. A two-year contractor who is effectively indistinguishable from your permanent team is a CLRA liability regardless of what the contract says. The mitigant is ensuring the engineer remains on agency payroll, HR is managed by the agency, and your engagement is project-scoped and outcomes-based rather than time-and-attendance based.

5. What is the PE risk of paying an Indian freelancer directly in USD without an agency or EOR?

If you pay an Indian freelancer directly to a personal bank account in USD and book it as a vendor payment, you face permanent establishment (PE) risk under Indian tax law, especially if the engagement exceeds 183 days in a 12-month period. Indian tax authorities can assess your foreign company for local PE obligations, which includes filing returns, paying corporate tax on India-attributed income, and potentially back-paying TDS. The engineer also has no social security coverage in this arrangement. Running the engagement through a registered Indian agency or an EOR eliminates PE risk because the statutory employment relationship sits with them, not with your foreign entity.

6. What is the right contract duration for Indian tech engineers in current market conditions?

Twelve months remains the most functional contract duration for most tech roles. It is long enough for the engineer to ramp and deliver measurable outcomes, and short enough to retain their focus before they start evaluating permanent opportunities. For specialist profiles like GCP architects, Salesforce solution leads, or S/4HANA consultants, 18 months is more realistic because ramp time is longer and counter-offers become aggressive around month 9. For project-bound roles such as a QA automation setup or a migration sprint, 6 months works but carries a market premium because engineers price in the short-tenure risk. Building in a modest rate uplift at renewal, typically 10 to 15%, is cheaper than a full replacement cycle.

7. What should an HR manager ask a staffing agency before signing a contract hiring agreement in India?

Five questions that separate credible agencies from risky ones: Does the agency hold a valid CLRA license for the states where engineers will be deployed, and will they share the license number? What is their PF and ESIC filing track record, and can they provide a recent compliance certificate? How do they handle engineer exits, including IP return and system access revocation? What is their replacement guarantee and under what conditions does it apply? Do they carry employer liability insurance that covers misclassification disputes? If an agency cannot answer questions two, three, and five clearly and in writing, continue evaluating. Compliance failures with contract workers in India carry retroactive financial and legal consequences that far exceed any fee saved by going with an underpowered vendor.

8. How do you convert an existing informal contractor relationship in India into a compliant structure?

Start with a legal review of the current arrangement by Indian counsel, specifically to assess CLRA exposure and PE risk. If the contractor has been on your rolls informally for more than 120 days with direct supervisory control, the first step is to transition them to a registered agency payroll or EOR immediately. The transition involves the agency issuing a fresh employment contract, running background verification, and enrolling the engineer in statutory schemes (PF and ESIC). Your engagement then moves to a formal vendor contract with the agency rather than a direct contract with the individual. Any historical payments made directly should be reviewed for TDS compliance. Most clients who approach us for this cleanup are surprised by how quickly it can be done cleanly, typically within 3 to 4 weeks per engineer with the right legal and payroll partners in place.