Omar Tarek AliSenior .NET Engineer & Contractor

Senior .NET engineer for existing software systems

I take over .NET systems that already run a business.

I step into existing C# systems, figure out how they actually work, and ship features, fixes, data changes and releases without forcing a rewrite.

C# · .NET · WinForms · ASP.NET Core · SQL Server

Based in Cairo · Available remotely

Omar Tarek Ali

What I can take off your plate

Features, fixes and risky technical work inside software your business already depends on.

Existing .NET systems

I get productive inside C# codebases I didn't write, understand the critical parts, and start shipping without asking for a rewrite.

SQL Server & data

Schema changes, migrations, data repair and performance work where correctness matters and mistakes are expensive to undo.

Safer releases & modernisation

I improve fragile systems incrementally, with tests and rollback paths around the areas being changed.

Technical ownership

Code review, architecture and technical direction for teams that need senior ownership, not just another pair of hands.

For agencies, I can work directly inside your team or behind your client relationship.

Selected work

Systems I've built, inherited and improved.

Enterprise platform

Making a metadata-driven WinForms platform safer to change

I became one of the principal engineers on a large metadata-driven WinForms platform that generates database structures, queries and application screens. The system was powerful but difficult to change safely: a small mistake deep in the platform could affect many generated screens.

I owned core platform behaviour, including view generation, SQL joins and data binding, reviewed changes across the system and improved the tooling used to maintain it. Along the way I built 19 of the platform's 20 internal tools and the shared base that 85 generated screens inherit from.

  • Principal platform engineer
  • WinForms + SQL Server
  • Shared engine & tooling

Legacy data

Safeguarding a legacy ERP data migration

A long-lived ERP was being migrated into SQL Server with incomplete documentation and years of accumulated data assumptions. I owned much of the validation work: column mapping, integrity checks and rollback safeguards.

I built cross-database checks that compare migrated data column by column, surfaced discrepancies for triage, and established checkpoint and rollback procedures so a failed step could be reversed cleanly.

  • SQL Server migration
  • Cross-database validation
  • Rollback safeguards

Product engineering

Building a multi-branch clinic platform from the ground up

I co-founded a multi-branch clinic management platform built on .NET 9 and Blazor, and I own the software end to end: architecture, data design, implementation, testing and deployment.

The system spans appointments, patient records, treatment planning, billing, inventory, HR, reporting and branch-level access control, in Arabic and English. Because it handles clinical and financial data across branches, automated tests, audit logging, branch isolation, deployment safeguards and backup-and-restore verification are built into the architecture rather than added as afterthoughts.

  • .NET 9 + Blazor
  • Multi-branch architecture
  • 1,300+ automated tests

A simple way to start

For unfamiliar systems, I usually start small: get the application running, understand the critical paths and ship one contained piece of work. From there, we continue only if it makes sense.

  1. 01 · fixed price · 7–10 business days

    Existing .NET system takeover

    I get the system running, understand the codebase, database and release process, then ship one contained change.

    • Working local environment
    • One delivered change
    • Tests around what changed
    • Clear next priorities
  2. 02 · 8 reserved days across 4 weeks

    Delivery pilot

    I take ownership of a meaningful piece of backlog and deliver it end to end, with regular updates and working software you can review.

  3. 03 · monthly · 4–8 reserved days

    Reserved engineering

    A reserved block of engineering time each month for features, defects, integrations, database work and releases.

Technical range

The stack behind the work above.

Core .NET

  • C#
  • .NET Framework 4.8
  • .NET 8 / 9
  • ASP.NET Core
  • Blazor

Desktop & data

  • WinForms
  • DevExpress
  • SQL Server
  • T-SQL
  • EF Core
  • Dapper
  • Schema migrations

Delivery & infrastructure

  • IIS / Windows Server
  • Azure DevOps
  • Azure Pipelines
  • ClickOnce
  • PowerShell

Engineering practice

  • xUnit
  • Integration testing
  • Playwright
  • Code review
  • Architecture
  • Production debugging

Why me

I'm a Cairo-based .NET engineer who leads developers, reviews production code and takes ownership of architecture and delivery. Most of my experience is in software with users, data and history: systems that can't stop operating while engineering improves them.

I separate actual risk from ugly-but-working code, then improve the system while it keeps shipping.

I take on selected contract work for teams that need a senior engineer to step into an existing .NET system and own the work. You work with me directly, with clear scope, regular updates and working software you can review.

Have a .NET system that needs an owner?

Tell me what you're dealing with.

me@omartarekali.com

Send me the stack, what needs to change, and what's making it difficult. I'll tell you whether I'm a fit and what I'd do first.