Walmart SE3 UI 2025: Frontend Engineer, 4 Rounds, Offer Declined Because It Was Below Current Base

TL;DR. Frontend engineer with 4+ years in JavaScript and React, recruited via LinkedIn by a Walmart recruiter who said the profile "stood out." Four rounds: DSA (First Missing Positive, Valid Parentheses, Two Sum in 60 minutes), React/JS technical discussion (Virtual DOM, useMemo implementation, Context API with API results, responsive vs adaptive design, GraphQL, Next.js), hiring manager (project innovation via STAR, testing frameworks, CI/CD, React performance), and HR connect (compensation discussion). Cleared all four. Got the offer. Negotiated for 3 weeks. Final number still fell below current base salary. Declined. No further communication from HR.

This is not a Walmart interview preparation guide. This is the rarer story: what happens when you clear the entire loop, get the offer, and still walk away. The interview questions, the React/JS depth, the compensation dynamics, and the silent close from HR after a candidate declines.

What declining a Walmart offer looks like

Most interview experience posts end with "got the offer" or "got rejected." This one ends with a third outcome that is rarely discussed publicly: the candidate cleared every round, received the offer, spent 3 weeks negotiating, and declined because Walmart's final number did not match their current compensation.

This matters for two reasons:

1. SE3 at Walmart Global Tech is a senior position. SE3 maps roughly to Staff/Senior Staff at smaller companies. The compensation band for SE3 in India (as of 2025) is approximately ₹50 to 80 LPA depending on team, location, and negotiation. If a candidate with 4+ years of frontend experience found the offer below their current base, it suggests their current compensation was already in the upper range of the market for frontend specialists.

2. HR ghosted after the decline. The candidate explicitly noted that there was no follow-up communication from Walmart HR after declining. No counter-offer, no "let us revisit this in 6 months," no acknowledgment. This is common at large companies with structured compensation bands. If the candidate's ask exceeds the band, and the band cannot be extended, the conversation simply ends.

The frontend profile that got recruited

The LinkedIn recruitment channel is significant. The candidate did not apply on Walmart's careers page. A Walmart recruiter found their profile and initiated contact. This means the candidate's LinkedIn signaled strong frontend expertise (React, JavaScript, likely performance optimization or architecture experience) at a level that Walmart's talent acquisition flagged as SE3-caliber.

Round 1: DSA (60 minutes)

Three problems in 60 minutes, all solved with complexity explanations.

Problem 1: First Missing Positive

This is a hard-rated LeetCode problem. Solving it in a 3-problem round means you have roughly 20 minutes. The cyclic sort approach is the canonical solution. Hash set works but uses O(n) space, which will get you a follow-up question about space optimization.

Problem 2: Valid Parentheses

Standard stack problem. In a multi-problem round, this is the warm-up. Complete it in 5 to 7 minutes and move on.

Problem 3: Two Sum

The easiest problem on LeetCode. In a round that also includes First Missing Positive, this is the anchor: if you cannot solve Two Sum cleanly in 3 minutes, the interviewer recalibrates their assessment downward.

Round assessment: The DSA round at Walmart SE3 UI mixes one hard problem with two easy problems. The hard problem is the calibration signal. The easy problems are confidence checks. Failing either easy problem is a stronger negative signal than struggling with the hard problem.

Round 2: React/JS Technical Discussion (60 minutes)

This round had no coding. It was a 60-minute technical conversation on frontend concepts, frameworks, and architecture. The interviewer tested both breadth and depth.

Topics covered

Analysis: This round is distinctly frontend-focused. Walmart's SE3 UI position is not a generalist SDE role. They expect deep React knowledge, framework internals, and opinions on architecture trade-offs. If you come from a backend-heavy background and are interviewing for a UI-specific role at Walmart, this round will expose the gap.

The useMemo implementation question is particularly notable. Most frontend engineers use useMemo daily but cannot explain its internal mechanism: it stores the previous dependency array, compares each element with Object.is() on re-render, and returns the cached value if all dependencies are unchanged. Knowing this at the implementation level signals that you understand React's rendering model, not just its API.

