.png)
Why Norway Companies Use Employer of Record (EOR) in India
Updated: Aug 15
A software engineer we placed for an Oslo fintech was live on payroll, legally, with tax deducted at source in India and a compliant contract on file, nine working days after the client approved the candidate. No Norwegian entity was opened. No local company registration was filed. That timeline is a big part of why Norway companies use Employer of Record (EOR) in India: it removes the long entity setup runway that used to sit between finding the right person and actually getting them working.
Why Are Norwegian Companies Turning to EOR Hiring in India?
Norway has one of the tightest tech labour markets in Europe relative to its population. Oslo's product and fintech scene, companies building on Vipps and DNB's open banking APIs, has been hiring aggressively, and Stavanger's energy sector has been pulling senior cloud and data engineers into subsea digitalisation and industrial IoT projects. Both are competing for the same small pool of people.
A mid level backend or cloud engineer in Oslo takes, in our experience helping clients think through this, anywhere from 10 to 16 weeks to close through a purely local search, and salary expectations have moved up sharply as companies bid against each other for the same shortlist. Two separate Norwegian clients told us, almost in the same words, that they had budget approved and a role open, but the local search wasn't producing candidates fast enough to hit their product roadmap.
That gap is why Norwegian companies are looking at India, not purely as a cost play, but as a talent availability play. It's also shifting with the wider market: as AI tooling changes how much output a single engineer can ship, Norwegian teams increasingly want engineers who are strong at systems thinking and cloud infrastructure rather than just raw coding speed, and that's exactly where India's larger, deeper engineering pool has an edge simply through scale. Bengaluru alone produces more engineers with several years of production cloud experience each year than Norway's entire tech workforce turns over.
The real obstacle historically wasn't finding the talent. It was employing it legally without opening a Norwegian registered entity, or relying on informal freelance arrangements that don't hold up under Norwegian or Indian labour law. This is where Employer of Record (EOR) structures solve a problem that plain contract hiring alone can't. An EOR lets the Norwegian company direct the work while a locally compliant entity in India handles the legal employment relationship, statutory contributions, and payroll, with no Norwegian entity required if the engineer is based and working from India.
Which Indian Cities Have the Right Talent for Norwegian Hiring Needs?
For Norwegian companies hiring through EOR, four Indian cities cover almost every mandate we run, and they aren't interchangeable.
Bengaluru has the deepest bench for cloud infrastructure, backend, and platform engineering, the profile Norwegian fintech and SaaS companies ask for most. Engineers here have typically worked at scale on AWS or GCP, often inside Indian unicorns or global capability centres for European and US banks, so they've already operated in compliance heavy environments before we place them with a Norwegian client.
Hyderabad has the strongest data engineering and analytics talent, driven by the concentration of GCCs for financial services and pharma companies that run large internal data platforms there. If a Norwegian mandate is built around data pipelines, Kafka, or AI and machine learning infrastructure, Hyderabad candidates usually shortlist faster.
Pune produces strong full stack and enterprise Java talent with a manufacturing and fintech client base, and Delhi NCR gives us breadth across DevOps and site reliability engineering, largely because so many US and European IT services firms run delivery centres there.
This is one reason Norway companies use Employer of Record (EOR) in India as their first move rather than a last resort: it lets them tap this deeper talent pool immediately instead of waiting months for a local search to produce results.
What Indian engineers consistently bring to a Norway focused mandate is strong fundamentals in distributed systems and cloud native architecture. Most candidates we shortlist have already worked on production systems handling meaningfully higher transaction volumes than a typical Norwegian domestic product sees, simply because Indian engineering teams are often built around scale from day one.
What they typically lack, and where Norwegian clients get burned if a recruiter doesn't test for it, is exposure to how Norwegian and broader Nordic teams actually work: flat decision making, low context written communication, and a strong expectation of individual ownership without daily check ins.
We run a structured async communication assessment as part of every technical round for Norwegian mandates, a short written technical brief the candidate has to produce and defend on video without live prompting, because this trait determines whether someone thrives on a Norwegian team months in, not just whether they can pass a coding test.
What Does Arbeidsmiljøloven Mean for Norway Companies Using Employer of Record (EOR) in India?
Norway's employment relationship is governed by the Arbeidsmiljøloven, the Working Environment Act, usually shortened to AML. It's mandatory law, meaning its protections can't be waived by contract even if both parties agree to different terms. If an engineer's habitual place of work is treated as falling under Norwegian jurisdiction, AML protections apply regardless of what the contract says or where the parent company is registered.
Two details make this especially relevant right now. Recent amendments to the AML tightened dismissal procedures, shortened written contract deadlines, and added new duties specifically for foreign employers and employer of record arrangements. Alongside that, a presumption rule means a worker is now treated as an employee, not an independent contractor, unless the engaging company can show it's highly likely a genuine contractor relationship exists. Administrative fines for getting this wrong can now reach the equivalent of roughly EUR 597,000, or 4% of the company's annual turnover, whichever is higher.
The mistake we see most often: a Norwegian founder or engineering lead engages an Indian developer directly on an invoice based, "independent contractor" arrangement to move fast, without realising that if the working relationship looks like employment (fixed hours, exclusive engagement, direction over how the work gets done), Norwegian and Indian authorities can both reclassify it. That exposes the company to back pay claims and statutory contribution liabilities.
This is exactly why Norway companies use Employer of Record (EOR) in India rather than trying to manage cross border employment directly. The Indian EOR entity becomes the legal employer of record, runs statutory PF, ESI, and gratuity contributions correctly, issues a compliant offer letter and payslip, and the Norwegian company signs a services agreement with the EOR instead of attempting to directly employ someone across a border where it has no registered presence. It's the same logic that makes payroll outsourcing the practical answer to cross border payroll compliance rather than running it manually from Oslo.
Curious whether your team should structure this as EOR, contract, or a full entity? Talk to our hiring team here.
EOR, Contract Hiring, or Full-Time Hiring in India: What Should Norwegian Companies Choose?
This comes up in nearly every first call with a Norwegian client, so it's worth explaining plainly. Contract hiring means engaging someone for a defined project or fixed period, usually through an agency or an EOR, without the long term commitments of permanent employment. It works well for a specific product sprint, a migration project, or filling a skills gap for a few months. Full-time hiring means bringing someone on as a permanent employee with ongoing statutory benefits, notice periods, and long term commitment on both sides. It's the right call once a role is core to the team's roadmap rather than tied to a single deliverable.
Most Norwegian companies we work with start with contract hiring through EOR to test fit and pace before converting strong performers to full-time roles within the same India based team, without any disruption to the person's day to day work, since the EOR already holds a compliant employment relationship either way.
This table and use it in your own internal decision memo.
Factor | Direct Contractor (Invoice-based) | Employer of Record (EOR) | Own Entity in India |
Time to first hire | 1 to 2 weeks | 2 to 3 weeks | 4 to 8 months |
Upfront cost | Near zero | Setup fee only | NOK 300,000 to 600,000+ in legal, registration, and compliance setup |
Norway AML reclassification risk | High, misclassification exposure | None, India entity is legal employer | None |
Statutory compliance (PF, ESI, gratuity) | Not handled, a liability gap | Fully managed by the EOR | Company must build its own HR and compliance function |
Best for | A single short term freelance task | 1 to 30 engineers, ongoing roles | 30+ engineers, a multi year India strategy |
Exit flexibility | Simple but legally exposed | Clean offboarding, EOR handles termination compliance | Requires formal entity wind down if scaling back |
Who signs the employment contract | Nobody, legally ambiguous | The Indian EOR entity | The Norwegian company's own Indian subsidiary |
For most Norwegian companies hiring their first 1 to 15 engineers in India, EOR is the only option here that removes both the Norwegian AML exposure and the Indian compliance burden at the same time, which is exactly why it's become the default rather than a stopgap. Companies that outgrow it, typically once they're running a genuine GCC style engineering centre of 40 or more people, eventually convert to their own entity, but almost never start there.
How Does the EOR Hiring Process Actually Work for Norwegian Companies?
Our standard timeline for a Norwegian EOR mandate is 3 to 5 business days from shortlist to signed offer once the client approves a candidate, and typically 3 to 5 weeks total from kickoff to the engineer's start date, including technical vetting. Technical assessment runs in two stages: a take home exercise scoped to the actual stack rather than a generic algorithm test, followed by a live system design conversation with one of our senior technical assessors, someone with real production experience in the relevant domain rather than a generalist recruiter reading off a script.
One case worth walking through, anonymised: a mid sized Oslo based B2B SaaS company, roughly 60 employees, Series B funded, needed three backend engineers inside six weeks to hit a contractual product deadline with a Nordic banking client. We shortlisted and closed all three within 18 working days through EOR using our Bengaluru and Pune networks.
What almost went wrong: the client's initial job description didn't specify that the role required direct client facing calls with the bank's own engineering team, and our first shortlist, strong technically, included two candidates who showed clear discomfort working without a translator or intermediary in high stakes client conversations during our async communication assessment.
We flagged it before final selection, re-ran the shortlist with the client facing requirement explicit, and closed with three engineers who'd already worked directly with European clients. The client hit their deadline with four days to spare, and all three engineers are still on the account well over a year later.
This is also where the contract versus full-time question gets tested in real time. All three engineers on that account started as contract hires through EOR for the initial project, and two later converted to full-time roles once the engagement extended into ongoing product work, a common pattern we see once a Norwegian client confirms a role is permanent rather than project bound.
That's the value an experienced international recruitment firm adds over a generic freelance marketplace: catching the mismatch a resume and a coding test won't show you. AnjuSmriti Global has built this exact playbook specifically around Nordic hiring patterns, not adapted from a generic global template.
What Does It Actually Cost to Hire Through EOR in India?
Here's the honest cost comparison, using current market data for Norway based engineers against India based EOR engineers at equivalent seniority.
Level | Norway based salary (gross annual) | India EOR total cost (salary + statutory contributions + EOR fee) |
Mid level (3 to 5 yrs) | NOK 750,000 to 950,000 | Equivalent of NOK 260,000 to 340,000 |
Senior (6 to 9 yrs) | NOK 950,000 to 1,200,000 | Equivalent of NOK 340,000 to 460,000 |
Lead or Architect | NOK 1,100,000 to 1,500,000 | Equivalent of NOK 460,000 to 620,000 |
The India EOR total cost figure includes the engineer's India market salary, employer side PF and gratuity contributions, and our agency and EOR management fee combined, not a bare salary number, which is where most cost comparisons go wrong. Clients don't typically pocket the difference.
The Norwegian companies we work with almost always reinvest it into hiring a second or third engineer in the same India based pod, so a budget set aside for one senior Norway based hire often funds a two or three person distributed team instead.
Conclusion
Over the coming months, we expect the tightened AML obligations on foreign employers and EOR arrangements to push more Norwegian companies away from informal contractor setups and firmly toward structured EOR partnerships, simply because the compliance risk of getting it wrong has gone up.
In live mandates right now, we're also seeing a shift in what Norwegian clients ask for: fewer one off contractor requests, more requests for small standing pods of three to six engineers they intend to keep for years, along with growing interest in AI and cloud infrastructure specialists as Norwegian product teams rebuild around AI assisted development workflows.
Ready to talk through your specific hiring plan? Start the conversation with our team here.
Interesting Reads:
FAQs
1.Does Norway's Arbeidsmiljøloven apply to an engineer employed through an Indian EOR?
Not directly. The AML governs employment where Norway is the place of work, so an India based engineer employed by the Indian EOR entity falls under Indian labour law for day to day employment. The AML becomes relevant only if the arrangement is structured loosely enough that Norwegian authorities could argue the Norwegian company itself, not the EOR, is the real employer.
2.Which Norwegian industries currently hire the most India based engineering talent?
Fintech and banking adjacent SaaS out of Oslo lead by volume, driven by companies building on Vipps and open banking infrastructure. Energy tech and industrial digitalisation firms out of Stavanger are close behind, typically hiring data engineers and IoT platform specialists tied to subsea and offshore digitalisation. Trondheim based deep tech and research spinouts add smaller but steady demand too.
3.How do Norwegian companies handle IP ownership when hiring through an Indian EOR?
IP assignment works at two levels. The Indian EOR's employment contract assigns work product to the employer of record under Indian law, and the separate services agreement between the Norwegian company and the EOR assigns all resulting IP to the Norwegian company. Done correctly, this gives the Norwegian company clean ownership without needing the individual engineer to sign anything directly with a foreign entity.
4.Is it cheaper to set up an entity in India instead of using EOR?
Only past a certain scale. A compliant Indian subsidiary typically costs the equivalent of NOK 300,000 to 600,000 upfront in legal and registration work, plus an ongoing HR and finance function. Below roughly 25 to 30 engineers, that fixed cost isn't recovered by the marginal savings over an EOR's per employee fee, which is why most companies convert only after they cross that headcount.
5.Can a Norwegian company terminate an engineer hired through Indian EOR without following Norwegian dismissal rules?
Yes, provided the engineer is genuinely employed by the Indian EOR under Indian labour law. Norwegian dismissal procedures under the AML, including the objective justification requirement, don't apply to that employment relationship. Termination follows Indian employment law and the EOR's contract terms instead, which tends to be faster and less procedurally heavy than a Norwegian dismissal process.
6.What happens if an EOR employed engineer later relocates to Norway?
This triggers a separate process. Bringing the engineer onto Norwegian soil as a direct hire typically requires a Norwegian work permit application and a new Norwegian employment contract, which then falls fully under the AML. The original EOR arrangement doesn't carry over legally, it's effectively treated as a new hire, though the working relationship and track record carry over informally.
7.How does Norway's recent Working Environment Act update affect EOR structures?
The latest amendments explicitly extended obligations to foreign employers and EOR arrangements, tightening how dismissal procedures, HSE card requirements, and written contract deadlines apply when a Norwegian company engages labour through an intermediary. In practice, Norwegian companies now carry more direct responsibility for verifying their EOR partner's compliance quality than before, it's no longer purely the EOR's problem if something is done incorrectly.
8.What's the realistic timezone overlap between Oslo and Indian tech hubs?
India runs 3.5 to 4.5 hours ahead of Norway depending on the season. That gives roughly 4 to 5 hours of comfortable overlap in the Norwegian morning and Indian afternoon, typically 9:00 AM to 1:30 PM CET, or 1:30 PM to 6:00 PM IST. Most Norwegian clients schedule stand ups and client calls inside this window and rely on async written updates outside it.
Comments