Amazon India After Layoffs: Hiring Status in 2026

Amazon has been one of those dream logos for Indian students for years. Then layoffs hit, social media got loud, and everyone started asking the same thing: "Is Amazon still hiring in India, or is this just wishful thinking?"

Short answer in 2026: yes, Amazon India is hiring, but not in a random, open-flood way. Hiring is selective, team-specific, and much more tied to business priorities than it was in the high-growth years.

If you are a final-year student, a 1-3 year engineer, or someone switching from service to product, this is still a real opportunity. You just need to pick the right division, prepare for Amazon-style interviews, and apply through the channels that actually work.

This guide breaks it down in plain terms: what happened from 2023 to 2025, where hiring stands now, what roles are active, what salary bands look like, how the interview loop works, and how to deal with the PIP question that everyone whispers about.

Timeline of Amazon India layoffs: 2023 to 2025#

Let us start with context, because panic usually comes from half-info.

2023: Big global cuts, clear impact in India

2023 was the rough year. Amazon announced major global job cuts across phases, and India felt the shock through direct role reductions, paused hiring, and delayed backfills. Teams connected to retail support functions, devices programs, and recruiting operations saw the biggest stress.

A lot of candidates noticed this as "ghosted interview processes" or "frozen requisitions" rather than public team-wise announcements. If you were applying then, you probably remember roles disappearing after OA clearance.

2024: Fewer headlines, but targeted trimming continued

By 2024, the huge wave headlines were less frequent, but cuts did not fully vanish. Amazon kept doing smaller, focused trims in selected orgs globally. In India, the effect looked like tighter headcount control, slower replacement hiring, and more pressure to justify each open role.

Recruiting teams remained lean. Managers were careful with openings, and many posts stayed open only after internal approvals crossed several layers.

2025: Selective growth first, then another corporate cut phase

Early 2025 looked calmer than 2023. Hiring was still selective, but roles tied to clear business output kept moving. Then in late 2025, reports pointed to another global corporate reduction plan, with thousands of white-collar roles expected to be removed as Amazon pushed automation and tighter cost control.

In India, most candidates felt this as stricter approvals, slower backfills, and sharper role filters, not always as one public India-only mega announcement.

For candidates, this meant two things:

1. Good candidates with direct fit still got offers.
2. Generic applications without role match had very low hit rate.

So yes, layoffs happened in waves. But the story going into 2026 is still not "Amazon stopped hiring." The real story is "Amazon became far more selective."

Which divisions were hit hardest#

The pressure was not equal across Amazon. Some orgs saw much sharper cuts or freezes than others.

1) Retail corporate support and non-core programs

Retail itself remained huge, but support layers and certain project-heavy groups saw stronger cost control. Teams linked to slower-growth initiatives were more exposed than core revenue engines.

2) Devices and related product units

Devices-linked groups went through visible restructuring in multiple regions. In India, this translated into fewer fresh openings compared to peak years, plus slower movement in some product lines.

3) Recruitment and talent acquisition

This was one of the most affected functions globally, and India followed the same pattern. Recruiter bandwidth dropped, which is part of why candidate communication felt worse even when processes were active.

4) Middle-management-heavy structures

Across many large companies, 2024-2025 had a clear theme: flatter orgs, fewer managerial layers, tighter productivity expectations. Amazon reflected this too.

Current hiring status in 2026: where growth is happening#

Here is the practical view for 2026: Amazon India hiring is alive, but concentrated.

As of March 1, 2026, Amazon's public jobs site shows active India listings across engineering, cloud support, data, and operations roles in multiple metro hubs.

The strongest demand sits in teams tied to cloud, ads, core engineering, logistics efficiency, data-driven decisions, and customer-facing reliability.

Teams that are showing the most movement

• AWS engineering and customer-facing cloud roles
• Core software roles in retail platforms and internal services
• Data engineering and analytics in high-volume business units
• Operations technology and process optimization roles
• Supply chain and delivery network planning roles
• Trust, risk, and compliance tech roles in selected orgs

