Dishaya / Careers / Platform & Infrastructure Engineer

Platform & Infrastructure Engineer

Keep a trust product fast, cheap, and boringly reliable: the unglamorous engineering that makes it-just-works true, from deploys that are non-events to backups that provably restore.

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

A product that asks people to trust its answers cannot be flaky about anything else. Downtime, a slow report, a lost work package, or a leaked secret would each undermine the promise faster than any competitor could. This role owns the layer beneath the promise: the product stays up, stays fast, stays affordable, and never loses a user's work. When infrastructure is boring, trust compounds quietly. You are the person who keeps it boring.

What You'll Work On

• Uptime and latency users never have to think about: the product is simply there, and it is fast.
• Deploy safety: shipping many times a week without users noticing anything except improvements, with rollback anyone on the team can run.
• Backups and restore drills: not backups that exist, backups that provably restore, proven on a schedule.
• Cost per user: measuring it honestly and bending it down while usage grows, because affordability is part of reaching more people.
• Security hardening in the terms the industry already agrees on: least privilege, secrets hygiene, fail-closed defaults.

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 production end to end: provisioning, monitoring, alerting, and the response when something breaks at 3am.
• Build and maintain CI/CD with checks that catch problems before users do, and rollbacks that take minutes, not meetings.
• Run the backup and restore drill quarterly, fix what it exposes, and keep the runbooks current enough that anyone could follow them.
• Measure infrastructure cost per user, own the number, and drive it down with engineering rather than wishful thinking.
• Harden the platform continuously: least privilege everywhere, secrets that rotate and never touch code, defaults that fail closed.
• Write things down: runbooks, decisions, and honest post-mortems.

Required Qualifications

• Deep production Linux experience: you have debugged a misbehaving server from first principles, not just restarted it.
• Solid networking fundamentals: DNS, TLS, firewalls, load balancing, and the failure modes between them.
• You have built or owned CI/CD for a real product and can explain the safety checks you added and why.
• Observability that works: metrics, logs, and alerts that wake the right person for the right reasons, and stay quiet otherwise.
• You have been on call for something that mattered, and you can talk honestly about a night that went badly.

Preferred Qualifications

• You have been the entire infrastructure function at a small company and kept it reliable anyway.
• You have cut real infrastructure cost with real numbers and can walk through how.
• Production database operations: backups, restores, migrations, and the discipline to test all three.

Nice To Have

• You have handled a security incident or led a hardening effort, and wrote up what changed after.
• Infrastructure as code as a habit, not an aspiration.
• Public runbooks, post-mortems, or writing that shows how you think about reliability.

What Success Looks Like

• 30 days: you can deploy safely, you have mapped everything we run and written down the risks in plain language, monitoring tells us about problems before users do, and you have fixed the scariest thing on your own list.
• 90 days: deploys are non-events with a rollback anyone can run, the first restore drill has passed and the next one is on the calendar, and cost per user is measured with a credible plan to lower it.
• 365 days: every quarterly restore drill has passed, cost per user is lower than the day you started while usage is higher, and the platform has absorbed growth and at least one bad day without users noticing, with the post-mortems written to prove 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.