Software Engineer, Data Platform

WHY NUMERIC?

Every business relies on accounting. Yet most software in the space was built in the early 2000s — clunky, slow, and far behind the curve on AI. Today, accountants are facing a growing, unsolved data problem https://numeric.substack.com/p/accountings-data-problem as a consequence of complexity, data, and system fragmentation — and they lack the tools to solve it. The problems are real, hard, and increasingly urgent. But they’re solvable https://numeric.substack.com/p/accounting-will-retrace-the-path.

Enter Numeric — the modern platform for accounting and finance. We're building the platform that realizes the dream of live, rich, trustworthy data and insights for companies to drive decision-making & execution.

We tackle foundational challenges required to automate ingest, transformation, matching, projection, and reporting for an end-to-end graph of financial data. Weaving together data, automation, workflows, and AI-first experiences, we’re empowering accounting teams to own the continuous window into companies' finances and activity.

We have strong product market fit and a growing base of customers who love our product — including Anthropic, Brex, OpenAI, Plaid, Wealthfront, and many more. We’re backed by top-tier investors including IVP, Menlo Ventures, Founders Fund, and 8VC, along with founders and executives from Ramp, Segment, and other category-defining companies.

About the role

Numeric’s product is, at bottom, data: your accounting history, your ability to pass an audit, your capacity to catch mistakes before your auditors do. The Data Infrastructure team builds the financial data plane that makes that possible — the lakehouse that ingests raw data from ERPs, banks, payment processors, and customer warehouses, transforms it into typed canonical tables, and serves it to our accounting modules, reporting engine, and AI agents. We’re mid-way through a deliberate architectural bet (ClickHouse-backed lakehouse, SQLMesh, per-tenant isolation) and it is the layer we expect to carry the most new investment this year. Every engineer on the team owns a slice of the architecture end to end.

What you might work on

- Ingestion at scale: incremental, watermark-based extraction from API sources (NetSuite, Stripe, Brex, Ramp, HubSpot…), file-based S3 inboxes, and Postgres → ClickHouse replication — and making each new source cheap to add.

- Data contracts & typed source data: stop downstream consumers from touching untyped raw JSON; enforce schemas at the boundary and make datasets discoverable.

- Data Lakehouse schema management: a single declare → codegen → apply pipeline so schema intent is codified, reviewable, and applied consistently across tenants.

- Data Security: Scoping queries, building ACLs, and ensuring that we never, ever compromise our customer’s trust

- Batch processing & event-driven accounting: decouple event processing from downstream failures; give operators clear “what ran, what failed, and why” answers.

- Data correctness & observability: completeness checks rooted in platform data, ingestion health, two-phase re-ingest, and explanatory links from ledger entries back to raw events.

- Reporting scalability: the query patterns and materializations that let reporting drill from a board-level P&L to a single transaction without falling over.

- Tons of other stuff!

You might be a great fit if you…

- Have built or operated data pipelines / lakehouse / warehouse systems in production and have opinions about ETLs, idempotency, watermarks, and backfills.

- Treat auditability and “fail early, fail explicitly” as design constraints, not afterthoughts.

- Are comfortable across the stack: TypeScript services, SQL (ClickHouse and Postgres), and transformation tooling like SQLMesh or dbt.

- Like being close to the consumers of your data — accounting module engineers, the reporting team, and agents — and shaping the interfaces they use.

- Want to learn how accountants think about so …