Skip to content
AvailablePT

Professional and client work

Data operations console

Internal Liquid AI product that became the source of truth for operations: the stage, owner, deadline and health of each client dataset sit in one place, for the team and for leadership. React 19 interface, Hono API, role-based access with Firebase and insights generated by Gemini.

The problem

Tracking each client's datasets was scattered and lived in Jira, with no view per dataset: the team and leadership could not see in one place which stage each dataset was in, who owned it and whether its deadline was at risk.

Technical decisions

I built the interface in React 19 and the API in Hono, with role-based access control in Firebase. Each stage has a deadline, and the console classifies each dataset as on time, at risk or late. Extraction and pre-normalization start from the interface itself, and Gemini generates insights about the processing queue.

Outcome

Delivered to production at Liquid AI as the source of truth for the client portfolio, with the history of each stage. It started the migration that moves tracking out of Jira. The code and the client names are not public.

Work under confidentiality: the code and the URL are not public.

  • React
  • Hono
  • Firebase
  • Gemini
  • TypeScript

Ready to share.

Let’s talk about your project?

The person answering is the person building it. Tell me what you need and I will explain the simplest path.

I prefer to talk on WhatsApp