Info Edge Product Manager Interview: Questions & Prep (2026)

Info Edge is one of India's most established internet companies, running major consumer platforms: Naukri (jobs marketplace), Jeevansathi (matrimony), Shiksha (education search), and a real estate classifieds platform. As a publicly listed company, it attracts product managers who want to work at scale with real business accountability.

Knok's job radar shows 28 open Product Manager roles at Info Edge as of July 2026, across levels from Associate PM to Group PM. Salary bands, per industry surveys and publicly reported ranges, run from 12-20 LPA for Associate PMs to 40-60 LPA at Senior PM level, with Group PM roles commonly cited above 55 LPA.

The interview process typically runs across multiple rounds covering product sense, analytical thinking, and behavioural questions. Candidates report that the focus lands heavily on platform knowledge: interviewers want to know you have used Naukri, Jeevansathi, and Shiksha as a real user, not just read about them.

These are the questions candidates report most frequently at Info Edge PM interviews. Each tests a dimension the company cares about.

1. Walk us through one feature on Naukri you would improve and why.
2. How would you prioritise the next set of features for Jeevansathi? Walk us through your framework.
3. Naukri connects job seekers and recruiters. How do you balance the needs of both sides of this marketplace?
4. Tell us about a time you shipped a product or feature that did not meet expectations. What did you do?
5. How would you measure the success of a new candidate-to-recruiter matching algorithm on Naukri?
6. A recruiter complains that Naukri is sending them too many irrelevant CVs. How do you investigate and respond?
7. How would you grow paid listings on Info Edge's real estate classifieds platform?
8. Shiksha competes with newer edtech apps. What product strategy would you propose to keep it relevant in 2026-2027?
9. Tell me about a product you use every day. What is the one thing you would change?
10. How do you handle a situation where engineering tells you a feature is not feasible on your proposed timeline?
11. Walk us through how you would design and run an A/B test for a new layout on Naukri's job search results page.
12. If you were moved from the Naukri product team to Shiksha mid-year, how would you ramp up quickly?

Use these as templates. Adapt the specifics to your own experience. Each follows the STAR structure.

---

Q: Tell us about a time you shipped a feature that did not meet expectations.

*Situation:* At my previous company, we launched a 'quick apply' button on our job listing page. The hypothesis was that reducing friction would increase application rates.

*Task:* I was the PM responsible for defining the feature, setting success metrics, and driving it to launch.

*Action:* We shipped within a few weeks. Post-launch, I pulled the data and saw application volume rise, but employer complaints about 'low-quality applicants' spiked at the same time. I had optimised for one side of the marketplace and hurt the other. I called a review with the team, spoke with a handful of recruiters, and realised we had removed a step that was filtering out low-intent candidates.

*Result:* We added a single qualifying question back into the flow. Employer satisfaction scores recovered within the following sprint. The lesson: in a two-sided marketplace, always track metrics for both sides before declaring a feature successful.

---

Q: How would you measure the success of a new matching algorithm on Naukri?

*Situation:* In a previous role, I led the revamp of the recommendation engine for a classifieds platform.

*Task:* I needed to define the north star metric and guardrail metrics before we ran the experiment.

*Action:* I defined the north star as 'recruiter response rate within two business days,' because it captures actual value delivered to the job seeker. Guardrail metrics included job seeker satisfaction score (so we did not spam them) and recruiter seat renewal rate (a lagging signal of quality). I set up an A/B test with an even traffic split and a two-week run period.

*Result:* The new algorithm lifted recruiter response rate to a level that Glassdoor data suggests sits above the industry median for this category. We shipped to full traffic and used the same framework for every subsequent algorithm experiment.

---

Q: How do you handle disagreement with the engineering team on a feature's feasibility?

*Situation:* I proposed a real-time salary benchmarking widget for a B2B product. The engineering lead said it would take several months, which did not fit the quarter's roadmap.

*Task:* I needed to either find a solution within the constraint or make a transparent trade-off decision for the team.

*Action:* Instead of pushing back, I ran a scoping session to understand what was driving the estimate. We found that real-time data ingestion was the bottleneck. I proposed a 'cached daily refresh' version that took a few weeks and delivered most of the user value. I documented the trade-off clearly so stakeholders understood what we were shipping versus what we were deferring.

*Result:* We launched the lighter version on time. Users adopted it well. The real-time version became a prioritised item for the next quarter, with the engineering team already bought in because they had helped shape the solution.

Having a named framework ready shows structured thinking. These three work well for Info Edge interviews.

