Retrieval
Problem
Weak grounding creates confident but incorrect responses.
Decision
Hybrid retrieval + contextual memory + evaluation datasets.
Tradeoff
Higher infra complexity for better answer trust.
Engineering
I write and build from the engineering side of AI: stateful agents, retrieval quality, backend contracts, model runtime constraints, deployment topology, and the tradeoffs that show up after a demo becomes a real system.
engineering.log
Primary Lens
Production AI systems
Current Focus
Agents, RAG, backend reliability
Architecture Style
Explicit state, typed APIs, observable flows
Audience
Engineers, founders, platform teams
This page is for engineers who want to inspect my stack choices, developers who want a practical signal, and clients who need to understand how I make architecture decisions.
Architecture Radar
I use this as an engineering ledger: what I trust in production, what I am testing in labs, what I am studying carefully, and what I avoid when reliability matters.
Agent state, tool routing, memory boundaries, retries, and human approval gates.
Cloud and local runtimes evaluated against latency, privacy, cost, and reasoning depth.
Retrieval quality, hybrid search, pgvector patterns, reranking, and grounding loops.
FastAPI services, container paths, observability, deployment handoff, and frontend surfaces.
24
7
2
1
Manoj's primary choice for building stateful multi-agent systems. The checkpointer persistence pattern is vital for banking and business workflows.
Single-prompt loops fail on multi-step reasoning, resulting in brittle tool executions.
Deploy LangGraph to model agent transitions as deterministic state machines with persistence layers.
Requires explicit state modeling in exchange for predictable, resumable execution paths.
Decision Ledger
I do not pick tools because they are fashionable. I start from failure modes: weak grounding, opaque agent loops, prototype backends, missing traces, slow feedback cycles, and platform handoff risk.
Decision map
How production constraints shape architecture choices
Retrieval
Problem
Weak grounding creates confident but incorrect responses.
Decision
Hybrid retrieval + contextual memory + evaluation datasets.
Tradeoff
Higher infra complexity for better answer trust.
Orchestration
Problem
Single-agent flows fail on multi-step business operations.
Decision
LangGraph-style stateful agent routing with tool gating.
Tradeoff
More state modeling in exchange for reliability.
Backend
Problem
Prototype notebooks cannot support production workloads.
Decision
FastAPI services, async workers, queue-backed execution.
Tradeoff
More platform discipline for delivery velocity.
Observability
Problem
Teams cannot explain failures or regression causes.
Decision
Trace IDs, eval loops, latency/cost/error instrumentation.
Tradeoff
Instrumentation overhead for operational confidence.
System Maps
These are the recurring patterns I come back to when an AI product has to leave a notebook and become a service that developers can own, debug, and improve.
LangGraph-based workflows with explicit state, tool routing, memory, fallbacks, and evaluation.
Intent
Planner
Agent State
Tools
Human Gate
Trace
Tradeoffs
Retrieval pipelines designed for grounding quality, latency budgets, observability, and regression testing.
Corpus
Chunking
pgvector
Hybrid Search
Rerank
Evals
Tradeoffs
Async Python services, model gateways, queues, trace IDs, and deployment paths for AI product teams.
API
Queue
Workers
Model Gateway
Store
Observability
Tradeoffs
Stack
My work sits across orchestration, retrieval, model runtime, backend services, infrastructure, and frontend delivery. The breadth is intentional because production AI rarely fails in only one layer.
Trajectory
The AI work is built on years of frontend architecture, enterprise platform delivery, microfrontends, backend APIs, regulated banking systems, and cloud-native engineering.
Publicis Sapient
Leading the architecture design and POC-to-production lifecycle of enterprise Generative AI platforms, multi-agent orchestrations, and high-recall retrieval systems.
Designing resilient state-machine graphs (LangGraph), secure Cloudflare egress proxy tunnels, pgvector database configurations, and context compaction pipelines that survive enterprise audits.
Publications
I treat writing as part of the engineering loop. It forces architecture decisions to become clear enough for other developers, technical buyers, and platform teams to evaluate.
Architectural guidelines on multi-agent messaging protocols, state serialization, message schemas, and execution synchronization within LangGraph and Model Context Protocol architectures.
An in-depth systems analysis of hybrid retrieval execution. Focuses on combining dense vector search (pgvector/Qdrant) and sparse document keyword indexes (MongoDB), optimized through cross-encoder reranking.
Research on low-latency local agent runtimes. Analyzes hardware-accelerated local execution constraints on Apple Silicon environments using Ollama, MLX, and vLLM gateways.
A comprehensive design pattern for enterprise document ingestion. Combines layout-aware OCR parsers, layout bounding boxes, and multimodal LLMs to automate unstructured record extractions.
Systems research analyzing automated financial market research. Features multi-agent routers executing complex technical audits, sentiment parsing, and algorithmic risk evaluations.
Operating Philosophy
My engineering style is practical: study the system, build the smallest credible proof, measure the failure modes, and only then decide whether a tool deserves production trust.
By heart a Software Engineer — Look Beyond the System
I do not treat AI as a collection of magical black boxes. To build platforms that scale, you must look beyond the models themselves and understand the systems supporting them. For me, AI architecture is software engineering at its highest resolution—requiring the same rigor in state persistence, API contracts, latency budget allocations, and performance optimization as any legacy system.
Staying at the cutting edge requires a continuous feedback loop: reading research papers, analyzing distributed systems designs, exploring new tooling (like the Model Context Protocol or the UV package manager), and writing proof-of-concept (POC) scripts to evaluate performance limitations under load.
I treat AI as a powerful engineering multiplier. I utilize agent runtimes to automate scaffolding, test setups, and documentation. However, I anchor these tools with rigorous context engineering, ensuring structured inputs, predictable constraints, and direct architectural guardrails.
Work With Me
Bring the architecture constraint: retrieval quality, agent failure modes, backend latency, evaluation gaps, deployment topology, platform handoff, or developer adoption.