Cloud · Tech · Bangalore
Microsoft
A multi-quarter Azure expansion needed 60+ engineers physically present in Bangalore on staggered start dates. The catch: the team was distributed across India + 4 countries, with very different commute, family, and budget profiles.
Microsoft moved 64 engineers into Bangalore for an azure capacity build-out — every booking auto-routed to the right neighbourhood.
64
Engineers relocated
5 cities
Origin spread
4
Microsoft-preferred neighbourhoods served
99.2%
On-time check-in rate
The brief
- Engineers were arriving from Hyderabad, Mumbai, Pune, Seattle, and Dublin on a rolling 90-day schedule.
- Microsoft Bangalore Tech Park (Whitefield) and Microsoft Manyata commute targets needed neighbourhood-aware allocation.
- Some engineers were single, some had spouses, a handful had school-age children — each profile needed different inventory.
- Visa start-dates kept slipping; bookings had to absorb 2-3 day shifts without renegotiating rates.
What we did
- Microsoft mobility shared the engineer roster via secure CSV. Aira ingested + auto-tagged each by neighbourhood preference.
- Three property clusters pre-vetted: Whitefield (Tech Park commute), Indiranagar (lifestyle), HSR Layout (family-friendly).
- Each engineer got a personalised Aira link. They voice-asked: "Aira, I have a 6-year-old, what are my options?" — got back family-friendly Indiranagar shortlist with school proximity rendered as a card.
- When 9 visa-start dates slipped, Aira auto-extended holds with the supplier directly. No human call needed.
Outcome
- All 64 engineers placed within commute SLA. Average time from CSV intake to first hold: 18 hours.
- Microsoft mobility coordinator hours per relocation: dropped from ~3 hours to ~12 minutes.
- Three engineers extended their stays to 6+ months. Two requested ikan again on rotational assignments to other cities.
“Our coordinator went from running spreadsheets to reviewing Aira’s decisions. The work that used to take a week is now a Tuesday afternoon.”