ibrahim.samson
available · remote
Senior Full-Stack Engineer · 8+ yrs

Ibrahim Samson

Systems that stay fast when the load gets real.
I design and build high-throughput backend systems and real-time applications across gaming, fintech, and SaaS — with a focus on performance, reliability, and the kind of failure handling you only learn in production.

View the work Get in touch
api_response_time — coreloops optimization ● live trace
p95 before
4,500 ms
p95 after
<1,000 ms
uptime maintained
99.9%
Career impact

Numbers from production, not slides.

1M+
API requests served daily
10,000+
concurrent users supported
$500K+
monthly transaction volume processed
5,000+
active users across products built
60%
production bug reduction on key projects
200+
critical issues caught in code review
45%
load-time reduction via code splitting
99.9%
uptime on real-money gaming platform
Featured work

Problem → resolution → outcome.

Every project below follows the same structure I use in incident reviews: what was broken, what I changed, and what the system looked like after.

Coreloops AI
Engineering Lead
Next.jsReactNestJS GraphQLPostgreSQLDocker NxDrizzle

Problem

Document and accounting workflows were degrading badly. API responses took 4–5 seconds, frontend rendering choked on large datasets, and users were abandoning flows mid-task.

What I did

  • Diagnosed bottlenecks across the stack using profiling and tracing
  • Identified and eliminated N+1 query patterns in GraphQL resolvers
  • Re-architected the data access layer and caching strategy
  • Introduced memoization and virtualization to fix rendering across large datasets
  • Isolated Xero, Sage, and QuickBooks integrations into event-driven worker pipelines with retry and failure isolation

Outcome

  • API response time: 4–5 s → under 1 s
  • UI freezes eliminated when rendering millions of records
  • Integrations now survive partial third-party failures gracefully
Spinbet
Senior Software Engineer
Next.jsReactNestJS PostgreSQLDocker

Problem

Build a real-time gaming platform handling thousands of concurrent users, processing real money securely, under strict compliance requirements.

What I did

  • Designed backend architecture for real-time gameplay at 10,000+ concurrent users
  • Built session and game-state synchronization for multiplayer loops
  • Implemented provably fair gaming algorithms for transparency and compliance
  • Built payment pipelines for high-volume transaction processing
  • Optimized both layers for performance under peak load

Outcome

  • 10,000+ concurrent users sustained in production
  • $500,000+ monthly transaction volume processed
  • 99.9% uptime with measurable retention gains
Pade
Senior Full-Stack Engineer
Next.jsNestJS PostgreSQLSocket.IO

Problem

Businesses juggled disconnected tools for customer communication, invoicing, and payment tracking — fragmented workflows, lost context, slow operations.

What I built

  • WhatsApp Business API integration for real-time customer communication
  • CRM for customer lifecycle and conversation tracking
  • Payment-link generation and automated invoicing
  • Real-time messaging layer with reliable delivery and state recovery
  • Backend services unifying business workflow automation
Blockwinz
Senior Full-Stack Engineer
ReactNestJSMongoDB RedisSocket.IO

Problem

Build a real-time crypto gaming platform with multiplayer interactions, wallet integrations, and fair game mechanics.

What I built

  • Wallet integration layer for deposits, withdrawals, and balance tracking
  • Real-time multiplayer architecture on an event-driven backend
  • Game-state synchronization for live player interactions
  • Event pipelines for full game lifecycle management
  • Scalable structure for provably fair gaming systems
Wevestr & Joble
Senior Full-Stack Developer
ReactNext.jsNestJS PostgreSQLMongoDB

Impact

  • Led development of applications serving 5,000+ active users
  • Cut initial load times by 45% via code splitting and lazy loading
  • Code review standards that reduced production bugs by 60%
Foss Swim School
Senior Full-Stack Developer
AngularNode.js ExpressMongoDB

Problem

Legacy AngularJS application carrying architectural debt, security issues, and 100+ migration blockers — with zero tolerance for downtime.

What I did

  • Migrated AngularJS → Angular 14 with zero data loss
  • Resolved 100+ migration and compatibility issues
  • Fixed security vulnerabilities in the legacy codebase
  • Introduced modern Angular architecture patterns

Outcome

  • Performance improved 10% post-migration
  • Migration completed without downtime
Case studies

Including what didn't work first.

Architecture decisions, bottlenecks, tradeoffs — and the early attempts that failed before the real solution landed. That part matters most.

CS—01 Coreloops AI: from 5-second responses to sub-second performance +

Deep dive into diagnosing multi-layer performance issues across a document and accounting platform.

  • Identified query-level inefficiencies and N+1 patterns
  • Rebuilt caching and data-access strategy
  • Introduced frontend rendering isolation for large datasets
  • Split integrations into event-driven worker pipelines
What initially didn't work
  • Early frontend-only optimizations had minimal impact — the bottleneck was deeper
  • Basic caching introduced stale-data bugs before proper invalidation design
CS—02 Spinbet: scaling real-time gaming to 10,000 concurrent users +

The architecture behind a real-time gaming system operating under heavy, real-money load.

  • Designed WebSocket-based game loop architecture
  • Built session synchronization and state recovery model
  • Handled payment processing under concurrent load spikes
What initially didn't work
  • Naive WebSocket scaling caused memory pressure at high connection counts
  • The early state model lacked a proper reconciliation strategy
CS—03 AngularJS → Angular 14: migration at scale with no downtime tolerance +

A production migration where breaking things wasn't an option.

  • Incremental migration strategy with coexistence patterns
  • Progressive replacement of legacy modules
  • Test-driven validation during every migration phase
What initially didn't work
  • Full-module migration attempts caused instability early on
  • A phased rollout strategy was required to keep production risk acceptable
CS—04 Designing APIs for 1M+ daily requests +

The architectural and operational choices behind high-volume APIs.

  • Eliminated bottlenecks in request pipelines
  • Introduced caching layers and rate-limiting strategies
  • Improved observability for production debugging
CS—05 Real-time systems with Socket.IO: reliability beyond the happy path +

Designing real-time communication that survives reconnects, drops, and scale.

  • Event-driven architecture for messaging systems
  • State recovery and reconnection handling
  • Horizontal scaling considerations for WebSocket systems
Technical expertise

The stack I ship with.

Frontend

  • React
  • Next.js
  • Angular
  • TypeScript
  • Ionic

Backend

  • Node.js
  • NestJS
  • Express
  • GraphQL
  • REST APIs

Databases

  • PostgreSQL
  • MongoDB
  • MySQL
  • Redis

Infrastructure

  • AWS
  • Docker
  • CI/CD
  • Nx Monorepos

Real-Time

  • Socket.IO
  • WebSockets
  • Event-Driven Architecture
About

Failure here is visible immediately.

I've spent 8+ years working on systems where problems can't hide — slow APIs, broken payment flows, unstable real-time behavior. The user feels it within seconds.

So I build for the bad day, not just the demo: systems that stay stable under pressure, degrade gracefully when dependencies fail, and are observable enough to debug at 2am in production.

I've worked across distributed teams in the US, UK, and Europe, collaborating with engineers, PMs, and stakeholders to ship production systems at scale.