Celigo logo
Celigo

Design Engineer

USARemotePosted 1 month ago

Apply opens Celigo's site. When you're back, we'll ask whether you applied.

Job type
Not listed
Work mode
Remote
Level
Not listed
Department
Design
Experience
7+ years experience
Posted
Aug 24, 2026

About the role

Celigo believes integration should empower innovation and simplify how companies integrate, automate, and optimize processes. The Design Engineer will close the gap between design intent and production reality, building systems to make that gap smaller. This is the first Design Engineer role at Celigo, with ownership and the opportunity to shape the function.

The role sits within the UX organization and operates across Product Design, Design Systems, Content Design, and User Research and Insights, collaborating with Engineering and Product Management. It requires depth in both UX design and engineering, including visual hierarchy, interaction quality, usability, production-grade TypeScript and React, and focus on the UI layer.

This is an enablement role. Success is measured partly by how much faster and better the UX team works. The role owns results, not a step in the process.

What would you do if hired?

  • Maintain and evolve the production-ready React component library and Celigo design system.
  • Prototype complex interactions and animation behaviors in code, gather feedback, and iterate.
  • Build AI-assisted workflows, including agent rules and codebase and Figma library context, and create reusable skills and workflows for the UX team.
  • Enable the UX team by defining ways of working, teaching and pairing with designers and content designers, and improving team velocity.
  • Partner with Product Designers, Content Designers, and Product Managers to translate design intent into precise, accessible, performant UI components, advising on implementation cost versus experience impact and identifying engineering constraints.
  • Define and document interaction states and usage guidelines for consistent, efficient implementation.
  • Maintain the Figma component library alongside the coded library, including token architecture, component variants, interaction states, and usage annotations. Apply atomic design principles to determine pattern hierarchy.
  • Review front-end pull requests for design fidelity and WCAG 2.1 AA compliance.
  • Identify and address recurring friction between design and engineering through tooling, clearer specifications, or component conventions.
  • Participate in design and content workflows, contribute to design critiques, review work in Figma before handoff, flag interaction design issues, and pair with Content Designers on microcopy.

Who are we looking for?

Skills & Abilities

  • Strong command of React (or an equivalent component-based framework), TypeScript, and modern CSS, with depth on the UI layer: precise interaction and state logic, accessible markup, smooth motion, and the last 10% of polish (micro-interactions, loading states, animation timing) that makes an interface feel alive.
  • Expert-level Figma proficiency, not just inspection and handoff: building and maintaining shared component libraries, working with variables and design tokens, structuring files for team-scale use, and contributing to design reviews as a practitioner peer. You understand how a well-organized Figma library maps to a well-organized codebase.
  • Design systems expertise grounded in component-driven architecture: you understand atomic design methodology (tokens, primitives, molecules, organisms, templates), make principled decisions about abstraction and composition, think in systems rather than one-off solutions, and know how to build systems that scale without fragmenting.
  • UX Designer sensibilities: a working understanding of interaction design principles, visual hierarchy, usability heuristics, and information architecture sufficient to recognize when a design decision will create friction, and to articulate why, not just flag it. You do not need to own the design direction, but you need to understand it deeply.
  • Active, hands-on use of AI coding assistants, AI-powered prototyping tools, and workflow automation, integrated into your daily workflow rather than just experimented with. You could build everything in this system without AI; you use AI because it makes you faster. You can review, explain, and defend every line an agent produces.
  • Curiosity in practice: demonstrated experimentation with new tools and mediums, or exploratory work that shows you are energized by what you do not yet know.
  • A clear line from your work to the outcome it serves. You ask why before how, anticipate the second-order effects of a system decision, and choose the option that serves the experience rather than the one that closes the ticket.
  • An owner's mindset. When you see a gap between design and engineering, you step into it. You find the faster path and take it without being asked, and you measure yourself by whether the team shipped something better, not by how busy you were.
  • Communication and influence: you articulate design and engineering rationale clearly, teach as naturally as you build, and influence decisions across functions.
  • Ability to collaborate effectively across UX, Product Management, Engineering, and cross-functional partners.

