Skip to content
All work
Fintech

CIB Digital Banking

Payment features that clear compliance and ship to a national bank's customers.

Role
Software Engineer — requirements, backend services, API specs, UAT
Timeline
Mar 2025 — Present
Stack
  • Node.js
  • NestJS
  • REST API design
  • React
  • React Native
  • Agile & Scrum
  • Jira
Links
Not publicly available

In short

Problem
Business customers and call-center agents needed reliable digital channels without weakening the controls a bank is required to keep.
My contribution
Requirements with product owners and stakeholders, backend services and REST APIs, the API documentation, and UAT through to release.
Key decision
API documentation treated as a deliverable — the shared contract for frontend, QA and the business.
Outcome
Backend services for the Business Banking app (10,000+ downloads), the Unified Call Center Channel for 500+ agents, and the WE Bank portal.

The problem

What was broken, for whom

CIB's business customers needed a dependable mobile banking app, its call-center agents needed one unified channel to serve customers across digital touchpoints, and partner customers needed real-time visibility into payments — without any of it compromising the controls a bank is required to have.

Context & constraints

Banking software has a different failure mode than most software: a bug is not an inconvenience, it is somebody's money. Every feature here went through a heavier requirements and testing process than the equivalent would in a startup, for good reason. Specific internal architecture, data and metrics are not shown here — this is a description of the process and my role in it, not the system.

My role

What I actually did

I work across the stack on the features listed below: gathering requirements alongside product owners and business stakeholders, writing the backend services and REST APIs, documenting the API contract for other teams, and supporting UAT through to release.

Requirements

Requirements, API contracts and sign-off

  • Sat in requirements sessions with product owners and business stakeholders to turn a business ask into functional and technical requirements
  • Worked with QA and frontend engineers so a spec was implementable and testable before a line of code was written
  • Wrote API documentation and technical specifications used as the contract between business and engineering
  • Ran system testing, defect resolution and User Acceptance Testing with the people who would actually sign off the feature

Process

How a feature moves from ask to release

  1. 01

    Requirements

    Functional and technical requirements

    With: Product owners, business stakeholders

  2. 02

    API contract

    API documentation and technical specification

    With: Frontend engineers, QA

  3. 03

    Build

    Node.js / NestJS services, React and React Native

    With: Backend and frontend engineers

  4. 04

    System testing

    Defects found and resolved

    With: QA

  5. 05

    UAT & release

    Sign-off, then release

    With: Business users

A generic view of the delivery process and where I work in it. It shows no internal systems, data or architecture, and no product screens — none are approved for publication.

Key decisions

Trade-offs made on purpose

  1. Decision 01

    Treated API documentation as a deliverable, not an afterthought

    Why: It let frontend engineers, QA and business stakeholders work from the same source of truth instead of reverse-engineering behaviour from a running service.

  2. Decision 02

    Built UAT into the delivery process rather than bolting it on at the end

    Why: Defects surfaced against real business scenarios before release, not after.

Results

What actually happened

  • Built backend services for the Business Banking app, which passed 10,000 downloads
  • Delivered the Unified Call Center Channel to production for 500+ call-center agents
  • Designed and built the WE Bank portal end to end
  • Resolved production bugs by raising code quality and enforcing lint standards across the React Native codebase

Photo

CIB Business Banking app promotion showing account balances, approvals and investment options
Public CIB Business Banking reference image; internal feature screens and architecture are not shown

For the technical reader

Technical implementation

The solution

How it works

Backend services built with Node.js and NestJS, exposed as documented REST APIs, feeding a React and React Native frontend. The WE Bank portal is the clearest example: it integrates backend APIs to surface real-time payment information and transaction updates for customers, replacing what used to require a manual check.

Challenges

What broke, and what I'd change

  • Regulated banking features carry compliance requirements that a typical product feature doesn't — every requirement had to be traceable back to a business or regulatory need, which slows the first pass but prevents expensive rework later
  • Coordinating a spec across product owners, QA and frontend engineers who each read a requirement differently is a real skill, and the biggest lesson has been writing specifications specific enough to remove ambiguity without making them so rigid they can't absorb a late-stage business change

What I learned

The best banking engineers are not the ones who write the cleverest code — they are the ones whose spec a QA engineer, a product owner and a backend developer can all read the same way. That skill transfers to every team I've worked with since.

More work

GlimpseGems home screen with search and mood categoriesGlimpseGems Explore screen with the list and map toggleGlimpseGems saved collection filtered by Favorites, To Visit and Visited
Mobile

GlimpseGems

A mood-based city discovery app, designed end to end — from first sign-in to a saved, shareable list.

Product design

  • Onboarding
  • Search & discovery
  • Map / list
  • Filtering
  • Saved states
  • Gamification

Read case study

Hardware & IoTHonorable Mention — ETH Zurich

RescueTap

One tap — or a detected fall — sends a caregiver your exact location.

  • Python
  • Raspberry Pi 4
  • MPU-6050 / I2C
  • Twilio WhatsApp API
  • +2

Read case study

Contact

Have a problem worth solving?

I'm open to Software Engineer and Product Engineer roles — remote, or relocating. Based in Cairo, EET (UTC+2).