← Back to site
HomeWorkProjectsStackMethodArtifactsAboutResume
Download PDF

Mohammed Rezaan Riyaz

Senior Frontend Engineer

React · Next.js · TypeScript · 7+ years

  • UAE — open to relocation, onsite & remote
  • Tel+971-56-618-4561
  • Emailrezaan6@gmail.com
  • inlinkedin.com/in/rezaan6
  • GitHubgithub.com/rezaan6
  • rezaanriyaz.com

Senior Frontend Engineer with 7+ years owning large React codebases from architecture through production — hands-on as the primary engineer, and leading frontend teams. I work cross-functionally with design, backend and DevOps, and I'm the one who flags where a design will fight the design system. I make the structural decisions a codebase has to live with, and take responsibility for how it performs and how safely it ships.

2

platforms architected 0→1 — Hobber, Kodez

−40%

page load time, Kodez CMS

~90%

test coverage, Jest + Cypress

40+

production releases shipped

Experience

Hobber · Abu Dhabi, UAE

Jan 2026 — Present

Senior Frontend Engineer — Lead

Marketplace platform for entertainment, recreation, dining & tourism vendors

  • React
  • TypeScript
  • Vite
  • shadcn/ui
  • Feature-sliced architecture
  • REST
  • SignalR
  • Google Maps API
  • Sole frontend engineer on the Hobber vendor platform — the frontend is mine end to end, architected from an empty repository in React and TypeScript on a modular, feature-sliced structure.
  • Shipped seven core platform modules — authentication, vendor accounts, dashboards, scheduling, payouts, integrations, and team access — as independent slices over one shared component layer built on shadcn/ui and Radix primitives.
  • Built the vendor workflows on top: activity management, booking flows, stock scheduling, discount logic, and content management.
  • Set the architectural boundaries the codebase is held to, so a new domain is a new folder rather than a refactor — cross-slice imports blocked by a lint rule rather than a convention, and the contracts type-checked where slices compose.
  • Set up the testing layer from scratch — Vitest for unit and integration, Playwright for end-to-end across the vendor workflows.
  • Built real-time vendor messaging on SignalR against the .NET backend, and the location and routing surfaces on the Google Maps API.
  • Partner with backend and DevOps engineers on API contracts — pinned against Swagger before building — authentication systems, and platform features.

Axinom · Colombo, Sri Lanka (HQ Fürth, Germany)

Mar 2024 — Nov 2025

Senior Frontend Engineer — Lead

Enterprise media technology delivered on the Mosaic platform

  • React
  • Next.js
  • TypeScript
  • GraphQL
  • SCSS
  • Shaka Player / DRM
  • Zustand
  • React Hook Form
  • Zod
  • Azure Blob Storage
  • i18n
  • Azure DevOps
  • Led the frontend team building high-performance web applications for clients including the Goethe-Institut and the Lindau Nobel Laureate Meetings, delivering two client products 0→1 — the Goethe-Institut and Lindau builds — through full development, testing and production release cycles.
  • Reduced page load time ~15% through bundle optimization, lazy loading, and caching improvements.
  • Built on Axinom's Mosaic micro-frontends (Media, Catalogue, Entitlement, DRM) and its APIs for content synchronization and metadata management, rather than hand-rolling media delivery.
  • Implemented secure DRM playback with Shaka Player, building the player interface as our own event-driven components on top of its defaults rather than inheriting browser-native controls and caption rendering — which look and behave differently on every engine.
  • Held playback and layout across a browser matrix spanning Chrome, Edge, Firefox and Safari on macOS, Windows, iOS, iPadOS and Android — including that every iOS browser is WebKit underneath, so a defect reported against iOS Chrome is a Safari defect.
  • Designed i18n in from the start for multi-language experiences across regions.
  • Delivered large media assets out of Azure Blob Storage through the Azure SDK for the Goethe-Institut build — files big enough that the browser could not simply hold one, so the transfer had to be handled rather than requested.
  • Worked directly with designers to translate Figma into pixel-perfect, responsive interfaces, holding SEO and WCAG-aligned accessibility across every customer-facing surface.
  • Owned client-facing technical communication — requirements, feasibility, UX trade-offs, and scope — mentored junior engineers, enforced coding standards, and kept CI/CD stable with DevOps across environments.

Kodez · Colombo, Sri Lanka (HQ Melbourne, Australia)

Mar 2021 — Feb 2024

Senior Frontend Engineer

