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

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 hybrid in New York, in-office first.

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.

• Partner with engineers during build to refine behavior, states, edge cases, density, polish, and product quality.

• Help identify and resolve rough edges across the product before they harden into product debt.

• Contribute to user story-led work, higher-fidelity refinements, and the reconciliation between prototype, production, and final product quality.

• Help define reusable patterns for review surfaces, object inspectors, inbox tasks, tables, panels, workflows, and AI-enabled product interactions.

• Work with our design-system lead on component adoption and with engineering on prototype-to-production details.

• Bring a strong point of view on craft, usability, and product clarity while staying pragmatic about what needs to ship now.

What We’re Looking For

• 5+ years of product design experience, ideally in a startup or high-ownership product environment.

• Strong visual, interaction, and product craft.

• Experience designing complex, technical, data-heavy, or workflow-heavy products.

• Ability to reason through edge cases, states, density, hierarchy, and product behavior.

• Comfort working independently with limited ceremony and proactively pulling in feedback.

• Experience partnering closely with engineers and PMs through implementation.

• Comfort prototyping quickly and using whatever tool is right for the problem.

• Experience or strong interest in code-based design workflows using tools like Claude Code, or similar.

• Ability to visually communicate a plan in low fidelity and create high-fidelity references when the work requires it.

• Strong written and verbal communication. You should be able to explain not just what you designed, but why it should work.

• Low ego and high agency. You can own a messy problem without needing it to be perfectly scoped.

Bonus Points

• Experience designing financial, accounting, data, developer, AI, or enterprise workflow products.

• Experience designing interfaces for tables, records, logs, approvals, review queues, automation, or data transformation.

• Ability to build lightweight prototypes in React / TypeScript or modify existing front-end code.

• Experience working with design systems as a living code/product system, not just a Figma library.

• Experience at an early-stage company where designers had to operate with high ownership and low process.

You Might Be a Fit If

• You are a deeply curious person.

• You like working directly with engineers.

• You are comfortable when the first artifact is a prototype, screenshot, branch, Loom, or Linear issue.

• You can take an ambiguous product area and make it more understandable.

• You care about craft but do not need weeks of isolated design time to produce value.

• You like dense, information-rich interfaces.

• You want to help invent the product surface for modern accounting software.

• You are have experience in AI, but are nuanced about where & how it’s applied.

• You can move between “what is this system doing?” (being able to reason about the underlying data model) and “what should this exact panel look like?”

You Might Not Be a Fit If

• You need a predefined, highly structured design process to do your best work.

• You prefer to stay far away from implementation.

• You want to work only in Figma.

• You are uncomfortable with technical product concepts.

• You mostly want to own brand or marketing design.

• You prefer long research cycles before making.

• You are not at all interested in accounting, finance, data, or enterprise workflows.