<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Avinash Chandra Srivastava on Medium]]></title>
        <description><![CDATA[Stories by Avinash Chandra Srivastava on Medium]]></description>
        <link>https://medium.com/@avinashchandrasrivastava?source=rss-9854d1ad6af1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*VBuVwpcUugSymB9q</url>
            <title>Stories by Avinash Chandra Srivastava on Medium</title>
            <link>https://medium.com/@avinashchandrasrivastava?source=rss-9854d1ad6af1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:20:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@avinashchandrasrivastava/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What I Learned From Conducting TPM Interviews: The Gap Between Polished Answers and Real Execution]]></title>
            <link>https://medium.com/@avinashchandrasrivastava/what-i-learned-from-conducting-tpm-interviews-the-gap-between-polished-answers-and-real-execution-48779dafa434?source=rss-9854d1ad6af1------2</link>
            <guid isPermaLink="false">https://medium.com/p/48779dafa434</guid>
            <dc:creator><![CDATA[Avinash Chandra Srivastava]]></dc:creator>
            <pubDate>Tue, 22 Sep 2026 05:30:21 GMT</pubDate>
            <atom:updated>2026-09-22T05:30:21.720Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How AI-generated prep is creating a new kind of interview gap — and what actually reveals whether someone can do the work — </em><strong><em>especially for early stage and Junior level</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*krVJrbZH5wfBt2Ka7T8-GA.png" /></figure><p>The interview started like most others.</p><p>“Tell me about yourself.”</p><p>The answer was polished. Confident. Structured perfectly — career arc, key achievements, why they’re excited about product management.</p><p>I could almost hear the ChatGPT cadence in the phrasing. <strong>Nothing wrong with being prepared</strong>. That’s expected.</p><p><strong>But</strong> then I asked: “Walk me through a specific decision you made on that GenAI project you mentioned. What was the problem, what questions did you ask, what trade-offs did you consider?”</p><p>Silence.</p><p>Then a generic response about “stakeholder alignment” and “Agile methodology.”</p><p>I’ve been on the interviewer side of TPM conversations lately (Specially for Junior , and I keep seeing this pattern: candidates show up with beautifully crafted answers to standard questions, but struggle when asked to explain what <strong><em>they</em></strong> specifically did.</p><p>Here’s what I’m learning from the other side of the table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mqOMXjvIgdweV1Uw_evKPg.png" /></figure><h3><strong>The AI-Generated Answer Problem</strong></h3><p><strong>Let me be clear:</strong> I’m not against using AI tools to prepare for interviews. I use Claude and ChatGPT every day in my work (Infact AI helped me in polishing this article also :) ). They’re incredible for brainstorming, structuring thoughts, drafting documentation.</p><p>But here’s the thing.</p><blockquote>When you rely too heavily on AI-generated interview prep, you end up with answers that sound impressive but lack the one thing that matters most: <strong>*<em>your</em>* story</strong>.</blockquote><blockquote>The difference becomes clear within the first few questions. It’s not about catching people out — it’s that prepared <em>with</em> AI assistance looks fundamentally different from memorized AI-generated scripts.</blockquote><p>How the gap shows up</p><p>One candidate I interviewed recently had a perfect answer about Agile methodologies, SDLC, and backlog management. Textbook stuff.</p><p>When asked to describe a time they had to align conflicting stakeholders, they gave a high-level response about “collaboration” and “building consensus.”</p><p>So I pushed: “What specific trade-offs did you present? What data did you use? Who disagreed with your approach and why?”</p><p>The answer came in patches. Disconnected fragments that didn’t quite fit together. No probing questions back to me. No structure.</p><p>They jumped straight to the solution without ever really explaining the problem they were solving.</p><p><strong>That’s the gap</strong>.</p><blockquote>“Prepared <strong><em>with</em></strong> AI looks fundamentally different from memorized AI scripts. The difference shows up the moment you ask for specifics.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oDIxrWXFuHcItuZuI09rEA.png" /></figure><h3>What Actually Reveals Real Capability ?</h3><p>After these interviews, patterns emerged about what actually separates candidates who can execute from those who just interview well.</p><p>And none of them have to do with having the most impressive resume or using the fanciest frameworks.</p><p><strong>1. Asking clarifying questions before jumping to answers</strong></p><p>When I asked one strong candidate about a complex technical architecture decision, they didn’t immediately dive into their solution.</p><p>They asked questions first:</p><p><em>”What’s the context you’re looking for — the technical depth or the stakeholder dynamics?”</em></p><p><em>”Should I focus on the architecture trade-offs or how we arrived at the decision?”</em></p><blockquote>That’s a PM mindset. You don’t have perfect information. <strong>You ask, clarify, then respond</strong>.</blockquote><p>The struggle often shows up differently<strong>:</strong> Candidates hear the question and race to show they have an answer. They jump to solutioning without probing and clarifying what problem they’re being asked to solve.</p><p><strong>2. Explaining problems clearly with concrete details</strong></p><p>One candidate walked me through building a GenAI-powered shopping assistant. But they didn’t just say “we built a chatbot.”</p><p><strong>They explained</strong>:</p><p>- The shopper pain points they were solving (cold start personalization problem)</p><p>- How the product was architecturally constructed</p><p>- The grounding and guardrails they designed</p><p>- Their specific role in defining the approach</p><p><strong>That’s the difference.</strong></p><blockquote>Concrete details. Not “we used Agile” or “we aligned stakeholders.” But <strong><em>how</em></strong> you structured the problem, <strong><em>what</em></strong> trade-offs you identified, <strong><em>why</em></strong> you chose one path over another.</blockquote><p><strong>3. Demonstrating execution capability, not just concepts</strong></p><p>I’ve seen candidates who can talk beautifully about product strategy, OKRs, and vision.</p><p>But when asked, “How did you break that epic into features and stories?” or “What did you do when engineering pushed back on feasibility?” — they go vague.</p><p><strong>For early-stage and junior TPM roles especially, execution is everything.</strong></p><p>The role requires translating a business goal into sprint-ready work. Driving a backlog refinement session. Unblocking a team when dependencies pile up.</p><p>If you can’t explain <strong><em>how</em></strong> you moved something from idea to shipped feature, it becomes difficult to assess whether you can do that work consistently.</p><blockquote><strong>At the junior level, execution fundamentals matter more than strategy narratives. Show me you can write a good user story before you tell me about your product vision.</strong>”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c16hpccUoC5u6B3TfI6qQw.png" /></figure><h3>What I’ve Learned Actually Matters</h3><p>If you’re preparing for TPM interviews right now, here’s what these conversations have taught me about what makes a difference:</p><p><strong>1. Prepare deeply on <em>your</em> projects, not generic examples</strong></p><p>You should be able to talk about your work for 30 minutes straight if someone keeps asking <strong>why</strong>? and <strong>how</strong>?</p><p>Pick 2–3 projects you know inside and out. Be ready to explain your specific contribution at every stage — discovery, definition, delivery.</p><p><strong>2. Ground yourself in the basics</strong></p><blockquote>Especially if you’re interviewing for <strong>junior or mid-level TPM roles</strong>, execution fundamentals matter more than strategy narratives.</blockquote><p>Being able to write a good user story. Understanding acceptance criteria. Knowing how to run a retro and actually improve team velocity.</p><p>Execution isn’t glamorous, but it’s what reveals whether someone can deliver.</p><p><strong>3. Be cognizant of the level you’re interviewing for</strong></p><p>I’ve seen candidates with 15+ years of experience and prior people management roles interview for individual contributor roles — and when asked why, the answer is vague or sounds like they just want to join the company, any role.</p><p>That creates questions.</p><p>If you’re making a move that looks like a step down on paper, be ready to explain <strong><em>why</em></strong> <strong>that move makes sense for you</strong>. Own the narrative.</p><p><strong>4. Practice explaining your work out loud</strong></p><p>AI tools can help you structure your thoughts, but they can’t replace the muscle memory of explaining your decisions in real time.</p><p>Practice with a friend, a mentor, or even record yourself.</p><blockquote>If you’re struggling to articulate what you did without looking at your notes, that’s a sign you need to go deeper.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eaNP2H1vU5QjH7MnJDcHsw.png" /></figure><h3>Final Thoughts</h3><p>Here’s what I’ve learned about what interviewers are actually trying to understand when they dig into details:</p><p>When the conversation pushes on specifics, probes on how you made a decision, asks for examples — <strong>it’s not about testing whether you’re “smart enough.”</strong></p><blockquote>For early stage TPM, It’s about understanding <strong>how you think</strong>. <strong>How you solve problems</strong>. <strong>Whether you can do the work the role requires</strong>.</blockquote><p>The strongest interviews aren’t the ones where someone has a perfect answer for everything. They’re the ones that feel like a conversation. Where the candidate asks questions. Where they admit when something didn’t go well and explain what they learned.</p><p><strong>That’s the human part that AI can’t replicate.</strong></p><p>Your job in the interview isn’t to perform a script. It’s to show <strong><em>you</em></strong> — <strong>your thinking, your approach, your real experience</strong>.</p><p>Prepare with AI tools as they help you organize your thoughts. But when you sit down for that call, put the script aside. <strong>Trust that you know your work better than any generated answer ever could</strong>.</p><blockquote>The details matter. Your specific contribution matters.</blockquote><p>That’s what reveals capability.</p><p><strong>What’s your experience been — either as a candidate or interviewer? What have you learned about what actually matters on the other side of the table?</strong></p><p><em>Drop your thoughts in the comments. I’m curious what patterns others are seeing.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48779dafa434" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Need Two Product Management Coaches (But Not at the Same Time)]]></title>
            <link>https://medium.com/@avinashchandrasrivastava/you-need-two-product-management-coaches-but-not-at-the-same-time-49da9ddd62ef?source=rss-9854d1ad6af1------2</link>
            <guid isPermaLink="false">https://medium.com/p/49da9ddd62ef</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Avinash Chandra Srivastava]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 12:17:05 GMT</pubDate>
            <atom:updated>2026-08-31T12:17:05.437Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Why mastering the fundamentals is just the beginning of your product leadership journey</strong></p><p>If product management were a game of chess, which coach would you want: <strong>Ram or Krishna</strong>?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kcIWxGwlrJLTOojkF1b2qg.png" /></figure><p>Here’s what I mean.</p><h3>The Ram Foundation</h3><p>When you’re new to product management, you need <strong>Ram</strong>. Someone who gives you the fundamentals without overwhelming you with the infinite possibilities of what could go wrong.</p><p>Ram teaches you the principles: —</p><ul><li>Prioritize ruthlessly,</li><li>Align with stakeholders,</li><li>Validate before you build,</li><li>Don’t ship broken features,</li><li>Keep your commitments.</li></ul><p>These aren’t just guidelines — <strong>they’re your foundation</strong>. They keep you from making rookie mistakes that sink products and erode trust.</p><blockquote>I spent my first few years in product following these principles religiously. Don’t promise what you can’t deliver. Always involve engineering early. Get UX feedback before dev starts. User research trumps opinions.</blockquote><p>And it worked. Those principles got me through telecom, fintech, early SaaS days. They built credibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5jisbWprfBsIgtybvW2jBw.jpeg" /></figure><h3><strong>But here’s where it gets interesting.</strong></h3><p>Once you’ve mastered the principles, you start realizing that <strong>blindly following them isn’t the end goal</strong>.</p><p>Sometimes, the right product decision is breaking the very rule that got you here.</p><p>That’s when you need <strong>Krishna</strong> as your coach.</p><p>Krishna knows when to bend or break a principle to serve the higher purpose — in product terms, <strong>to deliver real value</strong>.</p><p>The best PMs I’ve seen don’t just follow frameworks. They know:</p><ul><li>When to skip user research because speed matters more</li><li>When to bypass the “proper process” because the opportunity window is closing</li><li>When to say “we’re shipping this even though it’s not perfect” because waiting another sprint means we’ve missed the moment</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ypJmqAMmC3QdvK3Lih4r7g.jpeg" /></figure><h3>A Real Example: Building Maven</h3><p>Recently, I watched our TPM team getting buried in repetitive workflow tasks.</p><p>Every principle said: <em>document the problem, socialize it with leadership, get buy-in for a proper solution, allocate resources, follow the standard development process.</em></p><p>But our team was losing hours every week to manual work that could be automated.</p><blockquote><strong>I broke the rules.</strong></blockquote><p>I built <strong>Maven</strong> myself — an AI-driven internal tool to automate these workflows. No formal process, no committees, no six-month roadmap. Just focused on solving the immediate problem.</p><blockquote><strong>Result? We cut feature readiness cycle time by 70%.</strong></blockquote><p>It wasn’t perfect at launch, but it was useful immediately. And that mattered more than following the recommended path.</p><h3>The Ram-Krishna Framework</h3><p>Here’s the thing:</p><blockquote><em>Ram builds your foundation. Krishna expands your vision.<br>Ram gives you the way. Krishna gives you the target.<br>Ram teaches you to avoid putting your kind in danger. Krishna gives you that sometimes, you need to sacrifice your queen to </em><strong><em>win the game</em></strong><em>.</em></blockquote><p>The trap I see in product management — especially in complex matrix organizations — is people getting stuck in <strong>Ram mode</strong>.</p><p>Following the process for the sake of the process. Checking all the boxes because that’s what’s “recommended.” Optimizing for predictability instead of impact.</p><p>But the senior PMs, the ones actually moving the needle?</p><p><strong>They’ve learned to play Krishna’s game</strong>. They know which principles to honor and which ones to override when a higher truth — delivering value, serving the user, seizing the moment — demands it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r6FT2hQfTrokhF6rG3L0Qg.jpeg" /></figure><h3>Your Journey Matters</h3><p>So if you’re new to product management, start with Ram. Learn the principles. Master the fundamentals. Build your credibility by showing you can play by the rules.</p><p>But don’t stop there.</p><p>Because eventually, your job isn’t to follow principles.</p><p><strong>It’s to know when to rise above them.</strong></p><h3><strong>Where are you in your journey? Still building your Ram foundation, or learning to play Krishna’s game?</strong></h3><p><strong>About the Author</strong></p><p><a href="https://www.linkedin.com/in/avinash-srivastava-bb32979/">Avinash Srivastava</a> is a Sr Technical Product Manager at Optum (UnitedHealth Group) with 16+ years of experience delivering digital and platform products across healthcare, AI-driven SaaS, fintech, and telecom. He specializes in AI-first product strategy and cross-functional delivery in complex matrix organizations.</p><p>#ProductManagement #Leadership #ProductStrategy #AIProducts #TechLeadership</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49da9ddd62ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>