Self-taught AI/ML Engineer & Data Scientist crafting production-ready AI systems from Kathmandu, Nepal.
I'm a self-taught engineer from Nepal who cold-emailed a US fintech and, during a Data Scientist internship, built the core of their AI underwriting platform, all while completing a BCA degree.
What started as curiosity about data turned into a full journey through the ML and AI ecosystem. I went from training my first Random Forest to designing production-grade RAG systems and multi-LLM orchestration layers, without a formal CS degree, driven entirely by self-study and shipping real projects. When I believed I was ready, I reached out to a US-based commercial real estate fintech directly. They gave me a shot, and I made it count.
During the internship I built the core of the core AI platform for commercial real estate lending, authoring 150+ commits to the core service, roughly 70% of its recent production-branch history. The platform runs a RAG pipeline that classifies and extracts structured data from 20+ financial document types in 55–90 seconds end to end, multi-provider LLM orchestration (AWS Bedrock, Gemini, OpenAI) with fallback chains and a throttle-aware circuit breaker, and a deterministic credit-decision engine deliberately separated from LLM narrative generation, so model hallucination or prompt injection cannot alter a lending decision. Underneath sits semantic retrieval over pgvector with HNSW search and cross-encoder reranking, and a two-service async architecture deployed to AWS via CI/CD.
In parallel, I shipped six additional production services, including a solo-built payments integration with signed webhooks, an internal knowledge-base RAG service, and an intake-to-offer valuation engine, and contributed to SOC 2 and NIST 800-53 readiness, designing the control matrix and audit-trail documentation. Independently, I also built a semantic code-search tool over a 42-repository organization, using tree-sitter AST chunking, local embeddings, Postgres/pgvector, and a custom MCP server integration.
Underneath the production work is a deep classical-ML foundation: 20+ structured end-to-end projects across classification, regression, time series forecasting, clustering, and anomaly detection, including 1M+ rows for fraud detection and 1.7M+ rows for price forecasting. My approach combines rigorous evaluation, model explainability through SHAP, and reproducible research, including a published research preprint on SHAP-based feature selection.
Proper evaluation, CV splits, no data leakage. Results you can trust.
SHAP values and feature importance, so black-box outputs become actionable insights.
Docker, FastAPI, JWT auth, rate limiting: models that actually ship.
The core AI underwriting platform, broken down by capability. The parts I built, and how they fit together.
A production AI platform for commercial real estate lending, turning raw financial documents into auditable credit decisions. Built for fault tolerance: it keeps producing decisions even under simultaneous provider failures, with deterministic logic at the core and LLMs only where they add value.
Classifies and extracts structured fields from 20+ document types (rent rolls, tax returns, appraisals, bank statements, leases) with OCR routing and content deduplication.
pgvector HNSW index over Titan v2 embeddings with CrossEncoder reranking, narrowing the candidate pool down to genuinely relevant context for grounded generation.
Rule-based risk scoring across borrower qualification, financial underwriting (DSCR, LTV, NOI), and compliance, with zero LLM in the critical decision path for auditability.
Per-task provider fallback across AWS Bedrock, Gemini, and OpenAI, with a coroutine-safe circuit breaker per provider (CLOSED → OPEN → HALF_OPEN) for automated failover.
Two-service stack (a FastAPI API and an async ARQ job worker) deployed to AWS ECS Fargate via GitHub Actions CI/CD, with connection pooling and multi-tier caching.
Authentication, webhook verification, SSRF defense, PII-safe structured logging, and per-route rate limiting, applied consistently across every API surface.
From self-study to production AI systems
US-based Commercial Real Estate Fintech · Remote
Built the core of the AI underwriting platform: a RAG document-intelligence pipeline, a deterministic credit-decision engine, multi-provider LLM orchestration with circuit breakers, and a two-service async stack on AWS ECS Fargate via GitHub Actions CI/CD.
Self-directed Research & Projects
Transitioned from classical ML to generative AI. Built RAG systems with FAISS and Qdrant, explored vector embeddings, cross-encoder reranking, and LLM API integration. Developed a production-grade Personal Knowledge Base RAG API.
Independent Research · Supervised by Marshal Basnet
Published preprint on SHAP-Based Feature Selection and Iterative Hyperparameter Tuning for Customer Churn Prediction in Telecommunication Datasets, demonstrating interpretability and optimization in production ML models.
Self-directed Learning
Built 20+ end-to-end ML projects spanning classification, regression, time series, clustering, and anomaly detection. Handled 1M+ row datasets, implemented SHAP explainability, and developed web applications around ML models including ChurnShield.
Divya Gyan College, Tribhuvan University · Kathmandu, Nepal
Formal education in computer science fundamentals: algorithms, databases, programming, and software engineering. Applied formal knowledge through independent data science and AI projects running in parallel with academic studies.
A two-iteration SHAP-based feature selection framework combined with iterative hyperparameter tuning, applied to a 7,043-record telecom churn dataset across seven candidate models. Supervised by Marshal Basnet · available on LinkedIn & ResearchGate.
Followed up with an audit of my own work. The published result was leakage: one retained field is present only for churned customers, and another is a vendor-computed churn propensity. Re-running the pipeline with both removed moves test ROC-AUC from 0.997 to 0.854 and F1 from 0.980 to 0.604. The corrected figures and the method are recorded in the repository.