Ahmed Alaa
Full Stack Developer
JavaScript
TypeScript
C#
SQL
Data Layer & Database: 6/10
Security & Auth: 6/10
API Design: 5/10
Active 1 day ago
+20 (15) 58561998
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Senior .NET backend engineer specializing in building DDD-inspired APIs and background processing. The strongest proven skill is backend architecture and layering demonstrated by application and infrastructure modules such as LoginCommandHandler, BackgroundTaskProcessor, and RedisCacheService. Public code lacks CI/test-infra, contract testing, and formal performance/load testing artifacts.
Technical skills
JavaScript
TypeScript• Middle
C#• Senior
SQL
C#
AutoMapper
MediatR
xUnit
ASP.NET Core
Entity Framework Core
SignalR
Databases
Redis
Frontend
NgRx
Next.js
React.js
Tailwind CSS
Bootstrap
Angular
DevOps
Docker Compose
Rest API
Mobile
Clean Architecture
Capacitor
Ionic
Timeline
Full Stack Developer
•
Middle
Shoufli Marketplace Platform
•
Full-Time
Developed a full-stack service marketplace for customers and service providers across web and mobile. Built scalable RESTful APIs using ASP.NET Core and Entity Framework Core, and implemented a responsive Angular single-page application. Created cross-platform mobile apps with Ionic and Capacitor, added real-time updates and notifications with SignalR, and implemented an admin moderation workflow for user changes.
ASP.NET Core
Entity Framework Core
Angular
TypeScript
SignalR
SQL
Redis
Rest API
Ionic
Capacitor
Benha University
Bachelor's Degree •
Computer Science
Senior Backend Developer
Confidence: Medium API Engineer
Backend API engineer (senior-level, assessed conservatively) focusing on .NET APIs, authentication and background processing with a strength in layered architecture and persistent token handling. The strongest proven skill is backend authentication and token lifecycle design demonstrated by JwtProvider, RefreshTokenService and supporting migrations and repositories. There is limited evidence of production-grade observability, advanced operational hardening (retries with backoff and circuit breakers) and explicit rate limiting or API versioning strategies in public code.
API Design
5/10
How well APIs are designed
API design shows deliberate DTOs, validation layers and consistent error responses, but lacks explicit versioning, idempotency keys and advanced pagination patterns.
Evidence
TaskManagementSystem/TaskManagement.Api/Controllers/AuthController.cs
TaskManagementSystem/TaskManagement.Application/Common/Errors/ErrorResponse.cs
TaskManagementSystem/TaskManagement.Api/Requests/Authentication/RefreshTokenRequest.cs
Data Layer & Database
6/10
Working with databases
Data layer uses EF Core with explicit migrations, indexes and constraints, plus a Unit of Work and repository abstractions indicating conscious transaction/boundary choices; no hand-tuned raw SQL or explicit isolation-level handling is present.
Evidence
EmployeeManagementSystem/Migrations/20260616070739_InitialCreate.cs
TaskManagementSystem/TaskManagement.Infrastructure/Persistence/Migrations/20260707183048_AddSoftDeleteToUsers.Designer.cs
EmployeeManagementSystem/Repositories/UnitOfWork.cs
Scalability & Performance
5/10
Handling load and speed
There is practical work on scalability such as Redis caching and background task queues, showing attention to decoupling and performance, but no evidence of measured load testing, advanced cache invalidation strategies or rate limiting policies.
Evidence
TaskManagementSystem/TaskManagement.Infrastructure/Caching/RedisCacheService.cs
TaskManagementSystem/TaskManagement.Infrastructure/Background/BackgroundTaskQueue.cs
TaskManagementSystem/TaskManagement.Infrastructure/Background/PriorityEscalationProcessor.cs
System Architecture
5/10
Overall system structure
The codebase is layered (Domain/Application/Infrastructure) with DI registration and clear module boundaries, reflecting intentional architecture; it is not a distributed microservices design and secret/config management is limited to options classes.
Evidence
TaskManagementSystem/TaskManagement.Application/DependencyInjection.cs
TaskManagementSystem/TaskManagement.Infrastructure/DependencyInjection/InfrastructureServiceRegistration.cs
TaskManagementSystem/README.md
Security & Auth
6/10
Protecting data and access
Authentication and token lifecycle are explicitly implemented (JWT provider, refresh tokens, password hashing and refresh token persistence), and input validation patterns exist; there is limited evidence of dependency auditing, secret rotation, or advanced threat mitigations.
Evidence
TaskManagementSystem/TaskManagement.Infrastructure/Identity/JwtProvider.cs
TaskManagementSystem/TaskManagement.Infrastructure/Identity/RefreshTokenService.cs
TaskManagementSystem/TaskManagement.Application/Features/Authentication/Commands/RefreshToken/RefreshTokenCommandHandler.cs
Reliability & Observability
4/10
Stability and monitoring
There are reliability patterns such as global exception middleware, background worker base classes and unit tests for auth handlers, but advanced observability (structured logging with correlation ids, metrics/alerts), timeouts/retries with backoff, and graceful shutdown patterns are not clearly evidenced.
Evidence
TaskManagementSystem/TaskManagement.Api/Middleware/ExceptionHandlingMiddleware.cs
TaskManagementSystem/TaskManagement.Infrastructure/Background/BaseBackgroundWorker.cs
TaskManagementSystem/TaskManagement.UnitTests/Features/Authentication/Login/LoginCommandHandlerTests.cs
Verified artifacts
Expertise
Microservices & API Architecture• Middle
Backend AI & LLM• Middle
Technologies
Rest API
MediatR
xUnit
.NET• mentioned only
Core• mentioned only
Recommendations
- Develop authenticated REST APIs with JWT refresh-token lifecycle and EF Core migrations, including secure password hashing and refresh token storage.
- Implement background processing and prioritized queues for asynchronous work using the existing BackgroundTaskQueue and worker patterns.
- Build caching-backed read paths with Redis and design cache invalidation strategies for frequently-read endpoints.
- Extend observability by adding structured logging with correlation ids, metrics (Prometheus) and well-reasoned retry/backoff policies for external calls.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Senior QA Engineer
Confidence: High Generalist
Senior .NET backend engineer specializing in building DDD-inspired APIs and background processing. The strongest proven skill is backend architecture and layering demonstrated by application and infrastructure modules such as LoginCommandHandler, BackgroundTaskProcessor, and RedisCacheService. Public code lacks CI/test-infra, contract testing, and formal performance/load testing artifacts.
Test Automation Frameworks
2/10
Building automated tests
Minimal unit-test artifacts exist but there is no evidence of a dedicated test framework, fixtures, test isolation, parallelization, or mock servers; tests appear limited to application unit tests.
Evidence
TaskManagementSystem/TaskManagement.UnitTests/Features/Authentication/LoginCommandHandlerTests.cs
TaskManagementSystem/TaskManagement.Application/Features/Authentication/Commands/Login/LoginCommandHandler.cs
Test Coverage & Strategy
2/10
What and how to test
Some validation and command-validator classes are present showing thought about input validation and negative cases, but there is no clear risk-based test structure, property-based tests, or documented negative-path test suites.
Evidence
TaskManagementSystem/TaskManagement.Application/Features/Authentication/Commands/Login/LoginCommandValidator.cs
TaskManagementSystem/TaskManagement.Application/Features/Tasks/Commands/CreateTask/CreateTaskCommandValidator.cs
TaskManagementSystem/TaskManagement.Application/Features/Tasks/Commands/UpdateTask/UpdateTaskCommandValidator.cs
API & Integration Testing
2/10
Testing how parts work together
API and integration concerns are implemented in the application code with error-response models and caching, but there is no evidence of contract testing, schemathesis/pact usage, testcontainers, or explicit error-path integration tests.
Evidence
TaskManagementSystem/TaskManagement.Api/Middleware/ExceptionHandlingMiddleware.cs
TaskManagementSystem/TaskManagement.Application/Common/Errors/ErrorResponse.cs
TaskManagementSystem/TaskManagement.Infrastructure/Caching/RedisCacheService.cs
Performance & Load Testing
1/10
Testing speed under load
There are components related to background processing and caching which speak to performance awareness, but no load or performance test scenarios, SLOs, or benchmarking artifacts are present.
Evidence
TaskManagementSystem/TaskManagement.Infrastructure/Background/BackgroundTaskProcessor.cs
TaskManagementSystem/TaskManagement.Infrastructure/Caching/RedisCacheService.cs
Bug Reporting & Analysis
Finding and describing bugs
Not evidenced in public code
CI Test Integration
Running tests automatically
Not evidenced in public code
Expertise
Unit & Component Testing• Middle
Industries
Software• Middle
Technologies
C#• Senior
Docker Compose
ASP.NET Core
Entity Framework Core
AutoMapper
Docker• mentioned only
SQL• mentioned only
Recommendations
- Develop backend APIs and microservices in .NET using repository/unit-of-work and MediatR-style patterns.
- Implement integration and contract tests (testcontainers, schemathesis or pact) alongside existing unit tests to cover error paths and idempotency.
- Build CI test pipelines with per-test artifacts, selective runs on diff, and quarantine mechanics for flaky tests.
- Lead development of background-processing and caching features for internal admin or productivity tools that require resilience and scaling.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: Medium Fullstack
Fullstack developer focused on small-to-medium applications with an emphasis on integrating LLM/GenAI into Next.js server routes and building UI pages in Angular and Next.js. The strongest proven skill is server-side AI integration and defensive validation as implemented in stunning/lib/ai.ts (generateProductPlan + isProductPlan) and the API route at stunning/app/api/generate/route.ts. There is limited evidence of large-scale architecture, performance optimization, automated tests, or advanced accessibility engineering in public code.
UI Component Architecture
3/10
How interface parts are built
Basic, component-based UI work exists (Angular components and HTML templates) but little evidence of deliberate component APIs, composition patterns, or a custom design system.
Evidence
najood/src/app/first-page/first-page.component.html: multiple component templates using Bootstrap grid and routerLink
najood/src/app/second-page/second-page.component.html: RTL-aware page template and content blocks
Responsive & Cross-browser
4/10
Works on all screens and browsers
Responsive layout is implemented with Bootstrap grid and RTL support is present; no advanced responsive strategies or container queries found.
Evidence
najood/package.json: bootstrap dependency declared
najood/src/app/first-page/first-page.component.html: use of col-md-* classes and dir="rtl"
Performance Optimization
1/10
Speed of the interface
No measured performance work, bundle analysis, virtualization, or explicit code-splitting strategies are present.
Evidence
stunning/next.config.ts: default empty config (no performance tuning)
stunning/package.json: no build-analysis or bundle-analyzer scripts
Accessibility & Semantics
2/10
Usable for everyone
Some semantic HTML and alt attributes exist and pages include dir attributes for RTL, but no ARIA patterns, focus management, keyboard handling, or CI a11y tooling discovered.
Evidence
najood/src/app/third-page/third-page.component.html: img elements with alt and dir attributes
najood/src/app/second-page/second-page.component.html: dir="rtl" applied to UI blocks
State Management & Data Flow
3/10
Managing data in the app
Server-side input validation and output validation are implemented around the AI call, showing attention to server-state discipline; client-side state management patterns are minimal.
Evidence
stunning/app/api/generate/route.ts: request body validation, prompt length check, integrations allowlist and deduping before calling AI
stunning/lib/ai.ts: isProductPlan type guard and JSON parse/error handling in generateProductPlan
UX & Visual Polish
2/10
Look and feel quality
UI pages show basic polish and layout but lack explicit UX patterns for loading/error/empty states, skeletons, optimistic updates, or undo flows.
Evidence
najood/src/app/fifthpage/fifthpage.component.html: structured content blocks and list items without loading or error states
stunning/globals.css: baseline styling but no UI state styles (skeletons, spinners)
Expertise
React• Middle
Angular• Junior
Frontend AI Integration• Middle
Modern Web Frameworks• Middle
Industries
Artificial Intelligence• Middle
Software• Middle
Technologies
TypeScript• Middle
Tailwind CSS
Next.js
Angular
Bootstrap
React.js
NgRx
Recommendations
- Implement and extend server-side AI integrations and safe-guards for small-to-medium products, including schema validation and response parsing.
- Build and iterate UI prototypes and multi-page experiences using Angular or Next.js, focusing on RTL and responsive layouts.
- Add testing, CI a11y checks, and basic performance measurements (bundle analysis, Lighthouse) to strengthen production readiness.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: