Mostafa Ismail

Backend • Middle • Management: 1-2 years (1-5 people) • 31 years • Giza, Egypt • UTC+02:00 • Fully remote • Relocation • Work permits: Egypt • Citizenship: Egypt • English: B1 • Available in 3 weeks • from $20k per year

Frontend Developer

5+ years exp

Management: 1-2 years (1-5 people)

20+ projects

TypeScript

JavaScript

Node JS

Active 1 day ago

Invite to interview

Download CVCV

Overview

Technical skills

Timeline

Roles

Overview

Frontend engineer (Middle) focused on building React and Next.js user interfaces and application state flow. The strongest proven skill is client-side state and form workflows demonstrated by invoices-app AppProvider.js (context + reducer) together with AddInvoice.js form handling. There is little public evidence of automated tests, request cancellation/optimistic-update patterns, or formal accessibility/audit tooling in use.

Phone

Technical skills

Languages

TypeScript

JavaScript

Node JS

Frontend

Bootstrap

React Router

Framer Motion

Yup

JQuery

i18next

React Query

styled-components

npm

Emotion

React.js

Socket.IO

Next.js

ESLint

TanStack Router

Zod

Redux

Storybook

Chart.js

Lighthouse

GSAP

Anime.js

Husky

TanStack Start

Apollo Client

Jest

Swagger

Postman

Chrome DevTools

Vitest

BrowserStack

Sentry

Other

React Native

MongoDB

Adobe Photoshop

Adobe XD

Git

Sass

Material UI

Tailwind CSS

Firebase

Redux Toolkit

shadcn/ui

Zustand

Radix UI

Formik

GitHub

Rest API

GraphQL

Figma

Vite

CI/CD

State Management

Timeline

Front-end Developer (Next.js, React Native) • Middle

UNITS • Full-Time

May 2022 to Present 4 Years 4 Months In office

Developed and maintained high-performance web and mobile interfaces using React and state management with Redux. Improved key UX metrics through performance optimization and pixel-accurate UI implementation with design teams. Built reusable UI components across platforms and supported team quality by mentoring junior developers.

Next.js

React.js

Redux

React Native

Front-end Developer (Internship) • Junior

Cord Digital • Internship

Dec 2021 to Mar 2022 3 Months In office

Built responsive UI components for Mowzaf.com using front-end web technologies. Collaborated with the team to convert design mockups into working interfaces and followed code collaboration practices using Git.

JavaScript

Git

Thebes Academy

Bachelor's Degree • Administrative Information System

2016 Giza, Egypt

Middle Backend Developer Confidence: Medium API Engineer

API-focused frontend engineer at a Middle level whose main strength is building client-side API integration layers with TypeScript modeling. The strongest proven skill is the centralized client API layer and WordPress REST integrations implemented in src/app/lib/Controller.ts. There is little to no evidence of server-side databases, migrations, concurrency controls, or production-grade resilience and observability in the human-authored code.

API Design

3/10

How well APIs are designed

Light API design and a single centralized client API layer exist, but there is no documented versioning, idempotency strategy, or consistent error contract.

Evidence

younit-dev/wordpress-next/src/app/lib/Controller.ts: fetchData implementation centralizing calls and getProjects/getBlogBySlug wrappers younit-dev/wordpress-next/src/app/lib/Controller.ts: contactSubmitHandler POST to external WP endpoint

Data Layer & Database

1/10

Working with databases

No database code, migrations, or transactional boundaries; only client-side persistence via localStorage is present.

Evidence

MostafaIsmaiel/invoices-app/src/components/AppProvider.js: localStorage persistence useEffect and invoicesReducer

Scalability & Performance

3/10

Handling load and speed

Basic performance-minded choices are present (Next revalidation flag and selective caching) and some parallel fetches, but no measured optimizations, cache invalidation strategy, or queueing.

Evidence

younit-dev/wordpress-next/src/app/lib/Controller.ts: IS_CACHING and next.revalidate usage in fetch options younit-dev/wordpress-next/src/app/lib/Controller.ts: Promise.all used to fetch related projects in getProject

System Architecture

3/10

Overall system structure

Reasonable modular frontend structure and a central API helper show deliberate separation of concerns, but there is no multi-service decomposition or documented inter-service contracts.

Evidence

younit-dev/wordpress-next/src/app/lib/Controller.ts: central API layer for the app younit-dev/wordpress-next/types.d.ts: domain/type modeling for API payloads

Security & Auth

2/10

Protecting data and access

Minimal security hygiene: environment variables are used and external POSTs are made, but there is little evidence of auth lifecycle handling, input validation, or server-side protection patterns in the human-authored code.

Evidence

younit-dev/wordpress-next/src/app/lib/Controller.ts: uses process.env.NEXT_PUBLIC_API_URL and contactSubmitHandler but no auth/token handling MostafaIsmaiel/invoices-app/src/components/AddInvoice.js: client-side form handling without evident validation middleware

Reliability & Observability

2/10

Stability and monitoring

Basic try/catch error capture and local persistence exist, but there is no evidence of timeouts, retries with backoff, structured logging, correlation ids, or metrics/alerts.

Evidence

younit-dev/wordpress-next/src/app/lib/Controller.ts: fetchData uses try/catch and returns { error } MostafaIsmaiel/invoices-app/src/components/AppProvider.js: localStorage persistence but no observability hooks

Expertise

Node.js• Junior

Microservices & API Architecture• Junior

Technologies

Node JS• since 2024 • Middle

Rest API

Recommendations

Build RESTful backend endpoints or small Node.js services that exercise transactions, schema migrations and idempotency to strengthen server-side design experience.
Add structured observability (request timeouts, retries with backoff, correlation ids, and basic metrics) around the fetch layer in src/app/lib/Controller.ts.
Implement server-side input validation and authentication flows and add end-to-end tests that cover failure modes and edge cases.
Work on a project with a real database and migration history to demonstrate schema evolution, isolation choices and tuned queries.

Repositories

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

MostafaIsmaiel wordpress-next invoices-app

Middle Frontend Developer Confidence: Medium App Engineer

UI Component Architecture

4/10

How interface parts are built

Reasonable component boundaries with context + reducer for app state and styled component modules, but no evidence of a custom design system or advanced composition patterns beyond conventional patterns.

Evidence

younit-dev/wordpress-next/src/app/Components/Atoms/NavLink/styles.ts MostafaIsmaiel/invoices-app/src/components/AddInvoice.js MostafaIsmaiel/invoices-app/src/components/AppProvider.js

Responsive & Cross-browser

5/10

Works on all screens and browsers

Responsive layouts and breakpoints are used consistently; styles include media queries and reduced-motion support and there is some i18n/RTL awareness in header styles.

Evidence

MostafaIsmaiel/invoices-app/src/index.scss younit-dev/wordpress-next/src/app/Components/Organisms/Header/styles.ts younit-dev/wordpress-next/public/style/style.css

Performance Optimization

3/10

Speed of the interface

Some server-state caching awareness (Next revalidate/cache flags) and use of lightweight runtime improvements, but no measured performance work or advanced code-splitting/virtualization evidence.

Evidence

younit-dev/wordpress-next/src/app/lib/Controller.ts MostafaIsmaiel/invoices-app/src/components/CurrentInvoice.js

Accessibility & Semantics

3/10

Usable for everyone

Basic accessibility semantics are present (labels, htmlFor, screen-reader-text), but no ARIA on custom widgets, no focus-management patterns or accessibility tests shown.

Evidence

MostafaIsmaiel/invoices-app/src/components/AddInvoice.js younit-dev/wordpress-next/public/style/style.css

State Management & Data Flow

4/10

Managing data in the app

Practical client-state discipline with a React context + reducer, localStorage persistence and clear CRUD flows, but no advanced server-state patterns (no cancellations, optimistic updates with rollback, or request-race handling).

Evidence

MostafaIsmaiel/invoices-app/src/components/AppProvider.js younit-dev/wordpress-next/src/app/lib/Controller.ts

UX & Visual Polish

5/10

Look and feel quality

Strong visual polish and UX attention in SCSS and component styling, with theme variables, responsive tweaks and animated transitions, though loading/error/empty UX patterns are limited or not visible in code.

