Product Manager

Responsibilities:

• Decide what gets built. Talk to users every week. Sit on support and sales calls. Read the data yourself. Then write down what we're building, what we're not, and why. You defend the cuts.
• Ship it. Write the spec, cut the scope, work daily with engineering, design and QA, and personally unblock the ugly parts. We ship in small pieces, often.
• Own a number. Every area you run carries a metric. You set the target, report on it, and say out loud when you miss.
• Get into the technical detail. You'll read API docs, sketch data models, and argue about latency, cost and failure modes with engineers. You won't write production code. You will understand what you're asking for and what it costs.
• Turn mess into a plan. Most work arrives as a vague complaint or a half-formed idea. Your job is to convert it into a clear problem statement, a decision, and a plan people can execute.
• Kill things. Retire features that don't earn their maintenance cost. This is part of the job, not a failure.

Requirements:

• You've owned a product surface end to end, from problem to shipped to measured. Roughly 2+ years, but we care about what you shipped, not the count.
• You can name a feature you shipped and the number it moved. You can also name one you killed and why.
• You've done discovery yourself. Interviews you ran, not a research deck someone handed you.
• You can hold your own in a technical conversation and read an API spec without help.
• You write clearly. Short docs, real decisions, no hedging. We'll ask for a sample.

Bonus, not required:

• You've shipped something with LLMs or ML in the loop and dealt with the real problems: evals, non-deterministic output, latency, and unit cost.
• Background in engineering, design, or data.