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

Gullak is a fintech startup that helps Indian users build savings through digital gold and recurring savings plans. The company currently has 2 open Product Manager roles, making this a focused and competitive hiring cycle. Candidates report the interview process typically runs across several rounds covering product thinking, metrics, and fintech user behavior specific to India.

The PM role at a savings-focused product like Gullak sits at the intersection of user psychology, financial habits, and growth. Interviewers typically want to see that you understand why Indian users save or do not save, how trust is built inside a fintech app, and how you would measure and improve a savings habit product.

1. How would you improve Gullak's onboarding to get more users to set up a recurring savings plan?
2. What is the single most important metric for a habit-based savings product like Gullak, and why?
3. Walk us through how you would prioritize a roadmap when growth, operations, and users all have conflicting requests at the same time.
4. Gullak competes with other digital gold platforms. How would you differentiate the product?
5. A key savings feature has low adoption after launch. Walk us through how you would diagnose and fix it.
6. How would you design a feature to help users who miss a recurring savings installment stay engaged rather than drop off?
7. Tell us about a time you used data to change the direction of a product decision.
8. How would you explain digital gold to a first-time investor in a tier-2 city?
9. What does healthy retention look like for a savings app, and how would you improve it?
10. How would you build a referral program for Gullak?
11. Describe a product you shipped end to end. What would you do differently today?
12. If Gullak wanted to expand into a new financial product category, how would you evaluate which one to pursue first?

Q: Tell us about a time you used data to change the direction of a product decision.

*Situation:* I was PM for a mobile wallet feature at a fintech startup. The team had built an in-app rewards module and assumed it would drive repeat transactions.

*Task:* Several months after launch, retention was flat. Leadership wanted to add more reward categories, but I suspected the root cause was different.

*Action:* I pulled funnel data and found that users who completed a one-time KYC upgrade had much higher reuse rates than those who did not, regardless of rewards. I ran a cohort comparison across city segments and the pattern was consistent. I presented the finding to the team with a clear recommendation: pause the rewards roadmap and reduce KYC friction first.

*Result:* We simplified the KYC flow from multiple steps to a single selfie-plus-PAN screen. New user activation improved in the following quarter. The rewards module was re-evaluated later with a smaller, more targeted scope.

---

Q: How would you improve Gullak's onboarding to increase users who set up a first recurring savings plan?

*Situation:* Many fintech apps lose users between sign-up and their first meaningful action because the product value is abstract until users actually experience it.

*Task:* The goal is to lift the number of new users who complete their first recurring savings setup, which is the core activation event for Gullak.

*Action:* I would map the onboarding funnel step by step, identify the biggest drop-off point, and run user interviews with people who signed up but never saved. My hypothesis is that users hesitate because they are unsure of the minimum amount or fear losing liquidity. I would test a 'start small' nudge that lets users begin with any amount, paired with a clear explanation that they can withdraw anytime. I would also A/B test a projected goal screen to make the value tangible. The primary metric would be first-save completion rate.

*Result:* Based on publicly reported experiments at comparable fintech apps, reducing perceived commitment at onboarding typically lifts first-save completion by a meaningful margin.

---

Q: A key savings feature has low adoption after launch. How would you diagnose and fix it?

*Situation:* Post-launch, adoption data showed that a new auto-save feature was used by far fewer users than the team projected.

*Task:* I needed to identify whether the problem was awareness, comprehension, trust, or a friction point in the setup flow.

*Action:* I broke the diagnosis into layers. First, I checked whether users were even seeing the feature (impressions vs. clicks). Then I checked whether users who tapped on it were dropping off mid-flow. Finally, I ran a quick round of user interviews and found that users were confused by the 'debit date' selector, thinking they would be charged immediately. This was a comprehension problem, not a trust or awareness issue.

*Result:* We rewrote the copy on that screen, changing 'debit date' to 'savings date' with a short plain-language explanation. Adoption improved in the next cohort. The fix shipped quickly.

For product improvement questions, use a four-part structure: current state, user problem, proposed change, and success metric. Always name the single most important metric before listing secondary ones. For a savings app like Gullak, the primary metric is typically activation (first savings setup) or plan continuation rate, not just downloads or sign-ups.