Evidence

MostafaIsmaiel/invoices-app/src/index.scss MostafaIsmaiel/invoices-app/src/components/AddInvoice.js

Expertise

React• Middle

Modern Web Frameworks• Middle

Technologies

Zustand

Redux• since 2022

Tailwind CSS

Next.js• since 2022

Figma

CI/CD

Git• since 2021

React.js• since 2022

Vite

Radix UI

Material UI

Sass

shadcn/ui

Formik

Redux Toolkit

GitHub

GitHub• mentioned only

Recommendations

Develop medium-sized React/Next.js single-page apps that require client-side state, forms and local persistence.
Implement and extend component libraries and themed UI (MUI + tss-react patterns) for consistent cross-screen experiences.
Integrate Next.js frontends with REST/WordPress backends (data fetching and cache/revalidate strategies).
Hardening front-end quality by adding testing, accessibility audits, and measured performance profiling (Lighthouse, bundle analysis).

Repositories

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

MostafaIsmaiel wordpress-next invoices-app

Middle QA Engineer Confidence: Medium Generalist

Frontend TypeScript developer at a middle level specializing in component-driven React and Next.js application work. The strongest proven skill is building typed application data layers and API client logic as shown in src/app/lib/Controller.ts where locale handling, fetch wrappers and embed resolution are implemented. There is little to no evidence of automated tests, CI test integration, contract testing, or performance/load testing in public code.

Test Automation Frameworks

1/10

Building automated tests

Minimal test automation infrastructure exists only as lint configs; there are no test frameworks, fixtures, mocks, or parallelization/sharding configurations.

Evidence

MostafaIsmaiel/react-test/eslint.config.js MostafaIsmaiel/secure-print-system-desktop/eslint.config.js

Test Coverage & Strategy

1/10

What and how to test

No evidence of a deliberate test coverage or risk-based test strategy; no unit/integration/e2e test suites or tagging (smoke/critical/regression) are present.

Evidence

MostafaIsmaiel/react-test/package.json MostafaIsmaiel/secure-print-system-desktop/package.json younit-dev/wordpress-next/package.json

API & Integration Testing

2/10

Testing how parts work together

Application-level API client and data handling code exists with basic error handling and typed response shapes, but there are no contract tests, schema-validation test harnesses, or integration test containers.

Evidence

younit-dev/wordpress-next/src/app/lib/Controller.ts younit-dev/wordpress-next/src/app/lib/Schema.ts younit-dev/wordpress-next/types.d.ts

Performance & Load Testing

1/10

Testing speed under load

No performance or load-testing artifacts, scenarios, or threshold/SLO checks are present in the code or tooling.

Evidence

MostafaIsmaiel/react-test/package.json MostafaIsmaiel/secure-print-system-desktop/package.json

Bug Reporting & Analysis

1/10

Finding and describing bugs

No observable bug-reporting, changelog, or root-cause analysis artifacts; no reproducible-minimum examples or issue/PR tracebacks tied to fixes are present.

Evidence

MostafaIsmaiel/react-test/README.md MostafaIsmaiel/secure-print-system-desktop/README.md

CI Test Integration

1/10

Running tests automatically

No CI workflow or test-integration manifests (workflows, matrix configs, per-test artifact capture or quarantine mechanics) are present; repository relies on local scripts only.

Evidence

younit-dev/wordpress-next/package.json MostafaIsmaiel/react-test/package.json

Technologies

TypeScript• since 2022 • Middle • 10+ projects

Recommendations

Develop and maintain frontend applications and UI component libraries using TypeScript, React and MUI, focusing on typed data flows and reusable styles.
Implement API contract testing and schema validation for the existing fetch-based data layer (start from src/app/lib/Controller.ts and add schemathesis or Pact tests).
Add unit and integration test suites (Jest/Testing Library) for reducers and components and introduce CI workflows that run selective tests on changes.
Build Electron-based desktop features that mirror web logic, reusing shared TypeScript modules and adding end-to-end tests for key flows.

Repositories

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

wordpress-next react-test secure-print-system-desktop