Shehab Mohsen / Cairo —
Senior Frontend Engineer — Frontend Lead

Shehab
Mohsen

React Next.js TypeScript Design Systems

I build the systems behind the pixels — frontends that stay fast and maintainable long after launch.

View Work → Download Résumé ↓ Contact
Based in
Cairo, Egypt — remote, UTC+2
Focus
Fintech dashboards, data-heavy interfaces, design systems
Status
Open to senior / lead remote roles
Elsewhere
GitHub  ·  LinkedIn
Selected work, below
01 About

A senior engineer who cares about the parts users don't see.

Portrait of Shehab Mohsen Open to remote
Shehab Mohsen Senior Frontend Engineer · Cairo
● 6+ years ● Senior / Lead ● React · Next · TS ● Design Systems ● Remote · UTC+2

I'm a frontend engineer who enjoys the unglamorous half of the job — the architecture, the tokens, the component contracts, the performance budgets. The work that decides whether a product feels solid six months after launch, or starts to rot.

For six-plus years I've shipped fintech dashboards, admin portals, and design-system-driven apps. I translate ambiguous designs into clean interfaces, raise the floor through reviews and standards, and use AI tooling daily as a multiplier — while owning every decision that ships.

01

Designs, translated faithfully

Pixels-to-production with the detail intact — spacing, motion, and states included.

02

Systems, not screens

Reusable architecture and tokens so the next feature composes from what exists.

03

Quality that compounds

Reviews, standards, and tests that keep delivery fast as the codebase grows.

02 Selected Work

Real products. Shipped, measured, owned.

A few of the frontends I've led. Each one: the problem we started with, the approach I took, and what it actually meant for the people using it.

— 01

Gopay Biller Dashboard

Fintech · Billing

A billing product operators live in all day — rebuilt for speed and clarity.

ProblemSlow, cluttered screens where every extra click compounded across thousands of daily actions.
RoleSenior Frontend Engineer / Frontend Lead
SolutionA rebuild around real operator workflows — dense data tables, predictable billing flows, a component layer tuned for real-time data without jank.
ImpactSmoother day-to-day operations and a foundation the team could extend without rewrites.
ReactTypeScriptMUIGraphQL / ApolloDashboard architecture
billing · operator view
AllPaidReviewOverdue
AccountInvoiceAmountStatus
Acme Co#2048$2,480Paid
Nile Retail#2049$1,120Review
Zayed LLC#2050$3,760Paid
Delta Traders#2051$980Pending
— 02

Amplifidor Platform

Influencer × Brand

A two-sided platform — given a scalable architecture underneath it.

ProblemFeatures shipping faster than the frontend could absorb them — duplicated patterns, inconsistent UI, rising cost to build.
RoleSenior Frontend Engineer
SolutionA scalable React architecture: a shared component layer and workflow primitives so new features composed from existing blocks.
ImpactFaster delivery and a UI that finally felt like one product instead of several.
ReactTypeScriptReusable component architecture
component layer · reusable
CampaignCard
CreatorList
DealSheet
StatsRow
— 03

Kun Admin Portal

Gym Operations

A tablet admin for front-desk staff — designed to be used standing up.

ProblemA desktop-and-mouse UI forced onto tablet staff serving members in motion — fiddly, slow, awkward.
RoleSenior Frontend Engineer
SolutionA responsive, touch-first admin: large tap targets, thumb-reachable actions, layouts that stay fast and legible one-handed.
ImpactA front-desk experience staff could actually rely on during a busy shift.
ReactResponsive UITouch-first UX
tablet · front desk
312
Active
47
Checked in
8
In class
14
Renew due
— 04

UI Library & CLI Tooling

Internal · DevX

A shared UI library and CLI — one source of truth for every app.

ProblemMultiple projects rebuilding the same components differently — inconsistent UI and slow kickoffs.
RoleFrontend Lead
SolutionA custom UI library plus CLI scaffolding — tokens, components, and project bootstrap so apps start consistent and stay that way.
ImpactFaster setup, reusable standards, and one place to fix the UI for everyone.
UI libraryCLI toolingDesign systemsComponent architecture
@shehab/ui · cli
Button6 variants
Inputa11y
$ npx @shehab/ui init app
→ tokens · theme · components
$ @shehab/ui add data-table
— 05

