UI Engineer (Based in CA or NC only)

BlueRock builds application runtime security products. The UI Engineer will harden designer-authored interfaces, develop shared design-system components, and build and test operator-console features that help engineering and security teams monitor and manage protected systems and AI agents.

Responsibilities:

• 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, charts, and time-range and filter controls that work on a demo tenant also have to work on one with billions of events
• Wire UI to the API layer (GraphQL), and work with backend developers when a view needs a new query, field or endpoint
• Own UI test coverage: Vitest for units and Playwright for end-to-end flows, kept green in CI
• Test UI end to end in live, secured environments, with full authentication and authorization, real data and realistic load, before calling it done
• Keep UI work moving across release lines: shipping behind feature flags, and carrying fixes between branches when a release is frozen
• Fix UI bugs across the consoles and the Windows, Mac and Linux clients: layout and overflow, tooltips and popovers, empty and zero states, things that are technically correct and still confusing
• When needed, design new interfaces within the existing design system, and bring them to design for review
• Help set the guardrails that make AI-assisted UI development safe: lint rules, conventions, review checklists, and the instructions our AI coding tools follow

Requirements:

• Must be based in CA (preferably San Francisco Bay Area) or North Carolina
• 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
• 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
• You do need to be strong in TypeScript and React, and willing to read code before changing it
• About 3–5 years building production front ends in TypeScript and modern React: hooks, composition, state that lives at the right level, and an understanding of why a re-render happens
• An end-to-end view of the systems behind the UI. Designing in code gets a feature most of the way to working, and you close the rest of the gap. For you, “done” doesn't stop at the UI working. It means the UI is integrated and shown to work live, in a secured environment with full authentication and authorization, under realistic load
• Integration testing against complex backends. Tests that only run against mock data in a standalone dev stack aren't enough here. You can create, integrate and run tests in live environments to check data validity, load, security and scale, and you keep unit, integration and end-to-end suites green in CI
• Performance instincts for data-heavy UI: pagination, virtualization, server-side filtering, and knowing when a slow page is a query problem rather than a rendering problem
• A track record of reviewing other people's code and improving it without rewriting it
• Git in complex repositories with several active release branches, where a single fix may need to be cherry-picked, ported or graft-merged onto more than one of them. Readable commits, and responding to review without taking it personally
• Hands-on use of AI coding tools in real work, with clear habits for checking what they produce
• CSS that holds up: flexbox and grid, overflow and scroll containers, responsive behaviour, and why a tooltip or popover ends up clipped
• Experience building or contributing to a component library or design system
• Careful attention to visual detail and real interest in UX. Much of this work is noticing that something is two pixels wrong, or that a label is technically correct and still confusing
• Genuine interest in the AI and agentic space, and in the operational and security questions it creates
• Not required: a computer science degree, if your work shows the same rigor
• Experience building or contributing to a component library or design system, ideally with Storybook and design tokens
• Nice to have: Ant Design; GraphQL; ECharts or other charting libraries; design training or a portfolio; experience on a team where designers commit code; writing conventions or instructions for AI coding tools; desktop UI across Mac, Windows and Linux; dense operational tooling such as observability, security or infrastructure products