India-Specific Interview Guide¶

🇮🇳 Overview¶

Interviewing in India has unique characteristics whether you're targeting MAANG offices (Google Bangalore, Microsoft Hyderabad) or unicorn startups (Flipkart, Razorpay, CRED, Zepto). This guide helps you navigate the Indian tech interview landscape.

Key Differences from US Interviews: - 🌏 Time zone challenges - Collaborating with global teams - 💰 Cost consciousness - Building products for Indian market (price sensitivity) - 📱 Mobile-first - Most Indian users access via smartphones (2G/3G optimization) - 🏃 Fast-paced - Startup culture moves extremely fast - 👥 Large teams - Indian offices often have 500+ engineers

MAANG Offices in India¶

Google India¶

Locations: Bangalore, Hyderabad, Gurgaon, Mumbai
Size: 5,000+ engineers
Teams: YouTube, Google Pay, Chrome, Android, Search, Cloud

What's Unique: - Heavy focus on emerging markets (India, Southeast Asia, Africa) - Projects: Google Pay (UPI), YouTube Shorts, Android Go - Interview style: Same global standards, but may ask India-specific system design

Common Questions: - "Design a system optimized for low-bandwidth users" - "How would you build Google Pay to handle UPI's 10B transactions/month?"

Microsoft India¶

Locations: Hyderabad (largest outside US), Bangalore, Noida
Size: 8,000+ engineers (largest R&D center outside US)
Teams: Azure, Office 365, LinkedIn, Windows, AI

What's Unique: - Significant product ownership (not just support) - Strong research focus (Microsoft Research India) - More emphasis on distributed systems (time zone collaboration)

Common Questions: - "How do you collaborate with teams across 12-hour time zones?" - "Design a feature for Teams used by Indian enterprises"

Amazon India¶

Locations: Bangalore, Hyderabad, Chennai, Pune
Size: 5,000+ engineers
Teams: Amazon.in, AWS, Alexa, Prime Video, Fresh

What's Unique: - Heavy focus on cost optimization (Indian customers are price-sensitive) - Strong emphasis on frugality Leadership Principle - E-commerce challenges: Cash on Delivery, returns, logistics

Common Questions: - "How would you optimize delivery costs in tier-2 cities?" - "Design a feature for cash-on-delivery payments"

Meta India (Facebook)¶

Locations: Bangalore, Hyderabad, Gurgaon
Size: 2,000+ engineers
Teams: WhatsApp, Instagram, Infrastructure, AI

What's Unique: - WhatsApp is HUGE in India (500M+ users) - Focus on low-bandwidth optimization - Instagram Reels competes with Indian apps (Josh, Moj)

Common Questions: - "How would you optimize WhatsApp for 2G networks?" - "Design Instagram Stories for Indian users (Hindi/regional languages)"

Apple India¶

Locations: Bangalore, Hyderabad
Size: 1,500+ engineers
Teams: Maps, Siri, Services

What's Unique: - Smaller presence, very selective hiring - Focus on India-specific features (Maps for Indian cities, Siri Hindi)

Common Behavioral Questions (India-Specific)¶

1. Tight Deadlines with Limited Resources¶

Why this is asked: Indian offices often have aggressive timelines and smaller budgets.

Q: "How do you handle tight deadlines with limited resources?"

