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

Tamasha is a live entertainment and short-video streaming platform known for live cricket, sports, and creator-driven content. It currently has 1 Product Manager opening, making it one of the more selective targets in a market where knok jobradar tracks 2,009 active PM roles across India as of July 2026.

Candidates report the interview process typically runs across 3-4 rounds: a recruiter screen, a product sense or case discussion, an analytical or metrics round, and a final conversation with a senior leader or founder. The exact sequence varies by team and seniority, so treat this as a general guide rather than a guaranteed roadmap.

The PM role at Tamasha sits at the intersection of live content delivery, real-time user engagement, and monetisation on a competitive streaming platform. Interviewers are said to value product thinking grounded in user empathy, comfort with live-product trade-offs (latency, buffering, real-time moderation), and genuine interest in entertainment and sports.

Salary context (knok jobradar, all India PM roles, July 2026):

Tamasha-specific compensation is not publicly reported at scale. Use the above bands as a market reference when preparing for salary discussions.

These questions reflect what candidates typically encounter at consumer streaming and entertainment companies, shaped by Tamasha's product focus on live cricket, real-time engagement, and creator content.

1. How would you improve the live cricket viewing experience on Tamasha for a user who drops off after the first five overs?
2. Walk us through how you would design a feature to grow daily active users during non-cricket seasons.
3. Tamasha competes in a crowded streaming market. How would you differentiate the product for a tier-2 city user on a slower connection?
4. How do you choose between improving stream quality versus adding social features like live commentary, polls, or reactions?
5. Describe the one metric you would use to measure whether a live match push notification feature is working.
6. How would you think about monetisation for users who consistently watch live cricket but skip or block ads?
7. An A/B test shows that a chat overlay during live matches increases average watch time but also increases user complaints. What is your decision and why?
8. Design an onboarding flow for a first-time user who lands on Tamasha mid-way through a major IPL match.
9. Name a consumer product you genuinely admire. What is one specific thing Tamasha could borrow from it, and why?
10. How would you reduce churn among premium subscribers who joined specifically for the IPL season and are now inactive?
11. You have limited engineering bandwidth this quarter. How do you decide between a personalisation algorithm upgrade and a new highlights reel feature?
12. Walk me through how you combine qualitative user research with quantitative data when making a product decision.

Use these as templates. Replace company names and specifics with your own experience. The STAR format keeps answers focused and easy for interviewers to follow.

Q: How would you improve the live cricket viewing experience for a user who drops off after the first five overs?

*Situation:* At a consumer app I worked on, we saw high early-session abandonment on a live event feature. Users who joined mid-session often had no context about the current state of play.

*Task:* I needed to understand why they were leaving and design a targeted intervention without adding friction for users who were already engaged.

*Action:* I pulled session-level drop-off data and found the steepest exits happened in the opening minutes for users who had joined mid-match. I ran user interviews and heard a consistent theme: users felt 'lost' without a quick situational summary. I proposed a 'catch-up card': a contextual overlay in the first 90 seconds showing current score, recent wickets, and a one-line momentum note. I worked with design to prototype it and ran an A/B test with a two-week observation window.

*Result:* The variant outperformed control on session length and was rolled out. At Tamasha, I would start the same way: confirm where drop-off actually happens in the data before proposing any solution.

---

Q: An A/B test shows the chat overlay increases watch time but also increases user complaints. What do you do?

*Situation:* I faced a similar tension at a previous role with a user-generated content feature that boosted engagement metrics but also triggered moderation escalations.

*Task:* I needed to decide whether to ship, iterate, or kill the feature without discarding a genuine engagement gain.

*Action:* I segmented the complaint data by device type and screen size. A clear pattern emerged: most complaints came from users on smaller screens where the overlay obscured key on-field moments. I proposed a targeted rollout: enable the overlay for users above a screen-size threshold, and add a prominent one-tap 'hide chat' button for everyone else. I also looped in the trust and safety team to add basic content filters before a wider launch.

*Result:* Complaint rates dropped sharply in the next test cycle while watch time gains were preserved in the eligible segment. The lesson I carry is to not treat an engagement gain and a quality signal as a binary trade-off until you understand exactly who is having each experience.

---

Q: How would you reduce churn among premium subscribers who joined only for IPL and are now inactive?

*Situation:* Seasonal churn after a marquee event is a known challenge in subscription streaming. I worked on a post-event retention programme at a subscription product in a previous role.

*Task:* Reduce the post-IPL cancellation spike by creating meaningful reasons to stay beyond the cricket season.

*Action:* I mapped the post-season user journey and found two things: users did not know what else to watch, and the in-app discovery surface was generic rather than personalised to their viewing history. I proposed three interventions in priority order: a personalised 'what to watch next' push and email sequence triggered in the final week of IPL, a discounted annual plan offer surfaced at the point of highest intent (the last match), and a curated non-cricket content shelf on the home screen for subscribers who had only watched live sports. I estimated effort versus expected retention impact for each before committing to the build.

*Result:* The combined interventions reduced the post-season churn rate in our target cohort. At Tamasha, I would start by pulling data on exactly when subscribers cancel, what they watched (or did not watch) in their last active week, and which content paths historically retain users past the first season.

