Banking & Fintech Software Engineering, Built for Regulated Environments

If you're building for a bank, a payments company, or a regulated fintech, you already know what the frontend has to survive. A security review. A compliance audit. A QA team with actual teeth. As part of Eurisko Mobility's engagement with Riyad Bank / JEEL in Saudi Arabia, I worked on three production banking applications end to end. That covered requirements, architecture, implementation, and the CI/CD and documentation a regulated organization needs before it can ship. I now hold agentic AI platforms to the same standard: LLM-driven tools for regulated, executive-facing environments where people have to trust the output. This page covers that work, the stack behind it, and how I work with teams that can't afford a shortcut.

What I've shipped for Riyad Bank / JEEL

Riyad Bank / JEEL: Kids E-Banking

A banking app built for minors, with biometric-grade auth

→Owned authentication and biometrics for a React Native app built for a young, first-time-banking audience. The security had to hold up without ever confusing the user.
→Reworked the loading experience with lazy loading, optimistic UI and clearer loading states, which improved median time-to-interactive.
→Cut mobile API calls by roughly 50% with client-side caching and request de-duplication. On a mobile banking app that saves both latency and cost.

~50%

fewer mobile API calls

Riyad Bank / JEEL: Online Mortgage

Multi-step regulated financial flows, planned and documented before the build

→Led requirements planning for the online mortgage product. It's a multi-step flow, and its financial calculations and compliance constraints leave no room for ambiguity.
→Set the code review standards the rest of the team worked against.
→Documented the features and infrastructure well enough for new team members to onboard against them, then ran that onboarding myself.

Riyad Bank / JEEL: API Management Platform

The frontend layer for a bank's internal API platform

→Defined the frontend architecture and implementation approach for the platform the bank uses internally to manage its API layer. That tooling sits behind everything else the bank ships.
→Enforced testing and CI quality gates so multiple teams could deliver against the platform in parallel without breaking each other.

Riyad Bank / JEEL: WaaS SDK & Internal Platform

One SDK so every team stops rebuilding the same bank flows

→Built the WaaS SDK and shipped it for iOS, Android, Flutter and Web. It packages the bank's shared flows (transactions, cards, authentication and authorization, contact and location access) as a configurable library, with its own configuration documentation. Three internal projects and more than 15 developers built on it.
→The SDK cut per-team setup, integration and repeated requirements explanation from roughly 8 sprints to days.
→Integrated the bank's internal design-system platform, twelve packages in all, into production applications.
→Built a library-agnostic layer that separates the app components from the third-party libraries underneath them. Swapping a dependency used to mean a multi-sprint refactor. After that layer it took days of moving code.
→Defined and maintained the logging, tracking and crash-reporting standards, using Dynatrace, Splunk and Firebase. A regulated organization needs that layer in place before anything ships.

~8 sprints → days

per-team setup time

Stack

Frontend

ReactReact NativeTypeScript

Backend & integration

Java (Spring Boot)Node.js (NestJS)REST APIs

Cloud

AWS Cloud Practitioner (2024)AWS Solutions Architect (2024)

Observability & quality

DynatraceSplunkFirebaseJestReact Testing LibrarySonarQubeGitLab CIJenkins

How I work with regulated clients

01
Requirements & compliance framing first
I scope and document multi-step regulated flows before implementation starts. Discovering them mid-build costs far more.
02
Review standards, written down
I set the code review and testing gates, then hold the team to them. Regulated delivery depends on gates that survive deadline pressure.
03
Documentation someone else can use
I document features and infrastructure well enough for someone else to onboard against them. Banking teams have turnover and audits, and neither one waits for tribal knowledge.
04
Observability from day one
Logging, tracking and crash-reporting standards (Dynatrace, Splunk, Firebase) get defined early. Bolting them on after an incident is too late.

Frequently Asked Questions

Have you worked under a bank's security or compliance review process?+

Yes. The Riyad Bank / JEEL engagements all shipped inside a regulated banking environment: the mortgage platform, the API management platform, the kids' e-banking app, and the internal platform work behind the WaaS SDK. Each one carried the review and documentation standards that come with it.

Can you work with an existing design system or a bank's internal component library?+

Yes, and that's most of what I did at Riyad Bank / JEEL. I integrated the bank's internal design-system platform, twelve packages in all, into production applications. On top of it I built a library-agnostic layer, so swapping an underlying third-party library took days of moving code. Before that layer it was a multi-sprint refactor.

Do you sign NDAs or work under a contractor vetting process?+

Yes. Banking and consulting engagements come with vetting and confidentiality requirements as standard, and I've operated under them for several years without issue.

What's your role on a banking engineering team, frontend only or more?+

Primarily frontend architecture and implementation in React and React Native. I've also worked end to end on requirements planning, CI/CD, documentation and onboarding.

Do you work on-site in KSA, or remotely?+

Both, depending on the engagement. The Riyad Bank work was delivered as part of a Lebanon/KSA engagement model; I'm set up to work remotely or travel for the right project.

Have a banking or fintech product that needs to ship right the first time?

Tell me the scope. I'll tell you honestly if I'm the right fit.

Start the conversation Download CV