For prioritization questions, use a simple impact-vs-effort frame. State your assumptions about what 'impact' means for the business right now (growth, retention, or monetization), then rank accordingly. Do not present a prioritization matrix without first explaining the weights you assigned and why.

For metrics questions, follow this sequence: (1) define the goal of the feature, (2) name the north star metric, (3) name one guardrail metric to ensure you are not optimizing in the wrong direction. For a savings product, a useful guardrail is 'withdrawal rate after first save' to check that the product is building habit rather than anxiety.

For 'design a feature' questions, always start with the user and the job-to-be-done before proposing solutions. State the user segment, the friction they face, and then suggest the simplest effective intervention. Gullak's users include many first-time digital investors, so simplicity and trust signals matter more than feature richness.

Gullak interviewers typically look for a few specific qualities in PM candidates.

Fintech empathy. Can you articulate why saving is emotionally hard for users, not just technically complicated? Interviewers want to hear that you understand the anxiety around digital gold, recurring debits, and money moving automatically from a bank account.

Metric clarity. Can you quickly name the right metric for any feature and defend it? Vague answers like 'engagement' or 'retention' without specifics are a common red flag. Be ready to say exactly what you would measure and how you would instrument it.

Structured thinking under pressure. Candidates report that Gullak interviewers push back on your first answer to see whether you hold your ground or fold. Practice defending your reasoning, not just your conclusion.

Cross-functional awareness. A PM at a fintech startup works closely with compliance, operations, and engineering. Show that you have navigated these stakeholders before, or that you understand their constraints.

Speed to insight. At a startup of this size, interviewers typically value PMs who can move fast with imperfect data rather than wait for a large sample. Show that you can make a call and instrument it quickly.

Week 1: Understand the product.
Create a free Gullak account and go through the full onboarding. Note every screen, every copy choice, and every friction point. Write down the key things you would change and why. Read any publicly available interviews with the founding team to understand their thesis on building savings habits in India.

Week 2: Practice structured answers.
Pick the questions from the list above and answer each one out loud. Use STAR format for behavioral questions and the 'user, metric, solution' frame for product questions. Record yourself if possible. Keep your answers focused so you reach the key point quickly, without spending too long on setup.

Week 3: Fintech context.
Read the SEBI guidelines on digital gold, which are publicly available. Understand how digital gold differs from mutual funds and fixed deposits in terms of regulation and user trust. Be ready to explain this clearly to a non-technical interviewer.

Salary context. Based on knok jobradar data as of July 2026, PM roles in India range from 12-20 LPA at the Associate level to 40-60 LPA for Senior PMs. Glassdoor and industry surveys report Group-level PM roles going up to 90+ LPA at well-funded startups.

One week before the interview: Review your resume and prepare a clear narrative for every product you have shipped. Know the impact of each project in numbers you can defend.

knok checks 150+ job sites nightly, applies to jobs that match your resume, and messages HR for you, so you can focus your prep time on depth rather than searching.

Jumping to solutions before defining the problem. The most common mistake in fintech PM interviews is proposing features without first naming the user problem. Always spend a sentence or two establishing the 'why' before the 'what.'

Generic metrics. Saying 'I would track retention' without specifying which cohort, which action, or which time window signals shallow thinking. For a savings product, be specific: plan continuation rate, first-save completion rate, or reactivation rate after a lapse.

Ignoring trust as a product variable. Digital gold and recurring debits require a high degree of user trust. Candidates who design features without considering how trust is built or broken miss a core dimension of fintech PM work.

Overfitting to growth. Fintech products must balance acquisition with compliance and user safety. Candidates who propose aggressive growth tactics without acknowledging regulatory constraints often face pushback in interviews.

Not knowing the competitive landscape. Gullak operates alongside several other digital gold and micro-savings platforms. Know several competitors by name and be able to articulate Gullak's differentiation clearly.

Talking too long on setup. Candidates report that interviews at this stage of a startup move quickly. Get to your main point within the first minute of any answer. Save the detail for follow-up questions.