Skip to main content

Carnot AI

Founding Design Engineer

San Francisco$100k–$250kfulltimemidAdded 1 month ago

About this role

Join Jinba as the first dedicated design engineer to build a world-class design system and own the full visual experience of an AI-native enterprise workflow platform. You'll write production code alongside engineers while establishing design standards from the ground up for a fast-growing YC startup.

What you'll do

  • Design and build Jinba's design system including components, tokens, patterns, and documentation
  • Own UI/UX for core product surfaces from concept through implementation
  • Create motion design that guides users through complex workflow creation and execution
  • Write clean, maintainable frontend code using React and shadcn/ui
  • Collaborate directly with engineering to ship features rather than hand off specs
  • Establish design processes and standards as the first dedicated design hire

What they're looking for

  • Product design with portfolio demonstrating end-to-end ownership
  • Design system creation and contribution
  • Motion design with understanding of timing, easing, and animation
  • React and TypeScript proficiency
  • Component libraries (shadcn/ui, Radix, or similar)
  • Design tokens and scalable CSS architecture
  • Complex interface design (canvas editors, drag-and-drop builders, multi-step flows)
  • Experience with developer tools or workflow/automation products
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Carnot AI

Carnot AI builds an AI-native enterprise workflow automation platform designed to streamline complex business processes. The company is hiring design engineers, full-stack engineers, and customer success engineers to establish core product systems, architect scalable infrastructure, and drive enterprise customer implementations.

Website
carnot.ai
View all jobs at Carnot AI

Likely interview questions

  • Walk us through a design system you've built or significantly contributed to—what were the toughest decisions around component APIs and token architecture?
  • Tell us about a time you shipped your own design code. How did you balance design fidelity with engineering pragmatism?