• Go to top#top
  • Go to About#about
  • Go to Case studies#cases
  • Go to Experience#work
  • Go to Toolkit#skills
  • Go to Contact#contact
  • Switch to dark themetheme
  • Copy email addressclipboard
  • Download résumé (PDF)pdf
  • Write an emailmailto
  • Open LinkedInnew tab
  • Open GitHubnew tab
Portrait of Sourav Sharma

Senior Frontend Engineer · Dubai, UAE

Sourav Sharma

I build frontends for complicated systems: a bank’s rule engine, live classes for millions of students, a launch‑day checkout.

Open to senior roles · 30 days’ notice · in Dubai

sourav.ts
export const sourav = {  role: "Senior Frontend Engineer",  now: "Team Lead at Synechron",  builtFor: ["Emirates NBD", "BYJU’S", "Ola Electric"],  focus: ["React", "TypeScript", "Performance"],  leadsTeamOf: 4,  engineerSince: 2018,};

About

8 years where the frontend meets a hard backend problem.

I’m Sourav Sharma, a senior frontend engineer in Dubai. I’ve worked on the application where a bank writes its loan and credit-card eligibility rules, a learning portal used by millions of students a day, and a reservation flow that had to hold up through one of India’s largest EV launches.

I care most about the parts that don’t demo well: state that stays predictable, bundles that stay small, and interfaces that make a complicated system feel obvious to the person using it. Most of my work is React and TypeScript, with enough Node, Rails and SQL to own a feature end to end. I lead four engineers across frontend and backend today, and led five frontend engineers at BYJU’S.

  • BYJU’S52→91Lighthouse performance score
  • Emirates NBD−35%Memory use during large calculations
  • BYJU’S+42%Live-class attendance vs the legacy portal
  • Ola Electric100k+Concurrent requests on launch day

Case studies

A rule editor for a bank, and a learning portal for millions of students.

Emirates NBD, via Synechron · 2024 – present

Decision Management System

A bank’s in-house platform for deciding who is eligible for a loan, a credit card or an overdraft.

Role
Team Lead
Team
I lead four engineers, frontend and backend, in a team of 10–12

The system

Every application for a personal loan, credit card or overdraft has to be checked against the bank’s eligibility rules. The Decision Management System is the platform that runs that check. The rules themselves are written and maintained in their own application, the Business Rule Management System (BRMS).

This is a transformation project: the platform is being built in-house to replace the third-party tool the bank has used for these decisions. It is already live for multiple products, with more of the rollout due over the next couple of months.

My part

I lead four of the engineers and work on the BRMS myself. I also handle the non-functional requirements, such as memory use and security.

  • BRMS: I designed the configuration panel from scratch, including the flow-builder canvas where nested risk-eligibility models are composed.
  • Memory: I virtualised the heaviest UI modules. Memory use during large calculations fell by 35%.
  • Security: I set the frontend security baseline for public and private APIs, to meet the bank’s compliance requirements.

The hard part

One rule set holds several rules, and each rule is a chain of if, else if and else branches built from AND and OR conditions. The interface has to let someone write all of it without losing their place.

  • Rule sets: a single rule set can hold several rules.
  • Rules: each rule is a chain of if, else if and else branches.
  • Conditions: one to a row. The first row opens the branch, and each row after it joins with AND or OR.
  • Actions: each branch closes with a then block, the action to take when its conditions hold. One block can assign several values.
  • Drafts: work can be saved as a draft before it is finished.
  • Screens: the same editor fits a phone, a tablet and a desktop.
Rule setDraft
  1. Rule 1

    • if

      • Income meets the threshold
      • andAge is within range
      then
      • eligible = Yes
    • else

      then
      • eligible = No
      • reason = Criteria not met
  2. Rule 2

    • if

      • Employer is on the approved list
      • orSalary is transferred
      then
      • limit band = Standard
    • else if

      • Existing customer
      then
      • limit band = Lower
    • else

      then
      • decision = Refer for review

The shape of one rule set. An illustration, not the bank’s rules.

  • −35%Memory use during large calculations
How it fits togetherSimplified
  1. Rule authors

    Business teams who own the eligibility rules

  2. BRMSMy area

    Flow-builder canvas for nested eligibility models

  3. Decision engine

    Checks each application against the rules

    Applications in: personal loans, credit cards, overdrafts

  4. Eligible, or not

    The answer the bank acts on

BYJU’S · 2021 – 2024

Learn Portal 2.0

The replacement for BYJU’S legacy student portal: live classes, tests and learning videos for millions of students a day.

Role
Senior Software Engineer
Team
I led five frontend engineers

The system

Learn Portal 2.0 replaced the legacy learn portal. It was the web app where students joined live classes, caught up on past ones, took tests, watched learning videos and worked through topics from a very large content library.

Students were grouped into different kinds of batches, and the portal showed each student their own class schedule.

