Dashboard / Candidate
Priya Krishnan
Applied for Product Manager · pm_01_priya_krishnan.pdf
Private: squad_1@pg27.mesaschool.co · +91 98442 31075
Applied-role score
73/100#4 of 34 PM applicants
PM score
73/100SPM score
69/100Current status
AnalysedRecommend shortlist (AI suggestion)
Your decision
1
Why they fit
- Problem -> Change -> Result 25%
The candidate provides multiple clear examples of identifying operational friction, implementing targeted product or process changes, and achieving measurable outcomes (e.g., reducing exceptions by 34%, cutting integration timelines in half, and decreasing dwell time by 1.8 days).
- Evidence-Led Decisions 20%
The CV highlights a clear instance of stopping/killing 3 shipped features based on post-launch adoption data (<8%) despite positive qualitative discovery signals. It also notes feeding ongoing discovery findings directly into sprint planning.
- Builds Repeatable Ways of Working 20%
The candidate created a carrier performance tracking sheet that was subsequently adopted as the branch's standard reporting tool, establishing a new operating practice. Additionally, they introduced reusable API documentation that halved onboarding timelines.
2
Where they fall short
- Carries Ambiguous Problems Through to Closure −16 pts
While the CV mentions routine exception resolution and leading an improvement initiative, it lacks evidence of navigating an ambiguous, cross-functional issue, managing an escalation or failure, and following up after the immediate resolution.
| 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 operational friction, implementing targeted product or process changes, and achieving measurable outcomes (e.g., reducing exceptions by 34%, cutting integration timelines in half, and decreasing dwell time by 1.8 days). |
|
| Evidence-Led Decisions | 20% | 4/5 | 16.0/20 | The CV highlights a clear instance of stopping/killing 3 shipped features based on post-launch adoption data (<8%) despite positive qualitative discovery signals. It also notes feeding ongoing discovery findings directly into sprint planning. |
|
| Builds Repeatable Ways of Working | 20% | 4/5 | 16.0/20 | The candidate created a carrier performance tracking sheet that was subsequently adopted as the branch's standard reporting tool, establishing a new operating practice. Additionally, they introduced reusable API documentation that halved onboarding timelines. |
|
| Carries Ambiguous Problems Through to Closure | 20% | 1/5 | 4.0/20 | While the CV mentions routine exception resolution and leading an improvement initiative, it lacks evidence of navigating an ambiguous, cross-functional issue, managing an escalation or failure, and following up after the immediate resolution. |
|
| Gets to the Source Before Designing the Fix | 15% | 4/5 | 12.0/15 | The candidate embedded directly with client operations teams for two weeks to observe firsthand workflows, designing a proactive alert system that directly resulted in a 34% drop in exceptions. |
|
| Total | 100% | 73 | The candidate demonstrates strong alignment with the rubric on firsthand discovery, evidence-led decision-making (including sunsetting underperforming features), and delivering measurable process and product outcomes. Evidence is comparatively weak regarding guiding messy, ambiguous cross-functional escalations through to structured post-fix closure. | ||
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.
4
Evidence
Verified CV quotes used (PM rubric)
- “Reduced customer-reported exceptions by 34% through a proactive alert system designed after spending 2 weeks embedded with the operations teams of 3 freight forwarder clients” · Problem -> Change -> Result
- “Built the product's first API documentation in collaboration with engineering — reduced new customer integration timelines from 6 weeks to 3 weeks” · Problem -> Change -> Result
- “Led a process improvement initiative that reduced average dwell time at the Mumbai DC by 1.8 days over 6 months” · Problem -> Change -> Result
- “Shipped 7 features in 14 months; killed 3 after post-launch data showed <8% adoption despite strong qualitative signal in discovery” · Evidence-Led Decisions
- “Ran fortnightly discovery sessions with freight forwarder ops teams; fed findings directly into sprint planning with no translation layer” · Evidence-Led Decisions
- “Built a carrier performance tracking sheet that became the branch's standard reporting tool — introduced carrier accountability conversations that hadn't existed before” · Builds Repeatable Ways of Working
- “Built the product's first API documentation in collaboration with engineering — reduced new customer integration timelines from 6 weeks to 3 weeks” · Builds Repeatable Ways of Working
- “Managed day-to-day operations for 3 FMCG client accounts — carrier allocation, inbound shipment scheduling, and exception resolution across 400+ movements monthly” · Carries Ambiguous Problems Through to Closure
- “Led a process improvement initiative that reduced average dwell time at the Mumbai DC by 1.8 days over 6 months” · Carries Ambiguous Problems Through to Closure
- “Reduced customer-reported exceptions by 34% through a proactive alert system designed after spending 2 weeks embedded with the operations teams of 3 freight forwarder clients” · Gets to the Source Before Designing the Fix
- “Ran fortnightly discovery sessions with freight forwarder ops teams; fed findings directly into sprint planning with no translation layer” · Gets to the Source Before Designing the Fix
Outcomes stated in the CV
- Reduced customer-reported exceptions by 34% via a proactive alert system.
- Reduced new customer integration timelines from 6 weeks to 3 weeks by establishing API documentation.
- Reduced average dwell time at the Mumbai DC by 1.8 days over 6 months.
- Shipped 7 features in 14 months and deprecated 3 based on adoption data (<8%).
Anonymised CV (exactly what the AI saw)
[CANDIDATE] Product Manager [PHONE REDACTED] · [EMAIL REDACTED] · Mumbai · [PROFILE URL REDACTED] PROFESSIONAL SUMMARY Product Manager with 4 years of experience in logistics operations and freight-tech SaaS. Built fluency in how freight forwarders and 3PLs operate before moving into product. Owned product areas independently at an early-stage company. Ship fast, learn from what lands, cut what doesn't. WORK EXPERIENCE Product Manager Portzen Technologies Pvt. Ltd. (Freight Visibility SaaS, 35 employees), Mumbai · Mar 2022 – Present — Sole PM responsible for shipment tracking, exception management, and carrier integration modules — no PM manager above, decisions owned end-to-end — Shipped 7 features in 14 months; killed 3 after post-launch data showed <8% adoption despite strong qualitative signal in discovery — Reduced customer-reported exceptions by 34% through a proactive alert system designed after spending 2 weeks embedded with the operations teams of 3 freight forwarder clients — Built the product's first API documentation in collaboration with engineering — reduced new customer integration timelines from 6 weeks to 3 weeks — Ran fortnightly discovery sessions with freight forwarder ops teams; fed findings directly into sprint planning with no translation layer Operations Coordinator Mahindra Logistics Ltd., Mumbai · Jul 2020 – Feb 2022 — Managed day-to-day operations for 3 FMCG client accounts — carrier allocation, inbound shipment scheduling, and exception resolution across 400+ movements monthly — Built a carrier performance tracking sheet that became the branch's standard reporting tool — introduced carrier accountability conversations that hadn't existed before — Coordinated directly with CHA partners on customs documentation for time-sensitive pharma imports — learned the documentation chain from both sides — Led a process improvement initiative that reduced average dwell time at the Mumbai DC by 1.8 days over 6 months Graduate Trainee — Supply Chain Mahindra Logistics Ltd., Mumbai · Feb 2020 – Jun 2020 — 5-month rotational programme across warehousing, last-mile, and customer operations functions — Supported the ops team during a 3PL contract renewal — gathered usage data, documented service gaps, and prepared the internal review deck EDUCATION B.Com (Hons.) · Jai Hind College, University of Mumbai · 2016–2019 · First Division SKILLS & CERTIFICATIONS Product roadmapping · PRD authoring · Freight operations · JIRA · Figma · Mixpanel · SQL (working knowledge) · CargoWise One · Excel Product Management Certification – Product School (2022) · APICS CSCP (in progress)
Redacted: name ×1, email ×1, phone ×1, profile url ×1
5
Interview brief
Briefs are written when you shortlist a candidate.
6
Email draft
An offer or rejection draft is prepared once you make a decision. Nothing is ever sent without your approval.
Audit trail (2)
- 9/29/2026, 11:02:09 AMsystemanalysis completed{"PM_score":73,"SPM_score":69}
- 9/29/2026, 11:01:24 AMsystemcv ingested{"file":"pm_01_priya_krishnan.pdf","role":"PM","redactions":{"name":1,"email":1,"phone":1,"profile_url":1},"name_detected":true}