Shaminder
Singh.
I lead frontend architecture for AI-output interfaces — turning raw model output into dashboards, tools, and visualizations that people actually use to make decisions.
Looking for a team building something complicated enough that "just use a component library" stopped being the answer.
Three projects where the interface was the product.
Non-engineers on the sales and publisher teams needed to make real acquisition decisions off raw AI model output — scores, embeddings, and time-series that meant nothing without shaping.
Owned the end-to-end pipeline from REST API → normalized store → composable chart primitives on top of D3, ECharts and amCharts. React + TypeScript with strict typing at the API boundary; charts abstracted so a PM could reconfigure a dashboard without a rebuild.
Chose to build a thin custom chart layer over D3 rather than lean on a single vendor. Slower to start, but the sales team eventually asked for view combinations no OTS library supported — the abstraction paid for itself twice over.
Dashboards used directly by the sales team to drive new user and publisher acquisition. Set frontend code-review and Git standards that are still in use by the current 12-member agile team.
Head of Frontend Development
Own the AI-output-to-interface pipeline end to end. Built dashboards the sales team uses directly to drive new user and publisher acquisition. Mentor a 3-person frontend team and set the code-review and Git standards still in use inside a 12-member agile squad shipping alongside QA against REST APIs.
Freelance / Contract — Frontend & Mobile
Frontend and mobile engineering for Hirewho (Indianapolis), the full end-to-end build of the Bigfyre mobile app solo, and a real-time fleet-tracking web application for an Australian trucking company.
The tools I reach for, grouped by what they solve.
I don't collect logos. This is the working set I've pushed to production, at scale, over the last nine years — with strong opinions about when each is the right choice, and when it isn't.