From our research
What this interview looks like
Most Indian companies run an HR screen, one or two hiring-manager or technical rounds and a final HR discussion on expectations, spread over days. ExamPilot compresses the loop into one 17-minute panel (HR → hiring manager → role/technical lead → behavioural → closing) or a 12-minute one-on-one with the hiring manager. Rounds are pass/fail in real life; here you get a scored report on role knowledge, problem solving, communication and attitude, with STAR feedback on every behavioural answer.
How it is weighted
Pass/fail per round in real life; scored here against the corporate rubric.
Who this is for
Product managers, associate PMs and UX/product designers, including engineers or analysts moving into product.
The panel focuses on
- Prioritisation and metrics
- Product sense for Indian users
- Research vs data
- Stakeholder conflict and scope cuts
- Explaining a launch you owned
Step 1
Pick your domain
The expert on the panel probes these areas at the level of this role. Optional here; you can choose during setup.
Step 2
Choose how you want to be interviewed
1:1 interview
One interviewer runs every round and adapts the focus as you go. Lower pressure; ideal for a first attempt.
Mr. Siddharth Menon
Hiring manager
Panel interview · 3 members
Most realisticEach member leads their own round and hands over to the next. They hear each other, so a weak answer will be revisited.
Ms. Neha Kulkarni
HR member
Mr. Siddharth Menon
Hiring manager
Ms. Shalini Krishnan
Technical lead
What to expect
5 rounds · 17 minutes
A private-sector hiring loop compressed into one sitting, the way most Indian companies run it: HR screen → hiring-manager round on your actual work → role/technical round led by a lead → communication & behavioural (STAR) round → closing on expectations and your questions. Works for software, product, sales, finance, HR, support and campus hiring by swapping the role bank.
- Round 1
HR screen
· 3:00Understand background, motivation for this role and company, and basic logistics; check that the resume story holds together.
Ms. Neha Kulkarni2–3 questionsup to 1 follow-up each - Round 2
Hiring-manager round
· 4:00Assess ownership, judgement and how the candidate actually works: what they shipped, closed or ran, their specific part, and how they would approach this job.
Mr. Siddharth Menon2–3 questionsup to 2 follow-ups each - Round 3
Role / technical round
· 5:00Test role knowledge and problem-solving in the chosen specialisation: fundamentals, one scenario to think through aloud, and trade-offs.
Ms. Shalini Krishnan3–4 questionsup to 2 follow-ups each - Round 4
Communication & behavioural round
· 3:00Assess collaboration, conflict handling, resilience and clarity of expression through Situation–Task–Action–Result examples.
Mr. Siddharth Menon2–2 questionsup to 1 follow-up each - Round 5
Expectations & closing
· 2:00Cover practical expectations and let the candidate ask questions; close professionally.
Ms. Neha Kulkarni1–2 questions
Sample questions
Job interviews PM / UX interview questions
Questions panels commonly ask in the Job interviews PM / UX interview, with what a strong answer covers. Practise them aloud with the AI panel.
- Launch story
Pick a feature you launched or designed. What problem was it solving, how did you know it worked, and what would you change now?
What a strong answer covers
Frame the user problem with evidence, the solution and the alternatives you rejected, the metric that moved with real numbers, and one honest regret. Show what you personally drove. Avoid describing the feature list without any outcome or claiming credit for decisions the whole team made.
- Metrics
Daily orders on a food-delivery app dropped twelve percent last Tuesday in Hyderabad only. How would you investigate?
What a strong answer covers
Confirm the data is real, then segment by platform, app version, area, restaurant supply, payments and delivery time. Check external causes like rain, a festival or a competitor offer. Rank hypotheses and say what you would check first. Avoid jumping to a fix before isolating where the drop sits.
- Prioritisation
You have five feature requests, one engineering squad and six weeks. Sales wants a custom report for a big client. How do you prioritise?
What a strong answer covers
Use a framework such as impact versus effort or RICE, tie each item to company goals, and explain how the sales request is weighed on revenue and reuse. Show how you would say no or later to sales with reasons. Avoid saying you would simply build whatever the loudest stakeholder asks for.
- Product sense
How would you design a UPI bill-payment flow for a first-time smartphone user in a Tier 3 town who reads Hindi more comfortably than English?
What a strong answer covers
Start with the user's context: low trust, shared phones, patchy network and language. Cover vernacular UI, clear confirmation screens, recovery from failed payments and voice or icon cues. Mention testing with real users. Avoid designing for a metro power user or relying only on text-heavy screens.
- Research vs data
When would you trust user research over analytics data, and when the other way round? Give an example from your work.
What a strong answer covers
Explain that analytics shows what users do at scale while research explains why. Give a real example where one corrected the other, and how you combined both before a decision. Avoid treating one source as always superior or citing a five-user interview as conclusive proof.
- Scope cuts
An engineering lead says your design will take twice the estimated time. The launch date is fixed. What do you do?
What a strong answer covers
Understand where the effort sits, then explore scope cuts, phased release or simpler interactions that protect the core user outcome. Agree the trade-off openly with design, engineering and leadership. Avoid pressuring engineers to work weekends or quietly cutting quality without telling anyone.
- Design critique
Walk me through one screen in your portfolio and justify each major design decision on it.
What a strong answer covers
Explain the user goal for that screen, the hierarchy, why key elements are placed where they are, accessibility choices, and the testing or data behind them. Mention one version you discarded. Avoid answers like it looks clean or the client liked it, which show taste but not reasoning.
- Stakeholders
Think of a sales head, founder or engineering lead who fought your roadmap call. How did you bring them round, or did you change your mind?
What a strong answer covers
A STAR answer: the disagreement, how you understood their concern, the evidence you brought, the compromise or decision reached, and the relationship afterwards. Show listening as much as persuading. Avoid stories where you won by escalating to your manager without trying to resolve it first.
- Closing
If you join us, what would you aim to understand and deliver in your first ninety days?
What a strong answer covers
A realistic plan: first month learning users, data, team and product history; second month owning a small problem; third month shipping or proposing a roadmap item with metrics. Ask what success looks like here. Avoid promising a full redesign or big launch before understanding the context.
Reading is not rehearsing. Answer these out loud to an AI Job interviews PM / UX panel that follows up like the real one.
Practise these questionsMeet the panel
Your AI interviewers
Distinct personas, voices and questioning styles, briefed on this role.
Ms. Neha Kulkarni
ChairHR member
HR business partner, IT services
Friendly, efficient, detail-checking.
Female voice · 4 languages
Mr. Siddharth Menon
Hiring manager
Head of Product & Business (hiring manager, non-tech roles)
Structured, numbers-first, quietly demanding.
Male voice · 3 languages
Ms. Shalini Krishnan
Technical lead
Senior functional lead — business roles (finance, sales, marketing, HR, CX, product)
Practical, scenario-driven, warm but exact.
Female voice · 4 languages
Languages
Answer in the language you think in
The panel asks in your chosen language. Switch mid-answer if you like.
- English
- Hinglish (Hindi + English)Hinglish
How scoring works
A report you can act on
Every round is scored on the rubric
Each interviewer scores only the criteria their round covers. Weights add up to your overall score out of 100.
Only what you actually said counts
Feedback quotes your own answers. Rounds you skip show as “Not assessed” rather than a zero.
Communication is always measured
Fluency, clarity, confidence and structure are tracked across the whole interview, in any language.
Pass mark, then a plan
You see the pass mark for this interview, your gaps, and the courses that close them fastest.
Scored on
- Role knowledge30%
Depth and accuracy of role/domain knowledge; understands the tools, concepts and trade-offs of the job; grounds claims in real work.
- Problem solving & structure25%
Breaks problems down, asks clarifying questions, reasons about trade-offs and edge cases, structures answers (context, action, result).
- Communication25%
Clear, concise, confident; listens and answers the question asked; adapts the explanation to the listener; professional register.
- Culture & attitude20%
Ownership, honesty about limits, coachability, collaboration, motivation for this role and realistic expectations.
Pass mark 65 / 100 · Corporate interview — HR, hiring manager & role round (panel)
Keep exploring