Claude API features shipped inside a live .NET / SQL Server financial platform — prompt caching, structured outputs and queries written for the production database.
Result — LLM features live in production — Claude API with prompt caching and structured outputs, EF Core queries written for the live SQL compatibility level, and fallbacks when the model fails.
Role
AI Developer
Stack
.NET · EF Core · SQL Server · Claude API · Angular
Context — Safe Financials is a live fintech platform: .NET services, EF Core and SQL Server data layers, Angular interfaces, and customers who depend on it every day.
Problem — large financial workflows needed AI assistance, and it had to run inside the existing production platform, not a greenfield service with friendly constraints.
Constraints — a live database running at a lower SQL compatibility level than the beta environment, large document context, cost and latency budgets, responses that must arrive as validated structures, and sensitive financial data where a raw model error can never reach a user.
My work — .NET service integration around the Claude API: prompt orchestration with caching to keep cost and latency predictable, structured outputs validated before use, EF Core query design written and verified against the live compatibility level, Angular integration, and fallback paths that degrade gracefully when a model call fails.
Production concerns — cost, latency, model failures, schema validation of every response, and deployment with rollback. AI runs as non-blocking workflows, so a slow or failed model call never stalls the platform.
Impact — LLM-backed features are running in the live platform today. Specific metrics and customer details are omitted due to confidentiality.
I build production AI systems with .NET, Azure and Angular — LLM features that cite their sources, fail safely, and ship through pipelines that can be rolled back.
Shipping LLM features inside a live .NET finance platform — structured outputs, prompt caching, and queries written for the database that actually runs them.
Public AI work
Release-risk review, grounded retrieval and evaluation gates — public repositories with tests and stated limits.
Azure delivery
CI/CD, observability and rollback paths that carry AI changes to users without surprises.
01 / Selected work
Selectedwork
A flagship AI build, public experiments, production software, and a small collection of sites I make for people.
Featured AI Engineering
The flagship: a working release-risk review MVP with public code, tests, CI and Docker.
Claude API features shipped inside a live .NET / SQL Server financial platform — prompt caching, structured outputs and queries written for the production database.
LLM features live in production — Claude API with prompt caching and structured outputs, EF Core queries written for the live SQL compatibility level, and fallbacks when the model fails.
A cinematic, image-first site for an established Hyderabad fashion photographer whose editorial and campaign work includes Allu Arjun, Vijay Deverakonda, Rashmika Mandanna, and houses such as RWDY.
Live at sandeepsanka.com — a full-bleed, motion-paced editorial site built with Next.js, TypeScript and GSAP.
A cinematic, film-still portfolio for a freelance photographer shooting celebrity portraits, actor portfolios, brand campaigns, and pre-weddings between Bengaluru and Hyderabad.
Live at sujana.zip — a monochrome, film-still portfolio built with Next.js and TypeScript.
Portrait, drawn from live data — the loom remembers your movement.
A software engineer specializing in practical AI integration and the systems around it.
My day-to-day work crosses .NET services, EF Core and SQL Server data layers, Angular and TypeScript interfaces, Azure delivery, and LLM-powered product features. I care about grounded outputs, explicit failure modes and what happens after the demo reaches production.
My production experience includes fintech software at Safe Financials and enterprise systems at AmpleLogic. The public projects below show the same approach in the open: working code, tests and documentation.
I also design and build personal sites. The Portfolios collection is that side of the practice: a live photographer’s site and an editorial personal portfolio, composed as custom work rather than a template.
Based
Hyderabad, India
AI
LLM integration · RAG · evaluation · guardrails
Engineering
.NET · C# · Angular · TypeScript · SQL Server
Delivery
Azure · CI/CD · observability · rollback design
Fig. 01 — emblem, drawn to spec
03 / Capabilities
Capabilities
The parts of AI development that turn a promising prototype into software a team can inspect, test and operate.
01
AI Product Engineering →
Choosing where a model belongs, designing structured contracts around it, and building explicit fallbacks instead of treating the provider as magic.
Claude & OpenAI APIs
Structured outputs
Prompt caching
Fallbacks
02
Retrieval & Agents →
Citation-first retrieval, tool boundaries and human approval paths that keep AI systems useful without hiding uncertainty.
RAG
Tool boundaries
Human in the loop
Exploring: MCP · Agent workflows
03
Evaluation & Safety →
Regression gates, evidence checks, privacy boundaries and adversarial cases that measure behavior before an AI change ships.
LLM evaluation
Guardrails
Cost & latency
CI gates
04
Production Systems →
ASP.NET Core services, Angular and TypeScript interfaces, SQL data layers, Azure delivery, telemetry and recovery plans built for the environment that actually runs them.
.NET
Angular
Azure
SQL Server
CI/CD & observability
04 / Contact
Build AI people can trust.
Open to full-time roles and product engineering work — especially teams shipping AI features that have to hold up in production.