Having a mental toolkit for different question types helps you structure answers quickly under pressure.

For product design and feature questions: start by clarifying the goal and the target user, list user needs ranked by importance, generate solution options, evaluate trade-offs, and recommend one with a success metric. For Tamasha, always anchor your user definition in the live-content context. A cricket fan watching mid-match has very different needs from someone browsing on a quiet afternoon.

For prioritisation questions: use a lightweight impact-versus-effort approach. Describe the criteria you would use to score impact (reach, frequency, user pain severity) and effort (engineering complexity, dependencies), then show how you would rank two or three options against those criteria. Avoid picking an option without explaining the trade-off you are making.

For metrics questions: structure your answer in three parts. First, the primary metric that best captures user value. Second, one or two guardrail metrics to watch for regressions. Third, the leading indicator that tells you the primary metric is moving before the full data matures. For a live-content platform, engagement depth (minutes watched per session, return rate for the next match) typically matters more than raw install or sign-up counts.

For analytical or case questions: state your assumptions upfront, show your reasoning step by step, and flag where you would gather more data before committing to a number. Interviewers care more about the quality of your thinking than the precision of your output.

For behavioural questions: the STAR format (Situation, Task, Action, Result) keeps your answer focused. Keep each element brief: two to three sentences is usually enough. End with a clear result and, where possible, a reflection on what you would do differently.

Based on what candidates report from consumer streaming and entertainment PM interviews, a few themes come up consistently.

Deep user empathy for the live experience. Tamasha's core product moment is a user watching a live match in real time, often on a mobile phone with variable connectivity. Interviewers want to see that you can hold that specific user context throughout a design or prioritisation discussion, not just describe the user in abstract terms.

Comfort with trade-offs in live products. Live streaming involves genuine product tensions: latency versus quality, real-time moderation versus user freedom, personalisation versus content discovery. Candidates who acknowledge these tensions and reason through them thoughtfully do better than those who propose clean solutions without surfacing the hard parts.

Metric fluency without metric obsession. You should define success clearly and choose the right metric for the right problem. At the same time, interviewers want to see that you understand when a metric can mislead you. For example, watch time can increase because users are stuck on a broken playback experience, not because they are enjoying the content.

Structured communication. Product sense rounds at consumer companies reward candidates who frame their thinking before diving in. Lead with your interpretation of the problem, state any assumptions, and signpost your reasoning as you go.

Genuine interest in the product. Spending time on the Tamasha app before your interview is visible in the quality of your examples. Interviewers notice when a candidate references a real feature or a specific user moment versus speaking in generalities about 'streaming platforms.'

A focused preparation approach typically covers four areas: knowing the product, sharpening your frameworks, practising your stories, and understanding the market.

Know the product first. Download and use Tamasha for at least a week before your first round. Watch a live match, explore the content library, and note what works and what feels broken. Come with two or three specific product observations, grounded in what you think the user was trying to accomplish.

Sharpen your frameworks. Practise the user-first design approach, the impact-versus-effort prioritisation method, and the three-part metrics structure described in the frameworks section. Do one timed practice case per day, ideally with a peer who can give you feedback on how clearly you communicate your reasoning.

Prepare your STAR stories. Map your past experience to the question types in this guide. Have at least one strong story ready for each of these themes: a feature you launched and measured, a prioritisation call you made under constraint, a time you used data to change a product direction, and a situation where you navigated stakeholder disagreement.

Build market context. Read recent publicly reported news about the Indian streaming market, content licensing trends, and how platforms are approaching monetisation for price-sensitive users. You do not need to memorise statistics, but you should be able to hold a grounded conversation about where Tamasha sits in the competitive landscape.

Knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR directly on your behalf, so your applications keep moving while you focus on interview preparation.

These are the patterns that most often cost candidates in consumer PM interviews, based on what candidates report.

Jumping to solutions before diagnosing the problem. When asked how you would improve a feature, the first instinct is often to pitch an idea. Interviewers at product-driven companies want to see you ask 'what problem are we solving and for whom' before proposing anything.

Defining metrics too narrowly. Saying 'I would track daily active users' is not enough. You need to specify what counts as active, over what time window, and what guardrail metrics you would watch to make sure you are not gaming the number.

Being vague about your personal contribution. In behavioural questions, candidates often say 'we did this' and 'the team built that.' Interviewers want to understand specifically what you decided, what trade-off you navigated, and what you learned. Use 'I' deliberately.

Ignoring the live-content context. Generic answers about 'engagement' or 'retention' that could apply to any app miss the specificity a live-event product requires. Anchor your answers in the real-time, high-emotion, often-mobile context that Tamasha's users are actually in.

Over-engineering the prioritisation framework. Presenting a complex scoring model with many variables can look like a substitute for judgement. Show that you can use a framework to organise your thinking, then make a clear call and defend it.

Skipping clarifying questions. Jumping straight into an answer without confirming the goal, the target user, or any key constraints is a common early-round mistake. Taking 60 seconds to align on the problem almost always improves the quality of your answer.