.png)
Can a UK Company Hire Indian Software Engineers Without PE Risk
- Saransh Garg
- 4 days ago
- 9 min read
We get asked this question on almost every UK call we take, usually right after a founder has already found the engineer they want in Bengaluru or Pune. The honest answer is that a UK company hire Indian software engineers without PE risk approach is entirely achievable, and it does not need a subsidiary. What it needs is a clear read of Section 9 of India's Income tax Act, 1961, and Article 5 of the India UK Double Taxation Avoidance Agreement, the two provisions that decide whether Indian tax authorities can treat your UK company as having a taxable presence in India. Get the structure wrong, and one engineer with contract signing authority can put your company's global profits inside Indian corporate tax.
Why Are So Many UK Companies Hiring Software Engineers in India Right Now
A senior software engineer in London typically costs a UK company somewhere between £70,000 and £120,000 in base salary alone, before employer National Insurance, pension contributions, and the overhead of running a compliant payroll. For a bootstrapped or early stage company trying to ship a platform on a tight budget, one hire like that can consume a large share of the runway.
At the same time, London's engineering market has tightened noticeably. Senior and staff level candidates with production Kubernetes, distributed systems, or AI infrastructure experience are fielding multiple offers, and mid sized fintechs regularly lose candidates to counter offers in the final week of an offer process. This is what pushes most UK founders to look seriously at Bengaluru, Hyderabad, or Pune, not as a fallback, but as the only realistic way to build a senior engineering team on a Series A budget.
The gap is that most founders' due diligence stops at cost and never reaches the compliance question. We have sat with UK clients who signed a straightforward contractor agreement with an Indian engineer, had that engineer working full time and exclusively on UK facing infrastructure for over a year, and only realised the contractual hiring arrangement had drifted into employee like territory when an auditor flagged it during a funding round. That drift, not the hiring itself, is what creates PE exposure.
Which Indian Cities Have the Deepest Software Engineering Talent for UK Teams
Bengaluru has overtaken Hyderabad as India's leading city for software engineering talent, largely on the back of Global Capability Center (GCC) concentration, according to Karat's Top Cities to Hire Software Engineers report. Bengaluru now holds the deepest bench for backend, cloud native, and platform engineering roles, while Hyderabad and Pune remain strong for enterprise grade Java and fintech engineering, and Chennai continues to produce solid QA and embedded systems talent.
For a UK company hiring remotely, this matters more than it looks. At AnjuSmriti Global, we consistently find that engineers who have spent a few years inside a GCC serving UK or US clients already understand asynchronous handoffs, London hours stand ups run at Indian evening time, and the documentation discipline distributed teams depend on. What Indian engineers under index on for UK facing roles is rarely technical depth.
It is proactive escalation. Engineers trained inside large, hierarchical organisations are often reluctant to flag a blocked ticket to a UK product owner until it is already late, so we test for this directly with a live scenario interview where the candidate has to decide, unprompted, when to escalate an ambiguous requirement.
How Can a UK Company Hire Indian Software Engineers Without PE Risk
A UK company hire Indian software engineers without PE risk strategy has to be built around three specific triggers: fixed place PE (a dedicated, continuously available business location in India), service PE (personnel present or performing services in India beyond roughly ninety days in a twelve month window under most treaty readings), and dependent agent PE (an India based person who habitually concludes contracts, negotiates commercial terms, or binds the UK company).
Software engineers rarely trigger dependent agent PE through code alone. They trigger it when the role quietly expands, when a senior engineer starts discussing scope changes directly with a UK client, agreeing pricing on a call, or signing off on a statement of work. This is where the line between contract hiring and full time hiring actually matters. A genuine contractor engagement is deliverable based, non exclusive, and free of day to day supervision.
A full time employment relationship, even one dressed up as a contractor agreement, involves fixed hours, exclusivity, company issued equipment, and ongoing direction, and Indian labour and tax authorities will reclassify it accordingly, regardless of what the paperwork says.
The most common mistake we see is assuming a well drafted contractor agreement is protection on its own. It is not. An Employer of Record (EOR) sidesteps this because the EOR, not the UK company, is the Indian legal employer for tax and labour purposes, which is the cleanest way we have found to keep a UK company hire Indian software engineers without PE risk arrangement intact as headcount grows past one or two people.
PE Risk Checklist: Is Your India Hiring Structure Actually Safe
Run your current setup against this table before your next offer letter goes out. It is built directly from the risk patterns we screen for on every UK mandate.
Risk factor | Low PE risk | High PE risk |
Legal employer of record | Indian EOR or licensed Indian entity | UK company pays the engineer directly |
Contract authority | Zero authority to negotiate or sign client contracts | Engineer discusses pricing, scope, or SOWs with clients directly |
Work location | Home based, no dedicated UK leased office in India | UK company leases or maintains a fixed India office |
Engagement type | Genuine contract hiring, deliverable based, multiple clients | Effectively full time hiring dressed as a contract, fixed hours, one client |
UK staff visits to India | Occasional, well under the treaty day threshold | Frequent, recurring supervisory or sales trips |
Equipment and tools | Contractor uses own equipment or EOR issued assets | UK company issues and controls all hardware directly |
Two or more boxes in the right hand column is the exact fact pattern that has supported dependent agent PE assessments in the past. If that describes your current India hiring structure, it is worth a proper treaty position review before the team grows further.
Our Process, a Named Framework, and What Nearly Went Wrong
Every UK mandate we take on starts with what we call the 3 Layer PE Shield. We map contract authority first, then engagement structure (EOR, direct, or genuine contract hiring), and only then start technical vetting. Founders are often surprised legal structure comes before the interview loop, but doing it in the wrong order is how companies end up rebuilding a working relationship six months in.
Here is one scenario, details anonymised. A UK headquartered fintech, roughly twenty five people, had hired two backend engineers in Pune directly as contractors for close to a year before coming to us. Both were full time, exclusive, using company issued laptops, and one had started answering a UK enterprise customer's questions about API rate limits directly over email, effectively negotiating technical terms of service.
That single detail put the company one step from a dependent agent PE argument. We moved both engineers onto an EOR structure within three weeks and rerouted all commercial communication through the UK product manager. The company's own auditors later estimated the exposure they avoided at a six figure retrospective tax and penalty bill. Across our recent UK mandates, this exact pattern, a contractor drifting into client facing territory, has shown up in roughly one in seven, which is why the contract authority check now runs before we shortlist a single resume.
What we would do differently looking back: early on we treated PE risk as a one time check done at the offer stage. We since learned authority can drift months into a role as good engineers get handed more responsibility, so we now run a light authority recheck at the six month mark of every UK to India placement, not only at hiring.
How Much Does It Cost to Hire Indian Software Engineers vs UK Engineers
Current UK compensation data from Glassdoor and PayScale puts a mid level software engineer (three to five years) at roughly £45,000 to £65,000 in base salary, a senior engineer (five to eight years) at £70,000 to £95,000, and a lead or staff engineer at £85,000 to £120,000 or more, before employer National Insurance and pension contributions.
For the same three bands, hiring through an Indian EOR in Bengaluru or Pune typically runs ₹18 to 28 lakh per year for mid level (roughly £17,000 to £26,000), ₹32 to 48 lakh for senior (roughly £30,000 to £45,000), and ₹55 to 85 lakh for lead or staff engineers with architecture ownership (roughly £52,000 to £80,000).
Add India employer side EPF contributions at twelve percent of basic, the fee for global payroll outsourcing through the EOR (commonly eight to fifteen percent of gross salary), and our agency placement fee, and the fully loaded cost for a senior engineer through this structure still lands roughly 35 to 45 percent below the equivalent UK hire. Most clients reinvest that gap into a second engineer or a UK based product or sales hire they could not otherwise afford yet.
Worth stating plainly: contract hiring through an EOR and full time hiring through an Indian subsidiary solve different problems. Contract hiring suits a single role or a short term build, while full time hiring through a subsidiary makes sense once a team crosses roughly ten to fifteen engineers and the entity cost starts paying for itself.
What's Actually Changing in UK to India Tech Hiring Right Now
We are seeing more UK Series A and B companies specifically ask for EOR first structures from day one, rather than starting with contractors and migrating later, because founders now hear about PE risk before their first India hire rather than after.
On the technical side, the role itself is shifting. Pure DevOps and backend mandates are increasingly folded into platform engineering briefs, where UK clients want one senior hire who owns internal developer tooling and AI assisted delivery pipelines, not just deployments. Indian engineers are responding by picking up platform engineering and cloud native certifications faster than before, alongside sharper written and verbal communication preparation aimed specifically at UK stakeholder management.
Conclusion
A UK company hire Indian software engineers without PE risk approach is not a legal grey area to work around quietly. It is a solvable structuring problem, provided the legal employer, contract authority, and engagement pattern are set correctly before the first offer letter goes out. We expect more UK founders to build India engineering teams through an EOR from day one rather than retrofitting compliance after the fact, and in our live mandates right now, that is already the majority pattern among new UK clients.
If you are weighing a first India hire, or already have contractors whose roles have quietly expanded, it is worth a structural review before your next funding round's due diligence finds it first. Talk to our team here.
Interesting Reads:
FAQs
1.Does hiring an Indian software engineer through an EOR fully remove PE risk for a UK company?
An EOR removes the most common trigger by making the EOR, not the UK company, the Indian legal employer, but it does not remove risk entirely. If the engineer later gains authority to negotiate or sign client contracts, dependent agent PE exposure can still arise regardless of who runs payroll, which is why contract authority mapping matters as much as the EOR structure itself.
2.Do UK IR35 rules apply to Indian contractors hired by a UK company?
No, IR35's off payroll working rules generally do not apply to a worker who is non UK resident and performs all duties outside the UK, since HMRC treats them as outside UK income tax and National Insurance scope. What actually governs the relationship is Indian labour law and the India UK treaty's Permanent Establishment test, not the UK contractor rules most founders assume apply.
3.How many days can UK staff visit India before creating a service Permanent Establishment?
Most treaty readings place the threshold at roughly ninety aggregate days within any twelve month period, though this depends on treaty interpretation and the activity involved. Days are usually counted across all UK personnel combined, not per individual visitor, so several employees taking shorter trips can still cross the threshold faster than a founder expects.
4.Can one Indian software engineer really trigger Permanent Establishment for a UK company?
Yes, a single engineer can trigger dependent agent PE if they habitually conclude contracts, negotiate pricing, or bind the UK company commercially, even without a formal sales title. Job titles do not determine PE exposure, actual conduct does, which is why engineers who move into client facing technical work need a specific authority review, not just a payroll review.
5.What is the real difference between contract hiring and full time hiring an Indian engineer?
Contract hiring is deliverable based, non exclusive, and free of day to day supervision, while full time hiring involves fixed hours, exclusivity, and ongoing direction, whether or not the paperwork calls it a contract. Indian authorities look at actual conduct rather than the label, so a contractor who works exactly like an employee gets treated as one.
6.Is it cheaper to hire Indian software engineers directly or through an Employer of Record?
Direct hiring looks marginally cheaper because it skips the EOR fee, but it exposes the UK company to PE risk, misclassification penalties, and the administrative load of Indian statutory compliance with no local entity behind it. Once potential backdated liabilities are priced in, an EOR is typically cheaper on a risk adjusted basis for anything beyond one or two hires.
7.Which Indian cities have the strongest software engineering talent for UK facing roles?
Bengaluru currently holds the deepest bench for cloud native and platform engineering talent, driven largely by Global Capability Centers concentration, with Pune and Hyderabad close behind for enterprise and fintech adjacent engineering. Chennai remains strong for QA and embedded systems roles, so the right city depends on the specific engineering discipline being hired for.
8.What should a UK company do if its India contractors have started doing client facing work?
The first step is an authority audit, reviewing exactly what commercial decisions, if any, the contractor has been making on the company's behalf, since that determines whether PE risk exists today, not just at hiring. Most cases are fixed by restructuring who owns client communication and migrating the contractor onto a compliant EOR arrangement rather than ending a working relationship that is otherwise going well.
Comments