Hire Engineering Talent in India: IP and Moonlighting

Companies that hire engineering talent in India usually arrive with a contract that worked at home and a plan to reuse it. That is where the trouble starts.

At Wisemonk we have built India engineering teams for global employers for years. The same three things break every time: who owns the work, what happens outside your hours, and where a dispute gets decided.

This guide takes those three in the order a hiring decision actually runs. It cites the Indian sections that govern each one, because most of what circulates on this subject cites none.

How do you hire engineering talent in India?

Three routes are open to you. Hire an employee through an Employer of Record, engage an independent contractor, or contract an offshore development vendor. Each hands you a different default on who owns the work, a different amount of control over outside employment, and a different forum for a dispute.

The market is deep enough that all three are genuinely available. India's engineering R&D sector was worth $63 billion in FY26, sitting inside a $315.4 billion Indian IT-BPM industry the same year.

Here is what each route gives you and what it costs you in control:

Hire as an employee through an EOR

An Employer of Record becomes the legal employer in India while the engineer works to your roadmap. You get an employment relationship, which is the route with the strongest built-in position on ownership and exclusivity.

It is also the fastest way to hire in India without setting up an entity. The registrations, payroll and statutory filings already exist, so you are hiring rather than incorporating.

Provident fund, roughly India's equivalent of a 401(k), and the other statutory contributions are handled by the employer of record rather than by you.

Engage an independent contractor

A contractor engagement is quick to start and quick to end. It is the route where your IP position is weakest by default, and the route with the least room to demand exclusivity.

It suits genuinely independent specialists working to a defined output. It does not suit a person who sits in your standups, uses your systems and takes direction daily.

Contract an offshore development vendor

Engineering services outsourcing means buying a team from a firm that employs it. You sign a master agreement, the vendor manages delivery, and you never become anyone's employer.

The trade is control and chain of title. Your IP reaches you through the vendor's own paperwork with its engineers, and you cannot inspect what you did not draft.

Which of the three fits depends on how long you need the people and how tightly the work sits inside your product. If you are still weighing that, our guide to the best way to hire employees in India walks the comparison in more detail before you commit.

Which hiring route gives you the strongest claim to the IP?

The route decides your starting position. An employment relationship is a contract of service, and under Section 17 of the Copyright Act 1957 the employer is first owner absent a contrary agreement. A contractor engagement is a contract for service, where copyright starts with the creator. Everything a clause does afterward either confirms a default or reverses one.

We are deliberately staying on route selection here. For the ownership mechanics themselves, our guide to who owns the IP your India engineers create covers the assignment, waiver and data provisions in depth, and how patent ownership works in an India R&D team covers the patent side.

Why contract of service and contract for service decide ownership

US buyers reach for a phrase from their own copyright statute, the one that makes a commissioned deliverable the buyer's property automatically. That concept has no equivalent under Indian law.

Indian law asks a different question: is this a contract of service or a contract for service? A contract of service is employment, and the employer is first owner. A contract for service is a contractor engagement, and the creator is.

Drafting to the US concept produces a clause that names a category Indian law does not recognize. Naming the right category, and then assigning expressly, is what actually works.

What Section 17 covers, and what it does not

Section 17's employer default runs on works made in the course of employment, under a contract of service, and only where nothing to the contrary is agreed. Our IP ownership guide, linked above, walks the provisos.

One narrow point is worth carrying here because engineers hit it. The commissioned-work exception in the same section covers a photograph, a painting or portrait, an engraving and a cinematograph film. It does not cover engineering drawings, CAD files or source code, so commissioning those from a contractor moves nothing on its own.

Patents and designs do not follow the copyright rule

Copyright's employer default has no patent equivalent. Under Section 6 of the Patents Act 1970 an application can be made only by the true and first inventor, by their assignee in respect of the right to make the application, or by a legal representative.

So an employer reaches an invention as assignee, which means the assignment has to exist and has to cover the right to apply. Employment alone does not carry it.

Registered designs run the other way, and this catches people out. Under Section 2(j) of the Designs Act 2000, where the author executes the work for another person for good consideration, that person is the proprietor. A commissioned industrial design can therefore vest in you where the copyright in a commissioned drawing would not.

Semiconductor layout designs sit under their own statute, the Semiconductor Integrated Circuits Layout-Design Act 2000, where protection follows registration rather than arising automatically.

With a vendor, you are relying on someone else's paperwork

