UX Design Engineer (US Remote)

Oomnitza
Full-time$120k-165k/year (USD)

📍 Job Overview

Job Title: UX Design Engineer (US Remote)

Company: Oomnitza

Location: US Remote (or Ireland)

Job Type: Full-time

Category: Design Engineering / Product Development Operations

Date Posted: 2026-08-12

Experience Level: 5-10 years

Remote Status: Remote OK

🚀 Role Summary

  • Own and evolve the Oomnitza design system, ensuring a cohesive visual language, interaction patterns, and accessibility standards across the product.

  • Maintain and extend the Storybook component library, focusing on correctness, documentation, performance, accessibility, and ease of composition for Product Engineers.

  • Develop and manage prototyping tooling, including design tokens, AI-prompt scaffolds, and starter kits, to accelerate the Product Engineering team's ability to move from idea to validated prototype.

  • Act as a UX consultant for novel interactions, integrating new patterns or components back into the design system to maintain consistency and efficiency.

  • Partner closely with engineering teams to ensure seamless alignment between the design system and its implementation, identifying opportunities to promote successful one-off interactions into reusable system assets.

📝 Enhancement Note: While the title is "UX Design Engineer," the responsibilities and required skills strongly indicate a focus on the operational aspects of design systems and front-end development tooling, rather than direct user research or user testing. This role is about enabling other engineers to build efficiently and consistently. The emphasis on "product engineering team" and "design system end-to-end" suggests a GTM (Go-To-Market) enablement function through robust tooling and standardized components.

📈 Primary Responsibilities

  • Design System Ownership: Lead the entire Oomnitza design system, encompassing visual language, interaction patterns, accessibility guardrails, and overarching product consistency principles.

  • Component Library Management: Maintain and enhance the Storybook component library, ensuring all components are accurate, well-documented, performant, accessible, and easily composable by Product Engineers.

  • Prototyping Tooling Development: Build and manage the prototyping infrastructure, including design tokens, AI-prompt scaffolds, design markdowns, and starter kits, to facilitate rapid prototyping cycles for the Product Engineering team.

  • UX Consultation & Pattern Integration: Advise Product Engineers on UX interactions that fall outside existing patterns, and formalize these into new system patterns, components, or guidance.

  • Design-Engineering Alignment: Collaborate with engineering teams to ensure the design system and its code implementation remain synchronized, identifying and integrating successful one-off interactions into the system.

  • Quality Assurance: Uphold the design quality bar across the team by reviewing prototypes against the design system, identifying deviations, and making it easy for engineers to adhere to standards.

  • Industry Research & Investment: Monitor advancements in design tooling, AI design, headless component libraries, and accessibility standards, proposing strategic investments to enhance team speed and efficiency.

📝 Enhancement Note: The responsibilities highlight a critical operational function within the product development lifecycle. The role is focused on creating and maintaining the "engine" that drives consistent and efficient UI development, which is a core aspect of product operations and GTM enablement for a SaaS company.

🎓 Skills & Qualifications

Education: Bachelor's degree in Design, Human-Computer Interaction (HCI), Computer Science, or a related field, or equivalent practical experience.

Experience: 5+ years of combined experience in product design and front-end engineering, demonstrating equal comfort and proficiency in both Figma and modern front-end codebases.

Required Skills:

  • Design System Expertise: Proven experience owning or significantly contributing to a production design system and a component library (e.g., Storybook).

  • Front-end Development: Strong skills in React, TypeScript, modern CSS, including deep understanding of design tokens.

  • Accessibility Standards: Comprehensive knowledge and application of web accessibility best practices (WCAG).

  • Design Tooling Proficiency: High level of proficiency in Figma or equivalent design and prototyping tools.

  • Component-Based Architecture: Understanding of how to build and manage reusable UI components.

  • Written and Verbal Communication: Ability to clearly document patterns, brief engineers, and influence stakeholders without direct authority.

  • Self-Direction & Outcome Orientation: Demonstrated ability to identify high-leverage investments and prioritize tasks independently.

Preferred Skills:

  • AI-Enabled Design Workflows: Experience integrating AI tools into design and prototyping processes.

  • B2B SaaS or Enterprise Software Experience: Familiarity with the unique design and development challenges of enterprise-grade software.

  • Interaction Design: Experience defining and documenting nuanced interaction patterns.

  • Headless Component Libraries: Understanding of headless architectures for UI development.

