Lenskart Business Analyst Interview: Questions, Experience & Prep (2026)

Lenskart is one of India's largest omnichannel eyewear retailers, combining physical stores, a strong e-commerce platform, and home eye-testing services. A Business Analyst at Lenskart works across retail performance, customer analytics, pricing, and new market expansion. The role is data-heavy: candidates report being tested on SQL, business case reasoning, and the ability to translate numbers into clear decisions.

As of July 2026, Lenskart had 228 open roles tracked by knok jobradar, signalling active hiring across teams. Across India, knok tracked 398 Business Analyst openings in the same period, with Bangalore (53 openings) and Delhi (48 openings) leading by city. The interview process typically runs across two to four rounds, moving from an initial HR conversation to technical and analytical assessments, and finally a business case or managerial discussion. Rounds are usually conducted online for outstation candidates, with some in-person steps for shortlisted applicants in the home city.

These questions come up frequently in Lenskart BA interviews, based on candidate reports and the nature of Lenskart's business.

1. How would you measure the success of a new Lenskart store opening in a Tier 2 city?
2. Lenskart sells through both its website and physical stores. How would you identify if one channel is pulling customers away from the other?
3. Walk us through how you would design a daily performance dashboard for store managers across multiple outlets.
4. A store's footfall is steady but conversion has dropped noticeably over two months. How do you find the root cause?
5. How would you approach pricing a new premium frame collection, given that Lenskart already has budget and mid-range options?
6. Lenskart's home eye-testing service has lower repeat bookings than expected. How would you investigate and recommend a fix?
7. How would you design an A/B test for a new discount offer on the Lenskart mobile app?
8. What single metric would you choose to track the health of Lenskart's customer base, and why?
9. Online orders have a noticeably higher return rate than in-store purchases. What would you do with that finding?
10. How would you estimate the market size for Lenskart if it launched a contact lens subscription service?
11. Describe a time you took raw data and turned it into a recommendation that changed a business decision.
12. How would you forecast demand for a new frame style before its launch?

Q: Describe a time you took raw data and turned it into a recommendation that changed a business decision.

*Situation:* I was working as a junior analyst at a retail company that was planning to open three new stores in the same quarter. The leadership team assumed all three locations had similar sales potential.

*Task:* My job was to validate that assumption using sales and footfall data from comparable existing stores in similar localities.

*Action:* I pulled transaction data from comparable stores, segmented by locality type, average ticket size, and customer demographics using SQL. I built a scoring model in Excel that ranked the three new locations on five factors: walk-in potential, nearby competition, catchment area income level, proximity to existing stores, and rental cost. I presented my findings with clear visuals, showing that one of the three locations was likely to underperform based on every signal we had.

*Result:* The team delayed the weakest location by one quarter and reallocated that budget to a faster-moving market. The two stores that did open hit their first-month targets. This taught me to question assumptions early, before capital is committed.

---

Q: How would you investigate why Lenskart's home eye-testing service has lower repeat bookings than expected?

*Situation:* Suppose the service shows strong first-time bookings but customers are not returning for follow-up appointments or eyewear purchases after their initial test.

*Task:* The goal is to identify whether the drop-off is a product issue, an awareness issue, a pricing issue, or a service quality issue, so the team can act on the right lever.

*Action:* I would start by segmenting customers who booked once versus those who booked more than once, looking for patterns in geography, age group, and purchase outcome (did they buy frames after the test?). I would then check customer feedback scores and read through support tickets to spot recurring complaints. Finally, I would run a short survey with one-time customers asking one direct question: 'What would make you book again?' This combination of quantitative segmentation and qualitative feedback usually points to the real blocker quickly.

*Result:* In a similar analysis I have done, the issue turned out to be that customers did not realise they could book follow-up tests. A simple in-app reminder moved repeat bookings noticeably within a few weeks.

---

Q: Walk us through how you would design a daily performance dashboard for Lenskart store managers.

*Situation:* Store managers at a retail chain were receiving performance reports weekly, which meant issues went unnoticed for days at a time.

*Task:* I was asked to design a daily dashboard that store managers could check each morning without needing a data team to run reports for them.

*Action:* I spoke to five store managers first to understand what decisions they actually make each day: staffing levels, running promotions, flagging slow-moving stock, and reviewing shift performance. Based on these conversations, I picked a small set of core metrics: daily revenue vs. target, footfall, conversion rate, average transaction value, and top and slow-moving SKUs. I built the dashboard in a BI tool connected to the POS system, with automatic refresh each morning, and kept the layout to a single screen so managers did not need to scroll.

*Result:* Within a month, several stores identified and corrected floor layout issues that had been quietly hurting conversion. The dashboard became the standard morning tool for that region.

Use these structured approaches when you get a 'how would you' question.

For diagnostic questions (why did a metric drop, why is something underperforming): Start by clarifying what the metric measures and what 'normal' looks like. Then break the problem into internal factors (team, process, product) and external factors (competition, seasonality, market shift). Pick the most likely cause first, state what data you would look at to confirm it, and only then suggest a fix. Lenskart interviewers appreciate candidates who do not jump to solutions before checking the data.

