Farseer is a fast-growing startup building an enterprise software stack from first principles. We aim to become the underlying database and operating system for every business-critical app, from financial planning and analytics to accounting and beyond. Farseer empowers humans to build enterprise software with the help of AI.

Over the next decade, we will rebuild the enterprise nervous system. We are starting with finance, a real-time collaborative planning and reporting platform that turns finance teams into proactive strategists. Once that foundation is solid, the same AI-native core will extend across the operational stack, reporting, supply chain management, manufacturing, procurement, revenue ops, and more.

Our mission is to build enterprise software that people enjoy using. No user-hostile screens. No bloated workflows. Just fast, intuitive tools that help teams solve real business problems.

What you'll do

Core Product builds the product itself — everything users see, touch, and rely on every day.

That includes sheets, variables, dimensions, scenarios, modeling logic, planning workflows, collaboration, dashboards, and the backend systems that make all of it feel fast, reliable, and coherent.

The technical surface area is broad, and the constraints are real: models with millions of cells, real-time recalculation across deep dependency graphs, multi-user editing on the same surface, enterprise-grade permissions and audit logs — all fast enough that finance teams choose to work in Farseer instead of going back to Excel.

As a Senior Backend Engineer on Core Product, you'll work on the systems behind that. You'd be joining a small team of senior engineers across backend and frontend.

You'll:

• Design and build backend systems for the modeling layer — sheets, variables, dimensions, scenarios, formulas

• Build the planning workflows customers run their business on — assignments, approvals, locks, scheduled processes

• Work on collaboration infrastructure: audit logs, comments, permissions, multi-user editing

• Make core product interactions fast, reliable, and predictable — especially when users work with large models and complex dependencies

• Design APIs that work cleanly for the frontend, for integrations, and for customer-built apps

• Think through scale, permissions, edge cases, and migrations as part of how you ship — not after

And one more thing — Core Product Engineers who develop broad product judgment here tend to go on to lead new specialized teams as the company grows.

What we're looking for

You don't need to know our stack by heart. You need to think like a senior engineer — which means clear judgment, real ownership, and the ability to make sound calls when the right answer isn't obvious.

You are a good fit if you:

• Have shipped production backend systems at a meaningful scale. Stack doesn't matter as much as judgment — proficient in at least one modern language, ready to pick up whatever the job needs

• Can design systems that handle real complexity: permissions, multi-tenancy, audit, concurrency, performance under load

• Know how to make tradeoffs between scope, complexity, and speed without being told

• Are comfortable working in an interconnected codebase where the right move is sometimes to delete or unify, not add

• Use AI tools to move faster — code generation, debugging, prototyping

Nice to have

• Experience with planning, modeling, or analytical products — anything where the data model has real structural depth

• Experience working with C++ or other systems-level code through bindings

• Familiarity with FP&A, accounting, or other finance workflows — not required, but it shortens the ramp

• Experience in environments where product surface area is large relative to team size, and reducing surface area is part of the job

A note about the role

Farseer is an enterprise product with real customers, real complexity, and a small senior team building it. The standard inside the team is clear thinking, real ownership of outcomes, and the agency to push work forward without waiting to be told. PR merged isn't done; users getting value is done.

If that's how you want to work, hit apply.