Siddharth Rao
Why they fit
- Independent Decision Ownership 30%
The candidate operated as the sole senior PM directly under a co-founder and made an independent, consequential architectural decision to move from a monolith to a modular suite based on discovery findings. While trade-offs are described, further detail on specific uncertainty or risk managed during execution is limited.
- Problem -> Change -> Business/Operational Result 20%
The CV provides multiple direct examples where candidate interventions solved operational or user issues and produced measurable business results (22% conversion increase, 60% support ticket reduction).
- Evidence-Led Prioritisation and Reversal 20%
The candidate demonstrates evidence-based decision-making and willingness to reverse course, killing 4 features post-launch based on usage data, including a feature they had personally proposed.
Where they fall short
- Multi-Party Resolution Under Pressure −9 pts
The CV highlights routine operational coordination under pressure across multiple external entities (shipping lines, CHAs, customs) and handling emergencies without escalation. However, it provides generalized responsibilities rather than a specific, closed multi-party incident resolution or post-mortem.
| 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 friction and directly implementing product changes that yielded tangible, measurable results. These include reducing primary support tickets by 60%, increasing conversion by 22%, and driving shift adoption of a new tracking tool. |
|
| Evidence-Led Decisions | 20% | 4/5 | 16.0/20 | The CV highlights clear instances of stopping or altering product direction based on concrete evidence rather than assumption. The candidate killed features (including their own) based on usage data and restructured the product architecture based on customer discovery rather than engineering preferences. |
|
| Builds Repeatable Ways of Working | 20% | 4/5 | 16.0/20 | The candidate created a digital container dwell-time tracker that transitioned from an individual operational tool into an adopted, repeatable practice across two other shifts within the port. |
|
| Carries Ambiguous Problems Through to Closure | 20% | 2/5 | 8.0/20 | The CV shows evidence of handling cross-functional operational crises and coordinating across multiple parties without escalation. However, it reflects general operational responsibility rather than an end-to-end ambiguous problem tracked through resolution and post-fix follow-up. |
|
| Gets to the Source Before Designing the Fix | 15% | 4/5 | 12.0/15 | The candidate demonstrates strong firsthand discovery, actively sitting in on onboarding sessions and spending months with customers to understand specific friction points before rebuilding the product suite and designing integrations. |
|
| Total | 100% | 77 | The candidate demonstrates strong alignment with the rubric, particularly in driving measurable product outcomes, relying on firsthand discovery, and making evidence-based decisions like killing underperforming features. While they show an ability to create reusable tools and manage cross-stakeholder operations, there is less evidence of a singular ambiguous project driven through full closure with post-resolution 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
- “Led the product function as the sole senior PM for 2.5 years — owned roadmap, discovery, and delivery with no PM manager; reported directly to co-founder” · Independent Decision Ownership
- “Rebuilt the entire product architecture from a single monolith to a modular suite after understanding that freight forwarders needed to adopt specific features without the full platform commitment — decision made after 3 months of customer discovery, not based on engineering preference” · Independent Decision Ownership
- “Shipped a multi-carrier rate comparison feature that increased booking conversion from the platform by 22%” · Problem -> Change -> Business/Operational Result
- “Led the integration with ICEGATE for automated customs filing status — reduced the most common client support ticket by 60%” · Problem -> Change -> Business/Operational Result
- “Shipped 12 features in 3 years; killed 4 post-launch based on usage data; one killed feature was my own idea from the previous roadmap cycle” · Evidence-Led Prioritisation and Reversal
- “Built the shift's first digital container dwell-time tracker; port management adopted it across 2 other shifts within 3 months” · Creates Systems Others Run
- “Coordinated daily with shipping lines, freight forwarders, CHAs, and customs authorities on vessel and cargo clearance timelines” · Multi-Party Resolution Under Pressure
- “Led the night shift terminal operations team of 18 for 14 months — managed emergency cargo releases, vessel delays, and chassis shortages without escalation in most cases” · Multi-Party Resolution Under Pressure
- Grew managed accounts from 8 to 34 over 2 years at Portwise Technologies
- Increased platform booking conversion by 22% via multi-carrier rate comparison feature at LogiStack Technologies
- Reduced most common client support ticket by 60% via ICEGATE integration at LogiStack Technologies
- Developed digital container dwell-time tracker adopted across 2 additional shifts within 3 months at JNPT
Anonymised CV (exactly what the AI saw)
[CANDIDATE] Senior Product Manager [PHONE REDACTED] · [EMAIL REDACTED] · Mumbai · [PROFILE URL REDACTED] Professional Summary Senior Product Manager with 7 years of experience — 3 years in port and terminal operations at JNPT, followed by 4 years in logistics SaaS product roles. Deep understanding of how freight moves through Indian ports, the operational pressures on freight forwarders and CHAs, and where software consistently fails them. Led product function independently at a startup for 2.5 years. Work Experience Head of Product (SPM-equivalent) Portwise Technologies Pvt. Ltd. (Port & Logistics SaaS, 55 employees), Mumbai · Aug 2022 – Present — Led the product function as the sole senior PM for 2.5 years — owned roadmap, discovery, and delivery with no PM manager; reported directly to co-founder — Rebuilt the entire product architecture from a single monolith to a modular suite after understanding that freight forwarders needed to adopt specific features without the full platform commitment — decision made after 3 months of customer discovery, not based on engineering preference — Shipped 12 features in 3 years; killed 4 post-launch based on usage data; one killed feature was my own idea from the previous roadmap cycle — Designed the JNPT container tracking integration after understanding the ICEGATE API limitations from my time in terminal operations — feature worked because I knew what the data actually contained, not just the field names — Grew managed accounts from 8 to 34 over 2 years; sat in on every new customer onboarding in the first year to understand where the product broke Senior Product Manager LogiStack Technologies (Freight Management SaaS), Mumbai · Jan 2021 – Jul 2022 — Owned the freight booking and carrier allocation module — led a 4-person squad — Shipped a multi-carrier rate comparison feature that increased booking conversion from the platform by 22% — Led the integration with ICEGATE for automated customs filing status — reduced the most common client support ticket by 60% Terminal Operations Executive → Senior Operations Executive JNPT (Jawaharlal Nehru Port Trust), Nhava Sheva · Jun 2017 – Dec 2020 — Managed berth allocation, vessel scheduling, and container handling coordination at JNPT's Terminal 4 — Coordinated daily with shipping lines, freight forwarders, CHAs, and customs authorities on vessel and cargo clearance timelines — Led the night shift terminal operations team of 18 for 14 months — managed emergency cargo releases, vessel delays, and chassis shortages without escalation in most cases — Built the shift's first digital container dwell-time tracker; port management adopted it across 2 other shifts within 3 months Education MBA, Operations · Jamnalal Bajaj Institute of Management Studies, Mumbai · 2015–2017 B.E., Mechanical Engineering · VJTI Mumbai · 2011–2015 · First Division Skills & Certifications Product strategy & roadmap · Port & terminal operations · Freight forwarding domain · ICEGATE · CargoWise · JIRA · Figma · SQL · Miro FIATA Advanced Freight Forwarding Module (2019) · SAFe 5 Product Owner/PM (2022)
Interview brief
The candidate demonstrates strong evidence in driving measurable outcomes and evidence-based decision-making, such as a 22% conversion increase and a willingness to kill underperforming features including their own. They also show high autonomy, having spent 2.5 years as the sole PM leading roadmap and architectural pivots based on discovery. However, the candidate falls short on demonstrating product-specific operating systems or frameworks that others run, and their multi-party conflict resolution under pressure is grounded in generalized port operations rather than detailed software incident post-mortems.
Shipped a multi-carrier rate comparison feature that increased booking conversion from the platform by 22% and delivered an ICEGATE integration reducing customer support tickets by 60%, directly fulfilling Problem -> Change -> Business/Operational Result.
Independent Decision Ownership (weight 30%): While the candidate decided to shift Portwise from a monolith to a modular suite based on discovery, the CV lacks detail on how engineering risks, scope compromises, and stakeholder pushback were navigated during execution.
The extent to which the candidate can design and institutionalize repeatable software product processes or PM frameworks that scale across teams without relying solely on their individual domain intuition.
- Creates Systems Others Run: May rely heavily on individual domain knowledge and hands-on execution rather than scaling team effectiveness through clear product systems.
- Independent Decision Ownership: Architectural or product decisions may lack documented risk mitigation frameworks when PM leadership is absent.
- Walk me through the execution of rebuilding Portwise's platform from a monolith to a modular suite: what unexpected technical or timeline risks emerged, and what trade-offs did you make to ship it?Probes Independent Decision Ownership to evaluate how the candidate manages risk, uncertainty, and engineering alignment during major architectural changes.
- Regarding the 4 features you killed post-launch, specifically the one you personally proposed: what exact usage thresholds triggered the decision to sunset it, and how did you manage stakeholder pushback?Validates Evidence-Led Prioritisation and Reversal to test objective decision-making and accountability when deprecating features.
- What product rituals, specs, or prioritization frameworks did you introduce at Portwise or LogiStack that engineering, design, or other stakeholders continued using independently?Addresses the gap in Creates Systems Others Run to determine whether the candidate can establish lasting software PM processes.
- Can you share a specific incident during your terminal operations or at Portwise where multiple external parties, such as customs authorities and shipping lines, had conflicting urgent demands, and walk through how you resolved it under pressure?Tests Multi-Party Resolution Under Pressure to move beyond high-level responsibilities into concrete, high-stakes stakeholder mediation.
- For the ICEGATE integration at LogiStack, how did you discover that ticket volume was linked to customs status, how did you navigate API constraints, and what was the rollout process?Verifies the Problem -> Change -> Business/Operational Result claim and assesses technical problem-solving depth.
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:01 AMsystemassessment generated{"model":"gemini:gemini-flash-latest"}
- 9/29/2026, 11:37:15 AMsystemauto finalist{"role":"SPM","score":65}
- 9/29/2026, 11:02:40 AMsystemanalysis completed{"PM_score":77,"SPM_score":65}
- 9/29/2026, 11:01:28 AMsystemcv ingested{"file":"spm_16_siddharth_rao.pdf","role":"SPM","redactions":{"name":1,"email":1,"phone":1,"profile_url":1},"name_detected":true}