Frontend Software Engineer

The Role
What You’ll Own
You’ll build the analyst-facing surface of Kepler’s AI research platform: the product financial professionals rely on for million-dollar decisions. The platform produces cited, verifiable data; you’ll package it into the workflows analysts run every day (researching a company, pulling comps, extracting financials into a model) and build the verification interfaces that let them trace any number back to its source.

This role is for engineers who want to build foundational technology at the intersection of AI and finance, where your code directly impacts how clients make critical business decisions.

In the first few weeks you might:

Ship the UI for a source explorer that lets users trace any value back to its exact origin in the original document.
Build the interface that shows an agent’s work in real time: which sources it’s reading, what it’s computing, and where each value came from.
Make our financial statement views feel like a native spreadsheet: fast rendering of thousands of cells, keyboard navigation, every cell one click from its source.
Rework how long-running research queries stream into the workspace, so analysts see cited results as they arrive instead of waiting on a spinner.
In the longer term, you’ll be given ownership of whole functional areas, from extending our platform to a new industry to leading new architecture as our infrastructure scales.

You’ll consistently own features end-to-end. In a small team, there’s nobody to hand things off to.

How We Work
We’re a close team, working together in an office in New York. We use AI tools heavily – Cursor, Claude Code, whatever makes us faster. Fluency is assumed. Our users are analysts at firms where a wrong number costs real money. The feedback loop on what you ship is hours, not quarters.

The pace is startup-fast but the engineering bar is high. We care about getting things right, not just getting things out. If you’ve worked somewhere that moves fast but ships broken software, this is different. If you’ve worked somewhere that’s rigorous but slow, this is also different.

The team has strong backgrounds and low ego. We expect everyone to roll up their sleeves and handle the unglamorous problems: the weird regressions, the subtle bugs, the last minute debugging session before a demo. We move as a team, not as a collection of individuals.

Who You Are
You’ve shipped production systems and you care about whether they’re correct – not just whether they work on the happy path. You think about failure modes before someone asks you to.

You’re comfortable in a codebase you didn’t write, moving between a component library and the API it calls in the same day. You’re drawn to early-stage not for the title but because you want your work visible in the product, not abstracted behind three layers of management.

From the technical side:

5+ years building production software. No upper limit, comp scales with experience.
Expert in TypeScript/React. Deep enough in the browser to know why an interface feels slow and how to fix it.
You’ve built data-dense interfaces – tables, charts, long documents, live-updating views – and kept them fast.
You have product taste: you sweat interaction details, and you can take a rough mock, or no mock at all, to a polished interface.
You’re a quick learner and are as comfortable in a codebase you wrote as one you’re reading for the first time.
From the personal side:

You care what the analyst does with what you shipped, not whether the code was clever.
You’d rather fix something than file a ticket about it.
You’ll tell someone their design has a flaw before the PR goes in, not after.
You communicate before it’s a problem, and when a teammate needs something from you, they don’t have to ask twice.
You know what it feels like when the plan changes twice in a day and the work still has to ship.