All work

Enterprise internal tools

Enterprise Sales Reporting and Field-Operations Platform

I built major frontend and backend parts of a bilingual enterprise reporting platform covering sales, stock, product, customer, credit, visit, commission, and field-location workflows.

Role
Full-Stack Product Engineer
Period
2024

Enterprise reporting system

Operational data made usable across web and mobile

Simplified system map

Operational SQL data

Identity and roles

Report service layer

Bilingual reporting UI

Generic evidence-led architecture; no internal reports, data values, identities, or deployment details are represented. Diagram connecting operational SQL data and identity systems to report services, a bilingual web interface, map context, and controlled mobile access.

Context

Private client platform

Role

Full-Stack Product Engineer

Product type

Enterprise internal tools

Core capability

Next.js

Product context

Making established operational data usable without replacing its source systems

Operational data lived behind an established SQL environment and needed focused report views with detailed filtering, totals, pagination, user roles, English/Arabic behavior, location context, and controlled mobile access.

Attribution anchor

What I was responsible for

I worked across the reporting interface, API and service layer, authentication and authorization integration, bilingual behavior, mapping, administration, and a mobile wrapper. The source data system and complete platform were shared client infrastructure, not something I claim to have created alone.

Selected scope

Selected contributions

  1. 01

    Implemented 12 report controllers and services with shared filtering, totals, dates, branch and supervisor context, validation, and error handling.

  2. 02

    Built complex filter forms, paginated tables, URL/query state, totals, and API-backed report pages in Next.js.

  3. 03

    Delivered English/Arabic localization and RTL behavior throughout the application.

  4. 04

    Integrated SQL Server reporting data, PostgreSQL/Prisma administration, Active Directory, JWT authentication, and role-based access.

  5. 05

    Added field-location map views and packaged a controlled Expo WebView application for mobile access.

  6. 06

    Fixed authorization, cache, API, and cross-layer integration behavior during delivery.

Evidence, not reconstruction

System view

A simplified view of verified responsibilities and system relationships. It does not reproduce a private or historical interface.

Enterprise reporting system

Operational data made usable across web and mobile

A generic system view with all client, employee, customer, location, and report values removed.

Simplified system map

Operational SQL data

Established reporting sources retained behind the application boundary.

Input

Identity and roles

Active Directory, JWT, administration, and role-based access.

Input

Report service layer

Shared filters, totals, validation, dates, and organizational context.

Process

Bilingual reporting UI

Typed filters, URL state, paginated tables, totals, and RTL behavior.

System

Field-location context

Controlled map views connected to authenticated reporting workflows.

System

Controlled mobile access

Packaged access for authorized field and operational use.

Output

Verified relationships

  • Operational SQL dataReport service layer
  • Identity and rolesReport service layer
  • Report service layerBilingual reporting UI
  • Report service layerField-location context
  • Bilingual reporting UIControlled mobile access
  • Field-location contextControlled mobile access
Generic evidence-led architecture; no internal reports, data values, identities, or deployment details are represented. Diagram connecting operational SQL data and identity systems to report services, a bilingual web interface, map context, and controlled mobile access.

Engineering judgment

Selected technical decisions

Decision 01

Kept reporting logic in explicit server-side services while sharing filter and totals behavior across report families.

Decision 02

Used URL state and typed form validation to make complex report views repeatable, navigable, and easier to troubleshoot.

Decision 03

Preserved the organization's existing identity and data systems through integration instead of replacing them for the sake of a new stack.

Technology context

  • Next.js
  • React
  • TypeScript
  • TanStack Table
  • React Hook Form
  • Zod
  • next-intl
  • Mapbox
  • Express
  • SQL Server
  • PostgreSQL
  • Prisma
  • Active Directory
  • JWT
  • Expo

Delivered capability

A coherent web, API, identity, reporting, mapping, and mobile-access layer around existing operational data, without exposing the underlying systems directly.

Internal tools · Data-heavy interfaces · Identity integration

Need to turn complex operational data into a usable internal product?