📝 Enhancement Note: The emphasis on 5+ years of combined experience in both design and front-end engineering, along with specific tool proficiencies like React, TypeScript, and Storybook, points to a highly specialized role. This isn't a pure UX designer or a pure front-end engineer, but someone who bridges the gap, making them invaluable for operational efficiency in product development. The requirement for strong written communication is critical for documenting and disseminating system standards.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

  • Design System Case Study: A comprehensive case study detailing your experience in building, maintaining, or significantly contributing to a production design system. This should showcase your understanding of visual language, interaction patterns, and accessibility.

  • Component Library Showcase: Examples of components you've built for a component library (e.g., Storybook), demonstrating code quality, documentation, and reusability. Include links to live examples or code repositories if possible.

  • Prototyping Tooling Examples: Demonstrations of any prototyping tools, scaffolds, or starter kits you've developed that accelerate design and development workflows.

  • Design-to-Code Alignment: Evidence of how you've ensured consistency between design specifications and front-end implementation, possibly through collaboration examples or process documentation.

  • Accessibility Implementation: Examples that highlight your commitment to and practical application of accessibility standards in design and code.

Process Documentation:

  • Design System Governance: Documentation outlining processes for design system updates, contribution guidelines, and version control.

  • Component Development Workflow: Clearly defined steps for creating, reviewing, and deploying new components to the library.

  • Prototyping Workflow Optimization: Evidence of how you've streamlined the process for Product Engineers to create functional prototypes.

  • Design Review Process: Examples of how you conduct design reviews to ensure adherence to the design system and maintain quality.

📝 Enhancement Note: For a role focused on operationalizing design, a portfolio is crucial. It needs to demonstrate not just design skills but also the ability to create scalable, documented, and maintainable systems and processes that enable other teams. The emphasis should be on how the candidate's work improves efficiency and consistency for the broader engineering organization.

💵 Compensation & Benefits

Salary Range: $120,000 - $165,000 USD per year.

Benefits:

  • Market-competitive salary

  • Equity options

  • Opportunities for career growth and shaping team initiatives

  • Working directly with founders to drive business initiatives

Working Hours: 40 hours per week (standard full-time).

📝 Enhancement Note: The salary range provided is typical for experienced Design Engineers or Front-End Engineers specializing in design systems in the US. The "US Remote (or Ireland)" location suggests potential for salary adjustments based on regional cost of living and market rates. The benefits listed are standard for a venture-backed startup, with a strong emphasis on growth and direct impact.

🎯 Team & Company Context

🏢 Company Culture

Industry: Enterprise Technology Management / SaaS. Oomnitza operates in the critical space of IT asset management and workflow automation, providing a SaaS solution that helps large organizations streamline IT processes, reduce costs, and mitigate cyber risks. This context implies a focus on robust, scalable, and secure solutions.

Company Size: Oomnitza is a growing, venture-backed business. This suggests a dynamic, fast-paced environment where individual contributions can have significant impact, and where processes are likely evolving. Roles in such companies often require adaptability and a proactive approach to defining and improving operational workflows.

Founded: While the founding date is not explicitly provided, the mention of venture backing from Shasta Ventures, SYN Ventures, and Riverside Acceleration Capital indicates a relatively established but still growth-oriented phase of the company. This stage typically involves scaling operations, refining product-market fit, and building out core teams.

Team Structure:

  • Product Engineering Focus: The role directly supports the Product Engineering team, implying a close working relationship. This team is likely responsible for developing the core SaaS platform.

  • Design System as a Product: The UX Design Engineer's work on the design system positions it as a foundational product for internal development, requiring collaboration with engineering leadership and potentially product management.

  • Cross-Functional Collaboration: While the primary focus is on supporting Product Engineering, collaboration with other departments (e.g., product, marketing, sales) might occur indirectly through the platform's user experience and feature development.

Methodology:

  • Low-Code Workflows: Oomnitza's platform emphasizes low-code workflows, suggesting an internal operational philosophy that values efficiency, automation, and empowering users (both internal and external) with streamlined processes.

  • Agentless Integrations: This technical approach to integration highlights Oomnitza's focus on efficient, non-intrusive solutions, a principle likely reflected in their internal tooling and processes.

  • Data-Driven Optimization: Given the nature of Enterprise Technology Management, data analysis and process optimization are core to Oomnitza's value proposition, suggesting these are also key internal operational principles.

