Philopateer Shaker

Backend • Middle • Cairo, Egypt • UTC+02:00 • Fully remote • Work permits: Egypt • Citizenship: Egypt • English: C1 • Available in 2 weeks

Software Tester

Java

C++

Python

SQL

Kotlin

Dart

Data Layer & Database: 4/10

Active 5 days ago

Invite to interview

Download CVCV

Overview

Technical skills

Timeline

Roles

Overview

Java backend developer at an early-to-mid career level focused on monolithic application development and UI-driven CRUD flows. The strongest proven skill is implementing direct data-layer JDBC logic and SQL-rich DAOs as seen in BorrowRecordDAO.java and BookDAO.java. The codebase lacks evidence of production-grade operations practices such as HTTP API design, password hashing, migration history, connection pooling, and observability.

Phone

Technical skills

Languages

Java

C++

Python

SQL

Kotlin

Dart

C++

STL

OpenGL

Game Dev

Unreal Engine

Unity

raylib

Other

Retrofit

Cloudflare

Firebase

Flutter

MySQL

GitHub

Glide

Firestore

Git

Frontend

Behavior Tree

NavMesh

Timeline

Software Testing Intern • Junior

OneHealth by AXA • Internship

Jun 2026 to Present 3 Months Cairo Fully remote

Performed manual testing of software features to find bugs, inconsistencies, and usability issues before releases. Wrote and maintained detailed, repeatable test cases to cover application functionality. Logged defects in Jira and coordinated with developers to verify fixes and close issues.

Jira

University of Prince Edward Island

Bachelor's Degree • Computer Science (Game Development)

2019–2026 Cairo, Egypt

Middle Backend Developer Confidence: Medium Generalist

API Design

1/10

How well APIs are designed

Minimal API design artifacts; the projects expose UI controllers (console and JavaFX) but there are no HTTP/REST API contracts, versioning, idempotency, or pagination strategies.

Evidence

pzshaker/Airline_System/src/others/Main.java: menu-driven console user flows and choice handling pzshaker/Library-Management-System/src/main/java/com/example/librarymanagementsystem/javaFX/Librarian/AddBookPage.java: JavaFX UI handlers and form submission logic with no external API contract

Data Layer & Database

4/10

Working with databases

Concrete JDBC data-layer code with prepared statements, JOINs and RETURN_GENERATED_KEYS, but no explicit transaction management, no migration history, and error handling is basic (printStackTrace).

Evidence

pzshaker/Library-Management-System/src/main/java/com/example/librarymanagementsystem/Backend/DAOs/BorrowRecordDAO.java: multi-table joins, INSERT/UPDATE patterns, RETURN_GENERATED_KEYS usage pzshaker/Library-Management-System/src/main/java/com/example/librarymanagementsystem/Backend/DAOs/BookDAO.java: addBook with generated keys and book_author linking pzshaker/Library-Management-System/src/main/java/com/example/librarymanagementsystem/Backend/DAOs/MemberDAO.java: common member queries and PreparedStatement usage

Scalability & Performance

1/10

Handling load and speed

Little to no evidence of scalability or performance engineering such as caching strategies, connection pooling configuration, queue-based decoupling, or documented optimization and load testing.

Evidence

pzshaker/Library-Management-System/src/main/java/com/example/librarymanagementsystem/Backend/DAOs/BookDAO.java: direct DB queries without caching or pooling hints pzshaker/Library-Management-System/src/main/java/com/example/librarymanagementsystem/Backend/DAOs/BorrowRecordDAO.java: sequential DB updates without explicit transaction control

System Architecture

3/10

Overall system structure

Reasonable modular separation for a monolith - controllers, model/others classes, DAOs and UI layers are separate, but service decomposition and inter-service contracts are not present; configuration and secret management are not evidenced.

Evidence

pzshaker/Airline_System/src/controllers/FlightController.java: controller layer handling domain flows and delegating to FileController/other controllers pzshaker/Library-Management-System/src/main/java/com/example/librarymanagementsystem/Backend/DAOs/BookDAO.java: DAO layer separated from JavaFX UI classes

Security & Auth

2/10

Protecting data and access

