Nexa TMS AI
Transport management, operations and financial reporting.
Overview
A transport management system with React interfaces and Go services. The role developed from Frontend Lead during the MVP to Senior Full-Stack, covering dispatch workflows, maintenance, reports and exports.
The challenge
Dispatch, maintenance and finance share business records. Fractional quantities, driver assignments by trip date and differences between load pay and driver gross affect the accuracy of reports.
Engineering decisions
Trace rules across the stack
Related frontend and backend changes cover preserving fractional maintenance quantities, resolving driver assignments by trip dates, and exposing differences between load pay and driver gross in reports and exports.
Keep module boundaries useful
Frontend modules separate domain contracts, data mapping, application hooks and presentation. Typed API integration helps operational screens follow the same business definitions as backend services.
Make access contextual
The system scopes access to the active company and the purpose of a workflow. Interfaces can offer the minimum information needed for a selection without treating that as permission to view an entire profile.
What it delivers
Contribution across frontend architecture, Go services, operational interfaces and financial reporting. The scope includes consistent quantities, historical driver assignments and payment breakdowns in reports and exports.
Sources & context
Role progression is owner-reported; frontend and backend contributions are supported by source and author-attributed Git history. This case study describes my contribution within a team.
Nexa TMS AI