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

Verse Innovation is the company behind Josh, one of India's largest short-video platforms built for a Bharat-first audience. As of mid-2026, there is 1 open Product Manager role at Verse Innovation, against a national market of 2,009 PM openings tracked across India.

Candidates report that the interview process typically runs three to five rounds, covering product sense cases, metrics reasoning, and behavioral questions with senior leaders. Some candidates also report a take-home product critique or a live product teardown session. The consistent theme across all rounds is Bharat-first user empathy: can you design for someone who may be a first-generation smartphone user, browsing in a regional language on a mid-range Android device with patchy connectivity?

These questions are drawn from candidate reports and reflect the themes most likely to come up in a Verse Innovation PM interview:

1. How would you improve content discovery on Josh for a new user in a Tier-2 city?
2. DAU on Josh dropped this week. Walk me through how you would diagnose it.
3. Design a feature to increase creator retention on Josh.
4. How would you prioritize between improving the follow mechanic and improving the recommendation algorithm?
5. Walk me through a product you shipped that did not perform as expected. What did you learn?
6. What metrics would you track to measure the health of a short-video feed?
7. Josh wants to expand its monetization model. What would you recommend and why?
8. How would you design and evaluate an A/B test for a new notification strategy?
9. Tell me about a time you had to align cross-functional teams with conflicting priorities.
10. How do you think about the competitive landscape for short-video in India in 2025 and 2026?
11. What does a healthy creator ecosystem look like on Josh, and how do you measure it?
12. How would you design the onboarding experience for a first-time creator?

Q: Walk me through a product you shipped that did not perform as expected.

*Situation:* At my previous company, we launched a social sharing feature for a content feed. I owned the roadmap for this feature end to end.

*Task:* The goal was to increase sharing actions per user per week and drive new user acquisition through viral loops.

*Action:* We shipped after a two-week build, but I had not validated the core assumption that our users actually wanted to share content to external platforms. I relied on qualitative signals from a small internal group rather than running a structured experiment with real users. Once the feature was live, I tracked adoption daily and noticed that engagement was low and concentrated in a narrow segment.

*Result:* I led a team retrospective where we mapped out our original assumptions and identified which ones we had skipped testing. I introduced an assumption log as a standard artefact in our PRDs going forward. The next feature we shipped used this framework and showed stronger early adoption signals.

---

Q: DAU dropped this week on Josh. How do you diagnose it?

*Situation:* During a planning cycle at a previous role, we saw a sudden drop in daily active users on our consumer app.

*Task:* As the PM responsible for the core feed, I had to identify the root cause quickly and communicate findings to leadership within a day.

*Action:* I broke the problem into three buckets: supply (is content being created?), demand (are users showing intent to open the app?), and platform (is there a technical issue?). I segmented the drop by user type (new versus returning), device type, geography, and acquisition channel. I checked push notification delivery rates, feed load performance, and creator posting volume. I also reviewed recent app releases for any regressions.

*Result:* We identified a notification delivery failure affecting a specific Android build. Engineering shipped a patch within two days, and session counts recovered by the end of that week. I documented the diagnostic framework so the team could reuse it for future metric drops.

---

Q: How would you prioritize between two competing roadmap items?

*Situation:* At a previous company, I had to choose between improving in-app search and improving the recommendation feed for the upcoming quarter.

*Task:* I needed to make a clear, defensible recommendation to the product leadership team.

*Action:* I mapped each item to a specific business outcome, scored them on estimated reach, potential impact on retention, and engineering effort. I ran a brief user research session to understand which friction point users felt most acutely. I also checked engineering readiness, since one item had cleaner data pipelines already in place.

*Result:* We prioritized the recommendation feed. It shipped as the core of our next release and the team hit their quarterly retention target. The search improvement was slotted for the following quarter with a clearer scope based on what we had learned.

For metrics and diagnostic questions: Start by confirming what the metric measures and what a healthy baseline looks like. Break the metric into its components (for example, DAU = new users plus returning users, minus churned users). Segment by user type, geography, device, and time period. Form a hypothesis, identify what data you would check first, and explain what action each finding would drive.

For product design questions: Open with the user. Who are they, what is their context, and what are they trying to accomplish? For Josh, this typically means a Tier-2 or Tier-3 user on a mid-range Android device with intermittent connectivity and a regional language preference. Prioritize the pain points, sketch two or three solution directions, pick one with a clear rationale, and define your success metrics before describing the feature in detail.

For prioritization questions: Use a simple framework: impact on the core metric, effort to ship, and strategic alignment with current company goals. Be explicit about what you are trading off and why. Interviewers want to see that you can make a decision and defend it, not just list pros and cons without a conclusion.

For behavioral questions: Use the STAR format (Situation, Task, Action, Result). Keep Situation and Task brief. Spend most of your time on Action, describing specifically what you personally did rather than what the team did. Quantify the Result with numbers you actually know from your own work.

Verse Innovation builds for users who are often first-generation smartphone owners accessing the internet primarily through short-form video. Interviewers are looking for PMs who genuinely understand this audience, not just candidates who know the frameworks.

User empathy for Bharat: Can you design for someone whose primary language is not English, who is on a slow connection, and who is discovering a feature type for the first time? Candidates who give generic metro-focused answers typically struggle here.

Metrics fluency for content platforms: For a short-video app, you are expected to know Day-1 and Day-7 retention, content completion rate, creator posting frequency, feed engagement rate, and monthly active user trends. Know how these metrics interact and what moving one means for the others.

Comfort with ambiguity: Verse Innovation operates in a fast-changing competitive space. Interviewers want to see that you can structure a problem, make a call with incomplete information, and iterate from the outcome.

Cross-functional leadership: PM roles here require close collaboration with engineering, design, data, and content teams. Expect questions about how you handle disagreement, unblock a stalled team, or get buy-in without direct authority.

Week 1: Know the product. Download Josh and use it every day. Pay close attention to how the feed recommends content to a new user, how the creator onboarding flow works, and where the experience feels slow or confusing. Write down three things you would change and your reasoning for each.

Week 2: Build your metrics vocabulary. For a short-video platform, be ready to define and discuss Day-1 and Day-7 retention, content completion rate, session length, creator posting frequency, and monthly active user trends. Practise explaining how you would track the health of the creator supply side versus the viewer demand side, and how a change in one affects the other.

Week 3: Practise cases out loud. Work through each question in this guide with a timer. Record yourself if you can. The most common failure mode is spending too long on the Situation and not enough time on Action and Result.

Ongoing: Follow the short-video space. Read publicly available commentary on what content platforms are doing in India in 2025 and 2026. Understand how Josh positions itself versus competitors on audience, content type, and language support.

If you are applying to multiple companies at the same time, knok checks 150+ job sites nightly, applies to roles matching your resume, and messages HR for you, so you can keep your energy on interview prep rather than tracking new listings.

Jumping to the solution. Many candidates hear a design question and immediately pitch a feature. Interviewers want to see you define the user, the problem, and the success metric before proposing anything.

Giving generic answers. Saying 'I would improve engagement' without tying it to Josh's specific audience, content type, or competitive context signals that you have not done your homework on the product.

Ignoring the Bharat user. Josh is not Instagram. Its core users often have different device constraints, language preferences, and digital literacy levels. Answers that assume a metro, English-first user miss the point entirely.

Treating metrics as an afterthought. Candidates often describe a feature and then add metrics at the end as a checklist item. Interviewers at a data-driven company like Verse Innovation want to see metrics built into your reasoning from the start, not appended.

Being vague about your own contribution. In behavioral answers, use 'I' not 'we' when describing what you did. Interviewers are evaluating you specifically, not your team.