A Nine-step Guide, from Job Description to Day One
The strongest backend engineer you’ll interview this quarter may live in Pune. She has three competing offers, a 90-day notice period, and a recruiter from a Bengaluru Global Capability Center messaging her every week. Whether she joins your team depends less on your salary band than on the next 21 days of your process.
That’s the part most guides skip. They explain why US startups are building in India, then stop just before the hard part: choosing a legal structure, pricing the role against the right market, running interviews that survive competing offers, and getting a compliant employee to Day One.
This guide covers all of it. Whether you want to hire developers in India for a first engineering pod or add a senior specialist to an existing team, the nine steps below take you from a blank job description to a working engineer, without opening an Indian company.
First, Pick the Legal Model: Three Ways to Hire Employees in India
A US company has three legal routes to hire employees in India. The right one depends on how many people you need, how long you’ll keep them, and how much Indian compliance you’re prepared to own.
Independent contractor | Employer of Record (EOR) | Your own Indian entity | |
|---|---|---|---|
Who Legally Employs them | Nobody — they invoice you | The EOR's Indian entity | Your Indian subsidiary |
Time to a working hire | Days | Days, once a candidate accepts | 3–6 months to incorporate and register |
Compliance you own | Classification risk | None — the EOR files PF, ESI, TDS | All of it: payroll, filings, audits |
Best for | Short, defined projects | Teams of 1 to roughly 20–30 | Large, long-term teams |
Main risk | Reclassification as an employee | Choosing a weak provider | Cost and time before the first hire |
Contractors look simplest, and for a genuine six-week project they are. But Indian authorities judge the working relationship, not the contract label. A developer with fixed hours, your equipment, and a manager on your team looks like an employee, and reclassification brings backdated Provident Fund, ESI, and gratuity with damages on top.
A contractor can still be the right call for a fixed-scope build with a clear end date, a specialist brought in for a few weeks of review, or a trial project before an offer. The test is simple: if you would be uncomfortable explaining the arrangement to an Indian labour inspector or to an investor’s counsel, it’s employment and should be structured as such.
For most startups, an employer of record India arrangement is the practical middle path. The EOR is the legal employer on paper and handles Indian payroll and compliance; you choose the person, direct the work, and own what they build. Once your team grows past 20–30 people, compare EOR vs setting up your own entity on total cost and control.
Step 1: Define the Role Around Your Time Zone
India Standard Time runs 9.5 to 13.5 hours ahead of US time zones, depending on your coast and daylight saving. That gap is a feature if you design for it and a daily frustration if you don’t.
Before writing a job description, decide how much live overlap the role actually needs:
- Async-first roles (backend services, data pipelines, QA automation, infrastructure) thrive on a handoff rhythm. Your team closes the day with a spec or a failing test; India picks it up and ships while you sleep.
- Collaboration-heavy roles (product engineering on a fast-changing UI, early-stage architecture) need two to three shared hours. Agree on a shifted schedule up front, such as India working 12 pm to 9 pm IST, rather than negotiating it after the offer.
- Ownership level: say clearly whether the engineer will own a service end to end or execute tickets. The strongest candidates in India are screening for ownership as hard as you are screening for skill.
Then write the job description for the Indian market. List the specific problems the engineer will solve in the first six months, the tools they’ll use, and who they’ll work with in the US. Say whether the role is remote or tied to a city, and state the working-hour expectations plainly. Vague descriptions attract hundreds of applicants and few strong ones; specific ones attract fewer, better candidates who have already decided the role fits.
Step 2: Choose Your City and Your Employment Partner
India’s developer talent is concentrated, and each hub has a different depth of skills. Matching the role to the city shortens sourcing more than any job board will.
City | Strongest For |
|---|---|
Bengaluru | Product engineering, AI/ML, SaaS — the deepest senior pool and the most competition for it |
Hyderabad | Cloud, DevOps, data engineering, enterprise-grade talent |
Pune | Backend, QA automation, experienced product managers |
Chennai | B2B SaaS, embedded, infrastructure — less competition, strong retention |
Delhi NCR | Consumer internet, growth engineering |
Remote / Tier-2 | Coimbatore, Indore, Kochi and similar — lower cost, rising quality, well suited to remote roles |
Many startups now hire remote developers in India without tying the role to one city at all, which widens the pool considerably. Your EOR handles state-specific obligations such as Professional Tax wherever the engineer lives.
This is also the moment to choose your EOR, before you have a candidate waiting. Entity ownership, contract terms, and exit costs vary widely between providers; our 12 questions to ask before signing with an EOR cover what to check.
Step 3: Benchmark Pay Against the Right Market
The most common pricing mistake is benchmarking against India’s national average. Aggregators put the typical software engineer salary around ₹9-12 lakh a year (Instahyre), but that average is weighted by large IT services firms. The engineers a funded startup competes for are benchmarked against product companies and GCCs, which pay several times more.
Level (product-company market) | Annual CTC (INR) | Approx. USD |
|---|---|---|
Junior (1–3 years) | ₹8–15 lakh | $9K–$16K |
Mid-level (3–5 years) | ₹12–25 lakh | $13K–$27K |
Senior (5–8 years) | ₹25–45 lakh | $27K–$48K |
Lead / Architect (8+ years) | ₹40–70 lakh+ | $43K–$75K+ |
Bands compiled from 2026 salary data (Instahyre, Hyring, Persol India) for product companies and GCCs. Bengaluru sits at the top of each band; Tier-2 cities run 15–30% lower. Converted at ₹93 = $1. CTC excludes EOR fees.
For a reference point, Bengaluru’s median software engineer earns about ₹14.5 lakh a year across all levels, with the 75th percentile near ₹24.7 lakh (Hyring). AI and ML specialists command a clear premium over general software roles.
CTC is also not your total bill. Add employer statutory contributions, benefits, and the EOR fee to get the full cost of employment in India, or run the numbers through our EOR cost calculator.
Step 4: Source Candidates Where Indian Developers Actually Look
To Hire software developers in India well, go where they already are. The channels differ from the US:
- LinkedIn works well for senior and product-company talent, especially with a founder-sent message rather than a recruiter template.
- Naukri, India’s largest job board, brings volume. Expect to screen heavily.
- Instahyre and Cutshort focus on tech roles and tend to surface stronger product-company profiles.
- Wellfound reaches engineers who specifically want startup work.
- Referrals and communities (GitHub contributors, local meetups, open-source projects) produce the best hit rate once your first hire is in place.
- A recruitment partner with India reach saves the most time for senior or niche roles.
When screening profiles, look past titles. “Senior” means different things at a services firm and at a product company, so weigh what the person actually shipped, the scale of the systems they worked on, and how clearly they explain their own decisions. Written communication matters as much as code for a remote engineer; a short written question early in the process tells you a great deal.
Whichever channel you use, lead with the problem the engineer will own, not the stack alone. Indian developers weighing a US startup against a stable GCC want to know why this role is worth the move.
Step 5: Run an Interview Process That Survives Competing Offers
Good candidates in Bengaluru and Pune routinely hold two to four offers. A four-week, six-round process loses them to whoever moves first. When you hire Indian developers, speed is part of the offer.
- Cap the process at about three weeks from first call to offer.
- Keep it to three or four stages: intro call, technical screen, a practical exercise, and a final conversation with a founder.
- Make the exercise respectful: a live pairing session or a short, clearly scoped take-home. Multi-day unpaid assignments drive away the candidates you most want.
- Schedule inside Indian working hours. A 7 am US Pacific slot is 7:30 pm in India, which is reasonable. A 4 pm Pacific slot is 4:30 am, which isn’t.
- Decide within 48 hours of the final round, and call rather than email.
The best signal is a short working session on a real problem from your codebase, run the way you’d actually collaborate. It tests async communication and ownership, the two things that decide whether a remote engineer thrives. |
Step 6: Build an Offer That Holds Up
An Indian offer letter has more moving parts than a US one, and getting the structure wrong creates liability later.
Structure the salary correctly
Since India’s Labour Codes took effect on 21 November 2025, the Code on Wages defines wages as basic pay, dearness allowance, and retaining allowance. If excluded components such as HRA, conveyance, and employer PF contributions together exceed 50% of total remuneration, the excess is added back to wages for gratuity and other statutory contributions. The popular “basic must be 50% of CTC” shorthand isn’t the rule; your EOR should show you the calculation.
Include what candidates compare
- Statutory benefits: PF, ESI where applicable, gratuity, and 26 weeks of paid maternity leave.
- Group health insurance covering the family. This is the first benefit most candidates check.
- Learning budget and equipment. A good laptop and a certification allowance signal a real employer.
- A salary review cycle. Aon projected average Indian salary increases of around 9% for 2026, so promise a scheduled review, not a reactive counter-offer.
Handle equity with care
Indian engineers value startup equity, but granting US parent-company options to an employee of an EOR’s Indian entity raises tax and foreign-exchange questions. Get counsel to set it up properly, or use a phantom or cash-settled long-term incentive until you have your own entity.
Close the offer, then keep closing
In India, an accepted offer is not a guaranteed start. Candidates serving long notice periods keep interviewing, and some accept a better offer weeks later. Reduce that risk by moving from verbal offer to written contract within a day or two, introducing the candidate to their future teammates, and sending equipment and onboarding material early. A joining bonus paid after the first month also helps.
Step 7: Plan Around the Notice Period
Notice periods are the part of the timeline US founders most often forget. Mid-level and senior engineers in India commonly serve 60-90 days; junior roles often 30–60. You cannot shorten the notice period, but you can plan around it:
- Budget for a buyout. Some employers release people early if the notice pay is covered; offering to reimburse it can bring a start date forward.
- Expect a counter-offer from the current employer, and stay in touch weekly during the notice period.
- Use the gap. Share documentation, codebase access plans, and first-month goals so Day One is productive.
Step 8: Onboard Compliantly Before Day One
When you hire programmers in India through an EOR, the onboarding paperwork runs through the EOR, but several items are yours to check:
- Employment contract issued by the EOR’s Indian entity, with the offer structure you approved
- IP assignment in two links: employee to EOR in the employment contract, and EOR to your company in the service agreement
- Confidentiality terms covering your code and customer data
- Data handling aligned to India’s DPDP Act 2023, with access limited to what the role needs
- Laptop, accounts, and repository access ready before the start date
- Security training completed in the first week
- A named buddy on your team and a 30-60-90 day plan
Step 9: Set the Team Up to Stay
Keeping a strong engineer is cheaper than replacing one, and India’s best developers are recruited constantly. The habits that keep them are simple:
- Protect the overlap hours for decisions and unblockers, and keep everything else async.
- Treat India as part of the core team, not a delivery arm: same standups, same roadmap context, same promotion criteria.
- Run regular one-to-ones and a clear review cycle. The engineers who leave at month 14 usually never had a compensation conversation after onboarding.
- Visit, or bring them over. A single in-person week does more for trust than a year of video calls.
Finally, show a path forward. Engineers in the three-to-seven-year range are weighing growth as much as pay. Define what senior and lead look like on your team, give your India engineers ownership of real systems, and let them interview and mentor the next hires. The first great developer you bring on is often the best recruiter for the second.
A Realistic Timeline: From Job Description to Day One
Stage | Typical duration |
|---|---|
Define the role, choose city and EOR | Week 1 |
Sourcing and first-round screens | Weeks 2–3 |
Technical rounds and final interview | Weeks 3–4 |
Offer, acceptance, EOR contract issued | A few days |
Candidate serves notice | 30–90 days |
Day One | Roughly 6–16 weeks after kickoff |
The notice period dominates the timeline, which is why the startups that move fastest open India roles a quarter before they need them. If you need someone in January, start in October.
Five Mistakes That Cost US Startups Their First India Hire
- Starting on contractor terms “for now.” Temporary arrangements tend to become permanent, and so does the classification risk.
- Pricing against the national average. The engineers you want are benchmarked against product companies and GCCs.
- A slow process. Four weeks of interviews is three weeks too many when candidates hold multiple offers.
- Ignoring the notice period when promising a delivery date to your board.
- No written IP chain. Investors check it in due diligence, and it’s far easier to set up on Day One than to fix during a funding round.
How StratEdge Global Helps You Hire Indian Programmers
StratEdge Global is an Employer of Record built for startups that hire Indian programmers and engineers without setting up a local company. Your developers are employed by StratGrid Private Limited, StratEdge’s own registered subsidiary in Bengaluru, so there is no third-party partner between you and your team.
What you need | How StratEdge Global handles it |
|---|---|
Compliant offer structure | Offer letters and payroll structured to the Code on Wages in force since November 2025 |
Existing contractors | Conversion to compliant employees within five business days |
Benefits candidates compare | Health insurance from Day One, KnowBe4 security training, and a welcome kit included by default |
Predictable pricing | Flat, published tiers from $349 per employee per month; no lock-in |
Visibility | Payroll and compliance status visible in the "EmpleYor" dashboard, with a dedicated experience manager |
Found your developer? Get them started in 48 hours.
Book a free 30-minute India assessment and leave with a sample offer structure and a clear onboarding plan.
Checklist: How to Hire Employees in India, Step by Step
Use this as a quick reference for how to hire employees in India from the US:
- Legal model chosen: EOR for ongoing roles, contractor only for defined projects
- Role scoped for time-zone overlap and ownership level
- City or remote policy decided; EOR selected and contract reviewed
- Salary benchmarked against product companies and GCCs, not the national average
- Sourcing channels live, with founder outreach for senior roles
- Interview process capped at about three weeks
- Offer checked against the Code on Wages; health cover and equity approach settled
- Notice period planned, buyout budgeted if needed
- IP assignment, confidentiality, DPDP, equipment, and access ready before Day One
The Bottom Line
Hiring a developer in India is no longer a question of whether it can be done legally or well. The infrastructure exists, the talent is deep, and an EOR removes the need for an Indian company. What separates the startups that land great engineers from the ones that lose them at the offer stage is process: the right legal model from the start, pay benchmarked against the right market, interviews that move in days rather than weeks, and an onboarding that’s ready before the notice period ends.
Get those nine steps right and your first India engineer becomes the foundation of a team, not an experiment.
About StratEdge Global
StratEdge Global is a US-India Employer of Record and global workforce company built for Seed-to-Series B startups across the US, Canada, and Australia corridors. Teams are employed through StratGrid Private Limited, StratEdge’s own Bengaluru entity, with 48-hour activation, Labour Codes alignment, and transparent pricing with no lock-in. EMPLEYOR, StratEdge’s workforce management platform, gives clients one view of onboarding, payroll, and compliance, and NAVTRI AI CRM extends the platform into pipeline management.
📍 Sheridan, WY (US) · Bengaluru, India │ stratedgeglobal.com