Drimva

Datadog

Staff Product Manager, Metering and Attribution

$244K–$305K

New York, New York, USA +1 · Staff · Full-time · Posted Oct 30, 2026

Location
New York, New York, USA
New York, NY, United States
Experience
8+ years of Product Management experience, or a track record showing Staff-level capabilities in related software roles.
Education
Bachelor's degree in Computer Science, Engineering, or equivalent experience.

About the job

Own product direction for Datadog’s usage metering and cost attribution platform, from telemetry events through billable output and customer-facing usage insights.

What you'll do

  • Set the multi-quarter product direction for metering, attribution, tagging, and capabilities supporting pricing and packaging.
  • Define customer-facing tagging and usage models, and ensure usage data is accurate, timely, auditable, and consistent with billing.
  • Align engineering and commercial partners, guide cross-product adoption, and build agentic capabilities that explain and help customers act on usage changes.

What they ask for

  • 8+ years of Product Management experience, or a track record showing Staff-level capabilities in related software roles, with significant ownership of complex technical products.
  • Bachelor's degree in Computer Science, Engineering, or equivalent experience.
  • Fluency in data models and pipelines, including usage aggregation, cardinality, deduplication, backfills, and processing latency.
  • Ability to influence across engineering, product, Support, Sales, and Finance, and own the quality of usage and cost data.

Nice to have

  • Experience with high-cardinality telemetry, usage-based monetization, metering, rating, or cost allocation.
  • Familiarity with billing or FinOps tools, pricing and packaging, platform adoption, or FinOps practices and specifications.

Pay

$244,000 — $305,000 USD yearly salary (base salary)

Tools

Metronome, Orb, m3ter, Amberflo, Zuora, Stripe Billing, CloudZero, Vantage

AI focus

Build agentic capabilities that detect consumption changes, explain the teams and services driving them, recommend next steps, and provide data contracts and interfaces for agents to reason about usage.

Model-written summary · the original posting is authoritative

First seen Oct 31, 2026 · Last verified Nov 5, 2026 (UTC)