Backend Engineering
Designing APIs, implementing business logic, structuring services, and keeping backend code understandable as systems grow.
About Me
Building software around real engineering constraints.
I'm a .NET Software Engineer focused on backend systems, enterprise applications, SQL Server, and the engineering problems that appear when software has to work in production.
Background
More than writing code.
01
I have more than three years of professional experience building and maintaining enterprise software with C# and .NET.
My work has involved transactional ERP applications, backend services, database-heavy workflows, and desktop production applications.
That experience has pushed me beyond simply implementing features. I care about how business rules are structured, how data moves through the system, how the database behaves, and what happens when the application is under real usage.
My current focus is backend engineering with ASP.NET Core and SQL Server, with particular attention to performance, maintainability, scalable APIs, and predictable data access.
Engineering Focus
Where I spend my attention.
Database Performance
Investigating slow queries, indexing problems, inefficient data access, and database-heavy application behavior.
Enterprise Systems
Building software around real business processes, transactional data, ERP workflows, and long-lived production systems.
Maintainable Software
I value clear boundaries, explicit dependencies, predictable behavior, and code that communicates its intent without requiring reverse-engineering.
Technical Stack
Tools I use to build systems.
Languages
C#
C++
SQL
Backend
.NET
ASP.NET Core
Web API
REST APIs
Data
SQL Server
EF Core
Query Optimization
Indexing
Applications
WPF
Desktop Applications
Enterprise Software
How I Work
Engineering decisions start with the problem.
Understand the actual problem
Before changing code, I want to understand the business requirement, current behavior, constraints, and where the actual bottleneck exists.
Measure before optimizing
Performance work should be driven by evidence. Slow queries, unnecessary database calls, and expensive operations should be identified before changing the implementation.
Keep complexity intentional
Architecture should solve real problems rather than add ceremony. I prefer clear boundaries, explicit dependencies, and predictable data access.
Build for the next engineer
Production software lives longer than the person who originally wrote it. Readability and maintainability are therefore part of the engineering job.
Education
Technical foundation.
2020 — 2023
Technical Diploma in Software Engineering
TCC — Damascus University
Software EngineeringNext
Want to see what I've actually built?
Explore selected projects and see how I approach libraries, desktop applications, backend systems, and engineering problems.