Technical lead · Full-stack .NET & Azure engineer

Software that holds up after launch.

I lead teams and build the difficult parts: modernizing established systems, designing cloud workflows, and turning operational complexity into software people can rely on.

Based in Pakistan. Remote worldwide · Contract or full-time · Open to relocation.

10+ yearsbuilding and delivering business software
3–7 engineersteams supported through technical leadership
.NET 4.7–10production systems and modernization work
Azuremessaging, functions, data and observability

Selected work

Three systems. Three different kinds of pressure.

A short, useful view of the work—not an inventory dump. Client identities stay private; the problem, technical shape and contribution remain visible.

Telemetry & scheduling · Technical lead

Turning asynchronous device signals into operational decisions.

Multiple device providers emitted data at different times. The system had to ingest those signals, apply business rules, and make them useful for fleet and staff scheduling without coupling the workflow to a single provider.

~20,000/dayverified device-ping volume · Azure Service Bus + Azure Functions

Platform modernization

Reducing monolith pressure in airline services.

Helped move shared multi-tenant capabilities toward independently deployable services and clearer ownership.

Read the case

Enterprise rollout · Six-person team

Delivery on customer-managed infrastructure.

Led planning, deployment and post-release change for a healthcare application outside the team’s direct infrastructure control.

Read the case

How I lead

Close to the code. Clear with the team.

My role is to create enough clarity for engineers to make progress, surface technical risk early, and keep stakeholders connected to delivery.

  1. 01
    Start with the workflow.

    Understand the user, constraints and operational risk before choosing a pattern or platform.

  2. 02
    Make difficult parts visible.

    Use design discussion, short feedback loops, tests, logs and observability to remove surprises.

  3. 03
    Raise quality while shipping.

    Use reviews, mentoring and disciplined debugging without separating engineering quality from delivery.

  4. 04
    Communicate in plain language.

    Keep estimates, trade-offs, progress and risks understandable to engineers and stakeholders.

Let’s work together

Need a technical lead who still builds?

Available for remote .NET and Azure roles, modernization work, cloud delivery, and international relocation opportunities.