Frontend (Dashboards / Data Visualization)

You will own the part of the product people actually look at: the dashboards and charts that operators watch 24/7 and that clients judge the whole platform by. Right now the data is there and the screens are not - raw telemetry streams in, and nobody has turned it into something a human can read at a glance, in a control room, at 3 a.m.

Day to day, this means: you take a requirement as rough as "operators need to see status", sketch how the screen should work, design the layout and hierarchy yourself, build it, wire up the live charts, ship it. No dedicated designer in the loop, no mockup handed to you. You own the screen end to end.

What you'll do

• Take over the existing dashboard and raise its visual and UX quality: consistent layout, clear hierarchy, a reusable component structure instead of one-off screens.
• Build the telemetry visualizations: time-series charts of live metrics per asset - updating in real time, zoomable and pannable over large datasets, readable on a control-room wall display.
• Design and implement the operator screens for the 24/7 use case: status at a glance, alarm visibility, dark theme, no ambiguity under stress.
• Establish a lightweight design workflow: quick mockups before implementation, a consistent style guide, reusable chart configurations.
• Work with the backend team on the data contract: what each endpoint must return for the screens, without over-fetching.

Must have

• 4+ years of frontend experience with strong vanilla fundamentals: semantic HTML, modern CSS (grid/flexbox, responsive layout), JavaScript you write without reaching for a framework by default.
• Real data-visualization experience with a serious charting library (amCharts, ECharts, Highcharts, Chart.js, D3): time-series, live-updating data, zoom/pan over large datasets, and the judgement to pick the right chart for the data.
• UI/UX grounding - decisions based on design reasoning, not decoration: layout, visual hierarchy, typography, spacing, colour. You can explain why a screen looks the way it does.
• Ability to work from rough requirements and deliver a designed, working screen without a designer.
• English B2 or above (documentation, day-to-day communication).

Nice to have

• amCharts 5 specifically.
• HTMX / Alpine.js or similar lightweight interactivity.
• WebSockets / SSE for live data streams.
• Figma (or similar) for quick mockups before code.
• Tailwind / Bootstrap, or experience building a small design system.
• Accessibility (WCAG) and dark-mode design - control rooms run dark themes.
• Dashboards for monitoring, industrial, logistics or finance - any data-dense UI domain.

What we care about beyond skills

• Empathy for the actual end user: operators on night shifts, not a demo audience.
• Taste with pragmatism: ships good-enough-and-improving, not pixel-perfect six weeks late.
• Takes design feedback without ego, and can defend a design decision with more than "it looks nice".

Probably not your role if

• You only build inside a framework and can't work close to plain HTML/CSS/JS.
• You implement other people's mockups but can't sketch a screen yourself.
• The charts in your portfolio are default-config demos, never adapted to the data or the reader.
• You design marketing pages, not working screens with high information density.
• You treat operator feedback as "users don't understand design".