This does not mean every listing will be in these buckets every week. It means your probability is better here than in teams with unclear cost ownership.

Amazon India office hubs: where roles usually sit#

Amazon hires across India, but five city hubs keep appearing in most role searches.

Bangalore

Still the biggest magnet for software and product-heavy roles. You will see many SDE, data, and platform positions here, including roles that support global systems.

Hyderabad

Large presence across engineering, operations, support functions, and business roles. Hyderabad often has a strong mix of tech + process jobs.

Chennai

Known for operations, support, and growing tech opportunities in selected teams. Chennai roles can be solid for candidates trying to enter via non-hype but high-impact functions.

Gurugram

Common for business-facing teams, ads-linked roles, category and program functions, and selected tech openings.

Pune

Seen in cloud, support engineering, and selected product or platform roles. Pune has become more relevant for candidates who want technical work outside the Bangalore crowd.

Roles Amazon India is actively hiring for in 2026#

If you are making a target list, focus on role families rather than random job titles.

Software Development Engineers (SDE)

SDE 1 and SDE 2 continue to be the core entry points for many engineers. Expect demand in backend services, distributed systems, API engineering, and performance-focused services.

What helps:

• Strong DSA for interviews
• Clean low-level design thinking
• Ability to explain trade-offs in scaling and reliability
• Good ownership stories from projects or internships

Data roles

Data engineer, business intelligence engineer, applied scientist support roles, and analytics-focused jobs are active in many orgs.

What helps:

• SQL depth
• Python for data pipelines
• Metrics thinking tied to business impact
• Experience with dashboards and experimentation logic

AWS-linked roles

AWS demand in India stays meaningful because cloud adoption keeps growing across startups and enterprises.

Role examples include:

• Cloud support engineer
• Solutions architect tracks (with experience)
• DevOps and platform reliability roles
• Technical account and customer success engineering paths

What helps:

• Cloud certs are useful but not enough by themselves
• Real project stories matter more than badge collection
• Networking, Linux basics, and incident thinking are important

Operations and supply chain tech

Amazon is obsessed with efficiency in fulfillment and delivery. That creates roles in planning, forecasting, process optimization, and automation support.

What helps:

• Comfort with data + operations
• Problem-solving with messy constraints
• Ability to improve SLA, turnaround time, or cost metrics

Delivery network and last-mile roles

These include area-level operations, planning, and program functions tied to customer promise and shipment quality.

What helps:

• On-ground execution mindset
• Data-backed decision making
• Ability to handle ambiguity and pace

Amazon interview process in India: what it looks like now#

Most candidates still see a version of this pipeline.

1) Online Assessment (OA)

Usually includes coding tasks and sometimes work-style or reasoning sections depending on role.

Your goal here is not fancy code. It is correctness, edge-case handling, and time discipline.

2) Recruiter or phone screen

For many roles, one early conversation checks fit, communication clarity, and baseline problem-solving. For experienced hires, this can include detailed project discussion.

3) Loop interviews (4 to 5 rounds)

This is the real filter. Typical mix:

• DSA or coding round(s)
• Problem-solving and system/low-level design
• Behavioral rounds mapped to Leadership Principles
• Role-specific deep dives

4) Bar Raiser round

This is the one everyone talks about. Bar Raiser focuses on whether you raise the hiring bar, not just pass average expectations.

You can do well in coding and still fail if your ownership, judgment, and principle alignment look weak.

Leadership Principles: all 16 and how to prepare#

Yes, you need to know all 16. Not for mugging up one-line definitions, but for story mapping.

The 16 principles:

1. Customer Obsession
2. Ownership
3. Invent and Simplify
4. Are Right, A Lot
5. Learn and Be Curious
6. Hire and Develop the Best
7. Insist on the Highest Standards
8. Think Big
9. Bias for Action
10. Frugality
11. Earn Trust
12. Dive Deep
13. Have Backbone; Disagree and Commit
14. Deliver Results
15. Strive to be Earth's Best Employer
16. Success and Scale Bring Broad Responsibility

