Skip to content
Numeric

Product Designer, Experience

New YorkOnsite · United States
FullTime · Product & Design
POSTED 5 JUNVERIFIED 1D AGO
Apply Ask
Pay · posted
$170k–200k
mkt median $158k
Open for
153d
since 5 Jun
H-1B · FY25
1
certified LCAs
Hiring · 30d
24
0 net · open roles
Figma

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 in-person, 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

We’re hiring a Product Designer to join our Experience Team.

The Experience team currently includes three product designers and one front-end engineer. The team owns the quality, coherence, and UI/UX differentiation of Numeric’s product surface area. We work across product design, design systems, code-based prototyping, and front-end implementation to make sure the product feels clear, dense, elegant, and trustworthy.

We are building complex, data-heavy, highly technical product surfaces. The work often starts before every requirement is clear and continues through implementation. You’ll partner closely with engineers and PMs, prototype quickly, use the product directly, reason through edge cases, and help turn ambiguous workflows into shippable product (including shipping some yourself!).

The best fit is someone who can work independently, seek feedback proactively, and move between rough prototypes, product reasoning, polished interaction design, and implementation details without needing a lot of ceremony. You should be someone who runs toward hard problems.

How We Work

This role is in-person in New York (in office, with flexibility).

We work in a way that is fast, direct, and unusually close to engineering.

We prototype early and often.

We use code, Claude Code, Linear, Figma, and the product itself as design artifacts.

We care about reusable patterns and design-system leverage, but we do not let process slow down product learning.

Designers are expected to be close to implementation and comfortable working with engineers in the details.

We do not have many formal design ceremonies. Designers need to be proactive about getting feedback and creating alignment.

We value sharp product judgment, low ego, high agency, and strong craft.

We care about speed and quality at the same time.

What You’ll Do

Own product design for complex workflows in our financial operating system, from early exploration through implementation.

Work closely with engineers and PMs to clarify ambiguous product problems and turn them into buildable interaction models.

Create prototypes, reference screens, interaction specs, and implementation notes as needed — using whatever artifact best moves the work forward.

Build or direct code-based prototypes where useful, including with tools like Claude Code.

Source · NumericFirst seen 2 NovOriginal ↗