What peoplesay after.

“Shayan finds the real problem before anyone else has finished describing the symptom.”

I worked with Shayan across two payment launches. Where most PMs stop at the spec, he kept going. Support tickets, session recordings, failed transactions, whatever it took until the actual cause surfaced. Both launches shipped on time and the numbers moved.

“The rare PM engineers ask for by name.”

Shayan speaks enough of our language to be dangerous, in the best way. He once stood up a mock payment API himself so my team could keep building while a partner sandbox was down. Requirements from him arrive pre-thought: edge cases, error states, the boring details that usually surface in week three.

“He ships outcomes, not documents.”

We brought Shayan in to untangle a checkout flow that was bleeding conversions. He diagnosed it in a week, designed the fix, and built the first working version himself with AI tooling before our sprint even started. The metric he promised moved exactly the way he said it would.

“Watches users the way designers wish every PM would.”

Shayan sat through hours of session recordings with us and caught behaviour patterns our research had missed. He treats design as evidence, not decoration, and he defends the user in rooms where that is not the convenient position.