Company Website: https://www.oomnitza.com/

📝 Enhancement Note: The company's focus on "orchestrating and automating key business processes for IT" and providing a "versatile Enterprise Technology Management platform" is highly relevant. This means the internal operations, especially around product development and design systems, are likely built with similar principles of efficiency, scalability, and robust process management. The role of UX Design Engineer is critical in operationalizing the company's product vision through its internal development tools.

📈 Career & Growth Analysis

Operations Career Level: This role is positioned as a Senior individual contributor, with significant ownership and strategic influence over core development tooling. It's a blend of senior product design and senior front-end engineering, focused on the operational enablement of a product engineering team. The expectation is for someone who can define and lead, not just execute.

Reporting Structure: The exact reporting structure isn't specified, but given the focus on owning the design system and tooling, the role likely reports into Product Engineering leadership, Head of Product, or potentially a dedicated Design Systems lead if such a role exists. The emphasis on "working directly with the founders" suggests a high level of visibility.

Operations Impact: The UX Design Engineer's work has a direct and significant impact on the speed, consistency, and quality of product development. By providing a robust design system and efficient prototyping tools, this role enables the Product Engineering team to:

  • Accelerate Go-to-Market: Faster prototyping and development cycles mean features reach customers sooner.

  • Ensure Brand Consistency: A strong design system guarantees a unified user experience across the platform, crucial for B2B SaaS credibility.

  • Reduce Development Friction: Well-documented and easy-to-use components minimize engineering effort and reduce bugs.

  • Mitigate Design Debt: Proactive system management prevents the accumulation of inconsistent or outdated UI elements.

Growth Opportunities:

  • Leadership in Design Systems: Opportunity to become a recognized expert and leader in design systems within the company, potentially building out a dedicated design systems team as the company scales.

  • Strategic Product Influence: Direct collaboration with founders and leadership provides a platform to influence product strategy and development methodologies.

  • Skill Specialization: Deepen expertise in front-end engineering, accessibility, AI in design, and advanced prototyping techniques.

  • Cross-Functional Expansion: Potential to influence design and development practices beyond the immediate Product Engineering team.

📝 Enhancement Note: This role offers a unique growth path for someone who excels at operationalizing design and development. It's not just about making things pretty; it's about building the system that makes development efficient and high-quality, directly contributing to the company's ability to scale its product offerings.

🌐 Work Environment

Office Type: This role is designated as "US Remote (or Ireland)." This implies a fully remote work environment with no mandatory office attendance. The company likely utilizes virtual collaboration tools extensively.

Office Location(s): While the role is remote, Oomnitza is headquartered in San Francisco, CA. The allowance for candidates in Ireland suggests a global approach to talent acquisition, leveraging remote work to access a wider pool of skilled professionals.

Workspace Context:

  • Virtual Collaboration: Expect a heavy reliance on tools like Slack, Zoom, Notion, or similar platforms for communication, documentation, and project management.

  • Tooling & Technology: Access to industry-standard design and development tools will be provided or expected. The role itself is about enhancing this toolset.

  • Team Interaction: While remote, opportunities for interaction will likely be scheduled through virtual meetings, design critiques, and collaborative work sessions within shared tools.

Work Schedule: Standard 40-hour work week. Given the remote nature and potential for international collaboration (US/Ireland), flexibility in working hours might be necessary to accommodate different time zones, but core hours or availability for critical meetings will likely be established.

📝 Enhancement Note: The remote nature of the role is a key aspect of its operational environment. It necessitates strong self-discipline, asynchronous communication skills, and proficiency with digital collaboration tools. The company's global talent strategy (US/Ireland) also implies a culture that values results over physical presence.

📄 Application & Portfolio Review Process

Interview Process:

  • Initial Screening: A conversation with a recruiter to assess general fit, experience alignment, and salary expectations.

  • Technical/Design Assessment: This will likely involve a deep dive into your portfolio, focusing on your design system experience, component library contributions, and front-end coding skills. Expect discussions around your process for building and maintaining these systems.

  • Design System Deep Dive: A session focused on your approach to owning and evolving a design system, including how you handle visual language, interaction patterns, accessibility, and documentation. This may involve presenting specific case studies from your portfolio.

  • Coding Challenge/System Review: You might be asked to complete a small coding task related to front-end development or component creation, or to critique an existing component/pattern and suggest improvements based on your design system principles.

  • Founder/Leadership Interview: A final interview with company leadership to assess strategic thinking, cultural fit, and overall alignment with Oomnitza's vision.

