I have spent the better part of a decade in the UAE building software and leading teams through the kind of technical puzzles and practical roadblocks that come with delivering real-world solutions. In each role, I’ve gravitated toward the intersection of hands-on engineering and team growth, whether that meant mapping out the architecture for city-wide smart parking or mentoring new developers as they tackled their first major deployment. The Technical Lead role you’ve described matches the trajectory I have followed so far, where careful design, clear communication, and steady leadership are the difference between a project that simply works and one that actually serves. At Energy International, I led a team through the architecture and delivery of scalable parking management systems, where every day brought a new set of priorities sometimes technical, often organizational. What helped us succeed wasn’t just technical know-how, though that certainly mattered. It was an ongoing effort to bridge the gap between code and context: translating project goals into technical requirements, and translating technical complexity into clear, actionable steps for both the team and non-technical stakeholders. I made a habit of holding regular code reviews not just for quality control, but as a space for developers to learn from each other and raise issues before they became problems. That mindset of guiding a team while staying close to the technical details is something I would bring to your organization. The stack you work with is familiar territory for me. .NET, C#, Angular, and SQL Server have been my main tools, and I have lived the full cycle from initial requirements to deployment and support. I have managed integration of new technologies like AI-based guidance and IoT into legacy platforms, ensuring we delivered on both innovation and stability. When technical challenges have surfaced whether bottlenecks in system performance or missed deadlines I’ve found that a mix of analytical thinking and honest conversation gets to the root quickly. What I enjoy most is helping people do their best work, whether that’s through clear documentation, thoughtful delegation, or simply making sure roadblocks are escalated before momentum is lost. I am also keenly aware of how the industry keeps shifting, and I make a point of staying current so I can advise my team on new tools or approaches worth adopting. If you are looking for someone who thrives at the intersection of technical leadership and hands-on engineering, and who believes in building strong teams as much as strong systems, I would welcome the chance to talk further.…I have spent the better part of a decade in the UAE building software and leading teams through the kind of technical puzzles and practical roadblocks that come with delivering real-world solutions. In each role, I’ve gravitated toward the intersection of hands-on engineering and team growth, whether that meant mapping out the architecture for city-wide smart parking or mentoring new developers as they tackled their first major deployment. The Technical Lead role you’ve described matches the trajectory I have followed so far, where careful design, clear communication, and steady leadership are the difference between a project that simply works and one that actually serves. At Energy International, I led a team through the architecture and delivery of scalable parking management systems, where every day brought a new set of priorities sometimes technical, often organizational. What helped us succeed wasn’t just technical know-how, though that certainly mattered. It was an ongoing effort to bridge the gap between code and context: translating project goals into technical requirements, and translating technical complexity into clear, actionable steps for both the team and non-technical stakeholders. I made a habit of holding regular code reviews not just for quality control, but as a space for developers to learn from each other and raise issues before they became problems. That mindset of guiding a team while staying close to the technical details is something I would bring to your organization. The stack you work with is familiar territory for me. .NET, C#, Angular, and SQL Server have been my main tools, and I have lived the full cycle from initial requirements to deployment and support. I have managed integration of new technologies like AI-based guidance and IoT into legacy platforms, ensuring we delivered on both innovation and stability. When technical challenges have surfaced whether bottlenecks in system performance or missed deadlines I’ve found that a mix of analytical thinking and honest conversation gets to the root quickly. What I enjoy most is helping people do their best work, whether that’s through clear documentation, thoughtful delegation, or simply making sure roadblocks are escalated before momentum is lost. I am also keenly aware of how the industry keeps shifting, and I make a point of staying current so I can advise my team on new tools or approaches worth adopting. If you are looking for someone who thrives at the intersection of technical leadership and hands-on engineering, and who believes in building strong teams as much as strong systems, I would welcome the chance to talk further.WWWW…