Product Designer

Responsibilities

• 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.

Requirements

• 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.

Nice-to-Haves

• 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.