Loading
MA
hello@byanees.comDownload CV
← All work

Platform & analytics · Systems Limited, 2026 – PresentInvestor and Admin Dashboards: One API per Dashboard

Nine dashboards, 4 for investors and 5 for admins, draw their data from another system's APIs. I centralised those calls in our ABP.io backend, so each dashboard makes one call, with a short-TTL cache in front.

Company

Systems Limited

Role

Product Engineer

Period

2026 – Present

Stack

.NET 9, ABP.io

9dashboards: 4 investor, 5 admin
1 callper dashboard from the frontend
how it workshow it works

Nine dashboards, one call each

Pick a step to replay it

our backend · ABP.ioInvestor4 dashboardsAdmin5 dashboardsDashboard APIone per dashboardCacheshort TTLExternal systemits own APIs12fresh?3calls

The problem

The dashboard data lives in another system, exposed through its own APIs. Calling them from the frontend would mean several requests per dashboard, made straight from the browser.

What I built

  1. Centralised the external system's API calls in our own ABP.io backend
  2. Exposed a single API per dashboard, so the frontend makes one call instead of many
  3. Added a caching layer with a short TTL, so repeat loads are fast and the data stays current
  4. Covered all 9 dashboards: 4 on the investor side and 5 on the admin side

Stack.NET 9, ABP.io, Caching and Angular

written upwritten up

Read the engineering note

next case studynext case study

Supervised Agentic Delivery

Agentic AISystems Limited, 2026 – Present

Supervised Agentic Delivery

Three mode agents, picked by the work item. The agent does everything I can undo; merges, migrations, and database writes stay with me. Runs in Cursor, Claude Code, or any other agent.

3mode agents, picked by the work item, in place of an orchestrator

Built withCursor, MCP, LLM agents and Azure DevOps

Read case study

Building something that has to work on the first attempt?

Open to product, full stack & backend roles.

Get in touch
Download CVDownload CV
Let's talk