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

Timesinternet is the digital arm of the Times of India Group, running some of India's most visited properties: Times of India, Economic Times, Cricbuzz, Magicbricks, Indiatimes, and more. As of our latest data, Timesinternet has 20 open Product Manager roles, making it one of the more active hiring companies in the Indian media-tech space.

The interview process typically covers three broad areas: product sense (how you think about users and features), analytical ability (metrics, data, and business reasoning), and behavioural depth (how you have handled real situations). Candidates report the process runs across multiple rounds, often including an HR screen, one or two product case discussions, and a final leadership or cross-functional round. Some candidates also mention a take-home case study or product critique exercise before the main rounds.

Timesinternet operates at a unique intersection of media, advertising, real estate, and fintech. Interviewers tend to look for PMs who understand both consumer-facing products and B2B advertising models, and who can speak to scale given the company's reach across India.

These questions reflect patterns candidates report for Timesinternet PM interviews. Prepare concrete answers for each before your rounds.

1. Walk me through a Timesinternet product you use regularly and how you would improve it.
2. The Times of India app's daily active users are dropping. How do you diagnose the problem and what steps do you take?
3. How would you prioritize features for the Economic Times app when product, business, and editorial teams all want different things?
4. Design a subscription product for Economic Times targeting young working professionals.
5. What metrics would you track for a news personalization feature, and how would you know if it is working?
6. Cricbuzz has a competitor that just launched a live score experience with noticeably better UX. You are the PM. What is your response?
7. How would you approach building a product for Bharat users (tier-2 and tier-3 cities) differently from metro users on the same platform?
8. Timesinternet has news, real estate, cricket, and finance products. How would you think about cross-platform user data to improve retention across properties?
9. Tell me about a product you built or significantly improved end-to-end. Walk me through your process and key learnings.
10. Describe a time when your data pointed one way and user research pointed another. Which did you trust and why?
11. How do you think about an advertising revenue model versus a subscription model for a news property, and when would you push for one over the other?
12. You need to cut scope before a major launch. How do you decide what stays and what goes?

Q: The Times of India app's daily active users are dropping. How do you diagnose this?

*Situation:* In a previous role, I faced a similar engagement drop on a content app shortly after a major redesign.

*Task:* I needed to identify whether the drop was caused by the redesign, an external news-cycle shift, or a problem in our content pipeline.

*Action:* I segmented the drop across several dimensions: new users versus returning users, Android versus iOS, and notification-enabled versus not. The sharpest drop appeared among returning users on Android who had auto-updated to the new version. A funnel analysis showed session length dropped at the homepage stage, not at the article stage, pointing to a content discovery problem. I ran a quick usability session with a small group of users and confirmed the new navigation was confusing long-time readers. In parallel, I checked competitor activity and correlated the drop against news cycle intensity to rule out external causes.

*Result:* We shipped a targeted fix to the homepage navigation within two weeks, recovering most of the drop. The diagnosis framework became a reusable template for the team.

---

Q: Tell me about a product you built end-to-end. What did you learn?

*Situation:* At my previous company, we needed a way for users to save and resume long-form articles across devices. Users had been requesting this for months.

*Task:* I owned the feature from discovery through launch, including defining success metrics and scoping with engineering.

*Action:* I started by interviewing a small group of heavy readers to understand their habits. I found two distinct patterns: commuters reading in short bursts and researchers bookmarking for later. I defined success as a combination of save rate and retrieval rate, not just saves. Working with engineering, I scoped an MVP that served the commuter case first, kept the design minimal, and deferred cloud sync to a second phase to hit our timeline. I ran a beta with a small cohort, gathered structured feedback, and iterated before broader rollout.

*Result:* The feature had strong adoption among our heavy-reader segment in the first month. The retrieval rate exceeded our initial target, confirming genuine intent behind saves rather than passive bookmarking.

---

Q: Describe a conflict between engineering constraints and a business deadline.

*Situation:* We had a hard deadline tied to a partner launch. Engineering flagged that the full feature as scoped would need two extra weeks beyond the committed date.

*Task:* I had to find a path that met the partner commitment without burning the team or shipping something unreliable.

*Action:* I mapped every requirement to either 'partner sees this on day one' or 'back-end processing only'. A meaningful portion of the scope was backend work the partner would never observe in the initial phase. I confirmed with the business lead that the partner's demo scenario only required three core user flows. I cut scope to those flows, negotiated a follow-up sprint for the deferred work, and documented the trade-offs clearly for leadership so there were no surprises.

*Result:* We launched on time. The partner was satisfied with the demo experience. The deferred scope shipped in the follow-up sprint as planned, and the team avoided unplanned crunch.

