Mustafa SaudiFig. 1 — Warp field. Every streak is a request in flight; steer with the cursor, scroll to accelerate.Sheet 01 / 08

Senior Software Engineer / Backend Architect

Engineering software that scales.

I help businesses design and build scalable SaaS platforms, reliable backend systems, and intelligent software solutions.

NestJS & Go / Microservices / SaaS / Cloud / AI

Engineering / 001System: ready
  • focusBackend systems
  • stackGo · Node.js
  • scopeSaaS · Cloud · AI
02Engineering terminal

Inside the engineering environment.

A short readout of who I am, what I work on and how to reach me. Pick a tab; every line is plain text.

tty/01 — engineering-profile

whoami

  • Tech Lead
  • Senior Software Engineer
  • Backend Architect
  • Technical Consultant
→ About me
Sessiontty/01
  • userMustafa Saudi
  • roleSenior Software Engineer
  • locationGiza, Egypt · remote worldwide
  • modesProjects · Consulting · Roles
03Business value

Complex engineering. Clear business outcomes.

Technology is the means. The point is software that lets your business move faster, serve more customers and stop firefighting.

  1. 03.1

    Build SaaS products

    From first architecture to paying tenants, with isolation, roles and billing designed in.

  2. 03.2

    Integrate disconnected systems

    Connect payment, messaging, ERP and partner APIs so data flows without manual copying.

  3. 03.3

    Modernise backend infrastructure

    Move from fragile deployments and drifting environments to reproducible, automated delivery.

  4. 03.4

    Improve system reliability

    Find the failure modes, add the retries, timeouts and observability, and make incidents rare and boring.

  5. 03.5

    Address scalability problems

    Locate the real bottleneck, whether it is a query, a lock or an architecture boundary, and fix that.

  6. 03.6

    Automate complex workflows

    Background jobs, event-driven processing and AI agents take repetitive work off people’s desks.

  7. 03.7

    Design maintainable architectures

    Clear boundaries and written decisions keep the system changeable long after launch.

04Services

What I can build for you.

Six ways I typically help. Each has its own page with deliverables, approach and common questions.

Table 1 — Services, by business problemAll services
  • SRV-01

    Backend Engineering & API Development

    Your product needs a backend that stays fast, correct and changeable as it grows.

    Production APIs and services in Go or Node.js / NestJS, with data models, background jobs and tests designed for the load you expect next year, not just today.

    • REST or WebSocket APIs with a written contract (OpenAPI where it fits)
    • Service code in Go or Node.js / NestJS with automated tests
    • Database schema, migrations and indexing strategy
    • Go
    • Node.js
    • NestJS
    • PostgreSQL
    • Redis
  • SRV-02

    SaaS Platform Development

    You need a multi-tenant product that is secure, billable and ready for real customers.

    End-to-end SaaS architecture and implementation: tenancy model, authentication and roles, billing hooks, admin tooling and the operational basics that a paying customer will expect.

    • Tenancy model chosen and documented (shared schema, schema-per-tenant or database-per-tenant)
    • Authentication, roles and permission checks enforced at the data layer
    • Tenant provisioning and configuration workflows
    • Multi-tenancy
    • RBAC
    • PostgreSQL
    • NestJS
    • Go
  • SRV-03

    System Architecture & Technical Consulting

    A big technical decision is coming and the cost of getting it wrong is high.

    Independent architecture reviews, system design and decision support: what to build, what to buy, where to draw service boundaries, and what to fix first.

    • Architecture review of the existing system with prioritised findings
    • Target architecture with diagrams and the reasoning behind it
    • Architecture decision records for the key choices
    • System Design
    • Distributed Systems
    • Microservices
    • Event-driven
    • DDD
  • SRV-04

    Cloud Infrastructure & DevOps

    Deployments are manual, environments drift, and nobody is sure what runs where.

    Containerised services, Kubernetes where it earns its keep, infrastructure as code and CI/CD pipelines, so releases are routine and environments are reproducible.

    • Container images and a deployment strategy for each service
    • Kubernetes manifests or Helm charts, or a simpler platform when that fits better
    • Infrastructure as code (Terraform) for networks, databases and clusters
    • Kubernetes
    • Terraform
    • Jenkins
    • CI/CD
    • Observability
  • SRV-05

    AI Integrations & Automation

    You want AI in the product, but it has to be reliable, safe and actually useful.

    LLM-powered features and AI agents wired into real backends: retrieval, tool use, human handoff, evaluation and cost control, treated as engineering rather than demos.

    • Integration architecture for LLM providers, including fallbacks and rate limits
    • Retrieval over your own content and data
    • Agent tools exposed through safe, permissioned APIs
    • LLM APIs
    • AI Agents
    • RAG
    • Tool calling
    • Human handoff
  • SRV-06

    Third-Party Systems Integration

    Your data and workflows are scattered across systems that do not talk to each other.

    Robust integrations with payment providers, messaging channels, ERPs, POS and partner APIs, built to survive rate limits, duplicates, outages and schema changes.

    • Integration architecture with clear ownership of each data flow
    • Webhook receivers with signature checks, idempotency and replay
    • Outbound clients with timeouts, retries, backoff and circuit breaking
    • Webhooks
    • REST
    • Queues
    • Idempotency
    • ETL
