Open to Work

Building scalable, reliable, cloud-ready backend systems.

Ahmed Amin — .NET Backend Developer / Software Engineer

I build enterprise backends in .NET and ASP.NET Core: distributed services on Azure, APIs and messaging, relational data at scale, authentication, and the integrations that hold large organisations together.

View projects Contact me Download CV

Egypt

C#lang.NETframeworkAzurecloud

available

Backend, end to end

Enterprise systems are mostly the parts nobody demos: the queue that drains, the trace that explains, the integration that keeps working.

role backend engineerruntime .NETcloud Azure

I am a backend engineer working on enterprise systems that large organisations depend on every day. Most of my work lives in ASP.NET Core services built on Clean Architecture, deployed to Azure per organisation, and measured in production rather than in demos.

Day to day that means designing APIs other teams build on, writing CQRS handlers behind the specification pattern, modelling data in SQL Server and PostgreSQL, moving work off the request path onto Service Bus queues and scheduled jobs, wiring authentication through Microsoft Entra ID, and integrating systems that were never designed to talk to each other.

I care about the parts that only show up under load: idempotent message handling, sensible retries, cryptographically signed documents, audit trails you can trust, and telemetry good enough to debug a problem at 2am from a trace ID alone.

Focus: .NET backend & distributed systems
Cloud: Microsoft Azure
Domain: Government-sector enterprise platforms
Based in: Egypt

Where the work happened

One team, two production platforms, and the government systems they integrate with.

since 2024-05team 5 engineerstenants 15+

Backend Developer

NexGen Solutions

May 2024 — Present

Backend engineer on enterprise platforms for government-sector clients: ASP.NET Core services on Clean Architecture, containerised to Azure and deployed per organisation, integrated with external government systems, and run in production by thousands of users. Work spans API design, CQRS handlers, data modelling, messaging, authentication, document signing, observability and live troubleshooting.

Trasul PlusCorrespondence and digital workplace platform, deployed to 15+ organisations

eTenderingProcurement and tendering platform

ASP.NET CoreClean ArchitectureCQRSFastEndpointsMediatRREST APIsAzureSQL ServerPostgreSQLRedisService BusMassTransitEntra IDSignalROpenTelemetry

Tools in daily use

Grouped by concern. Everything listed here has shipped in production work.

groups 7primary C# / .NETmeters none

Backend

RUNTIME

C#.NETASP.NET CoreFastEndpointsEF CoreDapperMediatRLINQ

Architecture

DESIGN

Clean ArchitectureCQRSSpecification patternREST APIsEvent-drivenDistributed systems

Databases

STORAGE

SQL ServerPostgreSQLRedis

Messaging

ASYNC

Azure Service BusMassTransitQuartzBackground workers

Azure

CLOUD

App ServiceAzure SQLBlob StorageSignalRKey VaultACRApplication InsightsManaged IdentityAzure OpenAI

DevOps

DELIVERY

DockerJenkinsGitGitHub

Observability

RUN

OpenTelemetrySerilogApplication InsightsStructured logging

Featured work

Two enterprise platforms, and the engineering problem each one actually posed.

count 2domain government sectorstatus in production

01 / Flagship

Trasul Plus

Enterprise correspondence & digital workplace platform

Official correspondence moves through multi-stage approval workflows across government organisations: drafted, routed, digitally signed, archived, and notified in real time. Built as the Digital Workplace solution and deployed per organisation to more than fifteen government entities.

.NETASP.NET CoreFastEndpointsMediatRSQL ServerPostgreSQLRedisService BusMassTransitSignalREntra IDMicrosoft GraphAzure OpenAISOAP

Five projects on a strict dependency direction — Web to UseCases to Core, Infrastructure to Core — so the domain layer never sees FastEndpoints, EF Core or a transport.
Every request is a MediatR command or query returning a result type rather than an exception, and every non-trivial read goes through a specification instead of an ad-hoc LINQ chain.
Two databases by design: SQL Server holds application data, PostgreSQL takes the Serilog structured-log stream, so log volume never competes with transactional load.
Long-running work moves onto Azure Service Bus through MassTransit, with one queue per message type, single-message concurrency where ordering matters, and a 2s/5s/15s retry ladder before dead-lettering.
Documents are signed in-process with iText and an X.509 key — detached CMS signatures applied in append mode, so each signature preserves every earlier one and the audit trail stays verifiable.
Dual JWT authentication: an Entra ID scheme and a local HMAC-SHA256 scheme behind one policy selector, both projecting the same claims so authorisation code never branches on which one signed the caller in.
Legacy government systems are reached over a SOAP connected service, wrapped behind typed clients so the transport stays in Infrastructure.
An MCP server exposes the correspondence domain to AI agents as tools — drafting, routing, search and delegation — over the same handlers the REST API uses.

System architecture

OpenTelemetry traces every band into Azure Monitor. Each organisation gets its own containerised deployment, built once and shipped through ACR.

One correspondence through the system

02 / Platform

eTendering

Enterprise procurement & tendering platform

Tender publication, supplier submission and evaluation, where deadlines are contractual and every action has to be provable after the fact.

.NETASP.NET CoreSQL ServerAzureREST APIsBackground jobs

What the work involves

The recurring problems, independent of which platform they showed up in.

Scalable backend APIs

Versioned REST endpoints built with FastEndpoints, designed around the contract other teams depend on.

Clean Architecture & CQRS

A strict dependency direction across five projects, MediatR command and query handlers, and specifications instead of ad-hoc queries.

Message queues

MassTransit over Azure Service Bus: a queue per message type, idempotent handlers, a retry ladder, and dead-letter review.

Distributed systems

Work split across services with explicit boundaries, ordering guarantees where they matter, and sane failure modes.

Azure architecture

App Service, Azure SQL, Blob Storage, Key Vault and Service Bus wired with Managed Identity.

Entra ID authentication

A dual JWT scheme — Entra ID and local — behind one policy selector, with app roles and delegation for thousands of users.

Real-time with SignalR

Live notification of state changes without polling, backed by a Redis backplane.

Digital document signing

Detached CMS signatures applied in append mode with an X.509 key, so each signature preserves every earlier one.

Audit logging

Append-only trails that answer who changed what, when, and from where.

System integrations

REST, SOAP and government-to-government interfaces behind typed clients.

Observability

OpenTelemetry traces into Azure Monitor and Serilog structured logs into PostgreSQL, correlated end to end.

AI tooling over the domain

An MCP server exposing correspondence drafting, routing and search to AI agents, over the same handlers the REST API uses.

Background

degree B.Sc. CS & ITtrack ITI .NET

B.Sc. Computer Science & Information Technology

Port Said University

2019 — 2023

Graduation project graded A / Excellent.

Full Stack .NET Track

Information Technology Institute (ITI)

2024

Intensive professional track covering .NET, ASP.NET Core and SQL Server.

07 / Contact

Let's build something reliable.

Open to backend engineering roles and focused consulting work. The fastest way to reach me is email.

[email protected]LinkedIn GitHub

Egypt