Enterprise CMS for service management and logistics

  • React
  • TypeScript
  • Storybook
  • Cypress
  • Redux
  • Zustand
  • TanStack Query
  • React Hook Form
  • MUI X Data Grid
  • Node.js / Express
  • Sequelize
  • MySQL
  • Atomic Design
  • AWS
  • Architected and delivered a React CMS from 0→1 to MVP as domain modules with SOLID boundaries — each feature owning its components, state and API access, depending only on the shared UI layer beneath it — then led 40+ production releases on it.
  • Migrated a legacy Laravel, jQuery and Bootstrap application to React and ExpressJS incrementally without freezing client delivery — I had worked in that codebase before replacing it, which is why the seams were obvious — and built Node.js BFF layers with the backend team to reduce API latency.
  • Introduced test-driven development with Jest and Cypress end-to-end gates, driving overall automated coverage to ~90% with every critical path behind the merge gate in CI/CD — which is what let releases stay frequent without a regression freeze.
  • Built a Storybook-based reusable component library that cut frontend development time ~30% across projects.
  • Reduced page load time ~40% through code-splitting, lazy loading, and asset optimization, with assets served from AWS S3.
  • Built REST integrations against the client's enterprise vendor stack — Amtek (Australia), running on Fiserv, Toshiba, NTT DATA, Park Assist and City systems — across a 250+ table schema.
  • Translated Figma designs into responsive interfaces; set frontend standards and ran code reviews as the company scaled from 10 to 60+ people.

RaSoft · Colombo, Sri Lanka

Dec 2018 — Feb 2021

Frontend Engineer

Seed-stage startup — internal systems and web products

  • React.js
  • JavaScript
  • SCSS
  • Agile / Scrum
  • Joined as a Frontend Engineer Intern in December 2018 and moved into the full role in June 2019 — first end-to-end UI ownership at a seed-stage startup.
  • Delivered an Employment Management System from concept to production as the end-to-end UI owner, in React.js, JavaScript, HTML, and SCSS.
  • Rebuilt the company website around responsive layout and accessibility, lifting UX and conversion ~15%.
  • Improved application performance through refactoring and component-level optimization, and ran code reviews and pair-programming sessions to keep the codebase maintainable as it grew.

Core Stack

React & Next.js

  • React
  • Next.js (App + Pages Router)
  • Server Components
  • SSR / CSR / ISR
  • Hydration
  • Suspense
  • Error boundaries
  • Memoization & render isolation

Language & frameworks

  • TypeScript
  • JavaScript
  • Zod
  • Typed API boundaries
  • Angular (legacy systems)

UI, interaction & design systems

  • Design-system fidelity & Figma handoff
  • Design collaboration & handoff
  • Storybook
  • Design tokens & theming
  • Tailwind CSS
  • SCSS
  • Material UI
  • shadcn/ui
  • Radix UI
  • Atomic Design

State & data

  • TanStack Query
  • Redux Toolkit
  • Zustand
  • React Hook Form
  • REST
  • GraphQL
  • Algolia search
  • Cache invalidation

Performance

  • Core Web Vitals (LCP, CLS, INP)
  • Bundle analysis
  • Code-splitting
  • Lazy loading
  • Caching strategies
  • Lighthouse

Testing & quality

  • Vitest
  • Playwright
  • Jest
  • Cypress
  • TDD
  • E2E & integration
  • CI quality gates
  • WCAG accessibility
  • BrowserStack

Security

  • XSS prevention
  • Secure authentication flows
  • Token handling
  • Content validation
  • Secure API integration patterns
  • Dependency risk awareness

Backend & delivery

  • Node.js
  • ExpressJS (BFF)
  • PHP / Laravel
  • MySQL
  • Sequelize
  • MongoDB
  • AWS S3
  • Docker
  • GitHub Actions
  • Vercel
  • Azure Blob Storage
  • Jira
  • Azure DevOps

AI-assisted delivery

  • Agent orchestration
  • MCP integrations
  • Synthetic test data
  • Automated PR & deploy workflows

Education

BSc (Hons) Computer Science & Software Engineering — First Class

University of Bedfordshire · 2022

Dissertation: BlockVote — blockchain-based e-voting on Ethereum (Solidity, Truffle, React, MetaMask)

Higher National Diploma — Computing (Software Engineering)

Pearson · 2020

Higher National Diploma — Mechatronics Engineering

Cardiff Metropolitan University · 2019

Measurement Notes

What each figure is, and where it stops — a count, a reading and a judgement are not the same kind of claim.

2 platforms architected 0→1 — Hobber, Kodez · Count

The Hobber vendor platform and the Kodez CMS, each architected from an empty repository through to production. An empty repository is not an empty problem. Hobber was greenfield in both senses; the Kodez CMS replaced a live Laravel and jQuery application whose feature set defined most of the requirements, and it was migrated onto in steps rather than switched over.

−40% page load time, Kodez CMS · Before/after reading

A before/after read around the code-splitting and asset work. Lab reading, not field data; one contribution among several.

~90% test coverage, Jest + Cypress · Tool report

The overall number on the merged Kodez coverage report. The suite ran as a merge gate in CI — every critical path had to pass before a merge. Not one column — branch sits lower. And the suite was gated, the number was not: a change that kept every test green while dropping the percentage would not have been stopped by CI.

40+ production releases shipped · Count

Production releases shipped on the Kodez CMS across three years — features, defect fixes and database work.