Auth, authorization, token flows, and risk-aware delivery.
Backend Systems Studio
Open to remote backend roles
I engineer the invisible backend systems that make products feel fast, safe, and dependable.
I’m Feroze Basha, a .NET backend developer focused on secure APIs, identity flows, automation, and delivery-ready architecture. The goal is simple: systems that stay understandable for the team and reliable for the user.
Delivery Window
2022 → now
Specialty
.NET 8, Identity, APIs
Working Style
Clean, secure, collaborative
System Snapshot
What I optimize for in production
Signal stable
Services that stay readable as features, teams, and domains expand.
Playwright, Selenium, and disciplined backend validation.
Clear contracts, practical communication, and fewer handoff surprises.
- Secure Migrated authentication hashing from MD5 to SHA-256.
- Automated Added end-to-end test flows for critical user journeys.
- Built Shipped systems across event, commerce, resort, and SDLC domains.
How teams use me
Backend partner for systems that cannot feel fragile.
Best fit for teams who need APIs, auth, and delivery structure without needless complexity.
Core themes
- Secure APIs and access control
- Architecture that survives iteration
- Automation that reduces regressions
Preferred stack
- C#, .NET 8, ASP.NET Core
- SQL Server, PostgreSQL, Redis
- Playwright, Selenium, Azure DevOps
Selected Systems
Projects framed like products, not placeholders.
Each build below reflects the kind of backend work I enjoy most: shaping APIs, protecting workflows, and making sure the architecture stays coherent under real delivery pressure.
Active Development
Eventra
Eventra is where I’m refining domain workflows for events, attendees, identity, and notifications. The focus is on predictable backend behavior now so the product can grow without turning brittle later.
What is being shaped
- Authentication and role-based access
- Scalable domain workflows for events and operations
- Reliable notifications and backend process boundaries
Design intent
- Clear contracts for frontend and product teams
- Feature-ready architecture instead of one-off endpoints
- Delivery discipline from the first version
Hospitality Operations
Resort Management
A backend-focused system for bookings and operational workflows, designed to stay structured while supporting multiple types of resort activity.
- Role-based access and backend consistency
- Booking-oriented workflows with future scale in mind
- Architecture built for extension, not just launch
.NET 8
ASP.NET Core
JWT Auth
PostgreSQL
Compliance Intelligence
SDLC Analyzer
This project combines backend architecture with model-assisted analysis so teams can surface important delivery signals earlier in the lifecycle.
- Structured API layer for analysis workflows
- ML-assisted processing kept behind stable backend boundaries
- Security-aware handling of inputs and outputs
.NET 8
ML.NET
Hugging Face
Clean Architecture
Commerce Backend
CongoCart
CongoCart focuses on the backend mechanics that make checkout dependable: validation, security, workflow clarity, and future support for scale.
- JWT-based access and role-aware checkout flows
- Order and cart behavior shaped for consistency
- Architecture designed to grow into a fuller platform
.NET 8
ASP.NET Core
JWT
PostgreSQL
Capabilities
The backend work I’m strongest at when stakes are real.
The common thread across my projects is disciplined backend thinking: design the right seams early, secure the important paths, and make ongoing delivery easier for the team.
API Platforms
Service boundaries that stay clean as features expand.
REST and backend workflows designed for clarity, maintainability, and future scale.
Identity
Authentication and authorization treated as product-critical.
JWT, access control, and secure defaults implemented with practical delivery in mind.
Messaging
Reliable integrations, notifications, and asynchronous handoffs.
Workflows that reduce fragility when services need to coordinate under load.
Data
Query discipline and persistence choices that respect performance.
SQL-first thinking, structured access patterns, and room for caching when it matters.
Testing
Automation placed where it genuinely protects release confidence.
Backend validation plus end-to-end flows using Playwright and Selenium where useful.
Delivery
Collaboration patterns that lower friction across product, QA, and frontend.
Readable contracts, clearer handoffs, and fewer surprises as the system evolves.
Process
My delivery model favors clarity before complexity.
I like systems that can be explained, tested, and evolved without drama. That only happens when the engineering process is intentional from the start.
Shape the domain
Understand the product flow, failure cases, and access rules before endpoint design starts.
Design the contracts
Define service boundaries, request flows, and naming that keep the system readable later.
Build with guardrails
Secure important paths, keep the codebase testable, and avoid infrastructure leaking everywhere.
Harden delivery
Support the release with automation, debugging clarity, and collaboration across the team.
Experience
Work that ranges from platform hardening to domain-focused product systems.
My background spans security, delivery engineering, and product-oriented backend builds. That mix helps me make architecture decisions that are both practical and protective.
Feb 2024 → Present
Olympus
Lead Engineer
- Migrated legacy cryptographic implementations from MD5 to SHA-256 in authentication modules.
- Improved performance, scalability, and maintainability through targeted backend enhancements.
- Built end-to-end automation for critical workflows using Playwright and Selenium with Python.
.NET 8, C#, Azure DevOps, Git, Python, Playwright
Nov 2023 → Jan 2024
HCL Tech
Software Engineer
- Built an SDLC requirement analyzer using .NET 8, ML.NET, and Hugging Face models.
- Supported implementation, deployment, and production readiness for enterprise .NET systems.
.NET 8, C#, ML.NET, Hugging Face, Git
May 2023 → Aug 2024
CTGI
App Developer
- Integrated IdentityServer-based authentication and authorization across the application.
- Added a mobile security layer that reduced vulnerability exposure and tightened access flows.
C#, .NET, OAuth 2.0, OpenID Connect, Azure, TFS
Nov 2022 → Apr 2023
Security Engineering
Security Framework Developer
- Enabled mTLS and JWT-based token security as part of a hardened application framework.
- Reinforced core authentication protocols to improve defensive posture for connected systems.
mTLS, JWT, OAuth 2.0, OIDC, .NET, C#, X.509 Certificates
Writing & Roadmaps
Learning systems I maintain in public.
I keep these guides as a way to sharpen fundamentals and document the kind of thinking I bring to real projects: practical, structured, and geared toward long-term growth.
Roadmap
SQL Master Roadmap
Practical progression for stronger database thinking and query discipline.
RoadmapC# Master Roadmap
A structured path for improving language fluency and production readiness.
Best PracticesSOLID Principles in C#
Readable examples of design principles applied to real backend code.
Guide.NET + React Mastery
Full-stack learning notes with backend-heavy engineering discipline.
RoadmapLINQ Master Roadmap
A focused path for writing cleaner, more expressive data access logic.
Contact
If you need a backend that feels trustworthy, let’s talk.
I’m most useful when a team needs stable APIs, stronger security, better architecture discipline, or someone who can help the backend become easier to ship with.
- Backend role opportunities
- Secure API and identity-focused work
- Product systems that need cleaner architecture