Malavika Jay

Most asked question: "You have an architecture background, why should we trust you as a PM?" I get some version of this in almost every interview. And honestly, I understand why. My answer is always the same: the skills that make a great PM aren't product-specific. They're human-centred. Discovery, systems thinking, translating complexity into decisions, building for people who don't have a voice in what gets made, I've been doing all of that for a decade. The domain changed. The instinct didn't. Architecture taught me to hold a problem from every angle before committing to a solution. To design for how people will actually use something on a Tuesday morning in five years, not how it looks in a presentation today. To coordinate across disciplines where everyone has different priorities and nobody naturally agrees. The honest gap is that I haven't shipped at scale. I haven't managed a product with millions of users or navigated a large engineering org. I know that. What I'd say is, the fundamentals are solid, the learning curve on domain is something I've proven I can close fast, and the instinct for finding the real problem underneath the stated one is something that's harder to teach than people think. I'm not a traditional PM. But I'm the kind of PM who makes the product better because I think differently than everyone else in the room.TABSwipe