01 · About

Engineer of real-time everything.

Software Engineer focused on full-stack web & mobile systems, distributed backends, applied cryptography, and scalable real-time architecture.

0+
Production Architectures
0+
Game Engines in Riv
0%
End-to-End Encrypted
0.0%
Failover Reliability

Applied Cryptography

Olm Double Ratchet, TOFU key pinning and End-to-End Encryption baked into real products.

Real-Time Distributed Systems

WebSockets, Redis Pub/Sub, multi-cloud failover state machines and write-behind queues.

Offline-First Design

Isar persistence and CRDTs (Yjs + Hybrid Logical Clocks) so apps survive zero connectivity.

System Design

Service-first BLoC architecture, static-analysis guardrails and CI/CD pipelines that keep code honest.

I specialize in building things that stay fast and correct under pressure — encrypted messaging that never leaks, canvases where dozens of cursors dance in sync, backends that fail over across clouds without dropping a beat.

I design and ship production systems across the entire stack: Flutter clients with clean BLoC architecture, clustered Node.js/WebSocket services, Redis-backed queues, and multi-cloud failover backends. I care deeply about offline-first design, cryptographic integrity, deterministic CI guardrails, and developer ergonomics.

System Design & ArchitectureReal-Time Distributed SystemsMobile EngineeringApplied CryptographyCollaborative ComputingCloud Infrastructure
02 · Projects

Things I've built & shipped.

Real systems with real constraints — encryption, concurrency, offline sync and clouds that fail over.

Featured build

Riv

Real-Time E2EE Social & Gaming Platform

FlutterNode.jsWebSocketsRedisFirebaseOlm CryptographyIsar DB
  • End-to-end encrypted messaging via the Olm Double Ratchet protocol with TOFU key pinning
  • Active/passive multi-cloud failover state machines (Render / GCP Cloud Run)
  • Redis write-behind outbox queue batching writes to Firestore
  • Clustered Node.js/WebSocket backend with Redis Pub/Sub for presence + 12+ multiplayer games
  • Offline-first Isar caching, Groq LLM chat via Cloud Functions v2, IAP + AdMob

InkLink

Collaborative Real-Time Canvas

  • Conflict-free concurrent multi-user drawing with CRDTs (Yjs & Hybrid Logical Clocks)
  • Service-first BLoC architecture (UI → BLoC → Domain → Repository) enforced by custom static-analysis guardrails
  • Firebase RTDB for sub-second cursor tracking and live presence; Isar for offline persistence
FlutterBLoCCRDTs / YjsFirebaseSocket.ioIsar DBCI/CD

SyncWave

Real-Time MERN Web Application

  • 1-on-1 chats, anonymous group discussions, AI chat assistance and media sharing
  • Socket.io full-duplex messaging with typing indicators and Web Push notifications
  • JWT + Google OAuth 2.0, Helmet and rate limiting; Multer + Cloudinary media storage
ReactNode.jsExpress.jsMongoDBSocket.ioJWTCloudinary
03 · Skills

The toolbox.

From pixel-perfect Flutter UIs to clustered Node.js backends and everything wired in between.

Languages

DartJavaScript (ES6+)PythonJavaC++C#SQLHTML/CSS

Mobile Development

FlutterBLoCProviderIsar DatabaseClean ArchitecturePlay Store Deployment

Web & Backend

ReactNode.jsExpress.jsRESTful APIsWebSockets (ws, Socket.io)Redis (Pub/Sub)

Cloud & Databases

Firebase (Auth, Firestore, RTDB, Cloud Functions, FCM)MongoDBCloudflare R2Cloudinary

Specialized Domains

End-to-End Encryption (Olm/Double Ratchet)CRDTs (Yjs)Offline-First DesignStatic GuardrailsCI/CD
FlutterNode.jsWebSocketsRedisFirebaseMongoDBReactIsar DBSocket.ioExpress.jsCloud FunctionsFirestoreFlutterNode.jsWebSocketsRedisFirebaseMongoDBReactIsar DBSocket.ioExpress.jsCloud FunctionsFirestore
Olm / Double RatchetYjs CRDTsHybrid Logical ClocksBLoCJWT + OAuth 2.0Groq LLMCloudflare R2GitHub ActionsStatic AnalysisMulti-Cloud FailoverOlm / Double RatchetYjs CRDTsHybrid Logical ClocksBLoCJWT + OAuth 2.0Groq LLMCloudflare R2GitHub ActionsStatic AnalysisMulti-Cloud Failover
04 · Contact

Let's build something real-time.

Engineering roles, high-impact projects, or a hard technical challenge — my inbox is open.

Direct lines

Usually responsive within 24 hours.

Based inRemote / Worldwide · UTC+5
Or use:

Protected by rate limiting · Max 3 messages per day