✅ Good Answer (STAR):
Situation: Had to launch payment feature for Diwali sale (3 weeks), only 2 engineers
Task: Deliver on time for biggest sales event of year
Action:
- Prioritized ruthlessly: MVP = UPI + Wallets, deferred credit cards
- Used existing payment gateway (Razorpay) instead of building from scratch
- Set up monitoring first (catch issues fast)
- Worked with design team to reuse existing UI components
- Automated testing from day 1 (couldn't afford manual QA delays)
- Daily standups with stakeholders (no surprises)
Result:
📊 Launched 1 day before deadline
📊 Handled 50K transactions on day 1 (2x expected)
📊 0 critical bugs (good monitoring)
📊 Added credit cards 2 weeks later (post-sale)
Learning: MVP mindset + automation > heroic efforts

❌ Bad Answer:
"I worked 18 hours/day and pulled multiple all-nighters"
(Shows: poor planning, unsustainable)

2. Working Across Time Zones¶

Why this is asked: Indian teams collaborate with US (9:30 AM IST = 9 PM PST), requiring async work.

Q: "Tell me about working with distributed teams across time zones"

✅ Good Answer:
S: Feature required approval from US-based architect (9.5 hour time difference)
T: Get reviews without delaying sprints
A:
- Adapted to async communication:
  - Sent detailed design docs EOD India time (morning for US)
  - Recorded Loom videos explaining complex parts
  - Made PRs small (easier to review asynchronously)
- Created 2-hour overlap window (7:30-9:30 PM IST = 9-11 AM PST)
  - Scheduled weekly syncs then
  - Used time for critical discussions only
- Documented everything (Confluence, GitHub comments)
- Proactively unblocked myself (made decisions, documented rationale)
R:
📊 Feature velocity: same as co-located team
📊 Architect appreciated async updates (no surprise reviews)
📊 Reduced meeting time 40% (better documentation)
Learning: Async work requires over-communication + documentation

❌ Bad Answer:
"I stayed up late for meetings every day"
(Shows: no boundary-setting, inefficient)

3. Everything is Urgent (Prioritization)¶

Why this is asked: Fast-paced startup culture in India means competing priorities.

Q: "How do you prioritize when everything is urgent?"

✅ Good Answer:
S: Product manager wanted 5 features for app launch, all marked "P0"
T: Deliver maximum impact with limited engineering bandwidth
A:
- Asked PM to define success metrics for each feature
- Created impact/effort matrix:
  - High impact, Low effort: Login with Google (2 days) → DO FIRST
  - High impact, High effort: Recommendation engine (3 weeks) → DEFER
  - Low impact, Low effort: Dark mode (3 days) → DO AFTER LAUNCH
- Proposed phased launch:
  - Week 1: Core features (login, browse, checkout) = 70% value
  - Week 4: Enhanced features (wishlists, reviews) = 20% value
  - Week 8: Nice-to-haves (recommendations) = 10% value
- Got stakeholder buy-in with data (70% value in 1 week vs 100% in 8 weeks)
R:
📊 Launched app in 1 week with core features
📊 User adoption: 10K users in Week 1 (validated product-market fit)
📊 Added remaining features based on user feedback
Learning: Not everything urgent is important, use data to prioritize

❌ Bad Answer:
"I worked on all 5 features simultaneously"
(Shows: context-switching, no prioritization)

4. Learning New Technology Quickly¶

Why this is asked: Tech stack changes rapidly in India (startups pivot fast).

Q: "Describe a time you learned a new technology quickly"

✅ Good Answer:
S: Company migrated from REST to GraphQL, I had 0 GraphQL experience
T: Become productive in 1 week to not block team
A:
- Day 1: Read official GraphQL docs (4 hours), watched 1 tutorial
- Day 2: Built "Hello World" GraphQL server (Node.js + Apollo)
- Day 3: Migrated one small REST endpoint to GraphQL
- Day 4-5: Pair programmed with teammate who knew GraphQL
- Asked questions in team Slack channel (no ego)
- Documented learnings for next person (blog post internally)
R:
📊 Shipped first GraphQL feature in 1 week
📊 Helped onboard 2 other engineers (shared learnings)
📊 Reduced API calls by 60% (GraphQL's strength)
Learning: Learn by doing + leverage team knowledge

✅ Even Better (India Context):
Added: "Also watched YouTube tutorials in Hindi to understand concepts faster"
(Shows: resourcefulness, comfort with regional content)

❌ Bad Answer:
"I took a 2-month Udemy course"
(Shows: too slow for fast-paced startups)

Cultural Nuances (India-Specific)¶

1. Hierarchy vs Flat Culture¶

The Paradox: Indian culture respects hierarchy, but tech companies promote flat structures.

How to Navigate:

❌ Too Hierarchical:
"I always waited for my manager's approval before making decisions"

✅ Balanced:
"I proactively made decisions within my scope, but consulted my manager 
for cross-team impacts. For example, when optimizing our API, I implemented 
caching (my scope) but discussed database indexing with my manager since 
it affected other teams."

In Interviews: - Show respect without being subservient - Use phrases like "collaborated with senior engineers" (not "they told me what to do") - Demonstrate ownership even as junior engineer

2. Modesty vs Self-Promotion¶

The Challenge: Indian culture values humility, but interviews require showcasing achievements.

How to Balance:

❌ Too Modest:
"My team built a feature that increased revenue by 30%"
(Unclear: what did YOU do?)

❌ Too Boastful:
"I single-handedly increased revenue by 30%"
(Red flag: no collaboration)

✅ Balanced:
"I led the implementation of dynamic pricing. While my manager provided 
strategic direction and my teammate built the ML model, I designed the 
pricing engine, integrated it with checkout, and monitored rollout. 
Together, we increased revenue by 30%."

Framework: - Use "I" for your actions, "we" for team results - Give credit generously, but don't erase your contributions - Quantify YOUR impact specifically

3. Team Player (Highly Valued in India)¶

Why it matters: Indian companies emphasize collaboration over individual brilliance.

What to Emphasize:

✅ Good phrases:
- "I partnered with..."
- "We collaborated to..."
- "I learned from my teammate..."
- "I mentored a junior engineer..."
- "I shared knowledge through tech talks"

❌ Red flags:
- "I did this alone"
- "My teammate was slow, so I took over"
- "I didn't need anyone's help"

Interview Strategy: - For every story, mention 2+ people you worked with - Show how you enabled others (knowledge sharing, mentoring) - Demonstrate cross-functional collaboration (PM, design, QA)

4. Adaptability to Fast-Changing Environment¶

India context: Regulations change (UPI rules), competitors emerge (new fintech apps), tech evolves fast.

Stories to Prepare: - Pivoted product strategy based on market feedback - Adapted to new regulations (e.g., RBI payment guidelines) - Learned new tech stack mid-project - Handled scope changes gracefully

5. Cost Consciousness (Frugality)¶

India-specific: Building products for price-sensitive market.

Examples to Use:

✅ Good:
"Optimized video streaming to reduce CDN costs by 40%. Indian users 
often have limited data plans, so we implemented adaptive bitrate 
streaming that switched to 480p on slow networks. This saved costs 
AND improved user experience."

✅ Good:
"Chose AWS Mumbai region over Singapore to reduce latency (80ms → 20ms) 
AND save 15% on data transfer costs."

❌ Neutral:
"I used the most expensive cloud provider because it's the best"
(Shows: no cost awareness)

Indian Startup Culture¶

Top Indian Unicorns/Startups (2026)¶

1. Flipkart 🛒¶

About: E-commerce giant (acquired by Walmart)
Size: 10,000+ engineers
Tech Stack: Java, Scala, React, Kafka, Cassandra

Culture: - Move fast - Weekly releases - Customer obsession - Tier 2/3 city focus - Jugaad mentality - Innovative solutions with constraints

Behavioral Focus: - Handling scale (10M+ daily users) - Cost optimization (thin margins in e-commerce) - Solving for Bharat (non-English speaking users)

Sample Questions: - "How would you optimize delivery routes for tier-3 cities?" - "Design a feature for users with low literacy"

2. Razorpay 💳¶

About: Payments platform (valued at $7.5B)
Size: 500+ engineers
Tech Stack: Node.js, Go, React, Kubernetes, PostgreSQL

Culture: - Move extremely fast - Daily deployments - Developer experience - APIs are the product - Compliance-first - RBI regulations are critical

Behavioral Focus: - Handling payment compliance (PCI-DSS, RBI) - Building developer-friendly products - High availability (99.99% uptime)

Sample Questions: - "How do you ensure payment data security?" - "Design an API for developers with 0 documentation"

3. CRED 💎¶

About: Credit card payments + rewards (valued at $6.4B)
Size: 300+ engineers
Tech Stack: Kotlin, Swift, Node.js, React, AWS

Culture: - Design excellence - Best UX in Indian fintech - High bar - Very selective hiring (1% acceptance rate) - Move fast - Weekly product launches

Behavioral Focus: - Design thinking - Attention to detail - Building delightful experiences

Sample Questions: - "How do you balance speed with design quality?" - "Tell me about a time you obsessed over user experience"

4. Zepto 🛍️¶

About: 10-minute grocery delivery (valued at $3.6B)
Size: 200+ engineers
Tech Stack: React Native, Node.js, Python, Redis, PostgreSQL

Culture: - Speed obsessed - 10-minute delivery = tech challenge - Hyper-growth - Scaling very fast - Execution excellence - Logistics + tech

Behavioral Focus: - Real-time systems (order routing, rider tracking) - Handling hyper-growth - Building under pressure

Sample Questions: - "How would you optimize delivery routing for 10-min SLA?" - "Design a system that handles 10x traffic overnight"

5. Swiggy 🍕¶

About: Food delivery + quick commerce (valued at $10.7B)
Size: 1,500+ engineers
Tech Stack: Java, Python, React, Go, Kafka, Redis

Culture: - Customer-first - 30-min delivery guarantee - Innovation - Swiggy Instamart (groceries), Genie (delivery) - Scale - Operating in 500+ cities

Behavioral Focus: - Real-time systems (ETA predictions, rider matching) - Handling scale and variety (food, groceries, packages) - Building for diverse markets (metro vs tier-2)

Sample Questions: - "How do you predict accurate delivery ETAs?" - "Design a feature for restaurants with no internet"

6. Zomato 🍽️¶

About: Food delivery + dining (valued at $8.6B, publicly listed)
Size: 1,000+ engineers
Tech Stack: Java, Python, React Native, Kafka, Cassandra

Culture: - Data-driven - Heavy ML/AI for recommendations - Product thinking - Gold membership, dining out - Scrappy - Bootstrapped culture despite being public

Behavioral Focus: - Personalization (recommendations, search) - Building products for discovery (not just delivery) - Public company pressure (quarterly results)

Sample Questions: - "How would you improve restaurant recommendations?" - "Design a feature to increase user retention"

Salary Expectations in India (2026)¶

MAANG Offices (Google, Microsoft, Meta, Amazon, Apple)¶

Level	Base (₹ LPA)	Stocks (₹ LPA)	Total (₹ LPA)	USD Equivalent
SDE-1 (0-2 yrs)	25-35	10-20	35-55	$42K-66K
SDE-2 (2-5 yrs)	40-60	30-50	70-110	$84K-132K
SDE-3 (5-8 yrs)	60-90	60-100	120-190	$144K-228K

Notes: - Stocks vest over 4 years - Hyderabad salaries ~5-10% lower than Bangalore - Signing bonus: ₹5-15 lakhs for experienced candidates

Indian Unicorn Startups¶

Company	SDE-1 (₹ LPA)	SDE-2 (₹ LPA)	Equity Value
Flipkart	25-35	40-60	High (RSUs)
Razorpay	20-30	35-50	Medium (ESOPs)
CRED	30-45	50-80	High (ESOPs)
Zepto	25-40	45-70	Very High (startup)
Swiggy	25-35	40-65	High (pre-IPO)
Zomato	22-32	38-58	Medium (public stock)

Notes: - Startups offer higher equity but more risk - CRED pays 20-30% above market (high bar) - Zepto growing fast = equity could be very valuable

Negotiation Tips for India¶

1. Research Salary Ranges: - Use: levels.fyi/India, Glassdoor India, AmbitionBox - Account for location (Bangalore > Hyderabad > Pune > Others)

2. Leverage Competing Offers:

✅ Good:
"I have an offer from [Company X] at ₹45 LPA. I'm very excited about 
[Your Company] because of [specific reason]. Is there flexibility 
in the compensation?"

❌ Bad:
"I have a better offer elsewhere" (vague, sounds like bluff)

3. Negotiate Beyond Base: - Signing bonus (especially if switching cities) - Relocation assistance (Bangalore rent is high) - Learning budget (courses, conferences) - Remote work flexibility

4. Understand Equity: - RSUs (MAANG): Liquid, vest over 4 years, taxed as income - ESOPs (Startups): Illiquid until IPO/acquisition, choose carefully

5. Consider Total Compensation:

Offer A: ₹40L base + ₹10L RSUs = ₹50L (MAANG)
Offer B: ₹35L base + ₹15L ESOPs = ₹50L (Startup)

MAANG is safer (RSUs are liquid)
Startup has upside (if company does well)

Office Locations (City-Specific Insights)¶

Bangalore (Bengaluru) 🏙️¶

Pros: - ✅ Most tech jobs (Google, Microsoft, Amazon, Meta, 100+ startups) - ✅ Best tech talent density - ✅ Startup ecosystem (easy to network, switch jobs) - ✅ Pleasant weather year-round

Cons: - ❌ Highest cost of living (rent: ₹25-50K for 1BHK) - ❌ Worst traffic (2-hour commutes common) - ❌ Water scarcity issues

Best for: Startup enthusiasts, job hoppers, networkers

Hyderabad 🏢¶

Pros: - ✅ Microsoft's largest office outside US (8,000+ engineers) - ✅ Lower cost of living than Bangalore (rent: ₹15-30K) - ✅ Good infrastructure (metro, wide roads) - ✅ Growing startup scene (T-Hub)

Cons: - ❌ Fewer startups than Bangalore - ❌ Hot summers (40°C+) - ❌ Less cosmopolitan culture

Best for: MAANG employees, cost-conscious, stable careers

Gurgaon (Gurugram) 🏗️¶

Pros: - ✅ Google's largest India office - ✅ High salaries (NCR correction: +10%) - ✅ Proximity to Delhi (international airport, culture)

Cons: - ❌ Poor air quality (AQI 300+ in winter) - ❌ Expensive (rent: ₹30-60K) - ❌ Traffic worse than Bangalore

Best for: Google employees, high earners, Delhi NCR natives

Pune 🎓¶

Pros: - ✅ Good quality of life (culture, weather, education) - ✅ Affordable (rent: ₹15-25K) - ✅ Persistent Systems, Thoughtworks, growing startups

Cons: - ❌ Fewer big tech offices - ❌ Lower salaries than Bangalore/Hyderabad

Best for: Work-life balance seekers, service companies

Mumbai 💼¶

Pros: - ✅ Finance + tech combo (fintech capital) - ✅ Google, Microsoft offices - ✅ Startup scene (Razorpay, CRED, fintech)

Cons: - ❌ Extremely expensive (rent: ₹40-80K) - ❌ Long commutes (local trains crowded) - ❌ Monsoon flooding

Best for: Fintech engineers, high earners

Referral Strategies (India-Specific)¶

1. LinkedIn Networking¶

Strategy:

1. Identify employees at target company (search "Software Engineer at Google Bangalore")
2. Filter by:
   - Same college (IIT, NIT, BITS alumni groups)
   - Same previous company
   - Mutual connections
3. Send personalized connection request:
   ✅ Good: "Hi [Name], I see we both worked at [Company]. I'm exploring 
   opportunities at Google and would love to learn about your experience 
   in the Bangalore office. Would you be open to a quick chat?"

   ❌ Bad: "Please refer me" (too direct)

Follow-up: - Schedule 15-min call - Ask about team, culture, projects - At end: "I'd love to apply. Would you be comfortable referring me?"

2. College Alumni Networks¶

India-specific advantage: IIT/NIT alumni help each other actively.

How to leverage: - Join college WhatsApp/Telegram groups - Post in alumni channels: "Looking for referrals at Google/Amazon" - Attend college alumni meetups (Bangalore has most)

Response rate: 50-70% (much higher than cold LinkedIn messages)

3. Meetups & Conferences¶

Active communities in India: - Bangalore: HasGeek, React Bangalore, GDG Bangalore - Hyderabad: PyHyd, Devops Hyderabad - Mumbai: Mumbai Tech Meetup

Strategy: - Attend talks, ask questions - Network during breaks (not just collect business cards) - Follow up on LinkedIn next day

4. Employee Referral Portals¶

Some companies have public referral portals: - Google: goo.gle/careers (friends can refer) - Microsoft: careers.microsoft.com (internal referrals only) - Razorpay: Has referral bonus (₹2-3 lakhs for employees)

5. Direct Reach-Out to Recruiters¶

LinkedIn search: "Technical Recruiter at [Company Name] Bangalore"

Message template:

Hi [Recruiter Name],

I'm a software engineer with [X years] experience in [tech stack]. 
I'm very interested in opportunities at [Company] Bangalore, particularly 
in [team/domain].

I've prepared thoroughly:
- Solved 200+ LeetCode problems
- Studied system design
- Familiar with [Company]'s products

Would you be open to reviewing my profile?

Resume: [Google Drive link]
LinkedIn: [Your profile]

Thanks,
[Your Name]

Response rate: 20-30% (recruiters want to fill roles)

Work-Life Balance Questions¶

Q: "How do you maintain work-life balance?"¶

Context: Indian companies moving towards better WLB (used to have 60-hour weeks).

✅ Good Answer:
"I set boundaries while delivering results:
- Focus time: 9 AM - 6 PM deep work, no meetings
- Async communication: Use Slack threads, reduce real-time pressure
- Say no strategically: Pushback on scope creep with data
- Automate repetitive tasks: Freed up 5 hours/week
- Take breaks: Exercise 3x/week, helps productivity
Result: Shipped more features while working 45 hours/week"

❌ Bad Answer:
"I don't believe in work-life balance, I work 80 hours/week"
(Red flag: burnout risk)

Q: "Would you work late/weekends if needed?"¶

Trap question: Testing if you're a pushover.

✅ Good Answer:
"I'm happy to work extra hours for genuine emergencies:
- Production incidents
- Critical customer issues
- Important launches with hard deadlines

But I believe in sustainable pace. If we're consistently working 
weekends, it signals poor planning or understaffing. I'd proactively 
suggest solutions: better estimation, automation, or hiring."

❌ Bad Answer:
"Yes, I'll work whenever you need" (no boundaries)

Remote Work Questions (Post-COVID)¶

India Context:¶

Most companies shifted to hybrid (3 days office + 2 days remote)
Some startups fully remote (Razorpay, GitLab)
MAANG requires office presence (Google 3 days/week minimum)

Q: "How do you stay productive working remotely?"¶

✅ Good Answer:
"I treat remote work with same discipline as office:
- Dedicated workspace (separate from bedroom)
- Fixed hours (9-6, not flexible)
- Overcommunicate: Daily standups, Slack updates
- Video on for meetings (better engagement)
- Proactive collaboration: Schedule virtual coffee chats
Result: Shipped features on time, manager didn't notice WFH vs office difference"

Pro Tips for Indian Market¶

1. Highlight India-Specific Projects¶

✅ Good:
"Built UPI integration for our payment service. UPI handles 95% of 
digital payments in India, so understanding NPCl's API, handling 
bank downtimes, and optimizing for 2-second timeouts was critical."

vs generic:
"Built payment integration"

2. Show Understanding of Indian Market¶

Know Aadhaar, UPI, DigiLocker if applying to fintech
Understand regional language support (Hindi, Tamil, etc.)
Aware of tier-2/tier-3 city challenges (low bandwidth, affordability)

3. Demonstrate Jugaad (Resourcefulness)¶

Example: "We couldn't afford third-party monitoring (₹5L/year), so I built custom alerts using free tier Prometheus + Grafana. Saved money AND got exactly what we needed."

4. Prepare for Hindi/Regional Language Questions¶

Some interviewers (especially startups) may switch to Hindi to test comfort. - Be comfortable code-switching - Shows cultural fit for Indian teams

5. Ask About India Office Specifically¶

Good questions: - "How does the Bangalore office collaborate with US teams?" - "What products are owned by India office vs US?" - "Do you have flexibility to work from tier-2 cities remotely?" - "How does compensation compare between Bangalore/Hyderabad offices?"

Red Flags to Avoid¶

1. Criticizing Indian Work Culture¶

❌ "I want to join MAANG because Indian startups have poor work-life balance" ✅ "I'm excited about Google's impact on emerging markets"

2. Only Motivated by Money¶

❌ "I want the highest salary possible" ✅ "I'm looking for growth opportunities and fair compensation"

3. US Obsession¶

❌ "When can I transfer to US office?" (Asked in first interview = red flag)
✅ Ask about growth, not geography

4. Not Knowing Indian Market¶

❌ Interviewer: "How would you design for Indian users?"
You: "Same as US users"
(Shows: no research)

Additional Resources¶

India-Specific Salary/Company Data:¶

levels.fyi/India - Salary ranges for MAANG in India
AmbitionBox - Indian company reviews
Glassdoor India - Salary insights
AngelList India - Startup jobs

Networking:¶

HasGeek - Tech conferences (Bangalore)
GDG India - Google Developer Groups (all cities)
LinkedIn India Tech Groups - Active communities

News & Trends:¶

YourStory - Indian startup news
Inc42 - Startup ecosystem insights
Medial - Tech community discussions

✅ Final Checklist for India Interviews¶

Before Interview: - [ ] Research company's India office (size, teams, products) - [ ] Understand India-specific products (Google Pay, Amazon.in, etc.) - [ ] Prepare 3-4 stories about working with constraints (time, budget, resources) - [ ] Prepare 2-3 stories about time zone collaboration - [ ] Know current salary range for role in that city - [ ] Research interviewer on LinkedIn (college, previous companies)

During Interview: - [ ] Balance modesty with showcasing achievements (use "I" and "we" appropriately) - [ ] Show team player mentality (mention collaboration in every story) - [ ] Demonstrate cost consciousness (optimization, frugality) - [ ] Highlight adaptability (fast-changing environment) - [ ] Ask about India office specifically (not just generic company questions)

After Interview: - [ ] Send thank-you email (Indian context: more formal tone) - [ ] Connect on LinkedIn with interviewers - [ ] If you have referrer, update them on interview outcome

Good luck with your interviews! 🇮🇳 💪

For more guidance, see: - Google India Behavioral Guide - Amazon India Leadership Principles