ProductJobs.io
← Back to all jobs

Job Description

Sycamore is building AI-powered products that move from customer conversations to usable software quickly. As a Product Manager in the San Francisco Bay Area, you will own the product loop for a single enterprise industry track, partnering closely with operators and a Deployment Strategist to turn messy requests into clear, reusable industry product shipped on Sycamore Forge.

You will work with real enterprise users, connect apps to trusted systems within their permissions, and iterate weekly or faster until the workflow sticks. You will also separate account-specific needs from what should become reusable across the industry, so Engineering can productize the patterns you validate in the field.

What you’ll do

  • Sit with operators and leaders in your industry (often with a Deployment Strategist) to learn how the work runs and what “good” looks like for the product.
  • Translate ambiguous requests into clear product direction, including who it is for, what first version to build, and what not to build.
  • Ship working apps and agents in Sycamore Forge in days, then place them in front of real users and iterate weekly or faster.
  • Connect apps to customers’ existing systems, operating within their permissions.
  • Iterate with users until the workflow sticks; Deployment Strategists own go-live dates, resourcing, and the commercial engagement.
  • Separate account-specific work from reusable industry product, documenting what Engineering needs to put it on the platform.
  • Maintain a simple industry product backlog, using accounts as evidence rather than engagements you own.
  • Demo what you built to customer executives.
  • Track product usage and whether the workflow changed; deal success criteria and the business case belong to the Deployment Strategist.

What you’ll bring

  • 5+ years in product management, or equivalent experience as a founder, early employee, solutions engineer, or forward deployed engineer who moved into product.
  • Industry experience in financial services, telecommunications, or data centers.
  • Evidence that you have shipped working software, such as links, repos, demos, or tools people used.
  • Strong discovery habits, including frequent customer conversations that turn input into product priorities.
  • AI-native execution, using tools such as Claude Code, Cursor, or Codex daily, and moving from a customer call to a working prototype in a day or two.
  • Enough technical depth to ship in Sycamore Forge yourself and identify where agents break, including bad permissions, weak integrations, or untrustworthy outputs in production.
  • Product judgment to select a useful first version and hold scope when a request would undermine the outcome.
  • Comfort with enterprise customers, including discovery, pushback, and briefing operators and executives.
  • Clear writing that turns messy conversations into a crisp problem statement and a first version worth building.
  • Comfort with startup ambiguity, broad ownership, and regular customer travel.

Technologies: Sycamore Forge, Claude Code, Cursor, Codex

Industry tracks

  • Financial services: banks, capital markets, lenders, fintechs. Potential areas include onboarding and review, alert triage, credit memos, and operations exception queues, plus governance workflows a firm can explain to a regulator.
  • Telecommunications and communications: carriers, cloud communications, network and service assurance, and media. Potential areas include order-to-activation, network incident and ticket triage, customer care and billing disputes, and partner operations.
  • Data centers: owners, developers, and operators building capacity with small central teams and many partners. Potential areas include site readiness (land, power, permits, interconnection), procurement and long-lead equipment, construction milestones, and commitments to boards, lenders, and partners. Focus is on the business of the data center company, not control systems.

Compensation and equity

  • Competitive cash compensation and meaningful equity.

Nice to have

  • LLM apps in production: prompts, tool use, MCP, and evaluations.
  • Experience building for regulated or security-conscious enterprises.

Interview process

  • 30-minute introductory conversation.
  • 30-minute culture fit interview.
  • Take-home app building assignment with a 30-minute presentation.
  • 30-minute systems design interview.

This role is not a Deployment Strategist position, a domain-expert-only specs role, a roadmap-only ticketing role, pre-sales, or customer success that collects feedback without turning it into product. You own the product and what becomes reusable across the industry.

Similar Jobs