The candidate received a same-day callback to schedule the next round, which is a strong positive signal.

Round 3: Hiring Manager (60 minutes)

The HM round combined behavioral assessment with technical probing.

Topics covered

The candidate felt uncertain about their innovation answer. This is a common friction point in HM rounds at large companies: "innovation" at a startup (building a feature from scratch) feels different from "innovation" at an enterprise (optimizing an existing system). Walmart's SE3 role expects the latter, where innovation means measurably improving performance, developer experience, or system reliability within an existing large codebase.

The interviewer appeared distracted during parts of the round. The candidate noted this specifically. Whether this affected the evaluation is unclear, but it added uncertainty to the candidate's self-assessment.

Round 4: HR Connect (30 minutes)

The final round was not a technical evaluation. It was a compensation and logistics discussion.

The HR connect round is where most candidates assume the process is complete. The candidate had cleared all technical rounds. The offer was in motion.

What followed was 3 weeks of negotiation. The candidate's current compensation was above Walmart's initial offer. The candidate pushed for a higher number. Walmart adjusted, but the final number "still fell below my current base."

The candidate declined.

No further communication from HR. No counter-offer. No "let us revisit this later." Silence.

The compensation cliff: when an offer is not an offer

Walmart Global Tech operates with structured compensation bands. Each level (SE1, SE2, SE3) has a defined range for base, bonus, and RSUs. Recruiters have some flexibility within the band but cannot exceed it without VP-level exception approval.

For SE3 UI positions in India, the compensation band (as of 2025 market data) is approximately:

If the candidate's current base was above ₹55 LPA (the upper end of the base range), Walmart's offer structurally could not match it without RSU loading, which candidates often discount because RSUs vest over 4 years and are subject to stock price risk.

This is a real constraint that senior frontend engineers encounter when interviewing at large companies. Your market rate at a well-funded startup or a FAANG competitor may exceed the compensation band of the specific role you are interviewing for. Clearing the interview loop does not guarantee a financially viable offer.

What frontend engineers should know about Walmart's interview bar

1. DSA is still tested at SE3 UI. Even for a frontend-specific role, you will face a coding round with LeetCode problems. First Missing Positive is hard-rated. Do not skip DSA preparation because the role title says "UI."

2. Framework internals matter more than API knowledge. Knowing that useMemo exists is not enough. Knowing how its dependency comparison works, when it actually prevents re-renders versus when it does not, and when to use useCallback instead is what SE3-level evaluation expects.

3. The HM round evaluates enterprise-scale thinking. "I built a todo app with React" is not an innovation story. "I reduced our bundle size by 40% through code splitting and lazy-loaded our heaviest routes, dropping first paint from 4.2s to 1.8s" is.

4. Compensation negotiation has structural limits. Walmart's bands are real. If your current comp is above the band, negotiation will not bridge the gap. Ask the recruiter for the compensation range early (before Round 1 if possible) to avoid investing time in a process that cannot produce a financially viable offer.

5. Post-decline silence is normal. Walmart will not chase you. If you decline, the file closes. There is no counter-offer mechanism for candidates who decline the final number.

Where this comes from

PapersAdda's verification standard requires a publicly accessible post URL, per-round detail from the candidate, and a stated outcome. This post meets all three criteria. The candidate described all 4 rounds, named the specific questions, and documented the offer-then-decline outcome, including the 3-week negotiation and the post-decline silence.

Source: My Interview Experience at Walmart Global Tech for the Software Engineer 3-UI Position by Phalgun Mittal on Medium.

Worth reading next

• Swiggy SDE-2 Backend Bangalore 2025: ₹40 LPA, Rejected at Train Booking LLD, the other side: rejected despite wanting the job
• CRED SDE-2 Bangalore 2024: Payment Processor Offer, Then Comp Failed, another case where the offer existed but the money did not
• Google L4 India: 7-Round Downlevel to Rejection, process outcomes are unpredictable even when signals are positive
• Goldman Sachs Analyst Campus 2025: 10.5-Hour Marathon, for contrast, a campus process where comp is standardized and non-negotiable