Dishaya / Careers / Founding Product Designer

Founding Product Designer

Make evidence calm, legible, and beautiful: design the surfaces where trust is won or lost.

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

The product's promise only counts if a reader can feel it. A verified claim that reads as clutter is not trusted; a disclosed failure that looks like an apology is not respected. Design is where our honesty becomes legible. And because the reports and decks leave the product and go out under the user's own name, your work is judged twice: once by our users, and again by the clients they send it to. You own that second impression too.

What You'll Work On

• The design system and its discipline: one visual language across the product, the exports, and the public site, held steady as new features arrive.
• How verdicts, sources, and costs read at a glance: a tired reader should know what is verified, what failed the check, and what a work package will cost without hunting for it.
• The first-run experience: the path from a first messy question to a first finished work package sitting in the Library, designed so it needs no manual.
• Export design: the reports and decks people send under their own name, which have to look like the user's best work, not like our branding exercise.

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 design system end to end: type, color, spacing, components, motion, and the discipline that keeps them coherent.
• Design the honest states first; failure, empty, loading, and partial results get the same craft as the happy path, because that is where trust is actually decided.
• Turn dense material, claims, sources, and the Confidence Ledger, into layouts that read at a glance without dumbing anything down.
• Work directly with engineering on the built result: review shipped screens against the intent, and care about the last five percent.
• Write things down: decisions, reasons, and honest critiques of your own work.

Required Qualifications

• You have shipped product design where you owned the system, not just the screens, and you can show how it held up as the product grew.
• Strong typography: hierarchy, rhythm, and restraint in dense, text-heavy interfaces.
• You design honest states, failure, empty, and loading, as deliberately as happy paths, and you can show examples.
• Clear, calm written communication.

Preferred Qualifications

• You have designed artifacts that leave the product: documents, exports, or anything printed, forwarded, or presented under someone else's name.
• You are comfortable enough in a codebase to adjust type, spacing, and states yourself, or to review the built result with precision.
• You have been the only designer somewhere and kept the quality bar up without a review chain behind you.

Nice To Have

• Public work that shows how you think: case studies, writing, or a design system you can walk through.
• Experience in research, reading, or knowledge tools, anywhere trust and density collide on one screen.

What Success Looks Like

• 30 days: you have audited the current design system, named where the drift lives, shipped fixes to production, and the honest states no longer look like afterthoughts.
• 90 days: the first-run experience carries a new user from first question to first work package without a manual, and the feedback we collect starts using words like calm and trustworthy.
• 365 days: the design system has absorbed a year of new features without drift, exports look like the user's best work by default, and users describe the product as calm and trustworthy without being prompted.

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.