Product Manager

Write the acceptance criteria for every epic. What "done" looks like is your call, anchored to the product note.

Define release readiness: what must be true before a release ships. Test coverage, behaviour-equivalence verification, governance hooks, customer-facing documentation.

Sign off on epics before they go to release. No epic ships without your acceptance.

Make day-to-day prioritization calls within a release: which bug first, which epic blocks which, what gets cut when the math doesn't work.

Escalate to founders only when a decision crosses the strategic line. Inside that line, you decide.

Review the product every single day. Use it like a customer would. Find the issues before customers do, and route them to the right engineer.

Maintain a running quality bar that the team can point at. "Would I demo this today?" is the test.

Own the scrum calls: planning, daily stand-ups, retrospectives.

Own the release process end-to-end: cut, validate, ship, post-release review.

Coordinate with DevOps and engineering on the deployment pipeline. Keep it clean and repeatable.

The founders set the release. You ship it.

Surface blockers and risks with enough lead time to mitigate. No surprises on release day.

After every release: what shipped, what landed, what didn't, what needs iteration. Write the retro, share it, and apply the lessons.

5 to 8 years in product management at a B2B SaaS or developer tools company.

Owned the delivery of a product surface end-to-end at least once: scope to ship to post-release iteration.

Strong written communication. Acceptance criteria, release plans, scrum notes, decision docs, retros. The PM's job is partly written; the writing must be good.

Came up through engineering. Built and shipped production software for at least 3 years before moving into product.

Read Python comfortably. Read other common languages (Java, TypeScript, SQL) well enough to follow a code review or a design doc.

Comfortable in design reviews for distributed systems, agent orchestration, or data pipelines. Has an opinion, not just questions.

Treats commitments as commitments. If a release date is on the calendar, you defend it or renegotiate it openly. You do not silently slip.

Runs scrum cleanly. No theater. The ceremonies exist to remove blockers, not to fill time.

Treats acceptance criteria, release plans, and retros as first-class deliverables, not paperwork.

Comfortable in a founder-led product environment where strategy comes from above and you own execution.

Bias to action. Decisions made and revised beat decisions deferred.

Strong English communication, written and spoken. You'll be in product reviews and customer-impacting release discussions.

Available to work with US business hours from India.

Enterprise modernization domain (mainframe, SAP, Oracle, large Java / .NET estates) or AI/agent orchestration product experience.

Familiarity with AWS production environments (EKS, ECS, Bedrock, DynamoDB).

Exposure to regulated industries (BFSI, healthcare, insurance) and the release discipline they require.

Prior experience as the only or first PM at a company.