myglamm Data Analyst Interview: Questions, Experience & Prep (2026)

MyGlamm is one of India's leading D2C beauty and personal care companies, running brands like WYCON, BabyChakra, and St. Botanica alongside its flagship makeup line. The company operates a high-volume e-commerce and app-first business with significant spend on influencer marketing, paid social, and seasonal campaigns, which makes data analysts central to every revenue and retention decision.

As of July 2026, knok's job radar shows myglamm has 4 open Data Analyst positions. Candidates typically go through 2-3 rounds covering SQL, a take-home or live analytics task, and a business case discussion with the hiring manager. The role sits at the intersection of marketing analytics, product analytics, and commercial finance, so comfort with both numbers and storytelling matters.

Salary bands for Data Analysts across India currently run 5-10 LPA at entry level (0-2 years), 10-18 LPA at mid level (3-5 years), and 18-30 LPA at senior level (6-9 years), based on knok's job radar across 319 active Data Analyst listings.

SQL and data manipulation

1. Write a SQL query to find the top customers by total spend in the last 3 months, broken down by product category.
2. Given an orders table and a returns table, write a query to calculate net revenue per SKU after accounting for returns.
3. How would you identify users who made a first purchase but never came back? Write the SQL logic.

Business and product analytics

1. MyGlamm runs frequent discount campaigns. How would you measure whether a campaign actually grew revenue or just shifted future purchases forward?
2. If the app's add-to-cart rate drops after a new feature release, how would you investigate the root cause?
3. How do you calculate Customer Acquisition Cost for a D2C brand, and what would a healthy CAC-to-LTV ratio look like in the beauty segment?

Python and tools

1. You receive a raw Shopify export with missing values and inconsistent SKU names. Walk us through how you would clean this in Python before analysis.
2. How would you build a repeat-purchase cohort analysis? What tool would you use and what would the output look like?

Influencer and marketing analytics

1. MyGlamm works with a large number of influencers. How would you design a dashboard to track influencer campaign ROI across Instagram, YouTube, and offline gifting?
2. How would you set up an A/B test for a new product page layout? What metric would be your primary success indicator?

Behavioral and situational

1. Tell us about a time you found an insight in data that changed a business decision.
2. How do you prioritize when multiple teams each want a report or dashboard urgently?

Q: Tell us about a time you found an insight in data that changed a business decision.

*Situation:* I was working as a Data Analyst at a mid-size apparel e-commerce company. The marketing team was planning to increase spending on a top influencer campaign that had run well in previous seasons.

*Task:* My job was to pull the campaign performance report before the budget was approved for the next cycle.

*Action:* I segmented repeat buyers versus first-time buyers within the influencer's discount cohort and noticed that a large share of orders came from existing customers who would likely have purchased anyway at full price. I built a simple incremental revenue model comparing this cohort against a matched control group who had not seen the influencer code.

*Result:* The analysis showed the campaign was cannibalising margin on existing customers rather than acquiring new ones. The team shifted budget toward micro-influencers targeting new-to-brand audiences, and this approach became the standard framework for evaluating influencer ROI going forward.

---

Q: If the app's add-to-cart rate drops after a new feature release, how would you investigate the root cause?

*Situation:* At my previous company, we noticed a dip in add-to-cart conversions the week after a new product listing template went live.

*Task:* I was asked to confirm whether the drop was real and, if so, find the cause.

*Action:* I first segmented the metric by platform (Android vs iOS), by product category, and by traffic source to isolate where the drop was concentrated. I then compared funnel drop-off data for the new template versus the old one on a matched set of SKUs. I also checked whether any other changes had gone live in the same window, such as a pricing update or a payment gateway issue.

*Result:* The drop was concentrated on Android users viewing the new template for skincare SKUs. The CTA button was partially hidden on smaller screens. The product and engineering team rolled out a fix within two days and the metric recovered fully.

---

Q: How do you prioritize when multiple teams ask for reports at the same time?

*Situation:* During a quarter-end crunch at my previous role, I had simultaneous requests from the marketing team, the category team, and the finance team, all marked urgent.

*Task:* I had to deliver quality work to all three teams without missing a genuinely critical deadline.

*Action:* I asked each stakeholder two questions: what decision does this report inform, and what is the decision deadline? Finance needed numbers for board reporting by a fixed date, so that took priority. The category team request turned out to be exploratory, so I scheduled it for the following week. I gave marketing a quick summary table the same day and flagged that a deeper cut would follow.

*Result:* All three teams got what they actually needed on time. The category team later said the delay helped them refine their question, which led to a more useful final output.

For SQL questions: think out loud before writing code. State the tables you need, the join logic, and any edge cases (nulls, duplicates, returns). Interviewers at D2C companies like myglamm care as much about your reasoning as the final query.

For business case questions: use a simple structure. First, clarify the goal (is this about acquisition, retention, or monetisation?). Then define your metric, explain how you would pull the data, and describe what the output would look like. End with what decision it enables.

For 'why did metric X drop' questions: always segment before you conclude. Check time (was it a spike or a sustained drop?), platform, geography, user segment, and recent product changes. Myglamm operates across app, web, and some offline retail, so a drop on one surface does not mean a drop everywhere.

For behavioral questions: use the STAR structure strictly. Keep the Situation and Task brief (two to three sentences). Spend most of your time on the Action, because that is where interviewers assess your skill level. Quantify the Result where possible, but if specific numbers are not available, describe the decision that changed or the process that improved.

Candidates who have spoken to myglamm interviewers typically report that the panel looks for three things above technical skill.

Business context awareness. Myglamm is a D2C brand where margins matter and customer retention is a key lever. Analysts who understand concepts like repeat purchase rate, cohort LTV, and marketing attribution are preferred over those who only know database queries.

Clear communication. Analysts here present findings to marketing heads and category managers who are not always technical. Interviewers want to see that you can explain a finding in plain terms, not just produce a chart.

Hands-on SQL. Candidates report that at least one round involves a live or take-home SQL problem. The questions are typically practical, covering cohort analysis, funnel drop-off, or revenue reconciliation, rather than abstract puzzles.

Knowing myglamm's product portfolio (skincare, makeup, baby care), their reliance on influencer marketing, and their app-first distribution model will help you frame answers in a way that feels relevant rather than generic.

Week 1: SQL and Python fundamentals

Practice cohort queries, window functions (ROW_NUMBER, RANK, LAG), and funnel analysis in SQL. Build one small Python project that cleans a messy CSV and produces a summary table. Focus on pandas groupby, merge, and fillna operations.

Week 2: Domain knowledge

Read up on D2C beauty industry metrics: CAC, LTV, repeat purchase rate, and return rate. Look at publicly available myglamm news (funding rounds, brand acquisitions, app milestones) so you can speak to the business context. Practice explaining what 'good' looks like for a D2C brand in each of these metrics without relying on invented benchmarks.

Week 3: Mock interviews and case practice

Do at least three mock SQL rounds with a peer or on a practice platform. Practice the 'metric drop' investigation structure out loud. Record yourself answering one behavioral question using STAR and listen back to check whether your Action section is detailed enough.

Before the interview

Review myglamm's current open roles (knok shows 4 active Data Analyst listings as of July 2026). Note which teams are hiring and tailor your examples to that team's domain where possible. Prepare two or three questions to ask the panel about the data stack, team structure, and what a successful first three months looks like.

Jumping to conclusions without segmentation. A common error is answering 'why did revenue drop?' with a single hypothesis. Always show you would break the data down by platform, category, and time before landing on a cause.

Writing SQL without explaining logic. Myglamm interviewers typically want to follow your thinking. If you write a query silently and it has a bug, you have no recovery path. Talk through the logic first.

Generic behavioral answers. Saying 'I improved the reporting process' without a concrete example loses credibility quickly. Have two or three specific stories ready with real context from past roles.

Ignoring business impact. Analysts who focus only on technical execution without connecting it to a business outcome miss what interviewers are evaluating. Always close with what decision changed or what action the team took based on your analysis.

Not asking clarifying questions. In case-based rounds, jumping into the answer without clarifying the goal, the audience, and the available data is a red flag. Interviewers expect you to ask before you build.

Overstating your role. Be precise about what 'you' did versus what the team did. Interviewers at myglamm report they probe for individual contribution, especially in collaborative projects.