Jobs-to-be-done (JTBD). When asked to improve a product, start by identifying the user's underlying goal, not just the surface feature. On Naukri, a job seeker's job-to-be-done is not 'browse listings' but 'get a relevant interview call within two weeks.' Frame your answer around that deeper goal.

RICE prioritisation. When asked how you would prioritise a roadmap, use Reach, Impact, Confidence, and Effort. Spell out the scores for the top two or three ideas you are comparing. Info Edge interviewers appreciate seeing you make trade-offs explicit rather than just listing features in vague order.

North Star plus guardrails. For any metrics question, name one north star metric (the thing that captures core user value) and two or three guardrail metrics (the things you must not break). For Jeevansathi, the north star might be 'successful introductions per month.' Guardrails could be user safety reports and profile verification pass rate.

Marketplace balance check. Info Edge's consumer platforms are two-sided: job seeker and recruiter on Naukri, buyer and seller on the real estate platform, student and institution on Shiksha. Any time you propose a product change, run it through both sides: does this help one side at the expense of the other? Can you improve outcomes for both simultaneously?

Candidates who clear Info Edge PM interviews consistently report that interviewers are looking for a specific profile. Here is what to demonstrate.

Platform fluency. Interviewers expect you to have spent real time as a user on Naukri and Jeevansathi before walking in. If you have not created a profile, posted a job, or searched for a course on Shiksha, do it before your interview. Generic answers about 'improving search relevance' without specific Naukri UI context read as lazy preparation.

Marketplace thinking. Naukri, Jeevansathi, and the real estate classifieds platform are all two-sided marketplaces. Interviewers probe whether you understand how monetisation, trust, and matching work differently in a marketplace versus a single-sided product.

Comfort with ambiguity and data. Candidates report being asked to define metrics, design experiments, and interpret hypothetical data. You do not need to be a data scientist, but you should be able to name the right metric for a given problem and explain how you would instrument it.

Stakeholder collaboration. As a listed company with multiple business units, Info Edge values PMs who can influence without authority. Expect at least one behavioural question about a time you drove alignment across teams without a direct mandate.

Business model awareness. Naukri earns primarily from recruiter subscriptions and resume database access. The real estate platform earns from agent and builder listings. Shiksha earns from lead generation for colleges. Knowing the revenue model of each product signals that you think like an owner, not just a feature builder.

A focused two-week plan, assuming you have a first round coming up.

Week one: platform immersion and product sense.

Spend real time as a user on each Info Edge platform. On Naukri, update your profile and apply to a few roles. On Jeevansathi, walk through the onboarding flow. On Shiksha, search for a course and read college reviews. Note three things you would change on each, with a reason tied to user value rather than personal preference.

Read Info Edge's last two annual reports, which are publicly available on their investor relations page. Note the revenue split across platforms, the growth numbers they highlight, and the risks they call out. This gives you factual grounding without needing to guess at any figures.

Study Info Edge's competitors in each vertical: LinkedIn and Apna in jobs, housing platforms in real estate, and newer edtech entrants in education. Be ready to articulate one key differentiator for each Info Edge product.

Week two: frameworks and mock practice.

Practise the RICE framework and JTBD out loud, not just in writing. Record yourself answering two of the twelve questions listed above. Listen back for filler words and for whether your answer has a clear structure.

Prepare three STAR stories from your own experience: one about a product that underperformed, one about a cross-functional conflict, and one about a metric-driven decision. These cover the most common behavioural angles at Info Edge.

On the day before your interview, spend thirty minutes on Naukri's homepage and job search page. Note any recent UI changes so you can reference them by name in the room.

These are the patterns that typically cost candidates at Info Edge PM interviews.

Generic product answers. Saying 'I would improve search relevance' without tying it to specific Naukri user pain points signals you have not used the product. Always anchor your answer to a specific flow or screen you have personally navigated.

Ignoring the two-sided marketplace. A feature that helps job seekers but floods recruiters with irrelevant CVs is not a good product decision. Show you think about both sides before proposing anything.

Skipping the 'why' on prioritisation. Listing features is not prioritisation. Interviewers want to see you make a choice and defend it with a framework and a clear reason tied to user or business impact.

Not knowing Info Edge's business model. The company publishes detailed financials as a listed entity. Not knowing roughly how Naukri earns versus how the real estate platform earns reads as a lack of basic preparation.

Over-indexing on execution stories for senior roles. At Senior PM and above, interviewers expect more strategy, vision, and cross-team leadership. Balance your STAR stories across execution and influence.

Vague metrics. When asked how you would measure success, 'engagement' or 'user satisfaction' are not sufficient. Name a specific, measurable metric and explain how you would instrument it.