A vendor can only assign you what its own engineers validly assigned to it. If that internal chain is weak, your assignment inherits the weakness and you will not find out until it matters.

You can ask for the vendor's employee IP terms during diligence. Most buyers never do, and that is the gap.

Exclusivity is the column most buyers skim, and it is the one that produces the fights. That is the next section.

For a wider view of the safeguards that sit around all of this, our guide to protecting intellectual property when hiring in India is the companion read.

What does Indian law say about moonlighting, and can you stop it?

India has no dedicated anti-moonlighting statute. What governs a second job is your contract plus Section 27 of the Indian Contract Act 1872, and the line the courts draw is temporal. A reasonable exclusivity obligation during employment is generally upheld. A restraint that bites after the employment ends is void.

That distinction is the whole of the practical answer, and it is the one most commentary on this subject leaves out.

The during-employment versus post-termination line under Section 27

Section 27 reads: "Every agreement by which any one is restrained from exercising a lawful profession, trade or business of any kind, is to that extent void."

The Supreme Court drew the line in Niranjan Shankar Golikari v. The Century Spinning and Manufacturing Company, decided on January 17, 1967. Negative covenants operative during the period of employment, when the employee is bound to serve the employer exclusively, are not restraints of trade and do not fall under Section 27.

The qualifier matters as much as the rule. Such a covenant stands unless the contract is unconscionable, excessively harsh, unreasonable or one-sided.

That case was itself a moonlighting case on its facts. The employee held a five-year exclusive contract, was trained in a specialist manufacturing process, and left to join a rival concern.

So write the two clauses separately. Exclusivity during the term is a different instrument from a non-compete after it, one is generally enforceable and one is not, and combining them into a single paragraph gets both argued about.

What the 2022 Indian IT terminations actually established

The public record on Indian moonlighting comes from Indian IT services employers, not from a statute. In September 2022 Wipro terminated 300 employees found to be working for competitors, and executive chairman Rishad Premji, who had earlier equated the practice to cheating, called it a violation of integrity in its deepest form.

Infosys emailed staff the same month telling them that dual employment was not permitted under its employee handbook and code of conduct, and that a breach could lead to disciplinary action up to termination.

Then it changed its mind. By October 2022 Infosys was allowing employees to take outside gig work with a manager's prior consent.

That reversal, in about six weeks, is the most useful thing in the whole episode. The employment contracts of the large Indian IT firms already made outside work difficult, and the sector still moved from prohibition toward permission.

Why disclosure and approval beats a blanket ban

A blanket ban gives you a clause you may not want to test. An approval requirement gives you a disclosure obligation, which is the thing you actually want to enforce.

Undisclosed dual employment is a breach you can evidence with a date and a document. "Working somewhere else" on its own is a much harder argument.

In practice we advise clients to write three things into the contract: full-time commitment during working hours, prior written consent for any outside engagement, and immediate disclosure of any conflict. Our guide to staying compliant with remote India engineers covers how that reads alongside the rest of the remote-work terms.

What you can ask of a contractor, and where asking becomes a classification problem

Demanding exclusivity from an independent contractor is the point at which the engagement starts to look like employment. India applies three tests: control, integration and economic dependence.

The three tests ask who directs how the work is done, how far the person is integrated into your operation, and how far their income depends on you. A full-time exclusivity demand pushes hard on the first and the third.

If you need exclusivity, you probably need an employee.

One correction worth making, because it circulates widely. Section 60 of the Factories Act 1948 restricted double employment, and its successor does the same: Section 30 of the Occupational Safety, Health and Working Conditions Code 2020 bars a worker from working in a mine or factory within twelve hours of working in another one.

Both provisions reach factory and mine workers, not salaried staff. Neither is India's moonlighting law for an engineering team, and anyone citing them at you is citing the wrong thing.

How do you find out whether an engineer is moonlighting?

The only control that works before someone is on your payroll is verification. Everything after that is contractual and technical, and it is harder to act on. Pre-hire checks give you a decision point with no exit process attached, which is why sequencing matters more here than clause wording.

What pre-hire verification can surface

This is the part India makes unusually tractable. Background checks in India verify employment history against the UAN and EPFO provident-fund record, and because a second employer filing contributions shows up against the same universal account number, a background verification can cross-reference it. Moonlighting is one of the 19 checks we run.

There is no equivalent single record in most markets, which is why this check exists in India and not elsewhere. It is a genuine advantage and most global employers never ask for it.

