Frontend Engineer (Web Portal / B2B UI)

About the Role

We’re building a B2B web portal where customers don’t just see numbers—they see whether those numbers are trustworthy right now. The UI needs to answer operational questions fast: “Are we drifting?”, “Is this sensor lying?”, “Why did the system abstain?”, “What changed since yesterday?”

This role owns the customer-facing experience: dashboards, alerts, timelines, spectral/diagnostic views, and explainability panels that turn algorithm decisions into actions.

What You’ll Do

• Dashboards operators actually use: overview pages (site/zone health, top risks, trends, anomalies, trust score).
• Alarms + workflows: alert lists, acknowledgement/snooze/escalation, and “what to check next” guidance tied to failure modes.
• Timeline views: interactive time-series for RH/T, drift, coherence, window validity score, residual energy, with zoom/compare and before/after.
• Spectral + diagnostic views: spectrum/coherence/phase-slope plots that stay fast and readable with annotations (bands, notch depth, confidence).
• Explainability UX: panels that answer: what was assumed, did it hold, what failed, and what receipt backs it up.
• Multi-tenant B2B UX: account switching, roles/permissions, audit trails, exportable reports.
• Performance & reliability: large data rendering, caching, virtualization, graceful loading/error handling.
• Design systems: reusable components (status pills, severity badges, chart scaffolds, empty states) so the portal stays coherent as it grows.

Concrete Deliverables

• A customer home dashboard: fleet/room status, top risks, recent alarms, trust overview.
• An alarm triage flow: click alert → see context → likely causes → recommended checks → acknowledge/escalate.
• A timeline + spectral drilldown page: synchronized cursors, window selection, overlays for validity/coherence, downloadable receipt.
• An explainability panel: “why we trust/don’t trust this” with crisp reasons and links to raw diagnostics.
• A component library for portal primitives: charts, tables, filters, severity badges, audit log viewers.

Required Qualifications

• Strong frontend engineering experience with modern web stacks (typically React + TypeScript or equivalent).
• Experience building data-heavy B2B UIs: dashboards, tables, filters, drilldowns, charting, state management.
• Comfort with interactive visualization (Canvas/SVG/WebGL as needed) and performance techniques (memoization, virtualization, workers).
• Product sense: ability to turn ambiguous operator needs into clean workflows and UI primitives.

Preferred Qualifications

• Experience with observability/monitoring products (alerts, incidents, timelines, single-pane-of-glass UX).
• Familiarity with time-series and signal visualization concepts (not a DSP expert, but comfortable rendering/annotating plots).
• Experience with accessibility and enterprise requirements (SSO, RBAC).
• Design system experience (tokens, component libraries, consistent interaction patterns).

How You’ll Be Measured (First 60–90 Days)

• You ship a first portal slice customers can use: dashboard + alarms + drilldown.
• The UI makes trust legible: users can tell what’s valid vs invalid and why without asking an engineer.
• Performance is solid on real datasets (no UI lockups when loading timelines/spectra).
• Operator workflows improve: fewer clicks to understand an alert, faster time-to-action.

Working Style

• You don’t hide uncertainty—you render it. Validity, abstentions, and failure labels are first-class UI elements.
• You like reducing complex systems to clear mental models (overview → drilldown → evidence → action).
• You collaborate tightly with backend/algorithms to turn diagnostics into customer-readable explanations.

Title & Level

Frontend Engineer (Web Portal / B2B UI) (mid-to-senior; can scale to Staff with ownership of portal architecture), partnering with product, backend, and systems.