Software Engineer, Developer Infrastructure

Why Numeric

Every business runs on accounting, but the systems underneath it were built for a different era. Today’s ERPs don’t store a company’s financial data. They store a diluted copy of it. Every contract, lease, and invoice gets flattened into a journal entry, and the context that made it meaningful is thrown away. That’s why accounting teams spend every month re-checking numbers, stitching together spreadsheets, and waiting on engineering, and why AI struggles to do real accounting work. Accounting doesn’t have a reporting problem. It has a data problem.

Enter Numeric: the data platform finance teams run on. We started with the month-end close, where the data problem hurts most, and hundreds of finance teams now run their close on Numeric. That work led us to rebuild the system of record itself. In September 2026 we launched the Financial Data Platform (FDP) , a platform built for the agent era. Instead of a journal entry, the real business object enters the system and the accounting is derived from it. Every number is traceable to its source, reporting works on any dimension, and accountants and AI agents finally have enough context to work together. While others bolted AI features onto the old data model, we built a new one.

We have a growing base of customers who love our product, including Anthropic, Plaid, Brex, Betterment, Wealthfront, and Asana. We’ve raised $89M from top-tier investors including IVP, Menlo Ventures, Founders Fund, and 8VC, along with founders and executives from Ramp, Segment, and other category-defining companies. We’re hybrid but in-office first, with teams in New York, San Francisco, and London, and we just shipped the product that will define our next decade. There’s never been a better time to join.

About the role

Platform Engineering at Numeric is engineering for engineering. Our customers are our own engineers and, increasingly, the AI agents working alongside them. The mission: make every engineer and agent dramatically more productive by building a shared platform, so anyone can go from idea to safely deployed change without bespoke setup or tribal knowledge. This role is the developer-infrastructure half of that mission — environments, CI/CD and deployment, infrastructure-as-code, environment parity, observability, security, and internal tooling. The current reality has gaps (deploys with no staging gate, migrations without clean rollback, a prod-DB-clone lock that blocks deploys, Terraform drift, two clouds where there should be one) and a roadmap to close them. You’d own pieces of that roadmap end to end and then watch engineers actually use them.

What you might work on

Deployment process: serialized, gated deploys across services; automated schema migrations with rollback; staging → production promotion that engineers trust.

Environments & parity: local and remote dev environments that are reliable and fast to stand up; sandboxes and preview/review environments so reviewers can verify behavior, not just read code.

Agent-First development: Including MCP gateways, governance, cost management, and foundation model selection.

Infrastructure-as-code: Spacelift/OpenTofu, drift remediation, consolidating off DigitalOcean onto AWS, and IaC standards that are easy to follow by default.

Repo standards & ownership: repository standards (linting, testing hierarchy, ownership manifests, idempotent onboarding), an ownership registry, and an internal developer portal.

Observability foundations: local tracing/logging/metrics for every engineer, Datadog cost and hygiene, incident-management maturity, status pages.

Security & access: unified secrets/config management, SSO in front of internal sites, IAM scoping, ECR scanning, audit logging, vulnerability management.

AI Internal tools hosting: Numeric Labs — the platform that lets anyone at Numeric ship an internal tool without re-solving auth, hosting, and observability.

You might be a great fit if you…

Are technically deep in infrastructure — AWS, containers/ECS, networking, IaC — and pragmatic about it.

Have a product builder’s instinct for developer experience: sane defaults, tooling that teaches, “shipping means seeing it work successfully.”

Like discovering the problem by meeting your users: pairing with engineers, watching onboarding, reading the friction in Slack.

Are comfortable building in-house when it’s the right call (and explicit about when a third-party tool earns its place).

What you need

3+ years of software engineering experience, including significant time on infrastructure, platform, or developer-productivity work.

Confidence with AWS, IaC (Terraform/OpenTofu or similar), CI/CD systems, and Linux/container fundamentals.

Strong general-purpose programming skills (primarily TypeScript, Python where it fits).