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

Timesinternet is the digital arm of Bennett, Coleman and Co. Ltd., home to Times of India, Economic Times, indiatimes.com, MagicBricks, TimesJobs, and Cricbuzz. These platforms together have a massive reach across India, making the Product Designer role here both high-visibility and high-impact.

A Product Designer at Timesinternet typically owns end-to-end UX on one product or vertical: research, wireframes, prototypes, and shipped features, in close collaboration with product managers, engineers, and editorial or business stakeholders. Mobile-first thinking is a practical requirement because a large share of the audience comes through mid-range Android devices, many on slow connections.

As of July 2026, knok jobradar tracked 20 open roles at Timesinternet. Nationally, 393 Product Designer roles were active, with Bangalore leading at 62 openings, Delhi at 33, and Mumbai at 13. Salary bands from the data:

The interview process candidates report typically includes a portfolio review, a design exercise (take-home or live case study), and rounds on product thinking, cross-functional collaboration, and culture. The exact structure varies by team and seniority level.

These questions come up frequently based on what candidates have shared publicly about Timesinternet Product Designer interviews.

1. Walk us through the project in your portfolio you are most proud of. What was your process from first research to final delivery?
2. Timesinternet properties serve a very large and diverse user base across news, real estate, jobs, and sports. How do you design when the audience spans so many different contexts and needs?
3. Tell us about a time you had to simplify a complex user flow. What trade-offs did you make and why?
4. How do you approach designing for users in Tier 2 and Tier 3 cities, where data speeds and device capabilities vary a lot?
5. Timesinternet products carry significant ad inventory. How do you balance user experience with monetisation requirements?
6. Describe a situation where you disagreed with a product manager or developer on a design decision. How did it get resolved?
7. How do you use data and user research together to validate a design? Give a concrete example.
8. Walk us through how you would redesign the Times of India mobile app homepage for a user who opens it every morning.
9. How do you handle feedback from multiple stakeholders who each have different opinions on the same design?
10. Tell us about a project where your first design direction did not work out. What did you learn and what did you change?
11. How would you approach adding a new feature to MagicBricks that helps first-time home buyers narrow down their property search?
12. Where do you draw the line between following a design system and breaking from it to solve a specific problem?

Use these as a starting point. Replace the projects and context with your own experience.

Q: Tell us about a time you had to simplify a complex user flow.

*Situation:* At my previous company, the registration flow for a lending product had grown across many screens over two years as compliance requirements were added one at a time.

*Task:* I was asked to reduce drop-off without removing any field that was legally mandatory.

*Action:* I audited every field with the legal and product teams, separating mandatory items from 'nice-to-have' ones. I moved non-mandatory fields to a post-registration profile step, restructured the mandatory fields into logical groups, and added a progress indicator. I then ran usability sessions with a small group of target users to find where people hesitated, and iterated on copy and visual hierarchy based on what I observed.

*Result:* The team reported a measurable improvement in registration completion in the weeks after launch. The modular structure also made it easier to add future compliance fields without disrupting the whole flow.

---

Q: How do you design for Tier 2 and Tier 3 users where data and device specs vary widely?

*Situation:* On a news aggregator project, analytics showed that a growing share of daily active users were on entry-level Android phones with slow connections.

*Task:* I needed to redesign the article landing page so it loaded fast and stayed readable on small screens, without removing the ad slots that funded the product.

*Action:* I worked with engineers to prioritise text content loading before images, introduced lazy loading for visuals, and increased font size and line spacing for readability. I also simplified the navigation so key actions were reachable without stretching on a small screen.

*Result:* Internally reported load times improved on slow connections and scroll depth on article pages increased for the Tier 2-3 segment. The ad team confirmed no revenue impact because ads loaded after content was already visible.

---

Q: Describe a time you disagreed with a PM on a design decision.

*Situation:* A product manager wanted to add a large interstitial pop-up promoting a premium subscription on the app home screen. I felt it would frustrate users who just wanted to read the news.

*Task:* I needed to present a counter-proposal that still met the PM's conversion goal.

*Action:* I pulled session data showing that users who encountered intrusive modals on the first screen had shorter sessions on average, and I shared research on banner blindness. I then proposed an in-feed card with the same offer placed after the third article, where users had already shown intent. I mocked up both options side by side so the PM could see the contrast clearly.

*Result:* The team agreed to test both variants. The card matched the interstitial on conversions in the internal test while session length held steady, so it became the default.

