I build systems that hold up — not just under normal load, but under the kind of complexity that reveals whether the architecture was actually thought through.

My work lives at the intersection of clarity and scale: APIs designed to outlast the requirements they were written for, frontends that stay coherent as they grow, and backend logic that doesn't collapse when the edge cases arrive. I graduated from Tanta University in 2025 and I'm currently deepening my foundations through MIT OpenCourseWare via edX — because I've found that the engineers who age well are the ones who understood why, not just how.

Beyond client work, I build tools for developers — utilities and libraries that reduce friction in day-to-day engineering: automation scripts, workflow integrations, and open-source projects that others can drop into their own stacks. Building for other builders sharpens the thinking considerably.

I've worked through 320+ algorithmic and system design problems — not as a performance, but because reasoning under constraint is a transferable skill that shows up everywhere, from database schema decisions to API contract negotiations.

I build around Clean Architecture — separating business logic from delivery mechanisms so that the core of a system stays readable, testable, and portable regardless of what framework happens to be surrounding it at any given moment.

In practice, this means:

• Real-time systems built with Socket.io that don't degrade under concurrent load
• Recommendation engines using hybrid weighting and behavioral feedback loops
• NLP pipelines for auto-tagging Arabic and English content
• CI/CD workflows with Docker and GitHub Actions that treat deployment as a first-class engineering concern
• Security as a structural property — RBAC, OAuth flows, and input sanitization are baked into the design, not bolted on afterward
• Developer tooling that removes repetitive work from the engineering process, giving developers time back for the decisions that actually require judgment

Things I'm building — not ""JUST :)"" for clients, but because the problem was worth solving.

[AxeCode]  ·  Developer Ecosystem

A platform built around the idea that developers grow faster in proximity to other developers. axecode brings together daily logs, structured courses, live events, and interactive problem solving — but the core of it is the workshop model: developers building real software together, in public, with other members of the platform. Less social network, more engineering community.

[Leafy]

Most of what a developer learns never makes it into their GitHub graph — a course watched, a problem solved on LeetCode, a concept worked through in isolation. Leafy fixes that. It tracks external learning activity and syncs it automatically to your GitHub profile, so your actual growth is visible, not just your commit history.

Phone: +20 10 13763861
mail: mohamedeleskanderwow@gmail.com