Lenskart interview reports describe a quick, practical process: an HR call, a DSA and project round, a coding or machine coding round (system design for backend), a techno-managerial round and HR. DSA is easy to medium on arrays, strings and hashing, but candidates who stopped at brute force were rejected. Backend candidates in 2026 got detailed questions on Kafka, distributed transactions and Spring. A sales manager was hired after one three-person panel at the head office.
Lenskart interview process round by round
| Round | What candidates reported |
|---|---|
| HR call | 5-10 min: current company, CTC, expected CTC, stack |
| Online assessment (some roles) | Medium to difficult DSA under a time limit; valid parentheses |
| Technical 1 | Project deep dive, DSA, CS fundamentals, SQL |
| Technical 2 | Coding with system design (backend) or JavaScript and React machine coding (frontend); automation framework (SDET) |
| Techno-managerial | Technical depth plus team and ownership |
| HR | Salary negotiation and joining |
Lenskart interview experiences: what candidates reported
These are self-reported accounts on GeeksforGeeks and Taro (jointaro.com). Each is one person’s experience.
- SDE-2 (GeeksforGeeks, updated July 2025, rejected). HR call, then a one-hour round with a tech lead: project discussion, pairs divisible by 60, a HashSet implementation and HashMap internals, and a SQL count by city. Rejected about 30 minutes later after giving only brute force for the first problem.
- SDE-2 backend (September 2026, no offer). Round 2 covered Kafka partitions and replication factor, a payment that succeeds without an inventory lock, Spring scheduled jobs on three instances, @Async side effects in a payment flow, and an RBAC schema.
- Frontend developer (June 2026, accepted offer). Four rounds: two easy-medium string and array problems, a JavaScript and React machine coding round, a techno-managerial round and HR.
- Senior SDET (May 2026, accepted offer). Three virtual technical discussions (Java strings and arrays, the automation framework, techno-managerial) and HR.
- Senior software engineer, Bengaluru (August 2026, no offer). A timed online assessment with medium to difficult DSA, including valid parentheses. About five days.
- Backend developer, Bengaluru (August 2026, no offer). HR called on a Friday evening; an onsite DSA round the next morning with an SDE 2, one LeetCode medium in pseudocode.
- SDE Android, Bengaluru (July 2026, no offer). A first round on Kotlin coroutines and Android: view lifecycle callbacks, which thread a ViewModel runs on, custom views, Compose and workers.
- Software engineer, Gurgaon (September 2024, accepted offer). DSA and resume questions the candidate called fairly easy: reverse a linked list optimally, easy SQL and core concepts.
- Application developer (GeeksforGeeks). A phone HR round, then a technical round with four questions: same BST from two arrays, word break into all sentences, all subsets, and a parking lot design.
- Sales Manager (GeeksforGeeks, updated July 2023, accepted offer). One panel at the head office with the Head of Sales, an HR manager and a senior sales executive. Offer a few days later.
Detailed interview experiences
Experience 1: SDE-2, Java backend (GeeksforGeeks)
HR call (5-10 minutes): current company, CTC, expected CTC, tech stack. HR said there would be three technical rounds: DSA and CS fundamentals, coding-heavy with system design, and techno-managerial.
Round 1 (about 1 hour, tech lead with 8-9 years’ experience):
- 20 minutes on a Java and Spring Boot project: database, microservices, deployment.
- Count pairs of song durations divisible by 60. Brute force O(n squared), then asked to optimize; the hash-map attempt was flawed.
- Implement a HashSet with O(1) add and contains; HashMap internals, load factor and collisions.
- SQL: count employees in Bengaluru, Delhi and Chennai with GROUP BY.
Result: rejection email about half an hour later.
Candidate’s advice: know your project schema and design reasons, revise arrays and strings, and practice moving past brute force.
Experience 2: SDE-2 backend (September 2026)
Round 2 questions:
- Why does Kafka need partitions?
- What is the Kafka replication factor?
- A payment succeeds but inventory is not locked. What happens?
- Why use a scheduler in Spring WebFlux, and what happens when three instances run the same scheduled job?
- How does @Async in one payment service affect other services, and how do you fix it?
- Design an RBAC schema for authentication and authorization.
Result: no offer.
Takeaway: For backend roles, Lenskart’s second round is distributed systems in an e-commerce setting: orders, payments, inventory.
Experience 3: Frontend developer (June 2026, offer)
Round 1: two easy-medium DSA problems on strings and arrays.
Round 2: pure JavaScript and React machine coding.
Round 3: techno-managerial.
Round 4: HR, including salary negotiation.
Experience 4: Application developer (GeeksforGeeks)
HR: a short phone round.
Technical: four questions: check whether two integer arrays produce the same BST (2,1,3 and 2,3,1 do); split a string with no spaces into all dictionary sentences; all subsets of a set; design a parking lot.
Experience 5: Sales Manager (GeeksforGeeks, offer)
Panel at the head office: the Head of Sales asked about background and record against targets; the HR manager asked how the candidate builds customer relationships and handles difficult situations; the senior sales executive asked how to grow Lenskart’s market share in a competitive market. Follow-ups on leadership style and motivating a team.
Result: offer a few days later, accepted.
Lenskart interview questions that come up often
DSA
- Pairs of song durations divisible by 60
- Implement a HashSet
- Reverse a linked list
- Valid parentheses
- Same BST from two arrays
- Word break into all sentences
- All subsets
Backend and design
- Kafka partitions and replication factor
- Payment succeeds without an inventory lock
- Duplicate scheduled jobs across instances
- RBAC schema
- Parking lot design
Android and frontend
- View lifecycle callbacks; which thread a ViewModel runs on
- JavaScript and React machine coding
HR and sales
- Current and expected CTC
- Growing market share in a competitive market
- Leadership style and motivating a team
Answers for the technical questions are on the Lenskart interview questions hub, and HR answers are on the Lenskart HR interview questions page.
Lenskart interview tips from these reports
DSA
- Never stop at brute force.
- Arrays, strings and hashing come up most.
Backend
- Kafka, sagas and distributed locks.
- Know your project schema cold.
Process
- Drives can be scheduled for the next morning.
- Have CTC and notice period ready for the first call.
Similar companies
Nykaa · Meesho · Flipkart · Swiggy
Sources
- GeeksforGeeks: Lenskart interview experience for SDE-2
- GeeksforGeeks: Lenskart interview experience for Application Developer
- GeeksforGeeks: Lenskart interview experience for Sales Manager
- Taro: SDE-2 backend, September 2026
- Taro: frontend developer, June 2026
- Taro: senior SDET, May 2026
- Taro: senior software engineer, Bengaluru, August 2026
- Taro: backend developer, Bengaluru, August 2026
- Taro: SDE Android, Bengaluru, July 2026
- Taro: software engineer, Gurgaon, September 2024