Software engineering · Cairo, Egypt

Software for real operations, from the database to the interface.

I’m Youssef Mohamed Fekry, a computer science student and product builder. I work on operational software, ERP systems, healthcare products, university platforms, embedded systems and games.

ReactTypeScriptNext.jsPostgreSQLSupabaseC++ArduinoESP32
Product architecture ERP & operations Healthcare Campus systems Robotics Game development
Selected work

Systems I’ve built and developed.

A selection of larger projects, verified from their repositories and documentation.

Deployments

Products running on the web.

Public deployments from my project history.

Engineering range

Web systems, data, hardware and interactive software.

01

Full-stack products

Role-based applications, operational dashboards, transactional workflows, bilingual interfaces and reusable product architecture.

ReactTypeScriptNext.jsVite
02

Database & backend design

PostgreSQL schemas, Supabase Auth/RLS, migrations, server-side business rules, inventory, finance and audit workflows.

PostgreSQLSupabaseSQLRLS
03

Robotics & embedded systems

Arduino and ESP32 robots, multi-sensor navigation, voice-controlled motion, fire suppression and Wi-Fi swarm coordination.

ArduinoESP32C++Sensors
04

Interactive & game systems

Three.js browser games, Unreal Engine C++ work, chess systems, combat mechanics, input systems and simulation.

Three.jsUnreal EngineC++PWA
Repository archive

The wider GitHub account.

Original work, learning repositories and upstream/reference repositories are labeled separately.

About

I like turning operational complexity into understandable software.

My work spans business systems, university software, healthcare products, embedded prototypes, C++ projects and games. The common thread is system design: roles, permissions, state, inventory, payments, scheduling, reporting and the rules that connect them.

I use AI tools as part of implementation and iteration, while keeping architecture, business rules, review and security boundaries explicit.

01Model the business before the interface.
02Keep critical rules close to the backend and database.
03Prefer reusable systems over one-off screens.
04Design bilingual and responsive products from the start.
Contact

Projects, systems, collaboration.