UI Engineer (Based in CA or NC only)

Mission: Live at the intersection of app runtime & security. Protect applications in a fundamental way so that developers can build great application services and not be constantly looking over their shoulder. BlueRock is changing the landscape of App runtime security. The role Location: Must be based in CA (preferably San Francisco Bay Area) or North Carolina You will work alongside BlueRock's product designers and the control plane development team on our operator consoles. These are the React front ends that engineers and security teams use to manage large fleets of protected nodes, see what AI agents are actually doing across those fleets, and author the policy that constrains them. The domain is AI and agentic systems, seen from the operations and security side. When an agent calls an MCP server, spawns a subagent, runs a shell command in a sandbox, or burns $40 of tokens in an afternoon, our UI is where a person sees it, understands it, and decides what to allow. So the interesting problems are visibility problems (how do you show a thousand agent sessions so someone can find the one that matters?) and control problems (how do you author an enforcement policy without a mistake taking production down?). This is a mid-level role. We expect about 3–5 years of professional front-end experience, or equivalent work that clearly shows the same judgment. The ideal candidate is passionate about user experience, design, and AI-assisted software development, with a demonstrated grounding in engineering best practices. The title says UI, but the work doesn’t stop there: you’ll work closely with our backend services, and a feature is finished when it’s proven working live, not when the screen looks right. Working with design delivered as code At BlueRock, product designers design and collaborate in code. Instead of handing off static mockups, they build working UI with AI coding tools, against real data, and open merge requests. Iteration happens so quickly that it has outpaced our capacity for robust engineering collaboration and review. This role closes that gap. You will collaborate directly with product designers and backend developers to keep UI development fast, by bridging the gap between vibe code and high-quality, sustainable, well-tested code. Some days that means reviewing and hardening a designer's branch so it can merge. Other days it means building the shared components, tests and guardrails that make the next branch need less hardening. Beyond reviewing and hardening code, you'll help shape how it gets made. Working with designers and the AI tools they use, you'll turn what each review teaches us into shared components, conventions, tests and agent instructions. Over time the whole practice becomes more predictable, and each new branch arrives closer to production-ready. Roles and collaboration Software development roles are blurring more than ever. This role reports to product design, with API and data-layer guidance from our control plane engineering lead. You must be attuned to the perspectives of both UX/Design and Engineering, acting as a bridge between the goals and priorities of both sides, while ultimately deferring to UX/design partners on matters of style, copy, and information architecture. In practice: when a designer's branch makes a choice about layout, copy or flow, you protect the intent and fix the implementation. When the implementation can't support the intent, because of performance, data shape or maintainability, you say so early and bring options rather than quietly changing the design. What you'll do Review designer-authored merge requests and bring them to production quality: structure, types, tests, accessibility, performance, and both light and dark themes. Turn one-off UI from fast iteration into shared, documented components in our design system and Storybook, and migrate the apps onto them. Make data-dense views hold up at real scale. Dashboards, tables, chart