In India, the notice period for a software engineer commonly runs 30 to 90 days, and 60 to 90 days is common for experienced hires, so the person you start looking for today will often join two to four months later. Startups keep shipping through that gap by pricing the wait honestly, negotiating a notice buyout where the candidate's contract allows it, handing the work that cannot wait to an interim contractor or to a delivery partner as a defined project, and re-scoping the rest so the roadmap does not depend on a start date they cannot control.

This guide covers what to expect from notice periods in India, what the wait actually costs, and how to run hiring and bridging at the same time.

What is a typical notice period in India?

A notice period is the time an employee must continue working for their current employer after resigning, as set by their employment contract and company policy. In Indian technology roles it commonly runs 30–90 days. Larger employers and senior roles tend towards the longer end, and the 90-day notice period is common enough that many founders now plan for it by default.

A few patterns are worth knowing:

  • Probation is usually shorter. Someone still on probation with their current employer may have a much shorter notice period.
  • The exit is negotiable, at the employer's discretion. Early release, payment in lieu of notice and adjusting unused leave against notice are all possible at some employers and refused at others.
  • Candidates often interview during notice. Someone who has already resigned may join sooner, but they are also likely to be talking to other companies.

How long does it take to get a new engineer working?

The notice period is the longest single stage, but it is not the only one. The timeline below is illustrative; your own numbers will vary with the role, the seniority and the market.

Stage Typical duration Running total
Define the role, source and screen 2–4 weeks 2–4 weeks
Interviews, decision and offer 1–3 weeks 3–7 weeks
Notice period 30–90 days about 7–20 weeks
Onboarding to independent contribution 2–6 weeks after joining about 9–26 weeks

In plain terms, if you open a role at the start of a quarter, do not count on that engineer contributing independently before the following quarter. For a senior hire with a 90-day notice period, it may be the quarter after that.

Why do accepted offers fall through during the notice period?

A long gap between offer and joining gives the candidate's situation time to change. The common causes are:

  • Counter-offers. The current employer responds to the resignation with a raise, a promotion or a more interesting project.
  • Competing offers. The candidate keeps interviewing and receives a better offer before their last day.
  • Second thoughts. Without contact from the new team, the new job stays abstract while the current team is real.
  • Release problems. The current employer refuses an early release or insists on a long handover.

You cannot remove this risk, but you can reduce it:

  • Agree a regular check-in between the candidate and the hiring manager during the notice period.
  • Introduce the candidate to the team informally and share context on the work they will own.
  • Put everything material in writing: role, level, compensation, start date and any buyout reimbursement.
  • Keep your pipeline warm, and be honest with runner-up candidates that the process is still open.

What does waiting really cost a startup?

The cost of a vacancy is easy to ignore because it never appears on an invoice. It shows up as work that does not happen.

  • Roadmap slip. A feature, integration or migration planned for this quarter moves to the next one.
  • Load on the existing team. The work is spread across engineers who are already busy, which slows everything and raises the risk of burnout.
  • Commercial timing. If a customer commitment, launch or fundraising milestone depends on the work, the delay has a direct commercial cost.
  • Compounding delay. The new hire then needs time to learn the codebase, so the gap is longer than the notice period itself.

Illustrative only: assume a team of five engineers opens a role for a sixth in week 1, and the new engineer joins in week 14 after a 60-day notice period. Roughly 13 engineer-weeks of planned capacity never arrive, and the first few weeks after joining go mostly on onboarding. If a launch depends on that capacity, it moves by about a quarter.

To compare that delay against the full cost of hiring, see the true cost of hiring a software engineer vs outsourcing.

Can you buy out a notice period in India?

Sometimes. A notice period buyout is an arrangement in which the employee, or the new employer on their behalf, pays the current employer for the unserved part of the notice period so the employee can leave early. Whether it is possible depends on the employment contract and the current employer, which may accept payment, refuse it, or insist on a minimum handover regardless.

