acko Product Manager Interview: Questions, Experience & Prep (2026)

Acko is one of India's leading insurtech companies, offering car, bike, health, and travel insurance entirely online through its app and website. PMs at Acko work on problems distinct from typical e-commerce or SaaS roles: insurance is a low-frequency, high-trust category where the product experience must work perfectly at the worst moment in a customer's life, a claim.

Candidates report a multi-stage process that typically includes a recruiter or HR screening, one or more product case interviews, an analytical or take-home assignment, and a final leadership panel. The exact number of rounds varies by team and level, so confirm the format with your recruiter early. As of July 2026 job market data, Acko has 1 open Product Manager role.

Salary bands for PM roles across the industry (knok jobradar, July 2026):

For Acko-specific figures, check Glassdoor or levels.fyi. Actual compensation depends on team, level, and negotiation.

Candidates report that Acko PM interviews lean heavily on product design, metrics, and behavioural questions set firmly in the insurance context. Here are 12 questions that come up frequently:

1. Walk me through how you would redesign Acko's car insurance purchase flow to improve conversion.
2. What metrics would you define to measure the success of Acko's health insurance product?
3. How would you reduce drop-offs during the claims filing process on the Acko app?
4. Prioritise three potential features for Acko's renewal experience: push notifications, a one-click renewal button, and a loyalty discount display. Explain your reasoning.
5. Tell me about a time you used data to reverse a decision you had already made.
6. How would you build trust with a first-time buyer who has never purchased insurance online before?
7. Engineering tells you a critical feature will take three months but your business target is four weeks away. What do you do?
8. Design a self-service minor claims settlement feature for Acko. State your key assumptions upfront.
9. How would you use WhatsApp or similar channels to improve post-purchase engagement for Acko policyholders?
10. Acko competes with large traditional insurers. Where do you see the biggest product gap Acko can close in the next 12 months?
11. Walk me through an A/B test you would run to improve the Acko onboarding flow. What is your hypothesis and how would you measure success?
12. How would you think about personalisation in a low-frequency category like insurance, where a customer may interact with the app only once or twice a year?

Q: How would you reduce drop-offs during the claims filing process on the Acko app?

*Situation:* At my previous company, our claims initiation funnel had significant abandonment after users attempted to upload the first document.

*Task:* I needed to identify the root cause of drop-offs and improve completion rates without waiting for a large engineering overhaul.

*Action:* I pulled funnel data and found most users were leaving at the third document upload step. I ran user interviews and discovered that people often did not have all their documents ready in one sitting, and the app gave no way to save progress. I scoped two solutions: a proactive checklist shown before the user even begins, and a 'save and resume' feature. I worked with engineering to ship the checklist as a low-effort win in the first sprint, then the save-resume feature in the following sprint.

*Result:* The team saw a meaningful improvement in funnel completion. I documented the learnings in a product brief that directly informed the next major claims redesign.

---

Q: Tell me about a time you used data to reverse a decision you had already made.

*Situation:* My team had launched a simplified onboarding flow we were confident would improve activation. We shipped it based on qualitative research and a small internal pilot.

*Task:* After two weeks in production, I owned the review of activation metrics and had to present findings to leadership.

*Action:* The data showed activation had dropped. I segmented by device type and found the simplified flow performed well on Android but significantly worse on iOS, where the new UI pattern clashed with system-level navigation. I called a team meeting, shared the segmented data clearly, and recommended reverting iOS while keeping the Android improvement live.

*Result:* We reverted the iOS version within two days. I added device-segmented analysis as a standard step in our post-launch review checklist, preventing the same blind spot in future releases.

---

Q: How would you build trust with a first-time buyer who has never purchased insurance online before?

*Situation:* At a fintech I previously worked at, a large portion of new users were first-time digital financial product buyers hesitating before completing a purchase.

*Task:* I was asked to improve activation among users who started the purchase journey but dropped before payment.

*Action:* I mapped the emotional journey of a hesitant buyer and identified three peak anxiety moments: understanding what is covered, trusting that a claim will actually be paid, and worrying about hidden charges. I proposed three product interventions: a plain-language 'what this covers in one line' card on the plan selection screen, a real customer claims story module, and a no-hidden-charges badge at checkout. I ran a quick usability test with a small group to validate the copy before shipping.

*Result:* Industry surveys suggest that trust-building interventions at checkout are among the highest-ROI improvements in insurance apps, though sample sizes in public studies are small. Internally, the changes contributed to a positive shift in our purchase completion rate.

CIRCLES for product design questions
CIRCLES (Comprehend, Identify users, Report needs, Cut through prioritisation, List solutions, Evaluate trade-offs, Summarise) is a strong default for questions like 'design a self-service claims feature.' Start by stating the goal and constraints, name the primary user segment, list their top pain points, propose two or three solutions with trade-offs, and land on a clear recommendation.

