About Priya Ramanathan
Priya Ramanathan is 33 and a product manager at a Series D business software company of about 700 people, based in Brooklyn and in the office three days a week. She owns two adjacent areas — workflow automation and a smaller notifications platform — working daily with one designer, one researcher and seven engineers, and reporting to a group product manager. She has six years in the role across three companies, three at this one, and is doing senior-level work under a mid-level title because her last promotion slipped a cycle. Her degree is in cognitive science. She earns about $200,000 in base plus equity and bonus, rents a two-bedroom in Park Slope with her partner, an engineer, and keeps a restaurant database in her notes app.
She optimizes for outcomes she can be held to, and she frames every decision as a trade-off rather than a pronouncement — she will name what is getting cut. Her register is direct but warm, casual with engineers, more polished with executives, and professional with vendors. She writes a four-to-six-page requirements document that is opinionated and skimmable, and summarizes a decision back at the end of a call. She prefers a sharp wrong opinion to a hedged correct one. What loses her is a cold opening congratulating her on a role she has held for three years, an automation claim with no specifics behind it, a demo-only sales motion with no way to touch the product, or an obviously paid case study. She is under real pressure to ship features described as artificial intelligence while the people she interviews keep asking for better permissions.
She is a strong subject at awareness, consideration and onboarding for product and analytics tooling, customer feedback platforms, research tools, design platforms and product-led growth infrastructure. She is a champion and evaluator rather than a signer — discretionary to about $10,000 a year and an influencer above that — which makes her the right subject for testing self-serve signup, free tiers, trial design, integration narratives and head-to-head comparison positioning. She reads well on per-seat pricing that punishes her for letting colleagues see a dashboard, and on the consolidation pressure and single-sign-on requirements that decide whether a pilot survives. She is weaker on procurement timelines and board-level decisions.
Her media is community-sourced and mostly written. Instagram, YouTube, Google search, LinkedIn, forums, X, podcasts and email all score high, with a paid product newsletter and its podcast doing most of the work, plus two or three practitioner writers she follows closely. Her real research layer is a peer community and a small set of former colleagues and managers she messages directly. Threads, TikTok, connected television and in-app push sit in the middle. Facebook, Pinterest, out-of-home and text messages are low; Snapchat, direct mail and print are absent. Her day is stand-up at half past nine, deep work until noon, customer calls and design critiques through the afternoon, and no laptop after seven except during launch weeks, which are many weeks.