Some basic security awareness is present via PreparedStatement usage to avoid SQL injection, but critical gaps exist: plaintext password storage/comparison, in-code default admin credentials, and no password hashing or token lifecycle management.

Evidence

pzshaker/Library-Management-System/src/main/java/com/example/librarymanagementsystem/Backend/DAOs/MemberDAO.java: checkMemberEmailAndPassword uses PreparedStatement but implies plaintext password checks pzshaker/Airline_System/src/others/LoginSystem.java: password comparison in-memory and default admin credentials created in Main.java

Reliability & Observability

2/10

Stability and monitoring

Basic reliability practices are used: input validation loops and try/catch blocks, but there is no structured logging, metrics, retries/backoff, graceful shutdown patterns, or observability instrumentation.

Evidence

pzshaker/Airline_System/src/controllers/FlightController.java: input parsing loops with exception handling and user prompts pzshaker/Library-Management-System/src/main/java/com/example/librarymanagementsystem/Backend/DAOs/BorrowRecordDAO.java: catch blocks that call e.printStackTrace() and rethrow RuntimeException

Expertise

Java• Middle

Industries

Education• Middle

Transportation & Logistics• Middle

Technologies

Java• since 2024 • Middle

Recommendations

Harden authentication: remove hardcoded default credentials, store hashed passwords, and implement secure sign-in flows (e.g., bcrypt + salts).
Introduce database migrations and explicit transaction boundaries for multi-statement operations (use a migration tool and set autoCommit=false with proper commit/rollback).
Build a REST API layer (Spring Boot or similar) and separate UI from service boundary to enable integration and automated testing.
Add observability and reliability: structured logging, metrics (Micrometer or similar), and basic retry/backoff for external operations.
Introduce unit/integration tests and CI validation for DAOs and controllers; use a connection pool (HikariCP) and consider basic load testing for hotspots

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

Airline_System Library-Management-System

Junior Robotics Engineer Confidence: Medium Generalist

A junior C++ GUI developer specializing in Qt-based desktop applications. The strongest proven skill is building simple Qt application flows as shown in mainsystem.cpp and secondwindow.cpp which implement user management, menu population, and cart UI interactions. There is little to no evidence of automated testing, CI, security hardening, or systems-level engineering practices in the public code.

Motion Control & Kinematics

Controlling robot movement

Not evidenced in public code

Perception & Sensor Fusion

Understanding sensor data

Not evidenced in public code

ROS & Middleware

Robot software framework skills

Not evidenced in public code

Control Algorithms

Algorithms that steer robots

Not evidenced in public code

Real-time Systems

Precise real-time control

Not evidenced in public code

Simulation & HIL Testing

Testing robots in simulation

Not evidenced in public code

Technologies

C++• since 2024 • Junior

STL

Recommendations

Develop small Qt-based desktop features, such as user-facing forms, dialog flows, and menu-driven UI components.
Work on C++ code quality improvements including input validation, bounds checking, and safer memory management.
Build experience with basic software engineering practices: unit tests, simple CI, and secure credential handling.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

Food_Ordering_System

Intern Frontend Developer Confidence: Low Generalist

Frontend developer at an intern level who produces simple static informational web pages. The strongest proven skill is authoring clear privacy and support HTML pages, evidenced by the privacy policy and support HTML documents. There is no evidence of component-based UI architecture, interactive JavaScript, automated tests, or advanced state management in human-authored public code.

UI Component Architecture

How interface parts are built

Not evidenced in public code

Responsive & Cross-browser

Works on all screens and browsers

Not evidenced in public code

Performance Optimization

Speed of the interface

Not evidenced in public code

Accessibility & Semantics

Usable for everyone

Not evidenced in public code

State Management & Data Flow

Managing data in the app

Not evidenced in public code

UX & Visual Polish

Look and feel quality

Not evidenced in public code

Technologies

Frontend

Cloudflare

Recommendations

Author and maintain static legal, support, and marketing pages or simple documentation sites.
Work on content-driven landing pages and help centers with responsive HTML and CSS.
Gain experience building interactive components and single-page applications using a modern framework and automated tests.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

uniview-legal