Fisayo Adegun
Backend Developer
5+ years exp
SQL
JavaScript
C#
Security & Auth: 4/10
Active 9 days ago
+234 (706) 2353260 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Backend .NET engineer (early middle level) focused on building REST services and identity flows with practical integration glue as a strength. The strongest proven skill is building simple CRUD REST endpoints and MongoDB-backed services as shown in AgentyJobApplication/Services/MyResumeService.cs and AgentyJobApplication/Controllers/AgentyJobApplicationController.cs. There is limited evidence of production-grade observability, resilience patterns, advanced performance tuning or automated test coverage in the public code.
Technical skills
SQL
JavaScript
C#• Senior • 5y+
C#
WPF
Entity Framework Core
ASP.NET Core• 5y+
xUnit• 3y+
Databases
PostgreSQL
RabbitMQ
MongoDB
MS SQL• 5y+
Frontend
Angular
Frontend
UI
DevOps
Amazon EC2
CI/CD
Rest API
AWS• 3y+
Azure• 3y+
Docker• 3y+
Git• 3y+
Kubernetes• 3y+
QA
Swagger• 3y+
Mobile
MVC• 3y+
Timeline
Cloud & Devops
•
Middle
Duteko LTD
•
Full-Time
Worked on cloud and DevOps using Microsoft Azure and AWS services, alongside containerized infrastructure. Used Docker and Kubernetes to support application deployment and operations, with IIS as part of the hosting environment.
Azure
AWS
Docker
Kubernetes
Backend Engineer
•
Middle
Duteko LTD
•
Full-Time
Developed and deployed backend services for a peer-to-peer delivery platform using C# and ASP.NET Core. Implemented JWT-based authentication and secured API endpoints, and modeled application data in SQL Server for improved query performance. Integrated Stripe payments for secure deposits and withdrawals, wrote unit tests to validate API behavior, and collaborated with mobile developers to support end-to-end integration.
C#
ASP.NET Core
MS SQL
University of Agriculture
Bachelor's Degree •
Electrical and Electronics Engineering
Software Developer
•
Middle
GMT Nigeria Limited
•
Full-Time
Designed and built a unified terminal operations management system covering bonded, off-dock, and barging workflows. Optimized SQL Server schema, queries, and indexing to reduce peak-time latency, and improved reliability with structured logging and monitoring. Developed warehouse and engineering inventory management applications using REST APIs and WPF, and deployed desktop/server components on Windows via IIS.
C#
ASP.NET Core
MS SQL
Rest API
WPF
Middle Backend Developer
Confidence: Medium API Engineer
Backend .NET engineer (early middle level) focused on building REST services and identity flows with practical integration glue as a strength. The strongest proven skill is building simple CRUD REST endpoints and MongoDB-backed services as shown in AgentyJobApplication/Services/MyResumeService.cs and AgentyJobApplication/Controllers/AgentyJobApplicationController.cs. There is limited evidence of production-grade observability, resilience patterns, advanced performance tuning or automated test coverage in the public code.
API Design
3/10
How well APIs are designed
API design shows conventional REST controllers and OAuth/OIDC flows via IdentityServer, but lacks explicit versioning, idempotency, consistent error contracts, or advanced pagination patterns.
Evidence
Mango.Services.Identity/MainModule/Account/AccountController.cs
AgentyJobApplication/Controllers/AgentyJobApplicationController.cs
Data Layer & Database
2/10
Working with databases
Data layer includes basic MongoDB usage and Entity Framework migrations, but there is little evidence of transactional control, tuned queries/indexes, or schema-evolution beyond generated migrations.
Evidence
AgentyJobApplication/Services/MyResumeService.cs
Mango.Services.Identity/Migrations/20230428135819_addedfirstnamelastname.Designer.cs
Scalability & Performance
2/10
Handling load and speed
Some asynchronous and messaging components are present in the project layout, but the provided code lacks concrete, reasoned scalability patterns such as cache invalidation strategies, connection pooling configuration, or measured performance tuning.
Evidence
Mango.MessageBus/AzureServicebusMessageBus.cs
Mango.Services.OrderAPI/Messaging/RabbitMQCheckoutConsumer.cs
System Architecture
3/10
Overall system structure
The repository is organized into multiple bounded projects (Identity, ProductAPI, OrderAPI, PaymentAPI, ShoppingCartAPI, Web), indicating service decomposition and modular boundaries, but the decomposition appears scaffolded and there is limited evidence of deliberate cross-service contracts, graceful degradation or config/secret management.
Evidence
Mango.Services.ProductAPI/Repository/ProductRepository.cs
Mango.Web/Services/ProductService.cs
Security & Auth
4/10
Protecting data and access
Authentication and authorization are handled via ASP.NET Identity and IdentityServer flows with anti-forgery attributes and event raising, showing reasonable security awareness; however, token lifecycle management, refresh/revocation flows and dependency audits are not clearly documented in the surfaced code.
Evidence
Mango.Services.Identity/MainModule/Account/AccountController.cs
Reliability & Observability
2/10
Stability and monitoring
Minimal reliability and observability patterns are visible: there are basic try/catch blocks and default ASP.NET host setup, but no structured logging, metrics, retries with backoff, circuit breakers or graceful shutdown handlers in the inspected code.
Evidence
AgentyJobApplication/Services/MyResumeService.cs
AgentyJobApplication/Program.cs
Expertise
.NET• Middle
Microservices & API Architecture• Middle
Industries
Commerce• Middle
Technologies
SQL
C#• Senior • 5y+
MongoDB
PostgreSQL
RabbitMQ
Azure• 3y+
MS SQL• 5y+
CI/CD
Git• 3y+
AWS• 3y+
Docker• 3y+
Kubernetes• 3y+
ASP.NET Core• 5y+
Entity Framework Core
WPF
xUnit• 3y+
Amazon EC2
Recommendations
- Develop small to medium ASP.NET Core microservices with REST APIs and MongoDB or EF Core-backed storage, owning the full request path including validation and simple error contracts.
- Implement message-driven integrations (RabbitMQ/Azure Service Bus) for decoupling, concentrating on idempotency, retries with exponential backoff and clear message schemas.
- Harden services by adding structured logging, telemetry (OpenTelemetry/Prometheus), and automated tests (unit and integration) for critical flows such as auth and payments.
- Improve API practices by adding versioning, consistent error DTOs, input validation at boundaries, and documented contract examples for clients.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern Frontend Developer
Confidence: Low UI Engineer
Frontend UI engineer (early-career) focused on maintaining and integrating legacy jQuery UI libraries. The strongest proven skill is integrating third-party frontend libraries, evidenced by the presence of wwwroot/lib/jqueryui/jquery-ui.js. There is little to no original application code, component design, async state management, tests, or modern-framework usage evident for deeper assessment.
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
Verified artifacts
Technologies
Frontend
UI
JavaScript
Angular
Recommendations
- Maintain or extend jQuery-based UIs and widgets such as datepickers and autocomplete where the codebase depends on jQuery UI.
- Perform incremental modernization or vendor-upgrades of legacy frontend libraries and improve dependency hygiene (audit and update jquery-ui, jquery.validate, unobtrusive scripts).
- Lead small migration projects to a modern component framework by extracting UI requirements and replacing widgets incrementally (eg porting datepicker/autocomplete to a modern library).
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern QA Engineer
Confidence: Medium Generalist
A junior ASP.NET Core developer focused on building simple REST APIs backed by a database. The strongest proven skill is implementing basic CRUD endpoints and MongoDB integration as shown in AgentyJobApplication/Controllers/AgentyJobApplicationController.cs and AgentyJobApplication/Services/MyResumeService.cs. No automated tests, CI integration, contract testing or performance/load testing are evidenced in the public code.
Test Automation Frameworks
1/10
Building automated tests
Minimal test automation artifacts; a web API project is present but there are no test fixtures, factories, mock servers or parallelization config.
Evidence
AgentyJobApplication/Startup.cs: services.AddControllers() and service registrations
AgentyJobApplication/Controllers/AgentyJobApplicationController.cs: simple POST and GET endpoints without test hooks
Test Coverage & Strategy
1/10
What and how to test
No visible automated test coverage or risk-based test structure; only basic error handling exists in service methods but no unit, integration or property-based tests.
Evidence
AgentyJobApplication/Services/MyResumeService.cs: try/catch around CreateAsync/GetAsync but no tests
AgentyJobApplication/Controllers/AgentyJobApplicationController.cs: controller logic implements CRUD endpoints but no test files or test tags
API & Integration Testing
1/10
Testing how parts work together
API and integration work is limited to direct use of a database driver; there is no contract testing, schema validation or idempotency/retry test coverage evident.
Evidence
AgentyJobApplication/Services/MyResumeService.cs: uses MongoDB.Driver InsertOneAsync and Find(...).FirstOrDefaultAsync()
AgentyJobApplication/Startup.cs: configuration binding for AgentyJobApplicationDatabaseSettings
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
Finding and describing bugs
Not evidenced in public code
CI Test Integration
Running tests automatically
Not evidenced in public code
Industries
Travel & Tourism• Intern
Technologies
Rest API
Swagger• 3y+
Recommendations
- Build unit and integration tests for service and controller layers using a test framework to validate both success and explicit failure cases (nulls, DB timeouts, 4xx/5xx).
- Add contract/schema validation for API responses and inputs and introduce small integration tests that exercise MongoDB interactions (use testcontainers or an in-memory approach).
- Introduce CI pipeline with selective test runs, failure artifacts and a per-test retry/quarantine strategy to improve reliability before expanding features.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: