Product Designer

About The Company

Dirac is building the creative suite for manufacturing engineering. Manufacturing engineering has been underserved by fractured tooling. The work of defining how a product gets built is spread across process plans, MBOMs, routings, work instructions, spreadsheets, PLM configurations, ERP tables, and internal tools. Each artifact represents only part of the process, forcing engineers to rebuild context whenever a design changes.

BuildOS brings these workflows together in one environment. Manufacturing engineers author, version, review, and distribute the Build—the canonical definition of how a product is produced. Figma owns the design file, GitHub owns the repo, Dirac owns the Build. We’re looking for an early Product Designer to define how that suite works and feels. You’ll build serious tools for technical users in a domain where great design can fundamentally change how someone works. We’re a small team that values autonomy, quality, feedback, and a bias toward action.

About The Role

You will own projects from pencil to release, working across user research, product strategy, prototyping, interaction design, visual design, and frontend development. You'll shape both Structure—flows, information architecture, and wireframes—and Surface—layout, typography, color, and interaction polish.

Responsibilities

• Design across BuildOS, including 3D CAD interaction, structured data authoring, document generation, and shop floor workflows.
• Define the patterns, primitives, and interactions that make complex workflows feel like one coherent product.
• Understand the spreadsheets, internal tools, and manual processes users rely on today, then design replacements that are faster, more complete, and more trustworthy.
• Become fluent in manufacturing workflows, including BOMs, BOPs, work instructions, GD&T, PMI, revision control, work centers, and takt time.
• Work directly with manufacturing engineers, operators, and customers, including spending time on factory floors.
• Help establish Dirac’s design language, design system, and product standards as Build OS grows.
• Partner closely with Product and Engineering from early exploration through implementation and release.
• Contribute beyond traditional product design through user research, prototyping, frontend development, and product polish.

Requirements

• 5+ years of product design experience, ideally designing complex B2B, technical, or professional software.
• High technical acumen and experience designing complex systems, workflows, and information-heavy interfaces.
• Strong interaction and visual design skills, from early concepts and prototypes through polished production-ready designs.
• Experience owning projects end-to-end, including research, problem definition, design, implementation, and release.
• Strong product judgment and the ability to balance user needs, technical constraints, business priorities, and speed.
• High attention to detail and a strong bar for craft, usability, and visual quality.
• Ability to self-direct, prioritize independently, and thrive in a fast-moving, ambiguous environment.
• Experience using qualitative and quantitative insights to inform design decisions.
• Familiarity with user research, usability testing, and prototyping.
• Ability to clearly communicate design decisions and rationale across Product and Engineering.
• A bias toward shipping and iteration over perfection.
• Curiosity about how physical things get made. Manufacturing experience is not required, but you should want to build that expertise.

Nice to Have

• Experience designing CAD, PLM, EDA, developer tools, data tools, industrial software, or other professional-grade applications.
• Experience designing complex data models, tables, hierarchical information, timelines, graphs, or 3D/spatial interfaces.
• Experience building or maintaining a design system.
• Ability to contribute frontend code, particularly with React, TypeScript, HTML, or CSS.
• Experience designing zero-to-one products or working at an early-stage startup.
• Experience conducting research with specialized technical users.
• Exposure to manufacturing, mechanical engineering, robotics, aerospace, automotive, industrial engineering, or hardware development.

Why This Role

CAD and PLM describe what a product is. ERP and MES record that production happened. Neither describes how the product gets built. There is no established software layer for this work and no established design language for it either. You will have the opportunity to define both.

Our users are manufacturing engineers who have spent their careers working around tools that were not built for them. This is an opportunity to define the interaction model and design language for an entirely new category of software.