Skip to content

Riyadh, Saudi Arabia

Open to senior frontend & full-stack roles

Hello, I'm Jamal

I build digitalexperiencesthat feel alive.

Senior software engineer crafting scalable, high-performance digital experiences with clean architecture and obsessive attention to detail.

Role
Front-End Team Leader
Focus
Interfaces · Systems · Payments
Jamal Barhoum — Front-End Team Leader. An interactive three-dimensional scene: a glowing core representing Jamal's engineering practice, orbited by the technologies and disciplines he works in, with source code flowing through the core and emerging as a running interface.

Selected work

Built and shipped.

Four production platforms, each carried from the interface down to the services and data behind it.

Production systems

Internal products. No public URL — the case study is the artefact.

012024 — 2026

Payment Operations

Full-stack owner · checkout to settlement

Internal product
  • Next.js
  • TypeScript
  • NestJS
  • Apple Pay
  • Tap
  • PostgreSQL

Production payment flows for an operations platform — from the checkout surface a customer touches to the backend orchestration that has to agree with the bank.

The problem

Payments fail in more ways than they succeed. A checkout that only handles the happy path is a support queue waiting to happen.

Architecture

  • Apple Pay and Tap integrated behind one internal payment contract, so the interface never branches on the vendor
  • Every transaction resolves to a terminal state — retries, timeouts and vendor callbacks all land somewhere an operator can read
  • Status handling designed around reconciliation first and the interface second
  • Credentials and confirmation stay server-side; the client is never trusted with either

Result

Live payment operations across Apple Pay and Tap, with a recovery path behind each failure state instead of a dead end.

022024 — 2026

ERP Platform

Frontend architecture · full-stack delivery

Internal product
  • React
  • Next.js
  • NestJS
  • PostgreSQL
  • Zoho
  • Deluge

Enterprise resource surfaces connecting finance, operations and internal workflows for teams who live inside the system all day.

The problem

ERP screens accumulate. Without a shared structure each module drifts into its own dialect and the product stops behaving like one system.

Architecture

  • Composable primitives and shared tokens, so a new module inherits the system instead of reinventing it
  • Module boundaries drawn around business domains rather than around screens
  • Zoho and Deluge automation where the operational reality already lived there
  • Typed contracts across the client/API boundary so business rules stay honest on both sides

Result

A modular platform where cross-department data stays visible and a new workflow ships without a redesign.

032024 — 2026

Point of Sale

Frontend lead · realtime surfaces

Internal product
  • React
  • TypeScript
  • Node.js
  • Socket.io
  • MongoDB

A counter-speed point-of-sale interface, where hesitation is measured in a queue of waiting customers.

The problem

Retail tempo is unforgiving. The interface has to keep up with the cashier's hands and stay honest about stock in the same moment.

Architecture

  • Interaction paths tuned for keyboard and touch tempo ahead of visual density
  • Realtime stock awareness over Socket.io so the counter and the back office never disagree
  • Transaction and receipt flows built to survive an interrupted connection
  • Hardware-aware layouts that hold on fixed terminals and tablets alike

Result

A point-of-sale surface that keeps the counter moving and stays accurate under load.

042025 — 2026

Sales & Purchasing

Full-stack · both sides of the trade

Internal product
  • Next.js
  • Redux
  • NestJS
  • PostgreSQL
  • REST

Sales and procurement in one system: quoting, ordering, inventory movement, and the supplier and customer flows that pull against each other.

The problem

Buying and selling touch the same inventory from opposite directions. Model them separately and the numbers quietly drift apart.

Architecture

  • One inventory model serving both the sales pipeline and the purchasing workflow
  • Order lifecycle expressed as explicit states rather than a spread of boolean flags
  • Operational dashboards built on the same contracts the transactional screens use
  • Relational persistence chosen for the joins this domain actually runs

Result

Sales and purchasing operating against a single source of truth, with dashboards the decision-makers can trust.

Engineering depth

I build the interface and the system behind it.