Pro tip: Run the background check before the start date, never after. Once someone is on payroll, acting on undisclosed dual employment stops being a withdrawn offer and becomes an exit process with notice, settlement and a state-law overlay on top. A basic check comes back in about five minutes and a full report takes 7 to 10 days, so the sequencing costs you nothing if you plan for it.

Device, access and confidentiality controls that hold up

After the start date, your levers are technical and contractual. Company-provisioned hardware, scoped repository access, and an NDA that names the systems and data in question.

Keep the access review boring and periodic. Anything that requires monitoring an individual's personal activity raises data obligations, and DPDP Act obligations for foreign employers are worth reading before you design a policy around surveillance.

What to do when you find it

Start with the disclosure clause, not the exit. Ask for the disclosure the contract already required, in writing, with a deadline.

Whether the answer reveals a conflict, a breach, or a misunderstanding decides what follows. Acting before you have that document is how a defensible process turns into a disputed one.

Verification also belongs in the wider onboarding sequence rather than sitting off to one side, and the India onboarding checklist shows where it slots against the contract, the equipment and the first payroll cycle.

Which clauses does an India engineering contract actually need?

Eight clauses do the work. Two of them are the ones US templates most often get wrong: the IP assignment, which has to be drafted to Indian formal requirements rather than assumed, and the restraint clause, which is void in India if it operates after the employment ends.

Take them in this order:

Express IP assignment, drafted to Section 19

Section 19 of the Copyright Act requires an assignment to be in writing, signed by the assignor, and to identify the work, the rights assigned, the duration and the territorial extent.

Leave any of those out and the Act fills the gap for you, in ways you would not choose. An assignment with no stated period is deemed to run five years. One with no stated territory is presumed to cover India only.

For a company buying engineering work it intends to own worldwide and forever, those two defaults are the difference between what you think you bought and what you actually hold.

Future work, and the limit on assigning it

Indian law does recognize assignment of copyright in future works, with a qualification. The proviso to Section 18 says an assignment of copyright in a future work takes effect only when the work comes into existence.

Practically, the clause survives, and the transfer happens as each deliverable is created rather than on signature.

Moral rights, waived to the maximum extent permitted by law

Section 57 gives an author the right to claim authorship and to restrain distortion, mutilation or modification prejudicial to their honour or reputation.

Read the section closely and you see why the hedge matters. Those rights exist independently of copyright and survive even after the copyright is assigned, and the section provides no waiver mechanism of its own. Use the phrase "to the maximum extent permitted by law" and keep it, because it is doing real work.

Exclusivity and disclosure of outside work

This is the clause the moonlighting section above is really about. Full-time commitment during working hours, prior written consent for outside engagements, immediate disclosure of a conflict.

Non-solicitation, and what Section 27 does to non-competes

A post-employment non-compete is void under Section 27, and no drafting rescues it. Non-solicitation is treated differently by some courts, but Indian authority is split and we do not assert that it is reliably enforceable.

If you want to see how the clause is constructed in a jurisdiction where it does hold, how non-solicitation clauses are drafted covers the US position. Read it as contrast, not as Indian authority.

Indemnity for third-party IP infringement

Require the engineer or vendor to warrant that deliverables do not infringe third-party rights, and to indemnify you if they do. This is the clause that matters when open-source licensing turns up in a codebase.

Confidentiality and data handling

Confidentiality and assignment are separate clauses doing separate jobs, and the data-handling half now carries statutory weight. The NDA and IP chain for India developers sets out how the two fit together.

Governing law

Name the governing law and the forum, and understand that the employment side of it is not fully yours to choose. That is the next section.

Two of our guides cover the surrounding documents in full: what an India employment agreement has to contain for the employee route, and an India independent contractor agreement for the contractor route.

How should you structure the contract for an employee, a contractor or a vendor?

The three models differ on four things that matter commercially: what your primary risk is, how you end the relationship, who owes statutory money, and which forum decides a dispute. Getting the document type right matters more than getting any single clause perfect, because the wrong document type cannot be fixed by clause drafting.

What changes when you hire through an EOR

You sign a services agreement with the employer of record, and the EOR signs an Indian employment contract with the engineer. Statutory obligations sit with the employer of record.

India's four Labour Codes have been in force since November 21, 2025, consolidating 29 central labour laws. The rules are still arriving: the Ministry of Labour and Employment issued a compliance handbook in February 2026 and further FAQs in March 2026, and several state rules are still rolling out as of September 2026.

What changes with an independent contractor

