About the company

Every business depends on accounting. Yet most software in the category was built in the early 2000s: slow, clunky, and badly matched to the complexity finance teams face today. Accountants are dealing with a growing data problem created by more systems, more transactions, more reporting requirements, and more fragmented workflows. The problems are real, hard, and increasingly urgent. They are also solvable.

This company is building the modern platform for accounting and finance, working toward live, rich, trustworthy financial data that companies can use to decide and move faster. It takes on foundational challenges across data ingest, transformation, matching, projection, reporting, and workflow — combining data infrastructure, automation, and careful product design to pull accounting teams away from manual work and toward a continuous view of a company's financial activity.

Product-market fit is strong, with hundreds of customers including some of the most recognizable names in AI and fintech. The company is at Series B, backed by top-tier venture firms alongside founders and executives from category-defining companies.

About the role

This Product Designer joins the Experience team — currently three product designers and one front-end engineer. The team owns the quality, coherence, and UI/UX differentiation of the entire product surface, working across product design, design systems, code-based prototyping, and front-end implementation to keep the product clear, dense, elegant, and trustworthy.

The surfaces here are complex, data-heavy, and genuinely technical. Work usually starts before every requirement is settled and continues straight through implementation. This designer will partner closely with engineers and PMs, prototype quickly, use the product directly, reason through edge cases, and turn ambiguous workflows into shippable product — including shipping some of it personally.

The best fit works independently, seeks feedback without being prompted, and moves between rough prototypes, product reasoning, polished interaction design, and implementation detail without much ceremony. Someone who runs toward hard problems.

How the team works

1. Fast, direct, and unusually close to engineering
2. Prototyping happens early and often
3. Code, Claude Code, Linear, Figma, and the product itself all count as design artifacts
4. Reusable patterns and design-system leverage matter, but process never gets to slow down product learning
5. Designers stay close to implementation and are comfortable in the details with engineers
6. There are few formal design ceremonies, so designers have to be proactive about gathering feedback and building alignment
7. Sharp product judgment, low ego, high agency, and strong craft are what the team values
8. Speed and quality are held as the same goal, not a tradeoff

Responsibilities

1. Own product design for complex workflows inside the financial operating system, from early exploration through implementation
2. Work with engineers and PMs to clarify ambiguous product problems and convert them into buildable interaction models
3. Produce prototypes, reference screens, interaction specs, and implementation notes — whichever artifact moves the work forward
4. Build or direct code-based prototypes where they help, including with tools like Claude Code
5. Stay with engineers through the build, refining behavior, states, edge cases, density, polish, and overall quality
6. Find and fix rough edges across the product before they harden into product debt
7. Contribute to user-story-led work, higher-fidelity refinement, and the reconciliation between prototype, production, and final quality
8. Help define reusable patterns for review surfaces, object inspectors, inbox tasks, tables, panels, workflows, and AI-enabled interactions
9. Work with the design-system lead on component adoption and with engineering on prototype-to-production details
10. Bring a real point of view on craft, usability, and clarity while staying pragmatic about what has to ship now

What the company is looking for

1. 5+ years of product design experience, ideally in a startup or another high-ownership environment
2. Strong visual, interaction, and product craft
3. Experience designing complex, technical, data-heavy, or workflow-heavy products
4. The ability to reason through edge cases, states, density, hierarchy, and product behavior
5. Comfort working independently with little ceremony, and the instinct to pull in feedback rather than wait for it
6. A history of partnering closely with engineers and PMs through implementation
7. Fast prototyping using whatever tool suits the problem
8. Experience with — or strong interest in — code-based design workflows using tools like Claude Code
9. The ability to communicate a plan visually in low fidelity, and to produce high-fidelity references when the work calls for it
10. Strong written and verbal communication: explaining not just what was designed, but why it should work
11. Low ego and high agency, with the ability to own a messy problem that has not been perfectly scoped

Bonus points

1. Design experience in financial, accounting, data, developer, AI, or enterprise workflow products
2. Experience designing interfaces for tables, records, logs, approvals, review queues, automation, or data transformation
3. The ability to build lightweight prototypes in React/TypeScript or modify existing front-end code
4. Experience treating a design system as a living code and product system rather than a Figma library
5. Time at an early-stage company where designers operated with high ownership and low process

You might be a fit if

1. You are deeply curious
2. You like working directly with engineers
3. You are comfortable when the first artifact is a prototype, a screenshot, a branch, a Loom, or a Linear issue
4. You can take an ambiguous product area and make it legible
5. You care about craft without needing weeks of isolated design time to produce value
6. Dense, information-rich interfaces appeal to you
7. You want a hand in inventing the product surface for modern accounting software
8. You have AI experience and a nuanced view of where and how it should be applied
9. You can move between "what is this system actually doing?" — reasoning about the underlying data model — and "what should this exact panel look like?"

You might not be a fit if

1. You need a predefined, highly structured design process to do your best work
2. You prefer to stay well away from implementation
3. You want to work only in Figma
4. Technical product concepts make you uncomfortable
5. Brand or marketing design is what you really want to own
6. You prefer long research cycles before making anything
7. Accounting, finance, data, and enterprise workflows hold no interest for you