Education & Experience

  • Hands-on expertise designing and building UIs for complex B2B SaaS products, ideally at enterprise scale, where deep configuration and long-lived workflows shape what the design system has to support.
  • 7+ years building web interfaces with a strong command of React (or equivalent component-based framework), TypeScript, and modern CSS. Depth and quality of experience matter more than years. You write code you are not embarrassed to share.
  • Working knowledge of accessibility standards (WCAG 2.1 AA) and practical experience implementing them at the component level.
  • A track record of working alongside design and content teams in a cross-functional setting: familiar with design critique culture, content pairing workflows, and how to give and receive direct design feedback.
  • A portfolio that demonstrates both design sensibility and code quality: work you designed, work you built, and ideally work where those two things overlap.
    • Production-quality UI components or component libraries
    • Design system contributions with documented usage guidelines, in both Figma and code
    • Figma-side systems work: annotated component libraries, token architecture, or design system governance artifacts
    • Examples of coded prototypes used to validate interaction decisions
    • (Portfolios focused primarily on feature delivery without design systems or code repo ownership will not be considered.)
  • Expert-level experience with design token pipelines, connecting the Figma design system to the codebase through a shared token layer rather than manual translation. You bring established best practices with you.
  • Expert-level experience building and maintaining a component documentation system such as Storybook, with documentation and usage guidelines that engineers actually adopt.

Nice to have

  • Background in integration platforms, iPaaS, or technically sophisticated B2B products, or a demonstrated ability to design for power users and simplify complex workflows.
  • Degree in Computer Science, Human-Computer Interaction, Interactive Design, or a related field, or equivalent practical experience

What This Role is Not

This role does not focus on:

  • Pure front-end feature development without design systems ownership or design quality accountability.
  • Visual or interaction design: owning the design direction is the domain of Product Design.
  • Marketing, brand content, or campaign work of any kind.
  • Producing documentation or prototypes for their own sake: prototypes and docs are means, team enablement is the outcome.

Success is defined by component quality, design fidelity, system adoption, and how much faster the whole team ships. Candidates whose primary background is front-end engineering without meaningful UX, Product Design, design systems, or cross-functional design collaboration experience will not be a fit. Candidates whose primary background is design, with coding experience limited to prototypes, AI-assisted output, or code that never shipped to production, will not be a fit.

Celigo reasonably expects to pay a base salary between $150,000 and $200,000 per year for this position. Actual starting base pay will be determined by skills, experience, geographic location, and other permitted factors. Total compensation may also include variable incentives, benefits, or other perks.

Celigo is proud to be

  • Celigo is the #1 ranked iPaaS platform (G2, 8 quarters running)
  • Celigo is a Visionary in the Gartner Magic Quadrant for iPaaS for the second consecutive year
  • Celigo is ranked #1 iPaaS on G2 for multiple quarters and is named a Leader in both B2B/EDI and API Management

Here you'll experience

  • Remote-first culture, built on trust, collaboration, and transparency
  • A high-growth, inclusive work environment where innovation thrives, and ideas are implemented
  • Lightspeed learning opportunities to keep you at the leading edge of your field
  • Exceptional coworkers who challenge and inspire you daily
  • Competitive compensation and benefits, including:
    • Three weeks of vacation (starting year one)
    • Wellness days and holidays to recharge
    • Parental leave and a generous benefits package
    • Monthly tech stipend
    • Recognition and career development opportunities

Diversity, Equity, Inclusion, and Accessibility

Celigo's values include fostering a safe, collaborative environment through its Taking a Stand Initiative, a volunteer committee open to all employees and representing underrepresented voices. Celigo is committed to equal employment opportunities and considers qualified applicants regardless of criminal histories, consistent with legal requirements.