Fatura Portals

Credit · Operations

Four audiences, one shared frontend — portals that fit each team.

ProblemOperations, audit, collectors, and clients each needed their own workflow over the same underlying data.
RoleFrontend Developer
SolutionRole-specific portals on a shared frontend layer — tailored dashboards and tools without duplicating the foundation.
ImpactWorkflows that fit each team instead of forcing everyone through one screen.
ReactTypeScriptVueNode.jsExpress.js
portals · shared core
Shared core Operations Audit Collectors Client
03 Experience

Six years, across fintech, platforms, and operations.

Now — Present

Senior Frontend Engineer / Frontend Lead — BitBang

Owns frontend architecture and quality, leads and mentors engineers, and sets the standards that keep delivery fast and maintainable.

Previously

Senior Frontend Developer — Walaplus

Delivered scalable, reusable React frontends and shared UI patterns for product surfaces serving real users.

Previously

Frontend Developer — Fatura LLC

Built credit-service, audit, operations, and collector portals on a shared frontend layer in React, TypeScript, and Vue.

Previously

Part-time Frontend Developer — Scandiweb

Frontend delivery work alongside a distributed team on ecommerce-adjacent products.

Previously

Frontend Developer — Andalusia Group

Production frontend work for healthcare-adjacent product surfaces.

Early career

Flutter Developer — Creator X

Started in mobile with Flutter — a foundation in cross-platform UI and state that still informs how I design for multiple surfaces.

04 How I think

A frontend that lasts.

Everything below is in service of one idea: code that the next engineer — or future me — can pick up and move forward without flinching.

01

Component architecture

Composable components with clear boundaries and predictable APIs. The shape of the code should make the wrong thing awkward to write.

02

Reusable patterns

Extract once, reuse everywhere. One source of truth beats five near-copies that drift apart over a year.

03

Design systems & tokens

Tokens, themes, and docs that keep the UI consistent and themable — so change is a variable, not a refactor.

04

Reviews & standards

Reviews that raise the floor, not the ego. Readable, tested, maintainable code as the default.

05

Performance

Real budgets and measured metrics. Rendering that stays smooth under the load that actually ships.

06

Developer experience

Tooling and docs that make the whole team faster. DX is a feature the users never see but always feel.

// how I want a feature to read on day one
type Feature = {
  contract: "clear",
  states:   "handled",
  perf:     "budgeted",
  tested:   "yes",
}

// if a teammate can ship on top of it tomorrow, it shipped.
05 Stack

The tools, by role.

Frontend
React.js · Next.js · Vue.js · Nuxt.js · TypeScript · JavaScript
State & Data
Redux · Zustand · Pinia · GraphQL · Apollo Client · REST
Styling & UI
Tailwind CSS · SCSS · shadcn/ui · MUI · Storybook · Framer Motion
Testing & Tooling
Jest · React Testing Library · Docker · Vite · Webpack · GitHub · Bitbucket · Jira
Backend exposure
Node.js · Express.js · NestJS
AI tooling
Cursor · GitHub Copilot · Claude · ChatGPT · Windsurf
06 Beyond the keyboard

Side interests that sharpen the craft.

— Game dev

Building interactive systems

Gameplay logic, loops, and feel — a different lens on state, timing, and feedback that keeps coming back into how I build UI.

— Unreal Engine

Real-time 3D

Materials, lighting, and cinematic sequencing — where performance budgets and visual polish meet at the frame level.

— Pixel art

Detail at the smallest scale

Hand-placing pixels trains an eye for precision and restraint — the same eye I bring to spacing and hierarchy.

— Let's talk

Let's build something that lasts.

shehabmohsen1995@gmail.com
LinkedIn
/in/shehab-mohsen
GitHub
github.com/shehab20089
Based in
Cairo, Egypt — remote, UTC+2