If you are considering a buyout:

  • Ask early. Find out the notice length, whether a buyout or early release is allowed, and the candidate's leave balance at the first screening call, not at offer stage.
  • Agree the mechanism in writing. Reimbursement is often paid as a joining bonus, commonly with a clawback if the hire leaves within an agreed period.
  • Check the treatment. Confirm the payroll, tax and documentation implications with your own advisers.
  • Expect some handover. Even with a buyout, many employers want a few weeks of handover, and pushing for none can sour the candidate's exit.

A buyout shortens the wait; it does not remove it. Plan for the rest of the gap regardless.

How do you keep shipping while you wait?

There are four practical options, and most startups combine two of them.

Option How it works How fast Best when Watch out for
Notice buyout Pay to shorten the candidate's remaining notice Depends on the current employer The role is critical and the remaining notice is long Not always allowed; cost and clawback terms
Interim contractor Engage an independent engineer whom your team directs Days to weeks, if you can find and vet one You know someone you trust and have time to direct them Vetting, supervision, continuity and IP rest on you
Defined project with a delivery partner Hand the feature, migration or platform piece that cannot wait to an outside team that scopes, builds and hands it over Once scope, timeline and price are agreed The work has clear boundaries and a clear definition of done Write acceptance criteria and plan the handover to your permanent team
Re-scope the roadmap Move or cut work that depends on the new hire Immediate The work can genuinely wait Deferral quietly turning into cancellation

The usual combination is to re-scope what can genuinely wait and bridge what cannot.

What makes a good project to hand over?

The difference between an interim contractor and a delivery partner is what you are buying. With a contractor you buy time, and someone on your team still plans and reviews the work every day. With a delivery partner you agree an outcome, and the partner plans, staffs and delivers it while your team reviews progress and accepts the result.

That suits work with clear boundaries: an integration with a third-party service, a data pipeline, a migration off a legacy system, a new service behind a defined interface, or an internal platform component. It suits less well the core system the permanent hire is meant to own for years, or work whose requirements change daily during product discovery.

How do you run hiring and bridging in parallel?

The common mistake is to treat bridging as a fallback for when a hire falls through. It works better as a plan from the day the role opens.

  1. Open both tracks in the same week. Start the permanent search and decide what cannot wait. If that work is going to an outside team, start scoping straight away, because agreeing scope takes time too.
  2. Choose bridge work that transfers well. Integrations, migrations, data pipelines, test coverage and well-defined services suit a contractor or a defined project. Avoid making anyone outside the company the sole owner of the system the permanent hire is meant to own.
  3. Keep knowledge in your systems. Code in your repositories, tickets in your tracker and decisions written down as they are made. Our checklist for onboarding an external engineering team covers access and conventions.
  4. Define done before work starts. Put acceptance criteria, documentation and handover sessions in the scope, so the permanent hire inherits something they can run.
  5. Bring the new hire in early. If the project is still running when they join, include them in code reviews and the weekly demo, then hold walkthroughs at handover.
  6. Keep the pipeline open until the start date is real. If an offer falls through, you lose weeks rather than months, because the critical work has kept moving.

If the line between interim help and long-term capacity starts to blur, revisit the decision with our guide to contract vs full-time engineers in India.

What should founders and engineering managers check?

  • Ask every candidate about notice length, buyout options and leave balance on the first call.
  • Plan the roadmap around a realistic joining date, not the hoped-for one.
  • Decide what cannot wait, and arrange a contractor or scope a project for it before the offer is signed, not after.
  • Stay in touch with accepted candidates every week or two until they join.
  • Keep a short list of runner-up candidates warm until day one.
  • Make sure everything built during the gap is documented and in your repositories, so the permanent hire inherits it cleanly.

Where NexaPrism fits

When the work that cannot wait is a defined piece of engineering, such as a feature, a migration, an integration or a platform component, NexaPrism can take it on as a project while your permanent hiring runs in parallel. A senior engineer reviews the brief and agrees the scope, deliverables, timeline and price with you before work starts. A lead engineer and senior engineers based in India build it, with working software every week, and deliver it documented and handed over, ready for your permanent team to own. Code and IP are yours from the first commit, and staffing and continuity are our problem, not yours: there are no job posts, recruiter fees or notice periods involved.

If you have a role open and a deliverable that cannot wait, tell us what you need built, or see how we work with companies in India.