Portfolio Review Tips:

  • Showcase Design System Impact: Clearly articulate the value your design system work brought to previous companies. Quantify improvements in development speed, consistency, or reduction in bugs where possible.

  • Structure for Clarity: Organize your portfolio logically. Dedicate sections to design system ownership, component library contributions, and any tooling development. Use clear headings and concise descriptions.

  • Demonstrate Process: For each project, explain your thought process, the challenges you faced, and how you arrived at your solutions. This is crucial for a role focused on operationalizing design.

  • Code Samples: Provide well-commented code samples for components or system elements. Ensure they demonstrate clean code practices, accessibility, and responsiveness.

  • Storytelling: Be prepared to walk through your portfolio items, telling a compelling story about your contributions and their impact.

Challenge Preparation:

  • System Thinking: Practice articulating how you would approach building or improving a design system from scratch or from an existing state. Consider governance, contribution models, and adoption strategies.

  • Front-end Fundamentals: Brush up on React, TypeScript, modern CSS (especially design tokens), and accessibility best practices.

  • Problem Solving: Be ready to discuss how you would handle conflicting design requests, engineering pushback, or the integration of new technologies into the system.

  • Company Research: Understand Oomnitza's product, target market, and their emphasis on efficiency and automation. Frame your answers to align with these company values.

📝 Enhancement Note: The interview process will heavily scrutinize the candidate's ability to translate design principles into scalable, maintainable code and processes. The portfolio is the primary tool for demonstrating this capability, so preparation should focus on showcasing structured thinking and measurable impact.

🛠 Tools & Technology Stack

Primary Tools:

  • Design & Prototyping: Figma (or similar industry-standard tools like Sketch, Adobe XD).

  • Component Library: Storybook is explicitly mentioned. Proficiency in its setup, maintenance, and documentation is key.

  • Front-end Framework: React is a core requirement.

  • Language: TypeScript is a core requirement.

  • Styling: Modern CSS, including CSS-in-JS solutions or utility-first CSS frameworks, and importantly, Design Tokens.

Analytics & Reporting:

  • While not directly stated for this role, experience with tools that track component usage, design system adoption, or development efficiency would be beneficial. This could include internal dashboards or analytics platforms. CRM & Automation:

  • Not directly applicable to this role, but understanding Oomnitza's core business in Enterprise Technology Management and automation provides context for the types of internal processes that might be prioritized. Development Environment:

  • Familiarity with modern JavaScript build tools (e.g., Webpack, Vite), version control (Git), and CI/CD pipelines for component deployment.

📝 Enhancement Note: This role is deeply technical and requires hands-on experience with the specific tools used in modern front-end development and design system management. The emphasis on React, TypeScript, Storybook, and Design Tokens indicates a commitment to robust, scalable, and maintainable UI development practices.

👥 Team Culture & Values

Operations Values:

  • Efficiency & Automation: Oomnitza's core business is built on these principles, so expect them to be deeply ingrained in the company culture. This role is a prime example of operationalizing efficiency through tooling.

  • Data-Driven Decisions: While not explicitly stated for this role, the nature of their product suggests a strong reliance on data for decision-making, which likely extends to product development and design.

  • Collaboration & Empowerment: The model of Product Engineers owning discovery and prototyping, supported by this role, indicates a culture of empowerment and distributed ownership.

  • Quality & Consistency: Owning the design system implies a commitment to maintaining a high standard of quality and consistency across the product.

  • Innovation: The mention of AI-enabled design and tracking industry trends suggests a forward-looking approach to technology adoption.

Collaboration Style:

  • Empowering Support: The role is designed to support and empower Product Engineers by providing them with the tools and guidelines needed to succeed.

  • Partnership with Engineering: Close collaboration with engineers is essential to ensure the design system is practical and well-implemented.

  • Influential Communication: The ability to influence without direct authority will be key, requiring strong communication and relationship-building skills.

  • Asynchronous Communication: Given the remote nature and potential for international teams, proficiency in asynchronous communication and documentation is vital.

