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

ixigo is one of India's most recognized travel tech platforms, used by millions to book trains, flights, and buses. It listed on Indian stock exchanges and has continued expanding its product teams through 2025-2026. The knok jobradar currently tracks 14 open PM roles at ixigo, indicating active and ongoing hiring.

The interview process typically runs across three to five rounds. Candidates report a conversational yet rigorous style: interviewers probe the reasoning behind your decisions, not just the outcomes. ixigo's core audience includes price-sensitive, mobile-first travelers from Tier-2 and Tier-3 cities, so empathy for the 'Bharat' user appears consistently across rounds.

On compensation, industry surveys and publicly reported data suggest PM salaries in India vary widely by seniority. Associate PM roles are commonly cited in the 12-20 LPA range, mid-level PMs with three to six years of experience in the 24-40 LPA band, Senior PMs in the 40-60 LPA range, and Group or Principal PMs in the 55-90+ LPA range. ixigo-specific offers may vary.

These questions reflect ixigo's product domain and are drawn from candidate reports. Treat them as representative, not exhaustive.

1. ixigo serves both urban power users and first-time internet users from smaller towns. How would you prioritize features for these two very different segments?
2. Train booking is a core vertical for ixigo. Walk through how you would improve the Tatkal booking experience for a user on a slow connection.
3. You notice hotel upsell conversion has dropped over the past month. What might be causing it, and how would you investigate?
4. Design a feature to help ixigo users who frequently miss their trains because of unexpected traffic delays.
5. Competitors like MakeMyTrip and Cleartrip are well-funded. How would you define ixigo's product moat?
6. A travel alert feature is seeing low engagement. How do you decide whether to improve it, pivot it, or shut it down?
7. Tell me about a product you shipped that did not meet its goals. What did you learn?
8. How would you set the North Star metric for ixigo's bus booking vertical?
9. You are launching ixigo into a new geography. Walk through your go-to-market thinking.
10. A cross-functional conflict arises: the growth team wants a full-screen interstitial ad and the UX team is strongly opposed. How do you resolve it?
11. How would you use AI or ML to meaningfully improve the experience for a repeat ixigo traveler?
12. What would you do to improve retention among users who booked once but never returned?

Use the STAR format (Situation, Task, Action, Result) for behavioral and execution questions. The examples below show how to adapt it to ixigo's context.

Q: Tell me about a product you shipped that failed to meet its goals.

*Situation:* I was PM for a loyalty points feature at a mid-size e-commerce company. Internal conviction was high that it would boost repeat purchases.

*Task:* My goal was to launch the feature within the quarter and achieve a lift in repeat order rate.

*Action:* We launched on schedule, but I had not done enough qualitative research to understand whether users trusted the system. Post-launch, I ran user interviews and learned that most users doubted the points had real value because redemption options were thin.

*Result:* The feature missed its targets in the first quarter. I expanded the redemption catalog and rewrote the onboarding copy to communicate value clearly. Repeat orders improved in the following quarter. The lesson I carried forward: test the value proposition with real users before engineering invests heavily.

---

Q: How do you resolve a cross-functional conflict between growth and UX goals?

*Situation:* At a previous company, the growth team wanted a full-screen interstitial on the app home screen. The UX team was firmly opposed, citing the risk of degrading the user experience.

*Task:* As PM, I needed to make a call that balanced near-term revenue with long-term retention.

*Action:* I proposed a controlled experiment instead of a debate. We ran the interstitial for a small user cohort and tracked both ad revenue and downstream metrics like session length and uninstall rate over a short test window.

*Result:* The data showed a short-term revenue lift alongside a statistically significant rise in uninstalls among new users. I shared the findings with both teams, and the growth lead agreed to test less intrusive formats. Because the decision came from data, neither side felt overruled by opinion.

---

Q: You notice a key conversion metric has dropped. How do you investigate?

*Situation:* I faced a similar drop in upsell conversion at a travel-adjacent product I had worked on earlier.

*Task:* I needed to isolate the root cause quickly so the team could act before the trend compounded.

*Action:* I started by segmenting the funnel to check if the drop was across all cohorts or limited to a specific user group or city. I then reviewed the change log to see if any product updates had gone live in that window. I also checked supply-side pricing to see if the prices shown had shifted relative to the previous month, and I spoke to the customer support team to spot any spike in complaints.

*Result:* A UI change had moved the upsell card lower on the confirmation screen, reducing its visibility. Rolling back the placement recovered most of the lost conversion within the same week. The episode reinforced the value of linking a change log directly to metric dashboards.

