How US Startups Build Overlap Hours Between India and California Teams

For a US startup with a team in California, hiring engineers in India brings a real time-zone challenge: the two locations are almost exactly half a day apart. Get the overlap design right and it becomes an advantage; get it wrong and the team feels permanently out of sync.

Unlike a near-overlap pairing such as Singapore or Australia, a California-India team cannot rely on a shared working day. The whole game is designing a small, dependable overlap window and running everything else asynchronously. This guide shows how to do that well.

We cover how the California to India gap actually works, how to design overlap hours, why US startups still choose India, what it costs in 2026, the compliance rules that apply, and how to keep a far-apart team aligned.

How far apart are California and India in time?

India Standard Time is UTC+5:30 and never changes. California uses Pacific Time, which is UTC-8 in winter (PST) and UTC-7 in summer (PDT). That puts India roughly 13.5 hours ahead in winter and 12.5 hours ahead in summer. It is close to a full half-day apart.

In practice, the natural overlap is tiny. A standard California 9-to-5 barely touches a standard India 9-to-5. Without any schedule adjustment, the only shared moments are very early morning in California and late evening in India, which is not enough to run a team on.

So a California-India team has to manufacture overlap rather than inherit it. The encouraging part is that you do not need much. A deliberate two to three hour window, agreed by both sides, is enough for the synchronous work that genuinely needs everyone present.

From our experience helping companies build engineering teams in India, the teams that thrive across this gap decide their overlap hours explicitly and protect them, instead of hoping a shared window will appear on its own.

This is one workable pattern: a late-evening window for India and an early-morning window for California. Some teams instead shift India earlier and use the California late afternoon. The right choice depends on what each side is willing to flex, but the principle is the same: one protected window, kept small and consistent.

How do you design overlap hours between India and California?

Designing overlap hours is mostly about being deliberate and fair. You are asking one or both sides to flex their day, so the window should be small, predictable, and genuinely useful. The practices that make it work:

• Pick one protected window: Agree a single two to three hour block where both teams are reliably online. Put it on every calendar and defend it from other meetings.
• Share the inconvenience fairly: Do not push all the flexing onto India. If California shifts an hour earlier and India an hour later, neither side carries the whole burden of an unsocial schedule.
• Use the window for high-value sync only: Spend overlap on standups, design discussions, decisions, and unblocking. Anything that can be written should not eat the window.
• Make handoffs explicit: End each side's day with a clear written handoff so the other team can pick up work without waiting. The end of one day should set up the start of the next.
• Default to async everywhere else: Code review, status, documentation, and most questions move through pull requests and shared docs, so progress never stalls waiting for the overlap.

One pattern we have consistently seen is that the smallest, most disciplined overlap windows outperform vague all-day availability. A team that knows exactly when it meets, and writes things down the rest of the time, ships faster than one that is loosely on call around the clock.

Why do US startups hire engineers in India despite the time gap?

Even with a half-day gap, India remains one of the most popular places for US startups to build engineering teams. The reasons outweigh the time-zone friction for most product teams.

• Talent depth: India produces a very large number of software engineers each year across backend, frontend, mobile, data, and AI or ML roles, far more supply than most US startups can hire locally.
• Cost efficiency: A loaded engineering hire in India typically costs a fraction of a California equivalent, even after benefits, employer contributions, and platform fees. For a startup managing runway, that matters.
• The gap can be an asset: When designed as a handoff, the time difference means work progresses while California sleeps. A well-run team effectively extends its working day.
• English fluency: India's engineering workforce works in English and is used to collaborating with US product teams, tooling, and processes.
• Speed to scale: You can grow an India engineering team faster than you can hire in the competitive California market.

Based on what we have seen, US startups that treat India engineers as core team members, on the same repos and standards, get far more out of the relationship than those who hand off isolated tasks across the gap.

How much does it cost a US startup to hire engineers in India?

Costs depend on role, city, and seniority, but the gap with California salaries is large. Even after employer contributions and EOR fees, the loaded cost per engineer stays well below a California hire. The figures below are indicative annual salaries sourced in 2026 and converted at roughly 95 rupees per US dollar.

