Product Engineer (UX

About The Role

Product Engineers at Dome own outcomes, not just implementations. In this role, you will own the experience layer across every surface of the Dome Platform - Dashboard, CLI tools, SDK interfaces, and API interactions - making design decisions, building what you design, and iterating based on what you learn from real usage. The boundary between interaction design and engineering execution does not exist here;

you operate across both.

Dome Platform is a governance control plane with seven distinct interfaces: a web application, multiple CLIs, SDKs, Documentation, and multiple sub‑components. The UX challenge is designing coherent interaction patterns across surfaces that range from graphical to programmatic. You think in terms of mental models, information architecture, and task flows and then translate those into whatever medium the user encounters.

This is an AI‑native engineering role. You understand how AI reshapes the development lifecycle and have experienced the productivity gains firsthand. You know where AI creates leverage and where it does not, and you use that understanding to deliver at a pace that traditional approaches cannot match. You specify intent clearly, delegate implementation, and focus your judgment on evaluation and refinement.

This is how you already work, not something you intend to explore.

You will help establish the design foundations and UX culture of a company in its earliest stages by working directly with customers and the engineering team to understand where the product creates friction and where it creates clarity, then iterate until the experience delivers.

You will define and ship the interaction design across Dome’s platform surfaces. This means understanding how platform engineers, security teams, and operators think about the development lifecycle and then designing experiences that make complex workflows feel tractable.

You will own the end‑to‑end experience: information architecture, interaction patterns, CLI ergonomics, dashboard layouts, error states, and progressive disclosure across a system with 100+ capabilities spanning multiple personas and areas of concern.

You will design for multiple interaction paradigms. A policy simulation might start in the CLI, surface results in the dashboard, and generate events consumed via the SDK. The experience must be coherent across all three.

You will build what you design, bringing your supplementary skills such as writing frontend code, prototyping interactions, and shipping production interfaces.

• You have designed and shipped interaction patterns for complex, technical products such as infrastructure tools, developer platforms, or enterprise systems with non‑trivial domain models.
• You think in systems, not screens. You can design an information architecture that holds together across a dashboard, a CLI, and an SDK, and you can articulate why each surface demands different interaction patterns.
• You have strong opinions on what makes a CLI ergonomic, an API discoverable, or a dashboard useful under pressure and you can defend those opinions while remaining open to being wrong.
• You understand frontend engineering well enough to build what you design or ensure it is a reasonable build. You are comfortable with modern web technologies, but your identity is rooted in interaction design, not web development.
• You have internalized an AI‑native development workflow and can demonstrate the productivity gains it enables. You use AI tools to specify, build, and validate not as occasional assistants but as core to how you deliver.
• You have experience with design systems or have built one. You understand how to create reusable patterns that scale across surfaces without becoming rigid.
• You communicate clearly and work effectively with customers, founders, and other engineers. You can translate user research and usage data into design decisions that the team can act on.

This is not a visual design role. We care about aesthetics, but the core challenge is interaction design for a complex domain. If your portfolio is primarily marketing sites, landing pages, or brand…