My part

I led the frontend team through the move off the legacy portal. Attendance in live classes was 42% higher afterwards. The parts of the build I’d point to:

  • Performance: I took the Lighthouse performance score from 52 to 91. The four changes behind it are set out below.
  • Assessments: I moved the assessment flow to optimistic updates, so the interface responds at once instead of waiting for the server.
  • Mobile: I built the message bridge that lets the React modules run inside the Flutter mobile shell.

How 52 became 91

There was no single fix. Four things moved the score:

  • Package choices: dependencies were picked with their bundle cost in mind.
  • Lazy loading: a student downloaded only the part of the portal they opened.
  • CDN: static assets were served from a CDN.
  • Service worker: it made the portal a progressive web app. Offline, students could still see the list of videos, though not play them.
  • 52→91Lighthouse performance score
  • +42%Live-class attendance vs the legacy portal
How it fits togetherSimplified
  1. Student

    In a browser or in the mobile app

  2. Learn Portal 2.0My area

    React progressive web app

    • Live classes
    • Past classes
    • Tests
    • Videos
    • Schedule

    Also runs inside the Flutter mobile app, through a message bridge

  3. Platform services

    Ruby on Rails, MongoDB, PostgreSQL

Experience

Four companies, from SaaS to banking. I’ve led teams at the last two.

  1. May 2024 – Present2 yrs 7 mos

    Synechronfor Emirates NBDNow

    Senior Associate, Team Lead

    I lead four engineers across frontend and backend on the Decision Management System, the bank’s in-house platform for deciding who is eligible for a personal loan, credit card or overdraft. It is already live for multiple products.

    Read the case study
    • Designed the configuration panel from scratch, including a flow-builder canvas for nested risk-eligibility models.
    • Cut memory use by 35% during large calculations by virtualising the heaviest UI modules.
    • Set the frontend security baseline for public and private APIs, to meet the bank’s compliance requirements.
    • React
    • TypeScript
    • Node.js
    • Python
    • Oracle
    • PostgreSQL
  2. Oct 2021 – Apr 20242 yrs 7 mos

    BYJU’S

    Senior Software Engineer

    I led five frontend engineers on Learn Portal 2.0, the student portal for live classes, tests and learning videos, used by millions of students a day.

    Read the case study
    • Took the Lighthouse performance score from 52 to 91 through package choices, lazy loading, a CDN and a service worker.
    • Attendance in live classes rose 42% after the move from the legacy portal.
    • Moved the assessment flow to optimistic updates, so the interface responds at once instead of waiting for the server.
    • Built the message bridge between the React modules and the Flutter mobile shell.
    • React
    • Ruby on Rails
    • MongoDB
    • PostgreSQL
    • Flutter
  3. May 2021 – Oct 20216 mos

    Robosoftfor Ola Electric

    Software Engineer L2

    I worked on the reservation and purchase portal for Ola Electric’s scooter launch, one of India’s largest EV rollouts.

    • Fixed race conditions in the reservation pipeline so it held up under 100k+ concurrent requests on launch day.
    • Built the serverless payment integration to PCI-DSS requirements.
    • React
    • Node.js
    • Express
    • MongoDB
    • Redis
  4. Mar 2018 – May 20213 yrs 3 mos

    Social FrontierClearout, Kintegra

    Software Engineer

    I worked across the stack on a small SaaS portfolio: real-time email verification, ad scheduling and lead generation.

    • Built a job queue on Node.js and AWS SQS that processed millions of verification requests a day.
    • Built the customer-facing analytics dashboards for dense, high-volume data.
    • React
    • Node.js
    • Express
    • MongoDB
    • AWS

Toolkit

React and TypeScript most days, with enough backend to see a feature through.

Frontend

  • React
  • TypeScript
  • Next.js
  • Redux Toolkit
  • Zustand
  • CSS
  • Vite / Webpack

Backend

  • Node.js
  • Express
  • Ruby on Rails
  • Python / FastAPI
  • REST & GraphQL

Data

  • PostgreSQL
  • MongoDB
  • Oracle
  • Redis
  • MySQL

Delivery

  • Vitest / Jest
  • Docker
  • GitLab CI
  • AWS
  • Performance budgets

Education

  • B.Tech, Computer ScienceDesh Bhagat University, Punjab, 2016
  • Diploma, Computer EngineeringMehr Chand Polytechnic, Punjab, 2013

Working on something hard? Let’s talk.

Roles
Senior Frontend Engineer, Senior Software Engineer
Location
Dubai, UAE (UTC+4)
Work mode
On-site only
Notice period
30 days
Visa
UAE residence visa. A new employer would need to transfer or sponsor it.
Relocation
Open to relocating abroad with visa sponsorship

Email is the fastest way to reach me, and I usually reply within a day or two. A job description or a few lines about the role is enough to start.

Or send a note