Manish Kumar

Work02 of 06

Dashboards you can share as a link

Data-heavy dashboards on a .NET Core Web API: filterable tables, charts, and filter state kept in the URL, so any view can be bookmarked, reloaded or sent to a colleague.

Company
Cyzerg
Years
2024 to now
Role
Frontend architecture
Stack
TypeScript, Angular, React, .NET Core API
Where this sits: Mid-Level Angular Developer, CyzergSelectedJan 2024 to now
Roles by date
CompanyRoleFromToStack
VenturepactAssociate Software DeveloperJun 2019Apr 2021TypeScript, Angular, Node.js, Express, MongoDB, Redis
CyzergJunior Angular DeveloperApr 2021Jan 2024TypeScript, Angular
CyzergMid-Level Angular DeveloperJan 2024nowTypeScript, Angular, React, Python
regionyearstatusowner?region=all&year=2026&status=open
Figure. a row of filter chips feeding a bar chart, with the active selection highlighted and echoed in a URL query string.

Context

Dashboards get used in meetings. When the filters only live in memory, the view someone wants to discuss is gone the moment they refresh or paste a link.

Approach

The URL is the single source of truth for filters. Tables and charts read from it, controls write to it, and the back button walks through previous views. The same pattern runs this site’s work table: pick a filter above and watch the address bar.

Insight, not only charts

My M.Tech in data science changes what I ask for in a spec: which comparison matters, what the default range should be, and which number deserves to be the biggest thing on the screen.

What shipped

Filterable tables and chart views across the product’s reporting modules, built as reusable TypeScript components across Angular and React.