For product improvement and design questions, use a user-first structure: start by clarifying the goal (growth, engagement, revenue), define the relevant user segments, identify the top pain points, propose solutions in priority order, then describe how you would measure success. Interviewers at media-tech companies like Timesinternet often expect you to connect features to monetization or retention, so always close with metrics.

For metric and diagnosis questions, walk through a layered funnel: acquisition, activation, engagement, retention, revenue. Name the specific metric you would look at first and explain why. If something is dropping, segment before concluding: by platform, user cohort, geography, or feature version. This shows analytical rigour without jumping to a solution prematurely.

For prioritization questions, use a simple value-versus-effort framing: state your criteria (user impact, revenue potential, strategic alignment, engineering cost), rank your options against those criteria, and name the trade-offs you are accepting. For Timesinternet specifically, the tension between advertiser value and user experience comes up often, so be ready to articulate how you balance both.

For behavioural questions, use the STAR structure: Situation, Task, Action, Result. Keep the Situation and Task brief (two to three sentences each), spend most of your time on the Action (your thinking and decisions), and quantify the Result where you honestly can. Avoid vague claims: if you do not have a specific number, describe the qualitative outcome clearly and concisely.

Deep familiarity with consumer internet at scale. Timesinternet products serve hundreds of millions of sessions. Interviewers want to see that you understand what changes at scale: personalization cost, content freshness, notification fatigue, and the difference between metro and tier-2 user behaviour.

Comfort with an ad-supported business model. Many Timesinternet properties earn primarily through advertising. Candidates who only think about user experience without connecting it to ad revenue or page-view economics tend to get pushed back. Know the basics: CPM, fill rate, and how session depth affects revenue.

Cross-functional maturity. Timesinternet's products touch editorial, ad-sales, and engineering simultaneously. Interviewers typically probe for examples of how you have worked across functions, managed conflicting priorities, and influenced without formal authority.

Data-first instincts. Candidates report that hypothesis-first, data-validated answers land well. Leading with 'I would first segment the data by X before forming a hypothesis' rather than jumping straight to a solution is consistently valued over candidates who lead with gut feel.

Ownership and speed. As a media company, Timesinternet moves with news cycles. Interviewers want to see that you can make decisions under uncertainty and move fast without waiting for perfect information.

Week 1: company and product immersion. Use all major Timesinternet apps (Times of India, Economic Times, Cricbuzz, Magicbricks) for several days each. Write brief product critiques for at least two of them: what works, what does not, and one improvement you would prioritize. Read their publicly available investor commentary to understand revenue mix and strategic priorities.

Week 2: case practice. Pick two to three of the most-asked questions above and write out full answers using the frameworks in this guide. Practise saying them out loud, ideally with a peer or mock interviewer. Focus especially on metric questions (what you would track and why) and prioritization questions (how you make trade-offs under competing stakeholder pressure).

Week 3: behavioural preparation. Map your past experience to the themes Timesinternet cares about: cross-functional conflict, data versus intuition, launching under constraints, building for diverse user segments. Prepare four to five STAR stories that can flex across multiple question types.

Before each round: review the specific Timesinternet product area the team works on (news, finance, real estate, sports). Prepare one or two specific observations about their product. Interviewers notice when a candidate has genuinely used the product versus prepared generic answers.

If you are actively applying while you prepare, knok checks 150+ job sites nightly, applies to jobs matching your resume, and messages HR for you so your applications keep moving while you focus on interview prep.

Jumping to solutions before understanding the problem. A pattern interviewers often see is candidates hearing a metric-drop question and immediately proposing features. Interviewers at Timesinternet typically want to see you diagnose first: segment the data, form hypotheses, rule out external causes, then propose solutions. Rushing to answers signals shallow thinking.

Ignoring the business model. Candidates who frame every answer around user delight without connecting to advertising revenue or subscription economics miss a core part of how Timesinternet products are evaluated internally. Always link your recommendations to a business outcome.

Being too vague in behavioural answers. Saying 'I collaborated with stakeholders and we found a solution' tells an interviewer nothing. Name the specific conflict, the decision you made, and what happened as a result. Concrete detail is what makes a STAR answer credible.

Not knowing the product portfolio. Candidates who have not used the products during their prep get caught out quickly. If you cannot name a specific friction point in the Economic Times app or a specific thing Cricbuzz does well, it signals low interest in the company.

Over-engineering the solution. Timesinternet moves fast. Candidates who propose extended roadmaps for a simple feature question, or who hedge every answer with excessive caveats, can come across as slow to act. Show that you can make a reasonable call with incomplete information.