← Jobs

Founding Product Engineer

We’re hiring a Founding Product Engineer to build the core of Thereby with the founders: the systems that turn a firm’s scattered evidence into records, chronologies and demands a lawyer can sign.

Reports to
The founders, directly
Location
Austin, TX or remote
Type
Full-time
Compensation
Salary and equity
Status
Open to the right person. We hire when the fit is right, not on a calendar.

Why this role exists

Forward deployed engineers build Thereby around one firm. You build what every firm gets.

We believe the line between product engineering and design is gone. The person who builds the screen should decide how it works, and the person who designs it should be able to ship it. You’ll do both.

The problems are real: thousands of pages of scanned records, facts that must be cited to the page, work where a mistake costs a client money, and a product that has to run in our cloud and on a firm’s own hardware.

The work

  • Own a product area end to end: record retrieval, medical chronologies, demand letters or Case Chat.
  • Build document pipelines that survive scanned faxes and productions thousands of pages long.
  • Make every output traceable to its source page, and measurably right.
  • Build for lawyers who check everything: review, approval and audit as first-class features.
  • Talk to users, ship often, and decide what not to build.

How we think

  • Simple beats clever. If a rule does the job, don’t use a model. If a model does the job, don’t build an agent.
  • Design is engineering. How it looks, how it reads and how it behaves are one decision, made by the person who ships it.
  • Right before fast. A fast wrong answer in legal work is expensive.
  • Leverage is the job. A few engineers with the right tools should do the work of a much larger team.

Who this is for

You’ve shipped product people relied on, ideally at an early-stage company. Any background, any path; no particular degree or title required. Former founders and early engineers tend to do especially well.

  • You own outcomes, not tickets.
  • You can trace a system from input to output and explain where it went wrong.
  • You build an eval before you trust an output.
  • You care about the person using it, and you go and watch them use it.
  • You have taste. You can take a screen from rough idea to something a lawyer trusts at a glance, in code.

Familiar ground

You don’t need all of it. You should have shipped with a good part of it, and equivalent tools count.

  • TypeScript
  • React
  • Figma
  • Design systems
  • Python
  • Postgres
  • LLM APIs
  • Context windows
  • Prompt caching
  • Structured outputs
  • Tool use / MCP
  • Agents
  • Evals
  • Embeddings / RAG
  • Rerankers
  • OCR and document AI
  • Background jobs and queues
  • Observability
  • Claude Code / Cursor

Applying

Send a thoughtful cold introduction to [email protected].

Show us something you built that people depend on, and tell us about a time you worked where product, design and engineering meet: what you owned, the hardest decision you made, how you knew it was right, and what you’d change.