Dishaya / Careers / Product Manager, AI

Product Manager, AI

Decide what earns a place in a product built on restraint, where every feature must compound trust.

Product & Design · Remote-First · Founding Equity

About Dishaya

Dishaya makes research people can actually send. One question in; a client-ready report, deck, and source ledger out, with every claim checked against the exact passage it cites and labeled verified, partial, unverified, or contradicted. What fails the check is disclosed, never hidden. We are early, independent, honest about both, and building toward one ten-year outcome: "Verified by Dishaya" becoming a mark a reader trusts before they read. More in About and Principles.

Why This Role Matters

A product that promises honesty cannot ship dishonestly. Every feature that does not make a work package more trustworthy makes the whole product less so, and the pressure to add things never stops. This role is the discipline: the person who decides what earns a place, who records why, and who keeps the public story, from the board to the pricing page, matched to what the product actually does. Here, saying no is not a failure mode of the job. It is the job.

What You'll Work On

• The roadmap: what we build next, in what order, and the written reasons anyone can challenge.
• The honesty of the public board: statuses that move with real dates, never wishful ones.
• Turning user evidence, from feedback, support, and usage, into shipped decisions with a traceable why.
• Pricing page truthfulness: what a plan promises is exactly what a user gets, checked every time either side changes.

We describe work by the outcomes you will own rather than by our internal systems; you will see everything on the inside from day one.

Responsibilities

• Own the roadmap end to end: gather evidence, write the decision, defend it, and revisit it when the evidence changes.
• Say no clearly and in writing, with reasons a user could read without flinching.
• Keep the public board a truthful record of what is planned, in progress, shipped, and declined.
• Audit the pricing page and product copy against shipped behavior; discrepancies are your bugs.
• Write decision documents that hold up months later, including the ones about things we killed.

Required Qualifications

• You have been the product manager on a technical product and can explain the hardest tradeoff you made and what it cost.
• You write decision documents that hold up: someone who disagreed at the time can reread one and still see the reasoning.
• Evidence over enthusiasm comes naturally to you; you have changed your mind in public because the data said so.
• Clear, calm written communication.

Preferred Qualifications

• You have killed a feature you personally liked, recorded why, and kept it killed when it came back around.
• Experience in a small company where product management also meant support, research, and copy.
• You have owned a pricing or packaging decision and lived with its consequences.

Nice To Have

• Public writing about product decisions, especially the ones that did not work.
• Experience in a research-adjacent product: search, knowledge tools, document intelligence.

What Success Looks Like

• 30 days: the public board reflects reality, every status has a real date behind it, and you have written one decision document that changed what we build next.
• 90 days: the roadmap exists in writing with reasons attached, at least one thing has been declined with its reasoning recorded, and one shipped change traces directly to user evidence you gathered.
• 365 days: the roadmap has a track record: shipped things get used, killed things stayed killed, the pricing page has never promised something the product did not do, and users cite the board as a reason they trust us.

Team Principles

• Honesty over fluency, in the product and in code review.
• Delete before you add; every abstraction earns its keep.
• Evidence over enthusiasm; direction comes from users.
• Small, senior, trusted; you own outcomes, not tickets.

Benefits

• Founding-level equity; early means it matters.
• Remote-first, judgment over time zones.
• The hardware and tools you need, without a procurement dance.
• Direct access to how the company runs: numbers, decisions, reasons.

Interview Process

1. Intro conversation (30 minutes): the honest state of the company, and what you want to build.
2. Craft deep-dive: real decisions inside work you shipped.
3. Paid working session: scoped, close to the real job, never spec work we ship.
4. References and a clear written offer, fast.

Equal Opportunity

Dishaya is an equal opportunity employer. We evaluate candidates on craft, judgment, and alignment with how we work, never on race, color, religion, gender, gender identity or expression, sexual orientation, national origin, disability, age, or veteran status.