A company decides it wants 15 engineers in India, and the first question is always the same: "how quickly can you build the team?"
We hear it every week at SquadXP, and our honest answer is another question: what do you mean by "build"?
If the goal is 15 signed offer letters, the timeline can be genuinely short. If the goal is 15 engineers who understand your product, work smoothly with your US team, follow your engineering process and ship meaningful output, the timeline is longer, and pretending otherwise is how offshore projects earn their bad reputation. A team isn't complete when the last contract is signed. It's complete when it can operate with reasonable independence.
So here's the realistic picture, drawn from the pods we've actually built: the ramp runs through defining the team, mapping the talent market, sourcing, screening, closing offers, onboarding, integrating with the product organisation and establishing a delivery rhythm. Measured honestly, that journey takes weeks and months, not days, typically 8 to 16 weeks to a substantially operational team. This guide breaks the whole thing down phase by phase, including where the time actually goes and how to compress it without wrecking quality.
First, define what "15 people" means
Before any timeline discussion, define the pod. A balanced 15-person team usually includes an engineering manager or technical lead, backend, frontend and full-stack engineers, QA, a DevOps or platform engineer, possibly a data or AI specialist, and some product or technical-support capacity.
The mix depends entirely on your product. Fintech needs deeper backend and security expertise. SaaS leans frontend and platform. AI products need ML engineers and data people. And here's the timeline implication nobody selling you "15 engineers in 30 days" mentions: the more specialised the mix, the longer recruitment takes. Treat any generic speed promise that ignores your role with suspicion; it's the offshore version of the sales red flags we've catalogued in our guide to choosing a staff augmentation company.
Phase 1: Define the team (week 1)
The fastest ramps we've run all started the same way: with a ruthlessly clear hiring specification. Week one should answer what you're building, the technology stack, which roles are essential versus flexible, required seniority, who manages the team, working hours, security restrictions, budget and target start date.
Sounds basic. It isn't, and here's why it matters: poor role definition is the single biggest cause of hiring delays we see. Change the profile after every interview and the entire pipeline resets, again and again.
"Senior backend engineer" is not a specification. "Java or Go, microservices, AWS, Kubernetes, PostgreSQL, event-driven architecture, eight-plus years, experience scaling B2B SaaS" is. The clearer the profile, the faster everything downstream moves.
Phase 2: Map the talent market (weeks 1 to 2)
Next, verify the talent you need actually exists where you're looking. India has multiple major hubs, Bengaluru, Hyderabad, Pune, Chennai, Delhi NCR, but availability varies sharply by skill.
Our own GCC location analysis surfaces a distinction worth internalising: the best city is not the cheapest city. Bengaluru has an exceptional density of senior and specialist engineering talent, and precisely because of that, a brutally competitive hiring market. Start from talent availability for your specific roles, not from a city's reputation, and the sourcing phase gets shorter automatically.
Phase 3: Build the pipeline (weeks 2 to 4)
With profiles locked, recruitment begins, and here's where first-time offshore builders miscalculate. For 15 positions, you will not interview 15 people. A healthy funnel needs dozens to hundreds of profiles depending on the roles, because candidates fail technical screens, reject the opportunity, accept competing offers, price themselves outside the budget, or turn out technically strong but wrong for your working model.
The pipeline must be much larger than the target. Providers with existing candidate databases and talent networks earn their keep right here, because building that funnel from a cold start adds weeks.
And understand what changes at this scale: hiring one engineer is a recruitment task; hiring 15 is a workforce-planning exercise. You're juggling role mix, seniority balance, interview capacity, offer conversion, staggered start dates, leadership, onboarding, equipment and access management simultaneously. If the first ten land quickly but the last five take three months, the pod still isn't operational. The bottleneck is rarely sourcing. It's coordination.
Phase 4: Technical interviews (weeks 3 to 6)
Assessment is where good pipelines go to stall. If every candidate must pass a recruiter screen, technical interview, coding test, system design round, hiring-manager interview, culture conversation and leadership approval, and each step waits days for a calendar slot, the process bleeds weeks.
The fix is never removing quality controls; it's removing waiting. Batch the interviews. Have hiring managers reserve standing interview blocks. Require same-day feedback. Define decision authority before interviews start so nobody schedules a meeting to decide whether to decide. A well-run process moves candidates through in days; a committee-run one loses them to competitors who moved faster. In India's senior-talent market, your best candidates always have another offer pending.
Phase 5: Offers and joining (weeks 5 to 8)
Here's the gap that surprises every US company building in India for the first time: an accepted offer is not a joined employee. Indian notice periods commonly run 30 to 90 days, so a candidate who signs today may start six weeks from now. The position is technically filled and operationally empty.
This is the difference between time to hire and time to productive capacity, and your planning must use the second number. Bias toward candidates with shorter availability where quality allows, and sequence offers so joins cluster rather than trickle.
Phases 6 and 7: Onboarding to first delivery (weeks 6 to 12)
When engineers join, two things must already be waiting for them. First, access: laptop, email, repositories, cloud environments, VPN, security systems, project tools, communication channels, all prepared before day one, not requested on day one. Second, context: product architecture, codebase orientation, development workflow, deployment process, sprint structure, coding standards and business goals.
Skip the context work and you'll have 15 employees and a low-output team, the most expensive combination in offshore engineering. Then, somewhere in weeks 8 to 12, comes the milestone that matters: the first meaningful sprint. Watch pull-request activity, sprint completion, bug resolution, deployment frequency and review turnaround. Don't demand maximum velocity; demand predictable execution. Predictability is what you're actually building in month three, and how you structure the daily rhythm between the US and India teams, covered in full in our time-zone overlap playbook, determines whether that rhythm forms in weeks or drags on for a quarter.
The realistic timeline, assembled
Put the phases together and a sound planning model looks like this: weeks 1 to 2 for planning and market mapping; weeks 2 to 5 for sourcing and screening; weeks 3 to 7 for technical interviews; weeks 5 to 9 for offers and joining; weeks 7 to 10 for onboarding; weeks 9 to 12 for the initial delivery rhythm; and months 3 to 4 for real operational maturity.
These are planning ranges, not guarantees. Specialised roles stretch them; commodity skills compress them; an established recruitment partner compresses the sourcing and coordination stages hardest of all.
So, can you build 15 engineers in 30 days? Sometimes, if roles are clearly defined, compensation is competitive, the stack is common, interviews move fast and candidates are immediately available. But 15 hired and 15 productive within 30 days are very different claims, and the real danger of a 30-day target is sacrificing quality to hit a headcount number. The better goal: as fast as possible without compromising the quality production work requires.
Hire the leader first, and phase the rest
The biggest hidden bottleneck in a 15-person ramp is leadership. Without an engineering manager or technical lead, you don't have one team forming; you have fifteen separate hiring decisions drifting toward each other. Identify the leadership role early, and in most cases hire it first: that person then helps interview candidates, defines architecture, sets standards, designs onboarding and establishes the sprint cadence with US leadership. Our GCC hiring analysis reaches the same conclusion, and adds a warning: strong local leadership is also the scarcest ingredient in the market.
On sequencing the rest, resist big-bang hiring. Bringing everyone in at once forms the team faster on paper, but concentrates hiring pressure, overloads onboarding and multiplies the odds of rushed decisions. The phased pattern works better in practice: month one, hire the technical leader and first senior engineers while preparing documentation and access; month two, bring in the bulk of the team and start normal sprint delivery; month three, fill the remaining specialist roles and stabilise; month four, optimise productivity, architecture and communication. The first wave interviews and onboards the second, which is a quality multiplier no recruitment process can replicate.
The truth underneath all of it: a team isn't finished when headcount hits 15. It's finished when you can predict what those 15 people will deliver.
What slows ramps down, and how to speed up honestly
The recurring delay culprits, in rough order of frequency: compensation below the local market (candidates simply vanish), overly narrow requirements demanding a technology combination three engineers in the country possess, too many interview rounds (candidates accept elsewhere mid-process), slow decisions (a two-day delay at every stage compounds into weeks), long notice periods, unclear team ownership, unprepared onboarding, and undefined time-zone communication rules that leave new engineers spending their first weeks waiting for answers.
The acceleration levers are all operational, and none involve cutting corners: lock job profiles before sourcing, standardise the interview process, reserve interview time in advance, set feedback deadlines, prepare equipment and access before joining dates, hire leadership early, and document the product so the team doesn't depend on tribal knowledge held by two people in California.
One more thing worth agreeing before anyone starts: what "productive" means. For one company it's the first production deployment; for another, the first completed feature; for a third, independent ownership of a service. Set milestones, understand the systems and ship low-risk work in the first 30 days, own defined components by day 60, deliver independently by day 90, operate as a mature pod after that, and you'll know whether the ramp is on track long before the quarter ends.
Where a dedicated team or Talent BOT changes the maths
A dedicated team provider compresses the phases that hurt most, because the recruiters, candidate databases, technical screening, employment infrastructure and onboarding processes already exist rather than being built alongside your hiring. You're not paying to stand up a recruitment machine; you're renting one that's already warm. That's also a meaningful chunk of the fixed cost in the fully-loaded cost per engineer comparison, which is why the timeline question and the cost question are really the same question wearing different clothes.
And for companies that ultimately want to own their India team but whose entity isn't ready, there's a sequencing problem with two answers. Wait for the entity, then hire, then onboard, then deliver, or build the team now, start delivering, establish the entity in parallel, and transfer the team when it's ready. Our Talent BOT model exists for the second path: engineers employed and operationally supported by us while your India setup completes, then structurally transferred to you. When time-to-market matters, months of delivery versus months of paperwork is not a close call.
Conclusion
How long does it take to build an offshore team of 15 engineers? Plan for 8 to 16 weeks from requirements to a substantially operational pod, tighter with common skills and an experienced partner, longer with rare specialisations. But don't run it as a race to 15 offer letters. Hire the leadership first, define roles precisely, keep interviews fast and rigorous, prepare onboarding before day one, and design the India-US operating model deliberately.
The fastest team was never the one with the quickest hiring cycle. It's the one that reaches productive engineering capacity first, and that's a systems outcome, not a sourcing outcome.
If you're planning an India pod, talk to SquadXP. We'll map your role mix against real market availability, give you a week-by-week timeline for your specific team rather than a generic promise, and show you whether a dedicated team or the Talent BOT path gets you to productive capacity faster. You'll leave the call with a plan you can put in front of your board, and a number you can actually hold us to.