One request, traced from the surface a person touches through to the row that finally changes. Move your pointer across the map.

  1. 01

    Interface

    What the user touches. Composable primitives, responsive systems, and motion that clarifies hierarchy instead of decorating it.

    • React
    • Next.js
    • Design System
  2. 02

    State

    Local UI state stays local. Only what must be shared gets lifted, and the tool is chosen by complexity rather than habit.

    • Redux
    • Zustand
    • Context
  3. 03

    Contract

    The typed boundary. Every request is validated at the edge so malformed data never reaches business logic.

    • TypeScript
    • REST
    • Validation
  4. 04

    Services

    Business rules and orchestration. Multi-write operations run inside a transaction, so a half-finished state can never be persisted.

    • NestJS
    • Express
    • Transactions
  5. 05

    Identity

    Who is asking, and what they are allowed to do. Enforced on the server for every route and never inferred from the interface.

    • JWT
    • Sessions
    • Permissions
  6. 06

    Realtime

    Live channels for surfaces where stale data is simply wrong data — counters, stock levels, and collaborative views.

    • Socket.io
    • Events
  7. 07

    Payment rails

    Money leaving the building. Idempotent, reconciled, and designed so a vendor timeout is a state to handle rather than a bug to chase.

    • Apple Pay
    • Tap
    • Reconciliation
  8. 08

    Persistence

    Relational or document, chosen by access pattern. Schemas designed for the queries the product actually runs.

    • PostgreSQL
    • MongoDB
    • Schema Design

Across every layer

Performance

Transform and opacity over layout. Budgets treated as a release criterion, not a retro item.

Scalability

Module boundaries that let a system grow sideways without asking for a rewrite.

Delivery

Sprint cadence, CI-minded deployment, and technical direction owned rather than delegated.

Quality

Accessibility, typed contracts, and code review treated as teaching rather than gatekeeping.

Technical ecosystem

The tools, and what they are for.

Grouped by the role they play rather than by a logo wall. Select a node to see where it has actually been used.

Frontend

Frontend

React

The default for every interface I have shipped since 2023, from ERP surfaces to a point-of-sale counter.

Working with it since
2023 · 3y
Used in
ERP PlatformPoint of SaleTalaqiJoyJoy StoreHomeJoJo Recipes

Hover a node

About

Not a resume. A working system.

I write the code that ships, and I own it after it ships.

I decide where the boundaries go before the first component exists.

I set technical direction, review the work, and raise the floor for the team.

I care how it feels, because a system nobody enjoys using is an unfinished one.

I build professional websites and software systems end to end. My foundation is the MERN stack and my focus today is frontend architecture — React and Next.js at production scale — without giving up the backend half of the problem.

That combination is the point. I have shipped payment operations, ERP surfaces, point-of-sale systems and sales and purchasing platforms, which means the interfaces I design stay honest to what the system underneath can actually do.

How I work

Systems over screens

I don't only style pages. I engineer the systems that hold the business logic behind them.

Frontend, with depth

Specialising in frontend, backed by full-stack experience, so the interface never promises what the API cannot deliver.

Lead by craft

Reviews, mentoring and shared primitives raise the floor for everyone building beside you.

Performance is a feature

Visually impressive has to also be technically impressive: measurable, accessible and fast.

Trajectory

How I got here.

  1. 2026

    CleanLife

    Front-End Team Leader

    2026 —

    • Lead frontend architecture across Next.js and TypeScript products, and guide full-stack delivery
    • Own sprint planning, code reviews and technical direction in an Agile cadence
    • Oversee payment integrations, ERP and point-of-sale surfaces, and commerce workflows
    • Next.js
    • TypeScript
    • NestJS
    • PostgreSQL

  2. 2024

    CleanLife

    Full-Stack Developer

    2024 — 2026

    • Built websites and production systems spanning React and Next.js frontends with Node backends
    • Delivered end-to-end payment operations and business platform features
    • Shipped ERP, point-of-sale and sales and purchasing experiences on reusable UI
    • React
    • Node.js
    • Express
    • MongoDB

  3. 2023

    MAP

    Front-End Developer

    2023 — 2024

    • Built data-driven React interfaces against REST APIs
    • Managed complex state with Redux across multi-step flows
    • Shipped responsive, cross-browser layouts with Material UI and Bootstrap
    • React
    • Redux
    • Material UI
    • REST

  4. 2023

    Tri-United Construction

    Front-End Developer · Freelance

    2023 — 2024

    • Designed and built the company website end to end
    • Owned performance, responsiveness and the full deployment pipeline
    • JavaScript
    • CSS
    • Deployment

  5. 2023

    Meraki Academy

    Full-Stack Development Bootcamp

    2023

    • 400+ hours of project-based training across React, Node.js, MongoDB and PostgreSQL
    • The MERN foundation everything since has been built on
    • React
    • Node.js
    • MongoDB
    • PostgreSQL

Contact

Have a systemworth building?

Open to senior frontend and full-stack roles, and to product work where the interface and the system behind it matter equally.

Email
jamallazeeez@gmail.com
Phone
0564324552
Based in

Riyadh, Saudi Arabia