You sign directly, or through a contractor of record. There is no statutory notice, no provident fund, and no gratuity, which is exactly why the classification tests matter.

What changes with an offshore development vendor

You sign a master services agreement with statements of work under it. Engineering services outsourcing on this model gives you commercial remedies and no employment exposure, and it puts the IP chain one step further away from you.

That last row is the one that surprises people, and it deserves its own section.

If the contractor column is where you are leaning, two guides go deeper than this table can: hiring and paying contractors in India on the payment and compliance mechanics, and contractor versus employee in India on where the line actually falls.

Where do you settle a dispute with an India engineering team?

It depends which kind of dispute it is, and most advice on this subject only covers one of the two. Commercial and contractor disputes can go to institutional arbitration under a governing law you choose. An employment dispute cannot be arbitrated away from Indian labour forums, whatever the contract says.

Employment disputes stay with Indian labour forums

Indian employment protections are statutory, and a clause choosing New York law does not switch them off for a person employed in India. The forum for a statutory employment claim is Indian, and the applicable state Shops and Establishments Act travels with the workplace.

Read that as a planning fact rather than a problem. It means the employment relationship is governed by India's labour and employment law framework and should be documented to it from the start.

Commercial and contractor disputes can be arbitrated

A vendor master agreement or a genuine contractor agreement is a commercial contract. Here your choice of governing law and arbitral forum does the work you expect it to do.

Institutional arbitration is the usual route for foreign-party contracts, and the Singapore International Arbitration Centre and the Mumbai Centre for International Arbitration are the two most often named in India-facing agreements.

What to specify: seat, rules, language and governing law

Four things belong in the clause, and leaving any of them implied creates a preliminary fight before the real one:

• Seat of arbitration: the legal home of the proceeding, which determines which courts supervise it.
• Institutional rules: the procedure the tribunal will run on.
• Language: English, stated, so it is never argued.
• Governing law: the law of the contract, distinct from the seat.

Specify all four in the commercial contracts and accept that the employment contract answers to India. That split is the practical takeaway.

What goes wrong when a US contract template meets Indian law?

Five failures, and every one of them comes from a document that was correct in its home jurisdiction. We see the same list on almost every contract handed to us for review, and none of them is a drafting error in the ordinary sense. They are jurisdiction errors.

Treating an engineer as a contractor because it is faster

Speed is a real motive and a bad reason. The three tests are control, integration and economic dependence, and a contractor who works your hours on your systems under your direction fails all three.

Relying on a post-termination non-compete

Void under Section 27, as covered above. If your retention plan depends on one, you do not have a retention plan.

Assuming a signed NDA transfers ownership

It does not. Confidentiality restricts what someone may disclose; assignment moves who owns the thing. They are different clauses doing different jobs, and a contract with only the first has a gap where the second should be.

Filing a patent abroad first on work done in India

Section 39 of the Patents Act 1970 bars a person resident in India from applying for a patent outside India first, unless they hold a written permit from the Controller, or an application for the same invention has been on file in India for at least six weeks with no secrecy direction in force.

Note what triggers it. The test is where the inventor is resident, not where you are incorporated, so a US company filing first at home on work its India-based engineer invented is the exact fact pattern the section catches. The detail sits in our R&D centers guide linked earlier.

Never saying who owns pre-existing background IP

Your engineer arrives with libraries, tooling and prior work. Your contract almost certainly says nothing about it, which means the boundary between what you bought and what they brought is undefined.

Name the background IP, grant yourself a licence to whatever is embedded in the deliverable, and assign only what was created for you.

Pro tip: Make the assignment clause name the deliverable categories your engineers actually produce, not "all intellectual property". Source code, CAD and design files, firmware, schematics, test fixtures, and documentation, each named. Section 19 requires an assignment to identify the work and the rights assigned, and a generic catch-all is the clause that gets argued about when a relationship ends badly.

The first failure on that list is the expensive one, and if you are unsure where an existing engagement sits, our two-minute misclassification check will tell you which side of the line you are on before a tax officer does.

How do you find and screen engineers in India?

Most global employers who hire engineers in India source through three channels: a recruitment partner, direct outbound, and referral from engineers already on the team. Screening then splits into technical assessment, which you own, and verification, which you should not skip. The legal work above only matters once you have someone to sign it.

Where engineering talent concentrates

Bangalore and Hyderabad carry the largest software and product engineering pools, with Pune, Chennai, the Delhi NCR region and Ahmedabad adding depth in specific disciplines. Embedded, data, AI, mechanical and electrical engineering do not distribute evenly across those cities.