05Technical authority

Built on engineering principles.

Grouped by what it is for, with links to where each area shows up in real work and writing.

  1. EX-01

    Backend Engineering

    Services and APIs that stay correct under concurrency, retries and partial failure.

    • Go
    • NestJS
    • Node.js
    • Express
    • gRPC
    • REST APIs
  2. EX-02

    Architecture

    Boundaries, data flow and failure modes decided deliberately and written down.

    • Microservices
    • Event-driven architecture
    • Distributed systems
    • System design
    • Clean code
    • Testable architecture
  3. EX-03

    Data

    Schemas that match the domain, and queries that stay fast as data grows.

    • PostgreSQL
    • MongoDB
    • MySQL
    • Redis
    • Google Datastore
    • Database optimisation
  4. EX-04

    Messaging & Infrastructure

    Reliable messaging between services, reproducible environments and automated delivery.

    • RabbitMQ
    • Kafka
    • Kubernetes
    • Terraform
    • Jenkins
    • Git
  5. EX-05

    Geospatial (GIS)

    Spatial data done properly: storage, queries and analysis on PostGIS, backed by a GIS diploma and a geography degree.

    • GIS
    • PostGIS
    • Spatial databases
    • Spatial analysis
  6. EX-06

    Engineering Practice

    The habits that keep a codebase healthy after the first release.

    • Technical leadership
    • Automated testing
    • Security
    • Database management
    • Shell scripting
  7. EX-07

    AI Integration

    LLM features and agents with real tools, guardrails and evaluation.

    • LLM APIs
    • AI agents
    • Retrieval (RAG)
    • Tool calling
    • Human handoff

Fig. 4 — Engineering matrix · Open the full matrix

06Experience & leadership

The journey behind the engineering.

Roles, responsibilities and what changed because I was there.

  1. T.01May 2023 — present

    Tech Lead — NestJS & Go · Exacall

    Technical lead for the backend, building microservices in NestJS and Go.

    Engineering
    • Developed microservices communicating over RabbitMQ, gRPC and HTTP
    • Applied clean-code principles to keep services maintainable and scalable
    • Designed services to be repository-testable, streamlining testing and improving reliability
    Leadership
    • Technical lead for the NestJS and Go backend
    • Oversaw security protocols and database management
    • NestJS
    • Go
    • RabbitMQ
    • gRPC
  2. T.02Present

    Technical Consultant · Bydotpy

    Technical consulting on backend architecture and microservices.

    Engineering
    • Developed microservices communicating over RabbitMQ, gRPC and HTTP
    • Applied clean-code principles to keep services maintainable and scalable
    • Designed services to be repository-testable, streamlining testing and improving reliability
    • RabbitMQ
    • gRPC
  3. T.03Feb 2022 — Apr 2023

    Backend Engineer — NestJS · Tabaqat

    Backend for the Tabaqat GIS platform (platform.tabaqat.net), specialising in geographic information systems.

    Engineering
    • Built back-end services around spatial databases and GIS technologies
    • Used PostGIS on PostgreSQL to optimise spatial data storage and retrieval
    • Applied a microservice architecture to manage complex data interactions and scale the system
    • Kept the central database performant and responsive to front-end requests
    Leadership
    • Oversaw security protocols and database management
    • NestJS
    • PostgreSQL
    • PostGIS
    • Microservices
07How I work

From problem to production.

A predictable path from the first conversation to software running in production, adapted to the size of the engagement.

Fig. 5 — Engagement schematicproblem → production
  1. 01 / DISCOVERY

    Understand

    Understand the business challenge, users and technical requirements.

  2. 02 / ARCHITECTURE

    Design

    Evaluate constraints and design the appropriate system, with trade-offs written down.

  3. 03 / IMPLEMENTATION

    Build

    Build maintainable software in small, tested, deployable increments.

  4. 04 / VALIDATION

    Verify

    Test behaviour, reliability, security and performance against the requirements.

  5. 05 / DELIVERY

    Ship

    Deploy, document and hand over, so your team owns the result.

  6. 06 / IMPROVEMENT

    Evolve

    Improve the system as requirements evolve, where ongoing support is part of the agreement.

08Contact

Have a complex problem worth solving?

Let’s discuss your product, architecture or engineering challenge.

tty/02 — new-engagementMustafa Saudi
Discuss a career opportunity
Fig. 6 — Live view of the warp field