.NET backend engineering
C#, ASP.NET Core, Web API, Entity Framework, microservices and performance tuning for enterprise ERP products.
AI Engineering · .NET · Azure
Senior Software Engineer | AI Engineer
Building production-grade AI, LLM, RAG, and backend systems with .NET, Python, and Azure.
# illustrative request flow
query = "user question"
rewrite_prompt(query)# prompt rewriting
embed(query)# embeddings
vector_db.search(top_k)# semantic search
rerank(chunks)# re-ranking
build_context(chunks)# retrieval
llm.generate(context)# Azure OpenAI
answer# grounded response
Figures are approximate and self-reported.
AI that is connected to real systems: ERP data, databases, APIs, industrial hardware and production infrastructure.
I am a software engineer with nearly six years of experience building enterprise software and backend platforms at Akij iBOS Limited. My foundation is C# and .NET: ASP.NET Core APIs, Entity Framework, microservices and database-driven systems for ERP, supply chain and accounting products.
Over the last few years I have added the AI layer on top of that foundation: LLM applications with OpenAI and Azure OpenAI, retrieval-augmented generation, embeddings, embedding-based semantic search over vector databases, tool calling and agent workflows, and RAG evaluation. Python and FastAPI are my tools for the AI services; .NET remains my tool for the enterprise systems they plug into.
What I care about is connecting AI to real systems: ERP data, SQL databases, enterprise APIs, industrial hardware and production infrastructure on Azure, Docker and Kubernetes. I also work on industrial and IoT solutions, from Modbus/RS485 control to computer vision on the production line, and I lead a small engineering team.
C#, ASP.NET Core, Web API, Entity Framework, microservices and performance tuning for enterprise ERP products.
Document ingestion, chunking, embeddings, vector search, context construction and grounded generation.
Function/tool calling, agent workflows and MCP-style integration of enterprise capabilities as tools.
Azure App Service, Azure Functions, Azure OpenAI, Docker, Kubernetes and Azure DevOps CI/CD pipelines.
ERP, SQL Server and PostgreSQL data, Google Workspace APIs and event-driven integration for downstream AI.
PLC, Modbus RTU over RS485, MQTT, ESP32-class hardware and computer vision for production monitoring.
Grouped by area. Ratings are my own honest self-assessment, and established production experience is deliberately separated from project, research and exploratory work.
Self-assessed, not certified. Scores are on a 10-point scale and are not test results or externally validated measurements.
LLM applications, retrieval and evaluation.
Agentic systems, open-weight models and exploratory work.
Enterprise .NET and Python service engineering.
Relational, vector, search and cache stores.
Azure-first delivery, containers and pipelines.
Field hardware, protocols and edge inference.
Enterprise software and applied AI in a production environment.
Akij iBOS Limited
toPresent
Building and running enterprise software for the iBOS ERP ecosystem, and adding LLM, RAG and automation capabilities on top of it.
Formal education, plus the areas I am actively learning. Exploration is labelled as exploration.
University of Asia Pacific (UAP)
CGPA 3.85 / 4.00
Udemy · 5 Aug 2026
Studying evaluation for LLM and RAG systems: relevance, groundedness, fluency, retrieval quality and context quality, including Azure AI evaluation concepts.
Working through model deployment on Azure AI Foundry, Foundry Local, and the regional availability and quota constraints that come with them.
Project-level exploration of LangGraph, LlamaIndex and A2A alongside MCP, mainly through the AgentMesh reference architecture.
Experiments with QLoRA, Hugging Face tooling and open-weight or small language models. Research and experimentation, not production training.
Running open-weight models with Ollama and vLLM on GPU hardware to evaluate enterprise AI that keeps data off external APIs.
Each card is labelled with its real maturity. Only Production means running in production; MVP, Prototype, Concept, Reference and Research are used wherever that is more accurate.
Showing 9 of 9 projects
AI & RAG
MVPEnterprise knowledge retrieval that grounds LLM answers in indexed company documents using embeddings, a vector database and embedding-based semantic search.
AI Agents
PrototypeA multi-agent interview platform design covering interview planning, question generation, answer evaluation, behavioral analysis and report generation.
Enterprise Systems
ConceptAn architecture for collecting events across business systems, detecting anomalies, scoring risk and recommending controlled actions.
AI & RAG
MVPJob recommendation and candidate matching that combines parsed profile and job features, semantic embeddings and a 100-point scoring framework.
Industrial AI
PrototypeProduction-line monitoring that combines computer vision, edge inference and telemetry, with industrial control over Modbus RTU / RS485.
AI Agents
ConceptA concept for exposing ERP capabilities to LLM agents as governed tools through the Model Context Protocol.
AI Agents
ReferenceA reference architecture for an enterprise AI platform: provider-agnostic LLM access, agent runtime, RAG and MCP behind a hexagonal core.
AI & RAG
PrototypeConnects email history, ERP master data and Google Workspace activity in a knowledge graph to power AI search and relationship analysis.
Research
ResearchResearch into serving open-weight models locally with Ollama and vLLM so enterprise AI does not have to send all data to external APIs.
Selected repositories, maintained by hand so the numbers and descriptions stay accurate.
@haque023
github.com/haque023
The request path of a typical RAG or LLM application, and the infrastructure around it. A general pattern, not a description of one specific deployment.
Employee, customer or calling system
Browser · API client
Authenticated chat or web interface
Web UI
Authentication, validation and business APIs
ASP.NET Core · FastAPI
Prompt assembly, tool calling, agent workflow
Python · MCP · tool calling
Query rewriting, embedding, semantic and hybrid search, re-ranking, context construction
Embeddings · semantic search
Chunk vectors with metadata
Qdrant · ChromaDB
Grounded generation from retrieved context
Azure OpenAI · OpenAI · Ollama / vLLM
Answer returned to the user and logged for evaluation
JSON · UI
AI coreSupporting infrastructure
01
A feature is done when it runs reliably for real users, not when the demo works.
02
Clear boundaries and replaceable adapters keep systems testable and easy to evolve.
03
Well-defined contracts let frontends, agents and other services integrate cleanly.
04
Logging, monitoring and tracing are designed in, so behaviour can be explained.
05
Measure first, then fix the real bottleneck. Latency is a product feature.
06
Authentication, least privilege and controlled automation from the first sketch.
07
Swappable models and stores, asynchronous work and stateless services.
08
Use the simplest approach that solves the problem, and evaluate it honestly.
Reach out about AI engineering, .NET backend or enterprise AI integration work. Email is the quickest way to reach me.
A short note about the problem, the systems involved and the timeline is all I need to get started.
Email me