software engineer

I work mainly on backend systems, from API design and service architecture to performance tuning and reliability.

I enjoy complex problems where distributed systems, observability, and resilient infrastructure all meet in production.

I like building systems that keep working under real pressure: high traffic, noisy dependencies, and tight latency budgets.

And yes, I love remote work so much my commute is just walking from my bed to my "global headquarters" (the coffee machine).

terminal

$ whoami
Mohammed Sayed

$ current_focus
distributed systems
backend architecture
edge infrastructure
developer tooling

$ uptime
22 years

$ location
somewhere between cairo and a cloudflare region

$ coffee_status
critical dependency

current stack

architecture principles

I prefer systems that are simple to reason about, easy to observe, and difficult to break.

I care deeply about reliability because production systems eventually fail in ways documentation never explains.

• boring technology scales surprisingly well
• observability is part of the product
• latency is a feature
• queues solve more problems than people think
• reliability matters more than clever abstractions
• infrastructure should be understandable at 3am
• developer experience affects product quality directly

now

Currently exploring and building around:

• distributed infrastructure on edge runtimes
• scalable chat and realtime systems
• workflow orchestration systems
• backend observability tooling
• AI-assisted developer workflows
• durable event-driven architectures

recent writing

• why boring infrastructure usually wins
• scaling websocket presence systems
• designing reliable background workers
• observability for small engineering teams
• edge runtimes beyond hype
• building systems that survive production traffic
• what actually matters in backend performance

You can find my writing here.