Salary data is drawn from current Glassdoor and Indeed listings for India engineering roles in 2026. Treat them as starting reference points, not fixed quotes.

On top of base salary, budget for statutory employer contributions such as Provident Fund, plus an EOR platform fee. For a full breakdown of what employing in India costs, see our guide to the cost of an Employer of Record in India.

What compliance rules apply to a US startup hiring engineers in India?

Indian employment law has central and state-level layers, and both apply to engineers. A US startup cannot simply pay developers as informal contractors without taking on misclassification and tax risk. The areas that matter most, as of 2026:

• India's four new Labour Codes took effect on 21 November 2025, consolidating 29 earlier central laws. Central and state rules are still being finalised through 2026, so employment terms must track the new framework.
• Statutory deductions: Provident Fund (a retirement contribution similar in spirit to a US 401k), Employee State Insurance, professional tax, gratuity, and tax deducted at source must be calculated and remitted correctly.
• Wage structure: Under the Code on Wages, at least 50% of total compensation must count as basic wages, which changes how Provident Fund, gratuity, and bonuses are computed. Older salary structures often need redesigning.
• IP assignment: For engineers this is critical. Employment contracts must clearly assign all code and intellectual property to your company, with confidentiality clauses that hold up under Indian law.
• Contractor misclassification: hiring developers as contractors to skip compliance creates real exposure, including weaker IP protection. If they work fixed hours under your direction, they usually look like employees to Indian authorities.
• State-level filings: Shops and Establishments registration, professional tax slabs, and leave rules differ by state, so where your team sits matters.
• Permanent establishment: A US company directing a team in India should understand permanent establishment risk, which can create a corporate tax presence. Using an EOR is one way to reduce this exposure.

This information is for general guidance. Consult with legal experts for your specific situation. From our extensive experience supporting international teams, getting contracts and IP assignment right from day one is what separates a clean engineering setup from one that creates problems later.

How do you keep a California and India team aligned across the gap?

With a half-day gap, alignment depends on writing discipline far more than on meetings. The practices that keep a distributed California-India team working as one:

• Protect the overlap and the deep work around it: Use the shared window for sync, and protect long uninterrupted stretches on both sides for focused coding.
• Keep one source of truth: Roadmap, specs, and decisions live in shared tools both teams trust. With little overlap, nothing important can live only in someone's head.
• Write handoffs that travel: Each side ends its day with a clear summary of progress, blockers, and next steps, so the other team starts with full context.
• Hold both sides to the same bar: Same code review standards, same definition of done, same on-call expectations. A two-tier team breeds resentment and quality gaps.
• Invest in a local lead early: Past roughly 8 to 12 engineers, a senior person in India who owns delivery and mentoring keeps the team healthy and reduces dependence on the overlap.

Companies often underestimate how much writing and handoff discipline matter once a team spans half the globe. For more on building this rhythm, see our guide to running async collaboration across distributed teams.

How Wisemonk helps US startups hire and manage engineers in India

Wisemonk is an India-native Employer of Record that helps US startups hire, pay, and manage engineers in India without setting up a local entity. You design the workflow and own the code. We handle the legal employment, payroll, and compliance underneath.

What that looks like in practice:

• Compliant hiring in days: Employment contracts with strong IP assignment and confidentiality clauses, statutory registrations, and onboarding handled end to end, so engineers can start quickly.
• Payroll built for cross-border teams: Salaries can be set in USD and paid in INR, with transparency on exchange rates at every transaction.
• Full compliance ownership: Provident Fund, Employee State Insurance, gratuity, professional tax, tax deducted at source, and the 2025 Labour Code changes managed for you.
• Equipment and onboarding: Laptops and equipment procured and shipped to your India engineers, so a new hire is set up on day one.
• Customizable benefits: Statutory coverage plus tailored health insurance and benefits that match what senior engineers expect.
• Local human support: Real India experts your team can reach with questions on taxes, benefits, or compliance, not a ticket queue.

We support more than 300 clients and over 2,000 employees across India. The goal is straightforward: let you focus on building product with a strong India engineering team, while the employment and compliance infrastructure underneath is taken care of.