📝 Enhancement Note: The company's values are likely centered around leveraging technology to drive efficiency and scalability, both in their product and their internal operations. This role is a direct embodiment of that philosophy, making it crucial for candidates to align with these values.

⚡ Challenges & Growth Opportunities

Challenges:

  • Balancing Standardization with Innovation: Effectively managing the design system to provide consistency while still allowing for novel and innovative user experiences.

  • Driving Adoption: Ensuring that Product Engineers actively adopt and correctly use the design system and its associated tooling.

  • Maintaining Alignment: Keeping the design system and its implementation in sync as the product and codebase evolve rapidly.

  • Scaling the System: Designing and evolving the system to support future growth and complexity without becoming unwieldy.

  • Integrating New Technologies: Staying ahead of the curve by evaluating and integrating new tools and methodologies (e.g., AI in design) effectively.

Learning & Development Opportunities:

  • Deepening Design System Expertise: Becoming a recognized authority on design systems and their operational impact within a growing SaaS company.

  • Front-end Technology Advancement: Gaining hands-on experience with cutting-edge front-end technologies and best practices.

  • AI in Design Tooling: Exploring and implementing AI-driven solutions to enhance design and development workflows.

  • Strategic Impact: Contributing directly to the company's growth and product strategy through the enablement of its engineering teams.

  • Leadership Potential: Opportunity to shape the future of design and development tooling at Oomnitza, potentially leading a team in the future.

📝 Enhancement Note: The challenges are inherent to the operational nature of managing a design system in a fast-growing tech company. The growth opportunities are significant for someone looking to make a substantial impact and build a career in a specialized, high-demand area.

💡 Interview Preparation

Strategy Questions:

  • "Describe your philosophy for building and maintaining a design system. What are the key pillars of a successful system?"

  • "How would you approach integrating AI tools into a design system workflow to enhance efficiency without compromising quality?"

  • "Imagine a Product Engineer comes to you with a novel interaction pattern that doesn't fit the current design system. What steps would you take?"

  • "How do you measure the success and adoption of a design system and its component library?" Company & Culture Questions:

  • "What interests you about Oomnitza's mission and its focus on Enterprise Technology Management?"

  • "How do you envision your role contributing to Oomnitza's culture of efficiency and automation?"

  • "Describe a time you had to influence stakeholders without direct authority to adopt a new process or tool." Portfolio Presentation Strategy:

  • Focus on "Why" and "How": For each portfolio item, explain the problem you were solving, your design and technical process, and the outcome.

  • Quantify Impact: If possible, provide metrics on how your work improved efficiency, reduced bugs, or sped up development.

  • Demonstrate Code Quality: Be ready to discuss the code behind your components, highlighting best practices for maintainability, performance, and accessibility.

  • System Thinking: Show how your individual contributions fit into a larger system and how you ensured consistency and scalability.

  • Interactive Walkthrough: Be prepared for a live walkthrough of your portfolio, using screen sharing to demonstrate your work in Figma, Storybook, or code repositories.

📝 Enhancement Note: Interview preparation should focus on demonstrating a deep understanding of design systems as operational tools, strong front-end engineering skills, and a proactive, problem-solving mindset that aligns with Oomnitza's culture.

📌 Application Steps

To apply for this UX Design Engineer position:

  • Submit your application through the provided application link on jobs.lever.co.

  • Portfolio Customization: Tailor your resume and portfolio to prominently feature your experience with design systems, Storybook, React, TypeScript, and accessibility. Highlight specific projects where you owned or significantly contributed to these areas.

  • Resume Optimization: Ensure your resume clearly outlines your 5+ years of combined design and front-end engineering experience. Use keywords from the job description and quantify your achievements where possible.

  • Interview Preparation: Practice articulating your design system philosophy, front-end technical skills, and your approach to problem-solving. Prepare to walk through your portfolio with specific examples of your impact.

  • Company Research: Thoroughly research Oomnitza's product, mission, and values. Understand their focus on efficiency and automation, and be prepared to connect your skills and experience to these company objectives.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.

Application Requirements

Candidates must have 5+ years of combined experience in product design and front-end engineering with strong proficiency in React, TypeScript, and Figma. A bachelor's degree in design, HCI, computer science, or a related field is required.