Senior Product Manager

TaskRay is a leader in post-sale work management in the Salesforce ecosystem, focused on providing a flawless customer experience. The Senior Product Manager will own the product area related to AI-driven project management, working closely with Sales, Customer Success, and Engineering to define and deliver innovative solutions.

Responsibilities:

• Prototype to test ideas, and write PRDs to get everyone aligned. You need both
• Write PRDs that start from goals and the jobs customers are trying to get done, then work down to journeys, requirements, and acceptance criteria clear enough to build from and defend at executive review
• Ship rough versions to opted-in customers early, watch how they actually use them, and adjust. Match polish to how proven the bet is
• Own the problem, the priority, and how success is measured. Leave the how to engineering, and weigh in when they raise tradeoffs
• Define agents, skills, and workflows that customers own and can extend, built for a product where people and agents are both users
• Find out which AI workflows customers will pay for through design-partner work and tested bets. Let pricing and packaging follow demand you have proven, not lead it
• Design for what happens when things go wrong, not only the happy path: audit trails, permissions, rollback, evaluation loops. Our agents run inside customers' Salesforce orgs, so a misbehaving agent breaks trust. How the system fails matters
• Use AI tools in your own work (discovery, PRDs, prototypes, analysis) and coach other PMs and product owners on the craft
• Run real discovery. Frame the questions worth answering, design tests that give clear answers, and spend meaningful time with customers and prospects learning what is forcing their hand and where today's options fall short
• Get from a conversation to something you can demo in days. A working prototype is often the fastest way to prove demand, and often the thing you pre-sell
• Map the whole buying group, not just the user: the economic buyer, the integration owner, procurement, and whatever actually decides adoption
• Run the design-partner motion for your area. Pre-sell a focused version of the vision to a handful of prospects before the product fully exists, and set up each engagement so what you learn turns into product you can repeat
• Tell real demand from polite interest. Treat complaints, requests, and excitement as things to investigate, not proof anyone will buy
• Share commercial strategy with sales for your area. Get into deals and renewals early instead of waiting for an invite, point conversations toward things we can build and sell, and earn your sales and CS partners' trust
• Bring what you hear in the field into pricing, packaging, and positioning
• Feed deal and renewal lessons back into the roadmap, so what the team builds ties to real pipeline, commitments, or expansion
• Work with Customer Success on rollout, adoption, and what customers hear before a change reaches their orgs
• Treat engineering as an equal partner. Agree on the problem and the definition of success up front, then let them own how it gets built
• When an area spans internal engineering and outside delivery partners, keep the scope lines clear and flag changes before they slip by
• After launch, measure adoption against the PRD's success criteria and carry what you learn into the next round

Requirements:

• 3+ years in product management for B2B or enterprise SaaS, preferably owning an area from discovery through adoption
• Track record of decisions that moved the business, with specifics: named accounts, revenue saved or won, deals turned around
• Hands-on prototype building with tools like Claude, Lovable, or Cursor. Building, not evaluating. You have made something a customer saw or a team used
• Real fluency with AI systems: prompt design, an honest read on what LLMs cannot do, experience building evals, and judgment about where a human belongs in an agent's loop
• Strong PRD writing: requirements a team can build from without constant back-and-forth, organized around user goals rather than a preferred solution
• Commercial range: comfortable on discovery calls, in sales conversations, pitching a vision to enterprise buyers before the product exists, and in a QBR
• You have worked where product owns the what and why and engineering owns the how, and you made that line clearer, not blurrier
• You have designed agent or conversational experiences and know a good one from a bad one, or worked with agent frameworks, MCP, and products used by machines as much as people
• Forward-deployed, solutions, implementation, or professional-services background. Time spent building in customer environments counts for a lot here
• Salesforce experience: managed packages, AppExchange, or building within platform limits
• Background in onboarding, project management, PSA, or post-sale workflow products, including early-access or design-partner programs