'Problem first, then pixels'
Before describing any design decision, name the user problem and the constraint you were working within. At a product-focused company like Timesinternet, interviewers want to see that your visual choices have a clear reason behind them, not just that they look good.

For research questions: 'What I knew, what I did not know, how I found out'
State what you already had (analytics, past research, stakeholder input), identify the gap, and explain the specific method you used to fill it. This shows structured thinking rather than a vague 'I just talked to users.'

For collaboration and conflict questions: 'Align on the goal, then debate the approach'
Show that you separated the shared objective (conversion, retention, load time) from the specific solution. This reframes disagreement as joint problem-solving, which is exactly the signal interviewers look for.

For redesign and case study prompts
A reliable structure to follow:
- Clarify the goal and success metric before sketching anything
- Name the user segment and their key task
- Walk through two or three options you considered and why you picked one
- Call out the trade-off you accepted

For portfolio walkthroughs
Candidates report that Timesinternet interviewers often ask 'what would you do differently now?' Prepare a crisp answer for each case study: one thing you would change about the process and one thing you would change about the output.

Understanding of the Indian internet user
Timesinternet's products serve users across a wide range of geographies, devices, and connectivity levels. Candidates who can speak concretely about low-bandwidth design, regional language considerations, or the habits of a first-generation smartphone user stand out from those who only reference polished Western design patterns.

Product thinking alongside craft
Beautiful screens are not enough. Interviewers want to see that you understand why a feature exists, what metric it is meant to move, and what the cost is if it fails. Bring business context into every portfolio walkthrough.

Comfort with real constraints
Ad-supported products come with non-negotiable limits: ad slots must load, click targets must be accessible, and performance always matters. Show that you have designed within messy real-world conditions, not just in ideal design system environments.

Cross-functional collaboration
Designers at Timesinternet work with editorial teams, ad operations, and product managers whose incentives sometimes pull in different directions. Candidates who can describe specific moments of alignment and negotiation, without framing them as battles won, do well.

Clarity in communication
Several candidates report that the ability to explain design decisions simply, without jargon, is tested across all rounds. Practice describing your work as if the person across the table has never opened Figma.

Week 1: Use the products seriously
Spend real time on Times of India, Economic Times, MagicBricks, and TimesJobs. Note what works well for Indian users and what you would change, with specific reasoning. These observations become ready-made answers to redesign and product-sense questions.

Week 1-2: Sharpen your portfolio
Select three to four projects that show range: at least one with a strong research component, one where you worked within technical or business constraints, and one where you can speak to a measurable result. For each, prepare a short spoken summary and a clear answer to 'what would you do differently.'

Week 2: Practice design exercises
Case study prompts candidates report from Timesinternet tend to focus on improving an existing feature rather than inventing something new. Practice redesigning a familiar app feature in a fixed time block: start with the user problem, sketch two options, pick one, and explain the trade-off. Time yourself.

Week 2-3: Ground your answers in real business goals
Read publicly reported goals for Timesinternet verticals: subscription growth for Times Prime, lead quality for MagicBricks, daily engagement for TOI. Frame your answers around these real objectives rather than generic UX principles.

Ongoing: Build your spoken answer bank
Write out full STAR answers for: a project that failed, a disagreement with a stakeholder, a research-driven decision, and a constraint you designed around. Say them out loud. Spoken practice matters far more than written prep.

Talking aesthetics without business context
Saying 'I made it cleaner and more modern' is a weak answer at a company whose products are tied directly to ad revenue and subscriptions. Every design choice needs a 'because it helps users do X, which supports Y' attached to it.

Ignoring the ad-supported model
Candidates who propose designs that bury or remove ad placements show they have not thought about how Timesinternet funds its products. Acknowledge the constraint and show how you would work within it creatively.

Generic portfolio walkthroughs
Saying 'I did research, made wireframes, and shipped the feature' describes a process, not thinking. Interviewers want to hear what was hard, what you got wrong, and what you would change if you did it again.

Designing only for a metro, premium user
Timesinternet's reach extends well beyond English-first, flagship-phone users. Candidates who never mention Tier 2-3 users, slow connections, or small screens miss a major part of the actual audience these products serve.

Not preparing questions to ask
Candidates who have nothing to ask the interviewer signal low interest in the specific role. Prepare two or three questions about the team's design process, the product you would work on, or how design decisions get made when business and user goals conflict.