For estimation questions (market size, demand forecasting): Use a top-down or bottom-up approach and say out loud which one you are choosing. For a market size question, start with the population of eyewear users in India, estimate what share Lenskart can realistically address, and build from there. State your assumptions clearly. Interviewers are testing your logic, not your ability to guess the 'right' number.

For metric design questions (what would you track): Use the goal-signal-metric ladder. Start with the business goal, identify what user or operational behaviour signals progress toward that goal, then pick the metric that best captures that signal. Avoid vanity metrics like total app downloads or page views unless they connect clearly to a business outcome.

For A/B test design questions: Cover four things in order: what you are testing and why, how you will split the audience, what your success metric is, and how long you will run the test before deciding. Mention the need for statistical significance without overcomplicating it.

For case studies: Structure your answer with a brief restatement of the problem, your approach, the data you would use, and your recommendation. Keep it concise. Practice saying 'I would first check X, because it tells me Y' rather than listing everything you know.

Lenskart BA interviewers are typically looking for five things, based on what candidates report from their experience.

Business intuition rooted in retail context. Lenskart is not a pure tech company. Interviewers want to see that you understand retail dynamics: footfall, conversion, ticket size, seasonal demand, and the difference between online and offline customer behaviour. Generic data answers that could apply to any industry score lower than answers that show you understand how an omnichannel eyewear business actually works.

Structured thinking under pressure. When you get a vague question, candidates who pause, clarify the goal, and then structure their answer stand out. Interviewers at Lenskart frequently report giving candidates open-ended problems on purpose, to see if they can impose structure without being prompted.

Comfort with SQL and basic analytics tools. The technical bar is real. Candidates report SQL questions involving joins, aggregations, window functions, and occasionally subqueries. You do not need to be a data engineer, but you should be able to write a query from scratch during the interview without hesitation.

Clear communication of trade-offs. Lenskart's business involves real trade-offs: premium vs. budget positioning, online vs. store growth, customer acquisition vs. retention spend. Interviewers want to see that you can name the trade-off, not just recommend one option as if the other does not exist.

Ownership mindset. Multiple candidates report being asked about times they took initiative beyond their immediate responsibilities. Lenskart values analysts who treat problems as their own, not as tasks assigned to them.

Week 1: Build your Lenskart knowledge base.

Read publicly available information about Lenskart: their product range, store expansion news, and any interviews their leadership has given. Understand the difference between their online business and their store business. Note which cities they are expanding into and what that might mean for a BA supporting that growth. Prepare two or three observations you can bring up naturally in the interview to show you did your homework.

Week 2: Sharpen your SQL and analytics skills.

Practice SQL queries covering joins, GROUP BY, HAVING, window functions (ROW_NUMBER, RANK, LAG), and subqueries. Use platforms like LeetCode at Medium difficulty or Mode Analytics practice problems. For Excel or Python, practice pivot tables and basic data cleaning. You should be able to write a moderately complex query quickly, without looking things up.

Week 3: Practice case interviews out loud.

Pick five business problems related to retail or e-commerce and answer them out loud, not just in your head. Record yourself once and listen back. Common problem types at Lenskart: metric drops, market sizing, A/B test design, and dashboard design. Use the frameworks in the Answer Frameworks section of this guide. Practice with a friend if possible and ask for honest feedback on whether your logic was clear.

Week 4: Mock interviews and story preparation.

Prepare four to five STAR stories from your own experience. Each story should cover a situation where you used data to change a decision, worked across teams, or fixed something that was broken. Review your resume line by line and be ready to go deep on any project listed. Do at least one full mock interview under conditions as close to the real thing as possible.

If you are still searching for the right BA role while you prepare, knok checks 150+ job sites nightly, applies to jobs matching your resume, and messages HR for you, so you can put your energy into interview prep rather than job hunting.

Jumping to solutions before understanding the problem. In diagnostic questions, many candidates immediately suggest fixes (run a discount, improve the UX) before checking what the data actually shows. Lenskart interviewers notice this and it signals poor analytical discipline. Always state what you would measure first.

Being too generic. Saying 'I would improve customer experience' or 'I would analyse the data' without specifics is the fastest way to lose points. Name the specific metric, the specific data source, and the specific action you would take.

Ignoring the business context. A technically correct answer that does not account for Lenskart's actual business model (omnichannel, price-sensitive market, rapid store expansion) will feel off to interviewers. Show that your recommendations are feasible for a company at Lenskart's stage.

Weak SQL preparation. Many candidates underestimate the technical round. Candidates report being given SQL problems on a shared screen with no reference material available. Practice writing queries from memory before you walk in.

Not quantifying results in STAR answers. 'The project was successful' is a weak result. Even if you cannot share confidential business numbers, say something like 'the team adopted the dashboard as their primary tool' or 'the recommendation led to the decision being reversed.' Concrete outcomes matter even without specific figures.

Overcomplicating the answer. Lenskart operates at pace. Interviewers prefer a clear, simple recommendation with acknowledged trade-offs over a complex model with many variables. When in doubt, simplify your answer and check if the interviewer wants more depth.