The engineer behind the systems.
Tech lead and backend engineer specialising in NestJS and Go. I design and build microservices, APIs and data-heavy platforms, from GIS systems on PostGIS to event-driven services on RabbitMQ, gRPC and Kafka, with a focus on clean, testable code and architecture that scales.
- Name
- Mustafa Saudi
- Roles
- Tech Lead · Senior Software Engineer · Backend Architect · Technical Consultant
- Location
- Giza, Egypt · remote worldwide
How I think about engineering
- 01.1
Boring is a feature
Production systems should be predictable. I prefer proven tools and simple designs, and add complexity only where it pays for itself.
- 01.2
Decisions are written down
Every significant choice gets a short record of the options and the reasoning, so the team can revisit it with context.
- 01.3
Failure is designed, not discovered
Timeouts, retries, idempotency and observability are part of the first version.
- 01.4
Business outcomes first
Technology is chosen for what it does for the product and the team, not for its novelty.
What I work on
Most of my work sits where business requirements meet backend architecture: SaaS platforms that serve many customers safely, integrations that keep data consistent across systems, realtime and event-driven services, and the cloud infrastructure they run on. More recently that includes AI agents and integrations built with the same engineering discipline as the rest of the backend.
I take on client projects and consulting engagements, and I am open to conversations about senior engineering, tech lead and architect roles.
From problem to production.
A predictable path from the first conversation to software running in production, adapted to the size of the engagement.
- 01 / DISCOVERY
Understand
Understand the business challenge, users and technical requirements.
- 02 / ARCHITECTURE
Design
Evaluate constraints and design the appropriate system, with trade-offs written down.
- 03 / IMPLEMENTATION
Build
Build maintainable software in small, tested, deployable increments.
- 04 / VALIDATION
Verify
Test behaviour, reliability, security and performance against the requirements.
- 05 / DELIVERY
Ship
Deploy, document and hand over, so your team owns the result.
- 06 / IMPROVEMENT
Evolve
Improve the system as requirements evolve, where ongoing support is part of the agreement.
Have a complex problem worth solving?
Tell me about the product, the architecture or the engineering challenge. I reply to every relevant inquiry.