Dishaya / Careers / Founding Full-Stack Engineer

Founding Full-Stack Engineer

Ship the product surface people trust with their work: the app where research runs, reports render, decks export, and every interaction stays calm and fast.

Engineering · 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

People come to Dishaya with work that carries their name: a report for a client, a deck for a boardroom, a due date that does not move. The app is where that trust is either earned or lost. A slow screen, a broken export, or a failure that hides behind a spinner costs more than a bug; it costs the user's confidence in everything the product claims. This role owns that surface, end to end, and makes it worthy of what people put on it.

What You'll Work On

• Complete product features, from database to pixel: the screens where research runs, reports render, decks export, and a user's Library grows week over week.
• The export quality bar: documents, decks, and spreadsheets that people actually send, formatted right the first time, on every machine that opens them.
• Performance and reliability of the app: fast on real hardware, steady under real load, and measurably better every month.
• Honest states everywhere: loading, empty, and failure states that tell the user the truth about what is happening and what to do next.

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

• Design, build, ship, and operate product features end to end: data model, API, interface, and the operational reality after launch.
• Own the moments users feel most: the first run, a work package in progress, an export leaving for a client on a deadline.
• Hold the export quality bar; a deck or report that embarrasses a user in front of their client is treated as a production incident.
• Treat performance as a feature with a budget: measure it, defend it, and improve it on the paths users actually take.
• Make every failure visible and recoverable; no silent failures, no fake success states, anywhere.
• Write things down: decisions, reasons, and honest post-mortems.

Required Qualifications

• Senior TypeScript and React, plus real backend ownership: APIs, data models, migrations, background work, and production issues you carried to resolution yourself.
• Taste. You notice the misaligned pixel, the jarring transition, the spinner that lies, and you cannot leave them alone.
• You have shipped products users paid for, and you can walk through what broke, what you fixed, and what you learned.
• Clear, calm written communication.

Preferred Qualifications

• You have built interfaces that render complex documents or long-running work in progress, and kept them honest while they did it.
• You have taken a slow app and made it fast, and can explain how you measured before and after.
• You have been the most senior product engineer on something and kept it boring and reliable.

Nice To Have

• A portfolio of shipped interfaces you are proud of, or writing about how you make product decisions.
• Experience in a research-adjacent or document-heavy product: knowledge tools, reporting, editors, exports.

What Success Looks Like

• 30 days: you have shipped to production, you own at least one surface users touch every day, and you have replaced one dishonest state (a spinner that lies, a failure that hides) with a true one.
• 90 days: features users voted for on the board have shipped and held without regression, the paths that matter are measurably faster, and exports leave in a form people send without apology.
• 365 days: the app itself is a reason users stay: calm, fast, dependable. Zero silent failures is a standard the codebase enforces rather than a goal on a slide, and users say the product feels solid without being asked.

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.