A few frameworks come up repeatedly in PM interviews. Here is how to apply each in ixigo's context.

CIRCLES (for product design questions). Start by Comprehending the situation, then Identify the user, Report the user's needs, Cut through prioritization, List solutions, Evaluate trade-offs, and Summarize. For ixigo, 'identify the user' often means distinguishing between the urban frequent traveler and the Tier-2 first-time booker, since the right solution can look very different for each.

HEART (for metrics questions). Google's framework covers Happiness, Engagement, Adoption, Retention, and Task Success. Use it to structure how you would measure a feature's health. For a travel alert feature, Retention and Task Success (did the alert actually help the user act in time?) are the most relevant dimensions.

Jobs-to-be-Done. Instead of describing what a feature does, describe the job the user is hiring the product to do. A traveler booking a Tatkal ticket is not just 'booking a ticket.' They are 'getting home for a family emergency with zero planning time.' This framing helps you surface opportunities that a feature comparison alone would miss.

Root Cause Trees (for metric drop questions). Break the drop into branches: is it a data issue, a product change, an external factor like a competitor launch, or a seasonal shift? At each branch, identify one diagnostic question you can answer with data. This shows structured thinking without needing to know the answer upfront.

ixigo interviewers typically look for a few qualities that reflect the company's context.

Bharat-first empathy. ixigo's growth has come from users in smaller cities booking trains on entry-level Android phones with patchy connectivity. Candidates who design for this user, rather than defaulting to a high-bandwidth urban persona, stand out.

Data fluency without data paralysis. You should be comfortable talking about funnels, cohort analysis, and metric trade-offs. But candidates report that interviewers equally value someone who can make a reasonable call under ambiguity rather than waiting for perfect data.

Ownership and follow-through. ixigo is not a large-team company. PMs here are expected to be hands-on, close to engineering, and willing to chase down blockers themselves. Stories that show you taking ownership of messy situations resonate well.

Clear, direct communication. Avoid framework jargon for its own sake. Interviewers generally respond better to a crisp answer in plain language than to a perfectly structured response that is hard to follow.

Comfort with ambiguity. Travel is a seasonal, competitive, and externally sensitive domain. PMs at ixigo regularly work with incomplete signals. Show that you can structure a problem before asking for more data, not after.

A structured plan based on what candidates typically report helps most.

Build your foundation first.

1. Use ixigo's app for a few days before the interview. Book a search, explore the train and flight flows, and note every friction point you hit. First-hand experience gives you specific, credible examples.
2. Read ixigo's public investor communications, press releases, and product blog posts. Understand the core verticals, revenue mix, and what the company has publicly said about its next phase of growth.
3. Revise one analytical framework per day: funnel analysis, cohort retention, A/B test design, and metric trade-off questions.
4. Draft your three to five strongest product stories using STAR format. Each story should show a measurable outcome.

Then sharpen through practice.

1. Do mock interviews focused on product design questions specific to travel: booking flows, alert systems, upsell features, and retention loops.
2. Prepare a structured answer to 'what would you change about ixigo?' Pick one specific, well-reasoned improvement rather than a laundry list.
3. Prepare questions to ask the interviewer. Good ones include: what does success look like for this role in the first few months, and what is the biggest product problem the team is trying to solve right now.
4. Review your CV with a PM lens: for every project, be ready to talk about the metric it moved, the trade-offs you made, and what you would do differently.

These are patterns that frequently come up in feedback from PM interview debriefs.

Designing for yourself, not for the user. A common trap is proposing features you personally find useful, without grounding the answer in who the actual ixigo user is. Before proposing any solution, state explicitly which user segment you are solving for.

Jumping to solutions before diagnosing. When given a metric drop or a product improvement question, many candidates skip straight to 'we should build X.' Interviewers want to see your diagnostic process first. Spend the first part of your answer scoping the problem.

Over-relying on frameworks without substance. Reciting CIRCLES or HEART without connecting it to ixigo's actual users and business context comes across as rehearsed. Use frameworks as a skeleton, not a script.

Ignoring constraints. A technically elegant answer that ignores ixigo's realities, such as low-bandwidth users, IRCTC API limitations, or competitive pricing pressure, misses the mark. Show that you understand the environment.

Weak behavioral answers. Vague answers like 'we collaborated as a team' do not land well. Your STAR answers need a specific situation, a personal action (not a team action), and a concrete result.

Not asking clarifying questions. Launching into an answer for a broad question without scoping it signals poor PM instinct. A brief 'can I clarify a few things first?' followed by a couple of targeted questions shows the kind of structured thinking ixigo looks for.