What are the legal, contract, and IP considerations when hiring developers in India?
Hiring developers in India requires you to get three things right: correct worker classification, enforceable contracts under Indian law, and watertight IP assignment. Miss any one and you expose yourself to tax penalties, unenforceable non-competes, or a scenario where the code your team wrote does not legally belong to you. This is the difference between a cost-effective offshore team and an expensive legal cleanup two years later.
The good news: none of this is exotic. India has a mature, predictable legal framework for software work. The traps are specific and well-documented, and once you know them, they are straightforward to avoid. Below is what a CTO or founder in Europe, the UAE, or India actually needs to decide before signing anyone.
Should you hire developers in India as contractors, through an EOR, or via your own entity?
There are three legal structures for engaging Indian engineers, and the right one depends on headcount, timeline, and how much control you need. Here is the trade-off in plain terms:
| Model | Who employs the developer | Best for | Main risk |
|---|---|---|---|
| Independent contractor | The developer (self-employed) | 1–3 people, short projects, specialist skills | Misclassification if you control them like employees |
| Employer of Record (EOR India) | A local EOR provider on your behalf | Fast hiring, 1–15 people, no local entity | Per-head fees add up; less control over IP chain |
| Your own Indian subsidiary | Your registered entity (Pvt Ltd) | 15+ engineers, long-term commitment | Months of setup, compliance overhead, board obligations |
Most European and UAE companies start with contractors or an EOR and only incorporate once headcount justifies the fixed cost. The mistake is defaulting to contractor agreements for a full-time team of ten — that is where misclassification risk becomes real. We break down the broader build-versus-buy decision in our guide to staff augmentation vs managed services vs freelancers.
What is misclassification risk when hiring contractors in India?
Misclassification happens when you engage someone as an independent contractor but treat them, in practice, as an employee. Indian authorities and courts look past the label on the contract and examine the actual working relationship. If a "contractor" works fixed hours you set, uses your equipment, reports to your manager, has no other clients, and cannot send a substitute, they are functionally an employee — regardless of what the paperwork says.
The consequences fall on you as the engaging company:
- Back-dated statutory contributions — Provident Fund (EPF) and Employees' State Insurance (ESI) you should have been paying, plus interest and penalties.
- Gratuity and leave liabilities under the applicable state Shops and Establishments Act.
- Tax exposure — mischaracterised payments can trigger scrutiny of TDS (tax deducted at source) obligations.
- Permanent establishment risk — a controlled, dependent workforce in India can create a taxable presence for your foreign company, exposing global profit to Indian corporate tax.
The permanent establishment point is the one founders underestimate. A genuine arm's-length contractor rarely creates PE. A team of ten people you manage daily, who work only for you, plausibly does. This single factor often decides whether contractors are safe or whether you need an EOR or entity.
How do you protect IP when hiring developers offshore?
IP protection offshore rests on one principle: in most jurisdictions, including India, the person who writes the code owns it by default unless there is a valid written assignment. Employment does not automatically transfer everything, and contractor relationships transfer even less. You must assign IP explicitly, in writing, with the right structure.
A defensible IP position for India-based development includes:
- Present assignment of future IP. The contract must say the developer "hereby assigns" all work product, not "agrees to assign." Present-tense assignment transfers rights automatically as work is created; a promise to assign later can fail if the relationship sours.
- Work-for-hire and moral-rights language. India's Copyright Act recognises certain moral rights that cannot be fully assigned, so well-drafted contracts include a waiver of the assertion of those rights to the extent permitted by law.
- An unbroken chain of assignment. If an EOR or vendor sits between you and the developer, the IP must flow developer → intermediary → you. A gap anywhere means you do not own the output. Audit this chain before you rely on it.
- Confidentiality and trade-secret protection. India has no standalone trade-secrets statute; protection is contractual and via equity. That makes a robust NDA and confidentiality clause load-bearing, not boilerplate.
- Tooling and access controls. Legal assignment is necessary but not sufficient. Repository permissions, SSO, secrets management, and offboarding revocation are what actually stop code from walking out the door.
If you are choosing where to base a team partly on IP risk, it is worth reading how the options compare in our breakdown of offshore vs nearshore vs onshore development — the legal mechanics differ less than people assume; execution and contract discipline differ enormously.
Are non-compete and non-solicit clauses enforceable in India?
This surprises most foreign employers: post-employment non-compete clauses are generally void in India. Section 27 of the Indian Contract Act, 1872, treats any agreement that restrains someone from exercising a lawful profession after the engagement ends as unenforceable, with narrow exceptions (mainly the sale of a business's goodwill).
What this means in practice:
- Non-competes during the engagement are generally fine. Non-competes after it ends are usually not.
- Non-solicitation of clients and employees is more defensible than a blanket non-compete, if drafted reasonably and tied to a legitimate interest.
- Confidentiality obligations survive termination and are enforceable — this is your real protection, not the non-compete.
The takeaway: do not rely on a non-compete to protect your business in India. Rely on strong IP assignment, enforceable confidentiality, and good security hygiene. Copy-pasting a US or German employment template will leave you with clauses that a court simply ignores.
What should an India developer contract actually contain?
Whether you engage directly, through an EOR, or via your entity, a sound agreement covers these terms:
- Governing law and dispute resolution — many cross-border contracts specify arbitration (for example, under the Arbitration and Conciliation Act, 1996, or an institutional body like SIAC in Singapore) for enforceability and neutrality.
- Present-tense IP assignment covering code, designs, documentation, and derivative works.
- Confidentiality and data-protection terms aligned with India's Digital Personal Data Protection Act, 2023, and — if you handle EU data — GDPR-compatible processing clauses.
- Clear classification language that matches reality: if it is a contractor agreement, the working relationship must genuinely be arm's-length.
- Payment, currency, and tax handling — including who bears TDS and how invoices are structured for clean cross-border remittance under FEMA rules.
- Termination and offboarding — notice periods, immediate access revocation, and return or destruction of confidential material.
Contracts are only half the job. The other half is running the relationship so it stays compliant and productive across time zones — a discipline we cover in managing a remote development team across time zones.
Does hiring compliantly in India change the cost equation?
Compliance has a price, but it is smaller than founders fear and far smaller than the downside of getting it wrong. EOR fees, statutory contributions, and proper contracting typically add a modest percentage to the base engineering cost — and even loaded with those costs, India remains substantially cheaper than European hiring for equivalent seniority. We put real numbers against this in our comparison of the cost to hire a developer in India vs Europe.
Frame it as insurance: a few percent of payroll to eliminate the risk of back-taxes, penalties, permanent-establishment exposure, and — worst of all — a dispute over who owns your product's source code. That is a trade almost every CTO takes once the numbers are on the table.
How ILMTEC helps
ILMTEC hires and hosts senior India-based engineers through our own registered Indian entity, so you get the talent without touching the legal machinery. Contracts, present-tense IP assignment, statutory compliance, and the developer-to-you IP chain are handled and documented before anyone writes a line of code — and the output is legally yours from day one. If you are weighing an India team and want the compliance and IP risk taken off your plate, our India engineering talent solution gives you vetted senior developers on a clean, entity-backed footing. You review the engineers; we own the paperwork.
