Kabir Mehta
Why they fit
- Problem -> Change -> Result 25%
The candidate provides multiple clear examples of identifying problems, implementing specific changes, and achieving measurable results. These include designing a returns triage process that cut cycle time by 2 days and cleared backlogs, building an integration that unlocked 5 stalled enterprise accounts, and creating a shift handover checklist that resolved dispatch delays.
- Evidence-Led Decisions 20%
There is a direct and clear example of killing a launched feature based on adoption metrics, redirecting resources to an alternative feature that subsequently achieved top NPS. The entry clearly explains the reasoning, the decision made, and the positive downstream result.
- Builds Repeatable Ways of Working 20%
The candidate built a shift handover checklist to solve dispatch delays, which became a repeatable operating artifact adopted across three additional hubs. This demonstrates clear reuse by others outside the candidate's immediate scope.
Where they fall short
- Carries Ambiguous Problems Through to Closure −12 pts
While the candidate managed operational peaks and operated as a sole PM navigating roadmap ownership, the CV lacks a detailed example of coordinating a messy, cross-functional issue through to resolution, including deliberate follow-up after an immediate fix.
| Criterion | Weight | Score | Weighted | AI reasoning | Evidence from CV |
|---|---|---|---|---|---|
| Problem -> Change -> Result | 25% | 5/5 | 25.0/25 | The candidate provides multiple clear examples of identifying problems, implementing specific changes, and achieving measurable results. These include designing a returns triage process that cut cycle time by 2 days and cleared backlogs, building an integration that unlocked 5 stalled enterprise accounts, and creating a shift handover checklist that resolved dispatch delays. |
|
| Evidence-Led Decisions | 20% | 4/5 | 16.0/20 | There is a direct and clear example of killing a launched feature based on adoption metrics, redirecting resources to an alternative feature that subsequently achieved top NPS. The entry clearly explains the reasoning, the decision made, and the positive downstream result. |
|
| Builds Repeatable Ways of Working | 20% | 4/5 | 16.0/20 | The candidate built a shift handover checklist to solve dispatch delays, which became a repeatable operating artifact adopted across three additional hubs. This demonstrates clear reuse by others outside the candidate's immediate scope. |
|
| Carries Ambiguous Problems Through to Closure | 20% | 2/5 | 8.0/20 | While the candidate managed operational peaks and operated as a sole PM navigating roadmap ownership, the CV lacks a detailed example of coordinating a messy, cross-functional issue through to resolution, including deliberate follow-up after an immediate fix. |
|
| Gets to the Source Before Designing the Fix | 15% | 4/5 | 12.0/15 | The candidate demonstrates firsthand discovery by spending three weeks embedded with client operations teams across four companies, directly informing the design and launch of the LTL tracking module. |
|
| Total | 100% | 77 | The candidate demonstrates strong alignment with the rubric, showing repeated instances of connecting concrete actions to measurable business outcomes, making evidence-led product trade-offs, and embedding firsthand user discovery into feature design. They also demonstrate the ability to create repeatable operational tools adopted across teams, though there is comparatively limited evidence of driving ambiguous cross-functional escalations through to long-term follow-up. | ||
Scoring scale
- 0: No evidence in the CV
- 1: Indirect or participation-only evidence
- 2: Partial: some elements of the description, weak link to outcome
- 3: One clear example matching the description
- 4: Clear example with a visible result, candidate's own action linked to it
- 5: Repeated, strong examples fully matching the description, with results
Weighted contribution = score ÷ 5 × weight. Every quote is checked against the CV text; if none can be verified, the score is capped at 1.
Evidence
- “Ran the returns processing team of 12 during an 8-week peak period — designed a triage process that reduced returns cycle time by 2 days and eliminated the backlog” · Problem -> Change -> Result
- “Built a shift handover checklist after a recurring miscommunication between shifts was causing delayed dispatches — adopted across 3 other hubs within 2 months” · Problem -> Change -> Result
- “Worked with engineering to build a basic integration with CargoWise One — opened up 5 freight forwarder accounts that had been stalled for 6 months” · Problem -> Change -> Result
- “Killed a supplier portal feature 3 weeks after launch when adoption data showed the problem was not where we thought it was; redirected the sprint capacity to a warehouse exception alert that became the product's highest NPS feature” · Evidence-Led Decisions
- “Built a shift handover checklist after a recurring miscommunication between shifts was causing delayed dispatches — adopted across 3 other hubs within 2 months” · Builds Repeatable Ways of Working
- “Ran the returns processing team of 12 during an 8-week peak period — designed a triage process that reduced returns cycle time by 2 days and eliminated the backlog” · Carries Ambiguous Problems Through to Closure
- “Shipped live tracking module for LTL shipments — feature designed after spending 3 weeks with operations teams at 4 FMCG and pharma clients across Maharashtra” · Gets to the Source Before Designing the Fix
- Shipped live tracking module for LTL shipments.
- Delivered a warehouse exception alert that became the product's highest NPS feature.
- Built an integration with CargoWise One that unblocked 5 freight forwarder accounts stalled for 6 months.
- Reduced returns cycle time by 2 days and eliminated backlog during an 8-week peak period.
- Created a shift handover checklist adopted across 3 additional hubs within 2 months.
Anonymised CV (exactly what the AI saw)
[CANDIDATE] [EMAIL REDACTED] [PHONE REDACTED] · Pune [PROFILE URL REDACTED] Professional Summary Product Manager with a background in warehouse operations and supply chain execution before transitioning to tech. 3 years in PM roles at a supply chain SaaS startup — the only PM on the product for the first 18 months. Understand how freight and warehousing teams think because I've worked in those rooms. Work Experience Product Manager TrackEasy Solutions Pvt. Ltd. (Supply Chain Visibility, Series A), Pune · Jan 2023 – Present — Took over as sole PM when the founding PM departed; owned roadmap, discovery, and delivery for the next 14 months without a manager above in the product function — Shipped live tracking module for LTL shipments — feature designed after spending 3 weeks with operations teams at 4 FMCG and pharma clients across Maharashtra — Killed a supplier portal feature 3 weeks after launch when adoption data showed the problem was not where we thought it was; redirected the sprint capacity to a warehouse exception alert that became the product's highest NPS feature — Worked with engineering to build a basic integration with CargoWise One — opened up 5 freight forwarder accounts that had been stalled for 6 months — Currently managing a 3-person engineering team and a contract designer; first full product hire below me joined in January Warehouse Operations Executive Aramex India Pvt. Ltd., Pune · Aug 2020 – Dec 2022 — Managed inbound sorting, put-away, and dispatch operations for an e-commerce fulfilment hub processing 6,000–8,000 orders daily at peak — Ran the returns processing team of 12 during an 8-week peak period — designed a triage process that reduced returns cycle time by 2 days and eliminated the backlog — Built a shift handover checklist after a recurring miscommunication between shifts was causing delayed dispatches — adopted across 3 other hubs within 2 months — Worked directly with the transport team on last-mile allocation and rescheduling; understood the carrier relationship from the warehouse side Education B.E., Mechanical Engineering · Pune Institute of Computer Technology (PICT), Pune · 2016–2020 · First Class Skills & Certifications Product ownership · Warehouse & supply chain operations · JIRA · Figma · SQL · Excel · Notion · Miro Product Analytics Certification – Mixpanel (2023) · Lean Six Sigma Yellow Belt (2021)
Interview brief
The candidate demonstrates exceptional execution on core product delivery and operational rigor, evidenced by hands-on discovery and a proven ability to redirect roadmap investments using adoption metrics. They align strongly with 'Problem -> Change -> Result' and 'Evidence-Led Decisions' through tangible wins in both supply chain software and operational environments. However, they fall short on 'Carries Ambiguous Problems Through to Closure', with limited evidence showing how they steer messy, cross-functional ambiguity through to sustained resolution.
Killed a supplier portal feature 3 weeks after launch when adoption data revealed incorrect problem assumptions, redirecting capacity to build a warehouse exception alert that achieved the product's highest NPS.
Carries Ambiguous Problems Through to Closure (weight 20%, score 2/5). The CV lacks clear demonstrations of guiding complex, open-ended problems involving divergent cross-functional stakeholders through to sustained post-implementation closure; test how the candidate handles messy, unresolved problems where root causes and team boundaries are contested.
It is unknown how effectively the candidate navigates strategic ambiguity and drives alignment when managing conflicting cross-functional stakeholders outside their direct operational or engineering scope.
- Carries Ambiguous Problems Through to Closure: May struggle when an ambiguous problem cannot be solved purely through direct execution or operational checklists, but requires persistent cross-organizational consensus.
- When you killed the supplier portal feature after 3 weeks, how did you identify that the initial problem assumption was wrong, and how did you manage pushback from stakeholders who backed the initial build?Verifies the depth of data analysis and cross-functional handling under the Evidence-Led Decisions criterion.
- Can you walk through a specific instance at TrackEasy where you inherited a messy, poorly defined problem with no clear owner, and explain how you drove it to closure and verified the solution stuck?Directly probes the gap in Carries Ambiguous Problems Through to Closure.
- During your 3 weeks embedded with operations teams at the 4 FMCG and pharma clients, what specific hypothesis did you initially have that turned out to be wrong before designing the LTL tracking module?Tests the depth of firsthand discovery and adherence to Gets to the Source Before Designing the Fix.
- When building the basic CargoWise One integration to unblock the 5 freight forwarder accounts, how did you scope the MVP against client requirements and what trade-offs did you make with engineering?Verifies execution rigour and stakeholder management under Problem -> Change -> Result.
- How did you ensure the shift handover checklist was consistently used across the other 3 hubs after initial rollout, and what steps did you take to inspect compliance?Validates the candidate's approach to establishing and maintaining standards under Builds Repeatable Ways of Working.
Email draft
An offer or rejection draft is prepared once you make a decision. Nothing is ever sent without your approval.
Audit trail (4)
- 9/29/2026, 11:40:28 AMsystemassessment generated{"model":"gemini:gemini-flash-latest"}
- 9/29/2026, 11:37:13 AMsystemauto finalist{"role":"PM","score":77}
- 9/29/2026, 11:02:05 AMsystemanalysis completed{"PM_score":77,"SPM_score":78}
- 9/29/2026, 11:01:24 AMsystemcv ingested{"file":"pm_02_kabir_mehta.pdf","role":"PM","redactions":{"name":1,"email":1,"phone":1,"profile_url":1},"name_detected":true}