Senior Software Engineer

About me

I’m a Senior Software Engineer and Team Lead based in Alexandria, Egypt, with over 6 years of experience building web applications that must perform well in real-world conditions. Currently, I’m leading an on-site development squad at Blink Tech, where I spend my days optimizing databases, architecting multi-tenant systems, and ensuring our event management platform can handle thousands of users without falling over.
How I Got Here
My journey into software engineering started at the Arab Academy for Science, Technologyyand Maritime Transport in Alexandria, where I earned aa Bachelor’s'sn Computer Science between 2016 and 2020. I’m currently working on my Master’s degree, though honestly, most of what I’ve learned about building production systems has come from actually creating them, breaking them, and figuring out how to fix them at 2 AM.
My first fundamental engineering role was at Enbarter back in 2018, while I was still in university. I was building features for a social network, learning the basics of web development, and probably writing code I’d cringe at now. But everyone starts somewhere, and that experience taught me the fundamentals.
After graduating, I served in the Egyptian Armed Forces from 2020 to 2021. I was assigned to the Navy, where I built a web application to manage buildings. Not exactly what you’d expect from military service, but it turned out to be valuable experience with government requirements and with building systems that need to be reliable and maintainable.
Finding My Groove
In 2022, I joined Acute Business as a Software Engineer, which is where things really started clicking for me. I was working on a platform that handled over 10,000 users and processed more than 1.5 million transactions. This is where I learned what it actually means to work at scale. You can’t just write code that works on your laptop. You need to think about performance, edge cases, database constraints, and all the things that go wrong when real users start hammering your system.
The experience at Acute taught me to care about the details. A slow query here, a missing index there, these things add up. I developed a habit of using PostgreSQL’s EXPLAIN ANALYZE to understand what my queries were actually doing, which later became one of my most valuable skills.
Leveling Up
My time at Bevatel (early 2023) was brief but intense. I built a real-time chat system and integrated the WhatsApp Business API, which was my first deep dive into building communication systems that need to work reliably. There’s something uniquely challenging about messaging systems. Users expect instant delivery, and if something breaks, everyone notices immediately.
Then came AIT, where I spent about seven months as a Senior Software Engineer. This is where I really got into performance optimization. I achieved a 30% performance boost across the platform through strategic database indexing and caching. More importantly, I learned how to identify bottlenecks systematically rather than just guessing at what might be slow.
The ILLA Chapter
My role at ILLA from February to November 2024 was formative in a different way. I led a Packwerk modularization effort to break our Rails monolith into clean, bounded modules. This taught me that architecture isn’t just about making things work. It’s about making them maintainable by a team of developers who need to understand what connects to what.
Modularization is one of those projects where the benefits aren’t immediately obvious. You’re not shipping flashy new features. You’re making the codebase easier to work with, reducing coupling, and setting up the team for long-term success. It’s the kind of work that matters more six months later when developers realize they can work on their modules without constantly breaking other people’s code.
I also integrated Firebase Cloud Messaging at ILLA, which gave me more experience with notification systems and third-party integrations. Every integration teaches you something new about error handling, rate limits, and the importance of having good fallback strategies.
Leading at Blink Tech
Since November 2024, I’ve been at Blink Tech as a Software Engineer III and Team Lead for the Onsite Squad. This has been my most comprehensive role yet. I’m not just writing code anymore. I’m coordinating with 14+ developers, managing production deployments, and owning projects from architecture through production.
The work at Blink has been varied and challenging. I architected a multi-tenant badge management system with QR code generation and access control, reducing manual processing time by 40%. I implemented Format-Preserving Encryption and GDPR-compliant data scrubbing across 18+ modular components. I optimized our database performance by 30% through strategic indexing and Redis caching. I migrated our entire notification infrastructure from a legacy system to Firebase Cloud Messaging without dropping a single notification.
Over the past ten months, I’ve contributed 780+ commits, executed eight strategic production deployments, and resolved 216+ production issues. But the numbers don’t tell the whole story. What I’m most proud of is building systems that our operations team actually enjoys using and that make their jobs easier, not harder.
How I Work
I’ve developed a pretty methodical approach to problem-solving over the years. When something’s broken, I start by understanding what’s actually wrong before jumping to solutions. I break complex problems into manageable pieces. I prioritize quick wins that buy time for bigger fixes. I measure everything because you need data to know if you’re actually solving the problem. And I think about maintenance because solutions need to work long-term, not just fix today’s issue.
I’m comfortable working autonomously. Give me a problem, and I’ll figure out what needs doing and why without constant oversight. But I also value collaboration. Some of my best work has come from pairing with other developers or getting feedback from people with different perspectives.
I use AI tools regularly now. ChatGPT and Claude help me debug faster, explore technical approaches, and speed up documentation writing. GitHub Copilot occasionally suggests helpful something, thoughI’vee learned to be selective about when to trust it. The key is using these tools to move faster without losing the ability to think critically about what you’re building.
What Drives Me
I get excited about making systems faster and more maintainable. Whether it’s optimizing a Postgres query, refactoring a monolith with Packwerk, or implementing security features like FPE and GDPR compliance, I enjoy technical challenges that have real impact. I like seeing the direct results of my work. When I optimize a database and response times drop from 3 seconds to 500 milliseconds, that’simmediately notice. When I build a system that reduces manual work by 40%, that’s people getting their time back for more valuable work.
I believe sound engineering is about solving problems thoughtfully, not just writing code.It’ss about understanding trade-offs, choosing the right tool for the job, and building things that other developers can maintain after you’re gone.
Looking Forward
I’m based in Alexandria, Egypt, which puts me in the UTC+2 timezone. I work well with distributed teams across different time zones, whether that’s overlapping with European mornings or US afternoons. Remote work suits me. I like the flexibility, the ability to focus without constant interruptions, and the trust that comes with being judged on output rather than hours in an office.
Right now, I’m looking for my next challenge. I want to work on problems that matter at scale, with smart people who care about building things right, in an environment that values autonomy and good engineering practices. I thrive when I have the space to own problems, make technical decisions, and see them through to production.
If you’re building something interesting and need someone who can optimize performance, architect scalable systems, and lead technical initiatives from concept to deployment, let’s talk.