Dishaya / Careers / Research Scientist, Knowledge Systems

Research Scientist, Knowledge Systems

Make accumulated knowledge compound for the person who owns it: research how a private Library becomes more valuable every week.

Research · 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 single work package is useful once. A Library that remembers what its owner has imported, researched, and written should make every later question easier to answer and every later answer better. Today most tools treat a user's hundredth hour of work like their first. This role exists to change that: to make sure the value of a person's accumulated work compounds, for that person alone, in ways they can actually see.

What You'll Work On

• How imported and created knowledge is represented, connected, and reused, so that one person's Library serves that person alone.
• Measurable compounding: a user's tenth report should benefit from the nine before it, and we should be able to show the difference honestly.
• Privacy-preserving design from the first sketch: one person's Library never informs anyone else's results, and we do not train on your content.
• Legibility of the Library itself: owners can see what has accumulated, why it helped, and remove any of it.

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

• Research, prototype, and ship how a private Library grows in usefulness over time, end to end.
• Define what "compounding value" means in numbers before building toward it, and defend those definitions in the open.
• Turn prototypes into shipped product; ideas here end as running software users touch, not papers in a drawer.
• Hold the privacy line in every design: reuse for the owner, never across owners, never for training.
• Write things down: findings, dead ends, decisions, and honest post-mortems.

Required Qualifications

• A background in knowledge representation, retrieval, or personal information management, from academia, industry, or serious independent work.
• You ship working prototypes; your research ends in something another person can try, not only in a write-up.
• You can design the measurement before the feature, and you distrust your own demos.
• Clear, calm written communication.

Preferred Qualifications

• You have worked on systems where value accrues to an individual user over time: notes tools, personal search, reading and reference tools, or similar.
• You have taken a research prototype into a shipped product feature and watched real users keep using it.
• You have studied or built for privacy as a design constraint, not an afterthought.

Nice To Have

• Published writing, talks, or open-source work that shows how you think.
• Experience in a research-adjacent product: search, knowledge tools, document intelligence.

What Success Looks Like

• 30 days: you understand how users' work accumulates in the Library today, you have defined the first honest measure of compounding value, and you have a working prototype in front of us.
• 90 days: a first version has shipped, and returning users measurably benefit from their accumulated Library on at least one real task. Our user base is small at this stage; the honest bar is a real effect for real people, not a big number.
• 365 days: the Library is one of the reasons people stay. The measures you defined show that a user's work keeps getting more valuable to them, users can see that for themselves inside the product, and we publish what we can say honestly about it.

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.