Aspirant's Scroll

What I Look for in a Junior PM's First 90 Days

MR
Mrinal Rai
5 min read

The Trap of the Shiny Deliverable

Every time we hire a junior Product Manager at Intugine, the same pattern repeats. They come in with a notebook full of ideas, ready to 'optimize' the dashboard or 'streamline' our carrier integration flows. They want to ship. They want to show off their Figma skills. They want the dopamine hit of a finished ticket in Jira. But here is the reality: in your first 90 days, I don’t care if you ship a single feature. In fact, I would prefer you didn’t.

When you are new to B2B SaaS—especially in a complex space like supply chain visibility where we are processing millions of GPS pings across thousands of trucks—your first instinct to 'improve' things is usually just noise. You do not understand the edge cases yet. You do not know why the data team hardcoded that specific filter, or why our enterprise clients in the FMCG sector get angry if a delivery notification is delayed by even sixty seconds. Your 90-day evaluation is not about output. It is about how you learn, how you question, and how you integrate into the chaos.

The Art of the 'Why'

I look for the PM who stops me in the middle of a stand-up. Not to be disruptive, but to ask: 'Why are we solving this for this specific client? Is this a one-off request or a platform-wide gap?' The best junior PMs are those who treat every request from Sales as a data point for a broader investigation, not as a command to be executed.

In the first 90 days, your most valuable asset is not your technical proficiency, but your radical intellectual curiosity about the customer's actual pain.

If you spend your first month mapping out our API documentation for third-party logistics partners, I am impressed. If you spend your first month trying to redesign the mobile app interface without talking to a single driver or depot manager, you are a liability. I want to see you getting your hands dirty.

Patterns of Maturity

I track three specific behaviors during those first three months:

  • Context Acquisition: Can you explain the difference between a geofencing failure and a telecom network latency issue? If you can talk to the engineering lead without needing a translator, you are winning.
  • Ownership of the 'Mess': Things break here. APIs go down, data fields get corrupted, and a client will email me at 2:00 AM. I am watching to see if you own the recovery process, even if it is just documenting the 'post-mortem' so we do not make the same mistake twice.
  • Resistance to Buzzwords: If you tell me we need to implement AI just for the sake of it, you have failed the test. Tell me how you are going to reduce the False Positive rate in our predictive ETA engine using better signal processing. That is product management.

The Reality of B2B Complexity

Supply chain is not about clean code; it is about messy, physical reality. When a truck gets stuck at a border checkpoint, your product has to account for that. Your users are not tech-savvy product enthusiasts—they are operations managers who just want to know where their cargo is so they can get home. If you lose sight of the human at the end of the supply chain, no amount of dashboard aesthetics will save you.

By day 90, I expect you to have developed a point of view. You should be able to argue with me. You should be able to say, 'Mrinal, this roadmap item is a distraction because it doesn't solve the core data-mapping bottleneck we discussed.' That moment—when a junior PM challenges my direction based on evidence they gathered themselves—is when I know we have a long-term builder on our hands.

Stop trying to impress me with features. Start trying to understand the business. The features will follow naturally once you actually understand what you are building.

product managementstartup adviceb2b saascareer growthscheduled30
Join the Chronicle
Get essays, reflections, and builder wisdom — delivered rarely, crafted carefully.
Continue Reading