Our comparison of Bangalore and Hyderabad for engineering teams covers cost, depth and attrition differences between the two largest hubs.

What the hiring timeline looks like

Notice periods in India are longer than most US employers expect, and they are the single biggest driver of time to start. Plan around the offer-to-join gap rather than the interview loop. Our breakdown of how long hiring in India actually takes sets out the stage-by-stage view.

Screening, including verification

Run your technical assessment the way you run it at home. Add employment-history verification before the offer is confirmed, for the reason set out in the moonlighting section above.

What it costs to model

We do not publish engineering salary bands, and that is deliberate. The figures circulating on aggregator and resume sites are not sourced well enough to plan a budget on, and we would rather give you a method than a number.

Model the fully loaded figure instead. Total cost is salary plus statutory employer contributions, benefits, equipment and your provider fee, and CTC, roughly the Indian equivalent of total compensation, is the number a candidate will negotiate on.

Two tools do this properly: our employee cost calculator for the fully loaded employer figure, and our India salary calculator for the gross-to-net view a candidate will ask about.

If your first hires are software engineers specifically, our guide to hiring remote developers in India covers the sourcing channels in more detail than this section can.

What do global employers ask most about hiring engineers in India?

These five come up in almost every first call we take. Short answers, in the order they usually arrive.

Does India have a law against moonlighting?

No. There is no dedicated anti-moonlighting statute in India. What you can enforce comes from your own contract, read against Section 27 of the Contract Act 1872, which is why the exclusivity and disclosure wording matters more here than it would at home.

Who owns the code my India contractor writes?

The contractor does, until a written assignment moves it. A contractor engagement is a contract for service, so copyright starts with the creator. No default transfers it to you, and an NDA alone will not either.

Can I make an Indian employee sign a non-compete?

You can put one in the contract, but a restraint operating after employment ends is void under Section 27. During the employment, a reasonable exclusivity obligation is a different matter and generally holds. Draft the two clauses separately.

Can I put my India engineering contract under US law?

For a vendor or genuine contractor agreement, yes. For an employment relationship, the choice does not remove Indian statutory protections or Indian labour forums, and the applicable state Shops and Establishments Act still governs the workplace.

Do I need a background check before hiring an engineer in India?

Nothing compels it, but we recommend it on every hire and we run it before the start date. Employment-history verification against the provident-fund record is where undisclosed concurrent work surfaces, and pre-hire is the only point where acting on it is simple.

How does Wisemonk help you hire engineering talent in India?

Wisemonk is an India-native Employer of Record. We help global companies hire, pay and manage engineering teams in India without setting up a local entity, and we support the employment and hiring side of these routes for teams in India.

More than 300 global companies work with us. We manage over 2,000 EOR employees, process $20M+ in payroll, and hold a 4.8/5 rating on G2.

What we cover for an engineering hire:

• Employer of Record: we become the legal employer in India, from the compliant employment contract and IP assignment through payroll, statutory filings and exit, with equipment procurement and shipping available as an add-on. From $99 per employee per month.
• Recruitment and TalentScout: free India hiring software through your first several hires, then usage credits with no subscription and no per-seat fee. Recruiter-assisted sourcing is contingent and paid on joining, and our recruitment concierge is 10% of annual salary with no upfront cost and a 90 day placement guarantee.
• Background verification: 19 check types across identity, employment, education, court records and moonlighting, with a basic check back in about five minutes. Our standard package starts at $50 per candidate, as of September 2026.
• Contractor of Record: we become the legal contracting party for your Indian contractors, with compliant agreements, IP assignment, classification memos and payouts, at 6% per contractor payment, as of September 2026.
• GCC and capability centre setup: stand up and staff an India capability centre, from operating model through hiring to run-state, on a custom quote.

That combination is what an engineering hire actually needs: someone to find the person, someone to check them, and someone to employ them compliantly.

Hear from industry leaders

I'm very Happy that I discovered Wisemonk. They have been a pure pleasure to work with, and their attention to detail is impressive. They helped us understand their pricing model, find top-qualified individuals, interview them, and then onboard them. I gave them criteria for the type of people we sought, and they delivered. The individuals they were able to find have been some of the best engineers I have ever worked with. I recommend Wisemonk to anyone who is in need of staffing assistance.
- Dan Sampson, Head of Engineering at Cobu, USA