How to prep them without sounding scripted

• Pick 6 to 8 strong stories from college, internship, full-time, or side projects.
• Map each story to 2 to 3 principles.
• For every story, keep proof points: numbers, timeline, constraints, and your direct contribution.
• Practice speaking in 90-second and 3-minute versions.

If you only memorize principle names, interviewers will spot it in two minutes. If you show real decisions and outcomes, they will remember you.

STAR method for behavioral rounds, with Indian examples#

STAR means Situation, Task, Action, Result. Everyone knows the acronym, but many answers still fail because they are too vague.

Example 1: College fest payment failure (Customer Obsession + Ownership)

• Situation: During our college cultural fest, UPI payment confirmations were failing during peak registration.
• Task: As tech lead for the registration portal, I had to stop payment confusion and reduce manual support load.
• Action: I set up a temporary verification queue using transaction references, added an auto-retry check every 2 minutes, and created a helpdesk sheet with status tags for volunteers.
• Result: Duplicate payment complaints dropped by around 60 percent in one day, and queue wait time fell from about 45 minutes to 12 minutes.

Example 2: Internship API bottleneck (Dive Deep + Deliver Results)

• Situation: At a Bengaluru startup internship, one API was timing out during afternoon traffic spikes.
• Task: I was asked to investigate without breaking current release timelines.
• Action: I profiled query latency, found missing indexes and repeated joins, proposed index changes, and added response caching for top endpoints.
• Result: P95 response time improved from 1.8 seconds to 700 milliseconds, and support tickets related to slowness reduced in the next sprint.

Example 3: Team conflict in final-year project (Earn Trust + Disagree and Commit)

• Situation: Our four-member final-year project team split over whether to ship fast or redesign architecture.
• Task: I had to resolve conflict and keep deadline safe.
• Action: I ran a 45-minute decision meeting, listed risks on both paths, pushed for a phased release, and agreed to own post-demo refactor work.
• Result: We submitted on time, demo worked without crashes, and the refactor plan was completed in two weeks.

Why these examples work

They show scale, pressure, decision quality, and measurable outcomes. That is what Amazon interviewers look for.

How to apply: amazon.jobs vs referrals vs LinkedIn#

Most candidates spray applications everywhere and then wonder why nothing moves. A better approach is channel strategy.

amazon.jobs (official portal)

This is still the base channel. Apply here for all roles, track IDs, and keep resume variants ready by role family.

Tips:

• Apply only to close-fit roles.
• Keep title alignment clear in resume.
• Use role-relevant keywords from JD naturally.

Referrals

Referrals help with visibility, not guaranteed selection. Good referrals come from people who can vouch for your fit, not from random cold DMs.

Tips:

• Send a short note with role ID, resume, and why you match.
• Ask once, politely. Do not spam.
• If referred, still prepare as if no advantage exists.

LinkedIn

Useful for discovering openings, reaching recruiters, and timing your application when a role goes live.

Tips:

• Follow Amazon recruiters and hiring managers in your target domain.
• Engage with relevant posts in a normal, professional way.
• Keep your headline and about section specific.

Best combo for most people: find role on LinkedIn, apply on amazon.jobs, then seek a relevant referral.

Salary bands in India: SDE 1, SDE 2, SDE 3#

Numbers vary by city, team, market cycle, and negotiation. So treat these as practical ranges, not promises.

SDE 1 (entry to early career)

Typical total annual range often lands around INR 18L to INR 30L, with fixed pay plus joining stock/bonus components depending on offer cycle.

SDE 2 (experienced IC)

Common total annual range is often around INR 30L to INR 55L, with stronger stock components and role-level expectations on ownership and system thinking.

SDE 3 (senior individual contributor)

Ranges can move widely, but many offers fall roughly around INR 55L to INR 90L+ total annualized value depending on business need and candidate strength.

Important notes:

• First-year vs second-year cash flow can look very different.
• Stock vesting schedule matters as much as CTC headline.
• Comp should be judged against role intensity and growth path, not just top number.

Amazon PIP culture: the elephant in the room#

You cannot discuss Amazon careers honestly without talking about performance pressure.

Yes, Amazon is known for high expectations. Some teams are intense, some are very manageable. Experience varies a lot by manager, org maturity, and business pressure.

What candidates should know:

• Performance clarity matters from day one.
• Documentation of your work and impact helps.
• Silent struggle is risky. Early communication is safer.
• Team selection matters more than brand hype.

How to reduce risk after joining:

1. Align with manager on 30-60-90 day goals in writing.
2. Track weekly impact with clear metrics.
3. Escalate blockers early, with options.
4. Build trust with peers who can unblock dependencies.
5. Keep interview readiness alive, even after joining. This is practical career hygiene.

Do not let internet fear threads make your decision for you. Ask better questions during interviews about team culture, on-call load, review cycle expectations, and success signals.

Tips from people who recently got Amazon India offers#

Based on common patterns from recent offer stories, these habits keep showing up.

1) They prepared for principles as seriously as coding

Many candidates over-focus on LeetCode and ignore behavior rounds. Offer winners did both.

2) They built a story bank before interviews

Not just one project story. They prepared 8 to 10 usable stories with metrics and clear ownership.

3) They practiced out loud

Silent prep is weak for behavior rounds. Speaking answers helps remove filler and confusion.

4) They targeted roles by fit, not ego

Candidates who applied to role families matching their actual strengths got better response rates than those chasing random titles.

5) They treated OA like a real elimination stage

OA failure usually ends the process immediately. Serious candidates timed mock sessions and practiced under pressure.

6) They asked smart questions in final rounds

Questions about team goals, architecture pain points, and first 90-day outcomes signal maturity.

AWS vs Retail vs Other divisions: what should you target?#

There is no one "best" division for everyone. Choose based on your skill profile and stress tolerance.

Target AWS if:

• You enjoy infra, systems, reliability, distributed computing
• You are comfortable with Linux, networking, and debugging under pressure
• You want exposure to enterprise cloud use cases

Target Retail tech if:

• You like high-scale consumer systems
• You enjoy fast shipping cycles and business-linked metrics
• You want broad product and platform experience

Target Operations or program-heavy teams if:

• You like execution, process improvement, and cross-functional work
• You are good with data-backed decisions in messy real-world settings
• You prefer business + tech intersection work

Target Ads and analytics-linked units if:

• You enjoy metrics, experimentation, and revenue-linked problems
• You can connect data work to customer and business outcomes

Simple rule: pick the division where your past work already sounds natural. Interviewers trust candidates whose stories fit the job reality.

A practical 30-day prep plan for Amazon India#

If you want to apply this month, here is a realistic plan.

Week 1

• Shortlist 20 relevant roles across your target cities.
• Build two resume variants: core SDE and data/cloud (as needed).
• Start a story bank document with 10 STAR stories.

Week 2

• Practice OA-style coding daily with timer.
• Revise one data structure family each day.
• Start mock behavior interviews with a friend.

Week 3

• Do 2 full mock loops: coding + behavior same day.
• Improve weak principles by adding better examples.
• Reach out for targeted referrals with role IDs.

Week 4

• Apply in batches, track status in a sheet.
• Follow up politely where relevant.
• Keep prep active until interviews are done.

This process is boring, but it works better than panic-applying to 200 roles.

Final take#

Amazon India after layoffs is not a closed door. It is a narrower door.

In 2026, teams are hiring where business impact is clear, especially in engineering, cloud, data, and operations-linked tracks. If you prepare seriously for coding plus Leadership Principles, choose the right division, and apply through the right channels, your chances are real.

If you want role-by-role tracking, team signals, and smarter targeting before you apply, use the JobRise Company Insights tool. It helps you filter noise, focus on active hiring pockets, and plan your applications with better odds.