The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online / Written Round | ~60–90 min | Coding fundamentals screen |
| Technical – DSA | ~45–60 min | Optimized problem-solving |
| System Design / LLD | ~45–60 min | Designing commerce systems |
| Hiring Manager / Project Discussion | ~30–45 min | Depth, scale, and fit |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Online / Written Round
~60–90 minAn online coding test or, in some campus loops, a pen-and-paper DSA round. Problems lean core data structures and algorithms at easy-to-medium difficulty. Correctness and clear complexity reasoning are what advance you.
- Array and hashmap manipulation
- String processing for product data
- Linked-list operations
- Basic tree traversals
- Simple DP or greedy on pricing
- Drill array, string, and hashmap mediums (leetcode.com)
- Review linked-list and tree templates
- Practice writing correct code by hand for the paper round
- Follow Striver's SDE sheet basics (takeuforward.org)
- Off-by-one and null-pointer errors
- No complexity analysis
- Overcomplicating an easy problem
- Correct, clean solutions
- Accurate complexity reasoning
- Solid fundamentals under time
Technical – DSA
~45–60 minOne or two problems where you write clean, bug-free, optimized code and explain your thinking and complexity. Expect follow-ups on optimization and edge cases. Communication of your approach is weighted heavily.
- Top-K products by rating with a heap
- Two-pointer on sorted price lists
- Tree/BST operations on category trees
- Sliding window over order events
- Hashmap-based frequency and grouping
- Solve 15+ heap, tree, and two-pointer mediums (neetcode.io)
- Narrate brute-force-to-optimal aloud
- Drill time/space analysis
- Do a couple of peer mocks
- Coding before explaining the approach
- Ignoring the optimization follow-up
- Missing edge cases
- Clean, optimized, bug-free code
- Clear complexity discussion
- Good approach articulation
System Design / LLD
~45–60 minYou design a retail-flavored system, sometimes low-level (classes and APIs) and sometimes higher-level with schema and scaling. Expect API implementation and data-schema design plus follow-ups. Practical, correct modelling beats over-engineering.
- Design a retail-outlet / store ordering system
- Cart and checkout with inventory holds
- Product catalog and search schema
- Order-tracking state machine
- Coupon / discount rule engine
- Study the System Design Primer (github.com/donnemartin)
- Practice API and schema design for commerce flows
- Review SOLID and LLD patterns (refactoring.guru)
- Design 3–4 e-commerce systems with a timer
- Skipping requirement clarification
- Vague or normalized-wrong data schema
- Ignoring inventory/payment consistency
- Clean API and schema design
- Sensible consistency handling for orders
- Right-sized design for the prompt
Hiring Manager / Project Discussion
~30–45 minA detailed walk through your past projects and experience, sometimes with a high-level design of a system at scale. The manager probes ownership, technical depth, and how you handle production reality. Behavioral and motivation questions round it out.
- A project you owned end to end
- Scaling or performance work you did
- A production bug you diagnosed
- Handling shifting requirements
- Why Nykaa / e-commerce
- Prepare 5 metric-backed STAR stories
- Be ready to sketch a past project's architecture
- Research Nykaa's platform and scale events (sales)
- Prepare good questions for the manager
- Shallow project descriptions
- No quantified impact
- Generic motivation
- Real ownership and depth
- Clear reasoning under scale
- Authentic interest in the domain
What to master
- Arrays, strings & hashmaps
- Linked lists & trees
- Heaps & two pointers
- Dynamic programming basics
- Low-level design / OOP
- E-commerce system design
- Databases & schema design
- Caching & consistency
Eligibility
open — role-based
Nykaa salary & compensation (2026)
Nykaa pays market India cash with ESOP that grows at senior levels; entry offers are solid product-company packages.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| SDE-1 | 0–2 yrs | ₹14–24 LPA | — | e.g. ~19L fixed + ~2L variable + ~2L joining bonus |
| SDE-2 | 2–5 yrs | ₹24–40 LPA | — | fixed + ~10% variable + ESOP |
| SDE-3 / Senior | 5–8 yrs | ₹40–60 LPA | — | larger ESOP and variable weighting |
| Staff / Lead | 8–12 yrs | ₹60–90 LPA | — | ESOP a meaningful slice of comp |
| Principal / EM | 12+ yrs | ₹90 LPA+ | — | equity-weighted; negotiable |
How the package is structured
- Packages are fixed base + ~10% variable + joining bonus + ESOP that grows with level.
- Specialized tracks (MLE/MLOps) can command a premium over standard SDE bands.
- Since Nykaa is public, ask about RSU/ESOP vesting and current price to value equity.
- Interview at the highest level you can justify — level placement outweighs negotiation.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Days 1–4: arrays, strings, hashmaps, and linked lists
- Days 5–7: trees, heaps, and light DP with a timed test
- Days 8–9: two LLD/API+schema designs for commerce flows
- Days 10–11: one HLD (cart/checkout or catalog) with follow-ups
- Day 12: five STAR stories and a project walkthrough
- Days 13–14: mixed mocks and cleanup
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
Is the interview very LeetCode-hard?
It leans moderate — solid easy-to-medium DSA plus practical design — rather than the hardest algorithmic bar among consumer companies.
Do frontend and SDET loops differ?
Yes. Frontend rounds add JS, framework, and UI-design questions, and SDET adds testing and automation depth, while DSA fundamentals remain common.
Should I expect a pen-and-paper round?
Some campus loops still use a written DSA round, so practice writing correct code by hand.