Software Engineer · SDE-2Making continuously changing data feel simple and responsive.
Built the frontend experience around live tracking, operational dashboards, data visualization, reporting, and continuously changing data.
SafetyConnect brought together live location data, operational metrics, reports, trends, and safety information into a single frontend experience.
The challenge was not simply displaying data. The interface had to remain responsive while data changed, APIs evolved, dashboards became more complex, and users moved between different views.
Built reusable dashboard structures that could render different datasets, scopes, charts, tables, and operational views without duplicating the same logic across every screen.
Built reusable visualization components for charts, trends, statistics, and operational data.
Built the frontend experience for continuously changing location data and live map tracking.
Built reporting interfaces that transformed collected operational data into readable summaries and visual reports.
Built the client-side data flow around caching, request deduplication, invalidation, timeouts, cancellation, and refresh behavior.
Driver and employee positions were updated continuously.
As location updates became more frequent, updating the map directly for every change made the frontend increasingly expensive to render.
Too many updates → too much rendering → map lag
The problem wasn’t the map itself. The problem was the amount of work happening between incoming location changes and what the user actually needed to see.
The map could continue receiving changing location data without making the interface feel overloaded or noticeably laggy.
The dashboard received data in different response structures as the API evolved.
Instead of allowing every visualization to understand every possible response shape, the frontend needed one predictable data model.
I centralized response-shape handling so dashboard components did not need to know where the data came from or which response structure was returned.
Visualization components could remain focused on rendering while the data-normalization layer absorbed API-shape differences.
Multiple dashboard interactions could trigger the same data request more than once.
Reduced redundant network activity while keeping the dashboard responsive and the displayed data aligned with the user’s current view.
The dashboard could operate at different scopes — global, region, and branch — but the underlying data structures were not always identical.
The UI still needed to present the same conceptual information.
Instead of duplicating dashboard logic for every scope, I handled the differences during data preparation and mapped the results into a common structure consumed by the visualization layer.
The same dashboard components could work across different scopes without duplicating visualization logic.
The dashboard was responsive and scrollable on screen, but exporting it to PDF introduced a completely different rendering problem.
A simple screenshot could crop content, miss scrollable sections, preserve visual effects incorrectly, and produce poor page boundaries.
The full dashboard could be exported as a structured multi-page report instead of a cropped screenshot of the current viewport.
A reusable chart component had to work with different chart types, different amounts of data, different screen sizes, and different label densities.
A configuration that works for ten categories may not work for fifty.
The same visualization system could remain readable across different datasets and viewport sizes without creating separate chart implementations for every case.
Start with what the user is actually experiencing.
Follow the data and rendering path until the source of the problem becomes clear.
Move complexity away from the UI whenever possible.
A frontend can receive more information than the user actually needs to see at once.
Good frontend engineering is often about deciding what to process, what to cache, what to render, and when to update.
Working on SafetyConnect changed how I think about the boundary between data and interface.
The interface still needs to feel calm.