Ziad Abou-El-Farah
Full Stack Developer
7+ years exp
Python
JavaScript
Node JS
TypeScript
Go
Active 2 days ago
+212 (63) 6959499 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Frontend UI engineer (junior level) focused on small React applications and component implementations. The strongest proven skill is building interactive React UI components as shown by the Todo app components (ziadab/TodoReact/src/App.js and ziadab/TodoReact/src/components/*). There is little evidence of advanced frontend engineering practices such as async state management, accessibility tooling, automated tests or performance analysis.
Technical skills
Python• Senior • 7y+
JavaScript• Junior • 7y+
Node JS• Senior • 5y+
TypeScript• Senior • 3y+
Go• Middle
Node JS
Dotenv
Databases
MySQL
PostgreSQL
MongoDB• 6y+
Redis• 3y+
RabbitMQ
AI/ML
Claude
Claude Code
Copilot
Cursor
Frontend
React Router
Vue.js• 8y+
React.js• 6y+
GraphQL• 5y+
Next.js• 5y+
Nuxt.js• 3y+
DevOps
AWS Lambda
CI/CD
Amazon EC2• 7y+
Nginx• 7y+
GitLab CI• 5y+
AWS
Docker
GitHub Actions
Rest API
QA
Sentry• 5y+
Swagger
Cybersecurity
GDPR• 3y+
Timeline
Senior Full Stack Developer
•
Senior
Paylik
•
Full-Time
Designed and maintained backend services using Python (Django) and Go for a fintech platform handling high-volume REST workloads. Implemented asynchronous transaction processing using message queues and event streaming to decouple latency and make retries safer under failure. Built CI/CD automation with GitHub Actions and managed multi-environment deployments, including Docker-based builds and testing. Implemented and maintained API standards with OpenAPI/Swagger documentation and GDPR-focused practices.
Python
Django
Go
AWS
Docker
GitHub Actions
RabbitMQ
Swagger
Rest API
GDPR
Full Stack Developer
•
Middle
AIESEC
•
Full-Time
Built Node.js and TypeScript automation tools that reduced manual work and supported internal teams at scale. Developed and operated background processing for scheduled and long-running tasks using Redis-backed queues and worker processes. Contributed to GDPR-compliant data handling and consent/security flows in a live EU production environment while owning delivery from requirements through production operations.
Node JS
TypeScript
Redis
BullMQ
GDPRsince 2023
Full Stack Developer (Node.js Lead)
•
Lead
Evold
•
Full-Time
Led development of a Node.js backend using Express and GraphQL to support flexible data retrieval. Delivered and launched a remote learning platform project with an interactive quiz engine and gamification features. Automated releases using GitLab CI/CD and improved observability by integrating analytics and error monitoring tooling.
Node JSsince 2021
Express
GraphQL
GitLab CI
Amplitude
Sentry
Backend Developer
•
Middle
Renights
•
Full-Time
Worked on Python backend services running behind an NGINX reverse proxy on AWS EC2, supporting growth to a large active user base. Took responsibility for backend API architecture and performance monitoring, coordinating work with engineering teams. Maintained and extended an e-commerce/martketplace backend with continuous feature delivery.
Pythonsince 2019
Nginx
Amazon EC2
Junior AI/ML Engineer
Confidence: Medium Generalist
Junior backend developer focused on small Flask-based HTTP API services with practical API-integration skills. The strongest proven skill is building simple Flask endpoints that call external services, concretely shown by deezerGrabber/app.py and expaGrabber/app.py. There is no evidence of machine learning work, automated testing, robust production deployment, or advanced security/hardening in public code.
Model Architecture & Training
How well models are designed and trained
Not evidenced in public code
Data Pipeline & Feature Engineering
How data is prepared for models
Not evidenced in public code
Experimentation & Evaluation
How results are measured and tested
Not evidenced in public code
MLOps & Deployment
How models are shipped to production
Not evidenced in public code
Computational Efficiency
How efficiently computing resources are used
Not evidenced in public code
Research Depth & Innovation
Depth of research and new ideas
Not evidenced in public code
Technologies
Copilot
Cursor
Claude
Claude Code
Recommendations
- Develop and maintain small REST API services and API integrations that fetch and reshape external data.
- Build proof-of-concept backend tooling and lightweight ETL scripts for ingesting remote JSON APIs.
- Harden services for production: add request timeouts, exception handling, input validation, and proper logging.
- Add automated tests and CI to increase reliability before moving to larger system design work.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Backend Developer
Confidence: Low API Engineer
Junior backend engineer focused on Node.js/Express API integrations. The strongest proven skill is building small API integrations and route handlers as seen in app.ts and route/service files such as routes/githubWebhook.ts and services/telegram.ts. There is little public evidence of production-grade resilience, schema migrations, testing, or observability practices.
API Design
2/10
How well APIs are designed
Basic API work and integration patterns are present (Express routes, GraphQL client types) but there is little evidence of deliberate API versioning, idempotency, or pagination strategy beyond basic route handlers.
Evidence
Neferpitou-TypeScript/app.ts (imports express and multiple route handlers)
Neferpitou-TypeScript/routes/githubWebhook.ts (webhook handling pattern)
Data Layer & Database
1/10
Working with databases
Minimal data-layer decisions visible; a Redis client appears to be used but there is no migration history, transactional logic, or hand-tuned queries in the inspected artifacts.
Evidence
Neferpitou-TypeScript/package.json (redis dependency listed)
Neferpitou-TypeScript/app.ts (imports redisClient)
Scalability & Performance
1/10
Handling load and speed
Little evidence of scalability work: Redis dependency suggests simple caching/coordination, but no documented caching invalidation, connection pooling, rate limiting, or queue-based decoupling.
Evidence
Neferpitou-TypeScript/package.json (redis dependency)
Neferpitou-TypeScript/api/updateCron.ts (cron/update script presence)
System Architecture
1/10
Overall system structure
Architecture appears to be a small Node/Express service composed of route handlers and clients for external APIs; no multi-service decomposition rationale, config/secret management beyond dotenv, or explicit graceful degradation patterns were found.
Evidence
Neferpitou-TypeScript/app.ts (wires routes and clients)
Neferpitou-TypeScript/routes/typeform.ts (single-purpose route handler)
Security & Auth
1/10
Protecting data and access
Some basic security hygiene (helmet in dependencies, webhook signature handling) but no systematic auth lifecycle, input validation layers, or dependency/audit evidence for production security hardening.
Evidence
Neferpitou-TypeScript/package.json (helmet listed)
Neferpitou-TypeScript/routes/githubWebhook.ts (uses crypto for webhook signature checking)
Reliability & Observability
1/10
Stability and monitoring
Minimal reliability and observability patterns visible: dev scripts and basic service code exist but there is no evidence of structured logging, correlation ids, explicit timeouts/backoff, or metrics/alerting.
Evidence
Neferpitou-TypeScript/package.json (dev/start scripts using ts-node/ts-node-dev)
Neferpitou-TypeScript/services/telegram.ts (third-party integration without retry/backoff patterns visible in metadata)
Expertise
Node.js• Junior
Microservices & API Architecture• Junior
Messaging & Real-time• Junior
Technologies
Go• Middle
MySQL
PostgreSQL
Redis• 3y+
Rest API
RabbitMQ
GitHub Actions
GitLab CI• 5y+
CI/CD
AWS
Docker
Nginx• 7y+
Dotenv
AWS Lambda
Amazon EC2• 7y+
Recommendations
- Develop new Express-based API integrations and lightweight webhooks where the scope is well defined (third-party API adapters, notification webhooks).
- Harden existing integrations by adding explicit timeouts, retries with backoff, structured logging and correlation ids in services like services/telegram.ts and external client wrappers.
- Add basic automated tests and a small migration history or documented schema changes for any persistent data layer work (even simple Redis key schema docs).
- Iterate on API contracts: add consistent error shapes, versioning plan and simple pagination/idempotency patterns for endpoints that may be consumer-facing.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Frontend Developer
Confidence: Medium UI Engineer
Frontend UI engineer (junior level) focused on small React applications and component implementations. The strongest proven skill is building interactive React UI components as shown by the Todo app components (ziadab/TodoReact/src/App.js and ziadab/TodoReact/src/components/*). There is little evidence of advanced frontend engineering practices such as async state management, accessibility tooling, automated tests or performance analysis.
UI Component Architecture
3/10
How interface parts are built
Simple, component-based React UI using class components and prop drilling; clear component boundaries but no design-system, composition patterns, or advanced custom hooks.
Evidence
ziadab/TodoReact/src/App.js: class App with state and methods addTodo/del/markDone passed as props
ziadab/TodoReact/src/components/TodosItem.js: TodosItem class reads props.todo and uses inline styling
ziadab/TodoReact/src/components/AddToDo.js: AddToDo component manages local form state and calls addTodo prop
Responsive & Cross-browser
2/10
Works on all screens and browsers
No evidence of responsive strategies beyond basic inline/flexible styles; no container queries, i18n/RTL support or progressive enhancement patterns.
Performance Optimization
1/10
Speed of the interface
No measurable or explicit performance work; no memoization, virtualization, code-splitting or bundle analysis artifacts.
Accessibility & Semantics
2/10
Usable for everyone
Basic semantic elements used but no explicit accessibility practices for custom widgets, missing labels/ARIA and no a11y checks in CI.
State Management & Data Flow
2/10
Managing data in the app
Local component state and prop drilling; no server-state discipline, request cancellation, optimistic updates, or state-machine patterns are evident.
UX & Visual Polish
2/10
Look and feel quality
Basic visual polish with inline styling and placeholder UX; loading/error/empty/stale states, skeletons, and undo patterns are not present.
Verified artifacts
Expertise
React• Junior
Technologies
JavaScript• Junior • 7y+
GraphQL• 5y+
React Router
Recommendations
- Assign to build and polish small-to-medium React UI features and internal dashboards where rapid iteration is valued.
- Have them migrate class components to hooks and implement shared hooks for form handling and todo state to increase reusability.
- Pair with a senior engineer to add accessibility improvements (labels, ARIA, keyboard focus) and introduce unit/interaction tests (Jest/React Testing Library).
- Let them implement simple API integrations (Express/Axios) and add basic error/loading states and request cancellation for robustness.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: