Founding Engineer

Job Description

About Inlet

\n

\n

Inlet is building automatic time-tracking software for legal professionals.

\n

\n

Lawyers and paralegals track their work in six-minute increments. That means either constantly stopping to record work or reconstructing it later from emails, documents, and memory. It is tedious and impossible to do perfectly. When billable work slips through the cracks, a lawyer can lose thousands of dollars in revenue every month.

\n

\n

Inlet captures that work automatically. We help legal professionals spend less time creating time entries and recover more of the work they have already done. And it works: our revenue is doubling every few months and we have strong product market fit.

\n

\n

The role

\n

\n

You will be our founding engineer. You'll report directly to our CTO and work closely with both founders on what we build, how we build it, and where the product goes next.

\n

\n

Automatic timekeeping is a challenging thing to get right. We receive streams of various types of user activity and must determine what work happened, which legal matter it belongs to, how it should be described, and how much time should be recorded. We must do this reliably and as fast as possible, reasoning over noisy signals and producing results legal professionals can trust.

\n

\n

The kinds of problems you will help us tackle:

\n

\n

\n
• Make our processing faster. Help architect and optimize the low-latency systems that turn activity streams into time entries.
\n
• Improve our modeling. Build evaluation pipelines, identify where accuracy breaks down, run experiments, and make improvements across our multi-stage modeling pipeline.
\n
• Make reviewing time effortless. Talk with attorneys, paralegals, and customer success, then improve the product and UX so users can review their time with fewer clicks and corrections.
\n
• Build out our development pipeline. Help us automate parts of our engineering process so we can continue to speed up how we ship.
\n

\n

\n

Who you are

\n

\n

You have built real software. You can investigate problems without a playbook and make good tradeoffs when speed, quality, and complexity pull in different directions.

\n

\n

You love building great products. You want to understand why a customer is struggling before deciding what to build, and you will cross boundaries between backend systems, models, data, and interface design to get the result right.

\n

\n

You learn quickly and take ownership. When something you built reaches production, you still consider it yours.

\n

\n

Prior experience in legal technology is not required. Neither is prior experience with our exact stack. We want someone who can get deep in unfamiliar territory and emerge with a working, well-reasoned solution.

\n

\n

Why join Inlet?

\n

\n

You'll be joining after the product has demonstrated real demand but early enough to shape how it is built. The feedback loop is clear: make Inlet more enjoyable to use, and more legal professionals will love and use it! We’ve found an incredibly powerful wedge on our path to transforming even more aspects of legal practice.

\n

\n

You'll have direct access to technical founders, meaningful influence on architecture and product decisions, and the chance to define the engineering culture rather than inherit it.

\n

\n

If it sounds fun to build a challenging product that automates something people hate doing, we would love to hear from you!