RICE for prioritisation questions
When asked to prioritise features, use RICE: Reach (how many users affected), Impact (how much it moves the needle per user), Confidence (how sure you are of your estimates), and Effort (engineering time). For an Acko renewal prioritisation question, push notifications might score high on reach but low on impact per user, while one-click renewal scores high on impact but medium on effort.

Metric trees for success metrics questions
Break a top-level goal like 'grow health insurance' into an input-output tree: acquisition (traffic, conversion rate), engagement (app opens, policy views), retention (renewal rate, lapse rate), and revenue (premium per policy). This signals structured thinking and avoids jumping straight to a single vanity metric.

STAR for behavioural questions
For every 'tell me about a time' question, use Situation, Task, Action, Result. Keep Situation and Task brief combined. Spend most of your answer on Action (the choices you made and why) and quantify the Result wherever possible. If you cannot share exact numbers, describe the direction and relative magnitude clearly.

Acko is building insurance as a technology product, not a distribution business. Interviewers are typically looking for a few specific qualities.

Deep user empathy in a low-frequency, high-stakes context. Insurance customers interact with the product rarely but intensely, at purchase and at claim. Interviewers want to see that you understand the emotional weight of the claims moment and design for trust, not just funnel conversion.

Data fluency. Candidates report that analytical questions at Acko go beyond defining metrics. Interviewers test whether you can interpret ambiguous data, identify confounding factors, and know when the data is insufficient to make a confident call.

Speed and pragmatism. Acko operates in a competitive insurtech market. Interviewers value candidates who can ship a good-enough solution quickly over someone who takes months to perfect a complete one. Show that you can scope, phase, and iterate.

Insurance and regulatory awareness. You do not need to be an insurance expert, but knowing that IRDAI regulates product pricing, that motor insurance is mandatory in India, and that health insurance has specific rules around pre-existing conditions signals genuine interest in the domain.

Structured communication under ambiguity. Case questions at Acko are often deliberately vague. Interviewers want to see you ask clarifying questions, state your assumptions out loud, and structure your answer before diving in.

Week 1: Understand Acko's products deeply
Download the Acko app and go through the full purchase flow for car and health insurance. Note every screen, every question asked, and every point of friction. Read Acko's blog and any publicly available commentary to understand their stated priorities. Identify two or three specific product decisions you find interesting or worth questioning.

Week 2: Build your case study toolkit
Practise the CIRCLES framework on two Acko-specific design questions such as improving the claims flow or the renewal experience. Practise RICE scoring on a prioritisation question. Time yourself: product case answers in an interview typically run fifteen to twenty minutes, with a few minutes for clarifying questions, several minutes for analysis, and several minutes for your recommendation.

Week 3: Behavioural prep and mock interviews
Write out five STAR stories covering: a data-driven decision, a time you handled stakeholder conflict, a feature you killed or descoped, a cross-functional win, and a failure with a clear learning. Do at least two mock interviews with a peer and record yourself so you can review pacing and filler words.

Week 4: Domain depth and final polish
Review one or two IRDAI regulation summaries to understand how insurance products are governed in India. Check Glassdoor for recent Acko PM interview experiences. Prepare three sharp questions for your interviewers that show you have thought specifically about Acko's product challenges.

knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR on your behalf. If you are actively job hunting, it keeps your pipeline moving while you focus on interview prep.

Ignoring the insurance context in case answers. Generic answers that could apply to any consumer app miss the mark at Acko. Always acknowledge the low-frequency, high-trust nature of insurance and the regulatory environment when framing your answer.

Jumping to solutions without defining the user. Candidates report that interviewers will stop you if you skip straight to features. Always start a design question by naming the user segment and their primary pain point before proposing anything.

Treating all metrics as equal. Saying 'I would track DAU, MAU, and revenue' for an insurance app signals a lack of domain thinking. Engagement looks very different in insurance: renewal rates, claims completion rates, and app opens around renewal time matter far more than daily active users.

Being vague about trade-offs. Candidates who say 'I would build all three features' without prioritising or acknowledging cost and time constraints come across as inexperienced. Always pick one recommendation and defend it with reasoning.

Under-preparing for analytical questions. Candidates report that Acko case studies often include a data set or a funnel scenario. If your SQL is rusty or you are not comfortable reading a conversion funnel table, spend time on these skills before your interview.

Memorising answers instead of practising structured thinking. Interviewers notice when an answer sounds rehearsed and will probe with follow-up questions. Know your frameworks well enough to apply them to an unfamiliar problem, not just the questions you have already practised.