Product Manager

Who We Are

Testsigma is building the world's first Quality Intelligence Platform — the infrastructure layer between every code change and every confident release. AI has collapsed how long it takes to build software. It has not changed how long it takes to trust it. That gap is the problem we exist to close — with autonomous agents that author the right tests, run them at the right time, heal them when the application changes, and signal whether a release is actually safe to ship.

Why This Role Exists

Test generation has been commoditized. The defensible moat has moved to autonomous testing: software that learns the customer's application, runs the right tests at the right time, heals itself when the application changes, and gives engineering leaders a calibrated release signal. This role owns a major surface of that product end-to-end.

What You Own

Two things above everything: what gets built, and whether customers actually use it to make a decision. Ownership areas include:

• Context and signal infrastructure — ingesting PRDs, code, analytics, and support signals into a compounding knowledge layer
• Agent surfaces — AI agents that author, plan, execute, heal, and analyze tests, with human-in-the-loop touchpoints
• Coverage, traceability, and release intelligence — requirement-to-test mapping and release-readiness signals
• SDLC and developer experience — authoring inside AI-native dev tools, Skills/MCP/CLI distribution
• Executive reporting — dashboards a VP Engineering can put in a board update
• Platform foundations — onboarding, integrations (Jira, GitHub, Confluence, Linear, Mixpanel, and more), and cross-cutting work that turns capability into a deployable product

What You'll Build in Year One

• Intake flow: new customer connects Jira, GitHub, and one analytics source in <30 min, sees first useful output in <1 week
• Coverage view an engineering manager uses during sprint reviews to make real decisions
• Release-readiness score a VP Engineering trusts enough for a board update
• Agent surfaces customers let run on production-adjacent systems — measured by autonomy rate
• Skills + MCP + CLI distribution surface with at least one AI-native dev tool as a launch partner
• Migration path from legacy suites (Selenium, Playwright, previous Testsigma TMS) without throwing away existing tests

Non-Negotiable

• 4–9 years total experience, minimum 3 years in product management. Engineer-turned-PM strongly preferred.
• Hands-on AI-native execution in the last 12 months — you've built something with Claude, Cursor, LangChain, or comparable tools and can describe specifically what broke.
• You generate your own prototypes: wireframes, clickable prototypes, or first-cut code.
• You can sit with engineers, read a PR, whiteboard a state machine, and pair-debug a flaky test.
• You've owned a 0-to-1 product to GA — a thing that didn't exist before you, that customers now use.
• You've had direct, hard customer conversations: renewals, escalations, churn calls.
• You write clearly without an LLM polishing it. The take-home will test this.
• 5 days in Koramangala office; comfortable operating across time zones for an 80%-NA customer base.
• Looking for 3–5 years of stability. Tenure pattern is checked; exits under 18 months are probed.

Nice-to-Haves

Prior testing/QA/developer tools experience; Selenium or Playwright familiarity including failure modes; knowledge graph vs. RAG architecture understanding; experience moving a product from QA-buyer to engineering-leadership positioning; LLM-as-judge or eval harness design; founder or early-stage product experience.

What Strong Looks Like

• Takes a vague directive and returns a sequenced roadmap in a week with customer interviews, a flow sketch, a draft schema, and explicit asks — not a request for more meetings.
• Runs toward where the decision is being made, not away from it.
• Ships rough things on Friday and learns on Monday rather than shipping perfect things in eight weeks.
• Treats GTM as a peer function — writes enablement, joins sales calls, brings a positioning POV with conviction.
• Has taste about what not to build and will defend killing a feature under pressure.
• Reframes the conversation to CTOs and VP Engineering on release confidence, not QA managers on test authoring speed.

What This Role Is Not

Not a PRD-writing, backlog-grooming, or strategy-deck role. Not research-to-quarterly-report. Not hybrid or remote. You execute the strategy alongside engineering, generate the first design cut, and own the full surface end-to-end.