Senior Technical Product Manager

Single Grain, LLC; Los Angeles, Northern (CA, KY); Hybrid; USD 120,000 - 150,000; Full time

Benefits offered by this job

Medical, dental, and vision

Life insurance

401(k) with match

Unlimited PTO

Monthly UberEats

MacBook

Home-office stipend

Remote-friendly

Job summary

Single Grain, LLC seeks a high-agency product leader responsible for defining metrics, guiding what to build, and why for Single Brain and the API Gateway. You will partner with a ~6-person engineering team, owning product judgment, customer discovery, and analytics.

This role emphasizes outcomes, not people management, with strong emphasis on AI-assisted product work. You will report to the CTO and own the product roadmap, instrumentation, and measurement plans to drive measurable outcomes and

Qualifications

• Experience owning a technical software product (APIs, integrations, auth, data fluency).
• Demonstrated sprint leadership and prioritization with engineering teams.
• Strong product analytics ownership (PostHog, Amplitude, Mixpanel, or similar).
• Advanced daily AI workflows for product work.
• High-agency ownership: you set roadmap direction; not just admin.

Responsibilities

• Identify high-leverage metrics for Single Brain and API Gateway.
• Diagnose blockers and define clear hypotheses for each initiative.
• Lead weekly sprint kickoffs ensuring actionable outcomes.
• Own customer discovery and differentiate high-leverage needs.
• Ensure instrumentation and measurement plans accompany launches.
• Prioritize roadmap and protect team from low-impact work.

Job description

Reports to: CTO
Type: High-agency individual contributor
Products: Single Brain + API Gateway
Location: Full-time, remote (Los Angeles a plus, not required)
Comp: $120,000–$150,000 USD / year

One-liner

Own what gets built and why across Single Brain and API Gateway — turn build → build → build into build → measure → iterate.

About the role

Single Grain combines marketing services, software, and AI. This seat owns product judgment for Single Brain and the API Gateway: which metrics matter, what is blocking them, and what engineering should build next.

Engineering owns how we build. You own what we build and why.

You report to the CTO. You work daily with a ~6-person engineering team. You do not manage that team as a people manager; you create clarity so their effort lands on the highest-leverage outcomes.

You should be an advanced AI user. Use AI for research, interview synthesis, analytics, specs, prototypes, experiment design, and competitive work so your product decisions get faster and better.

What you will own

• Identify the highest-leverage product metrics across Single Brain and API Gateway (activation, usage, retention, expansion, revenue, time-to-value, Gateway/integration adoption).

• Diagnose what is limiting those metrics.

• Decide what engineering should build next, with clear hypotheses and success criteria.

• Run strong weekly sprint kickoffs so the team leaves knowing: what metric are we moving, what are we doing to move it, and how will we know it worked.

• Own customer discovery — talk to customers often; separate loud requests from high-leverage opportunities.

• Own product analytics and instrumentation quality; no major initiative ships without a measurement plan.

• Review launches against real results and choose iterate, expand, revert, or move on.

• Keep the integration / Gateway roadmap intentionally prioritized.

• Protect the team from low-impact or poorly defined work.

What success looks like

• By day 30: deep product understanding; customer discovery underway; core journeys/funnels mapped; analytics audited; clear view of which metrics matter and where the biggest opportunities are.

• By day 60: you own weekly sprint kickoffs; major initiatives have metrics and measurement plans; core funnels instrumented and visible.

• By day 90: prioritized roadmap tied to measurable outcomes; multiple complete build → measure → iterate cycles; measurable improvement in at least one meaningful product metric. Failure = features still shipping without hypotheses, instrumentation, or post-launch learning.

• By 6–12 months: durable product OS (Metric → Diagnosis → Hypothesis → Build → Measure → Learn → Iterate); customer discovery and post-launch measurement are standard; CTO is no longer the primary person deciding what engineering builds next; key product/business metrics improved materially.

Evidence we want to see

• Experience owning a technical software product (APIs, integrations, auth, data fluency).

• Metrics you personally owned and improved — with diagnosis, not feature lists.

• Sprint leadership / prioritization with engineering teams.

• Product analytics and instrumentation ownership (PostHog, Amplitude, Mixpanel, or similar).

• Advanced daily AI workflows for product work.

• High-agency ownership: you set roadmap direction; you are not a conduit or Jira admin.

• Ideal: early-stage / growth-stage; developer tools, API, infrastructure, or AI products.

What this role is not

Not a project manager, not a backlog clerk, not “collect feature requests,” not “feature shipped = success,” not waiting for the CTO to dictate the roadmap.

How the process works

Application and evidence review → our standard six-question AI prescreen for selected candidates → live discussion / working session (metric → diagnose → propose build → mock sprint kickoff → measurement) → paid exercise if substantial work is required → references.

Benefits

Medical, dental, and vision; life insurance; 401(k) with 4% match; unlimited PTO; monthly UberEats; MacBook; home-office stipend/setup. Subject to plan terms and eligibility.