Senior UI/UX Engineer

Project description

Our Client is a leading global financial markets infrastructure and data provider. Their purpose is driving financial stability, empowering economies and enabling customers to create sustainable growth. The platform is a strategic automation and operational resilience initiative, giving operations and leadership teams a single, trusted view over hundreds of automated checks and jobs that used to be run and tracked manually. The UI/UX Engineer owns how that operational picture is presented: from executive summary through to individual check evidence, across a growing set of independently built, permission-gated product areas. We're building this on a Node.js backend serving multiple independent frontend applications, with a shared internal design system and clear rules about which team owns which part of the product.

Responsibilities

• We are looking for UI/UX Engineer to own frontend delivery within a large modular operations platform, building accessible, design-system-driven interfaces across multiple independently built product areas. Comfortable working directly with product and operational stakeholders to translate ambiguous requirements into shipped, WCAG-compliant UI, while respecting strict ownership boundaries between teams and clearly defined API contracts. Able to design a best-in-class experience for several different user types (e.g. executives, operations analysts, on-call engineers) even when requirements aren't fully defined up front, using judgement to fill the gaps rather than waiting for a complete spec.
• Taking ownership of a module's end-to-end UI/UX, from ambiguous requirements to shipped, accessible interface
• Engaging directly with operations or business stakeholders to understand workflows and translate them into interface design
• Designing best-in-class interfaces for multiple distinct user types (e.g. leadership, operations, engineering) from partial or evolving requirements, making sound design decisions without waiting for fully specified requirements
• Building production frontend using the shared internal design system and each product area's own conventions
• Reducing operational risk and confusion by making status, exceptions and evidence clear, truthful and accessible

SKILLS

Must have

• Mandatory Competencies: 1. Ownership (CRITICAL) Has taken ownership of a UI/UX delivery from concept to production. Drove work independently with minimal direction. Shipped interfaces that replaced manual reporting, ad hoc dashboards or spreadsheet-based views. 2. Stakeholder Engagement (CRITICAL) Comfortable reaching out directly to operations or business teams. Proactively gathers requirements and iterates on design based on direct user feedback rather than waiting for a spec to be handed over. Documents inputs, states and edge cases with the people who do the work. 3. Accessible, Design-System-Driven UI (CRITICAL) Has built production UI (not prototypes) using a shared component library and design tokens. Worked within clear boundaries between product areas — no shortcuts that reach into another team's interface, styling or state. 4. Designing for Multiple Personas Without Full Requirements (CRITICAL) Can design a best-in-class operations UI that serves several different audiences (e.g. leadership summary views vs. hands-on operational detail views) with different needs, comfortable making sound design judgement calls when requirements are incomplete, ambiguous, or still evolving, rather than needing a fully black-and-white spec before starting. 5. Process Understanding & Interaction Design Can understand operational workflows and identify how status, exceptions and evidence should be surfaced. Works with ops teams to simplify complex information. Designs maintainable, observable, truthful loading/empty/error states. Mandatory Technical Skills:
• Languages: JavaScript, TypeScript, HTML/CSS, JSX
• Frontend Frameworks: React 18, native Web APIs, consistent navigation and layout patterns shared across product areas
• Design System: Radix UI, Base UI, ShadCN-style primitives, class-variance-authority, clsx, tailwind-merge, shared internal component library used across all product areas
• Styling: Tailwind CSS, strict CSS naming conventions to prevent style clashes between product areas, design tokens, CSS custom properties
• Build Tooling: esbuild, Vite, Node.js build scripts, automated build and deployment of independent frontend bundles, asset manifests, caching strategies
• Accessibility: WCAG 2.x, ARIA semantics, roving tabindex, focus management, reduced-motion support, screen-reader testing
• Data Visualization: Grafana Scenes, RxJS, Recharts, timeline and execution-history style visual components
• Architecture: Clear boundaries between product areas, dynamic loading of features on demand, consistent lifecycle for loading/unloading screens, centrally managed navigation and browser history, routed subpages with canonical breadcrumbs
• API Integration: REST APIs, runtime response validation, request cancellation support, purpose-built, need-to-know API responses (never exposing full backend data to the browser)
• Security & Compliance: CSP, Trusted Types, feature visibility controlled and enforced by the backend, not just hidden in the UI, no client-side credential handling
• Testing: Node test runner, accessibility assertions, component/contract tests, automated checks to keep frontend and backend feature lists in sync
• Collaboration: Design handoff, stakeholder demos, cross-team alignment, documentation-first change management

Nice to have

• Grafana / Scenes dashboarding experience (used by our monitoring product area) • Financial services or regulated environment experience • Operational resilience / SRE concepts (status semantics, alerting, monitoring dashboards) • Data visualisation for time-series or execution-timeline data • Experience contributing to or maintaining a shared component library across multiple products • Modernising manual/spreadsheet-based reporting into a web UI