Loan delinquency forecasting
Can modern machine learning beat a classical forecast on five U.S. loan-delinquency series?
ARIMA beat both ML models after data leakage was fixed.
- Python
- statsmodels (ARIMA)
- XGBoost
- LightGBM
Data Analyst & Data Scientist
I make data trustworthy with SQL and Python, readable with Tableau, and defensible with causal inference.

“Every dataset has a story it isn't telling yet. I enjoy the process of finding it.”
Questions I explored, things I built, and what the evidence taught me.
Can modern machine learning beat a classical forecast on five U.S. loan-delinquency series?
ARIMA beat both ML models after data leakage was fixed.
I followed 40,000 synthetic customers to separate who joins a membership from what the program changes.
Net-payment 95% interval: −$0.0232 to +$0.0027 per customer/day. Higher payments were not established.
A cosy Android journal: one small thing a day, and on the same date a year later it comes back as a sealed letter from your past self.
Frame timing showed the GPU, not JavaScript, was the bottleneck; caching still paper objects as GPU textures cut scroll jank in a 73-memory year from 19% to 1.8%.
An unofficial Mac and Android app for Sony ULT WEAR headphones, built because Sony’s own app was slow to connect and clunky to use.
The headphones accept only one controlling connection, so the phone sends its commands through the Mac over the local network instead of fighting it for the link.
Turn the Smart Dial on the CMF Buds Pro 2 case into a Mac input device, and learn how I fidget along the way.
Measured before building: each click is one volume step, capped at about 3 steps per second; long and triple presses never reach the Mac.
Privacy-first computer vision for duplicate detection, event grouping, and explainable photo curation.
Near-duplicate F1 on a synthetic held-out benchmark (98.36% precision, 71.43% recall). Embedding hybrids added hard-negative false positives, so hashing stayed the default.
Turn scattered daily job postings into searchable, explainable market intelligence.
An automated pipeline turns job postings into computed statistics and AI summaries; generated text needs verification.
Adapt a small language model to write fantasy, romance, and science-fiction stories.
Validation perplexity fell 39.8%, but the adapted model scored lower than the base model on a small LLM-judged writing sample.
An academic prototype combining hospital records and environmental context to predict 30-day readmission.
Risk predictions paired with generated explanations and example follow-up rules. Clinical validation and real-world use are not documented here.
Take an insurance eligibility model from an experiment to a reproducible prediction service.
Versioned data, validation, and CI/CD support the deployed API.
Help movie lovers discover their next watch through personalized recommendations.
Recommendations, watchlists, ratings, and AI review summaries in one app.
Use academic and enrollment data to classify dropout, enrolled, and graduate outcomes.
The strongest tested model on accuracy and F1-score.
Roles, responsibilities, and results, most recent first.
Technical Support · Lab Operations · Student Data Support
University of Missouri-Kansas City
Construction Analytics · Machine Learning · Growth Analytics
Sree Nirman, Hyderabad, India
Financial Analytics · Education Data · ML Decision Support
Avanthi High School
Special report · Construction pricing
A construction startup with fewer than 200 past bids, a pricing tool it could trust, and the obvious approach we threw out first.
01
I joined Sree Nirman as the second employee and its first technical person. Pricing decisions were made on gut feel, because nobody trusted the numbers enough to use them. The company had 150 to 200 real bids on record: enough to see a pattern, far too few to train a model on their own.
| Bid | Zone | Plot, sq yd | Build | Quoted |
|---|---|---|---|---|
| B-041 | Zone A | 240 | 9 mo | ₹38.6L |
| B-057 | Zone C | 180 | 7 mo | ₹29.1L |
| B-063 | Zone B | 300 | 11 mo | ₹47.9L |
| B-078 | Zone A | 150 | 6 mo | ₹24.3L |
| B-092 | Zone D | 220 | 8 mo | ₹35.0L |
150–200 real bids on record
02
The obvious plan was to price new bids from old ones. In meetings with the co-founders we found the flaw: in the expanding parts of the city, terrain costs had reversed. History would have priced today’s bids against yesterday’s ground, so we ruled it out and built on current data instead.
03
I expanded the real bids with synthetic samples drawn from their own feature distributions, and engineered 20+ features from material costs, labor, location and project duration. Every price was checked against market rates, supplier pricing and material procurement costs.
| Bid | Zone | Plot, sq yd | Build | Quoted |
|---|---|---|---|---|
| B-041 | Zone A | 240 | 9 mo | ₹38.6L |
| B-057 | Zone C | 180 | 7 mo | ₹29.1L |
| B-063 | Zone B | 300 | 11 mo | ₹47.9L |
| S-001 | Zone B | 210 | 8 mo | ₹33.4L |
| S-002 | Zone D | 260 | 10 mo | ₹41.7L |
| S-003 | Zone A | 170 | 7 mo | ₹27.8L |
Checked against market rates, supplier pricing and procurement costs
04
I benchmarked Ridge and Lasso regression against a plain linear baseline on R², MSE and MAE, and tracked every experiment and model version in MLflow, so the choice could be traced and the selected model reused.
MLflow Every run logged; the selected version registered for reuse.
05
The model went live as an internal web tool built with FastAPI, Docker and AWS. For each bid it returns a price range of 10 to 20%, with the cost drivers ranked, so the team can see what moves the price. Bid analysis now takes half the time.
Bid B-104 · estimated price
A 10 to 20% range, not a single number
50% less time per bid
| Bid | Zone | Plot, sq yd | Build | Quoted |
|---|---|---|---|---|
| B-041 | Zone A | 240 | 9 mo | ₹38.6L |
| B-057 | Zone C | 180 | 7 mo | ₹29.1L |
| B-063 | Zone B | 300 | 11 mo | ₹47.9L |
| B-078 | Zone A | 150 | 6 mo | ₹24.3L |
| B-092 | Zone D | 220 | 8 mo | ₹35.0L |
150–200 real bids on record
Bids, zones, prices and driver weights in the exhibit are illustrative. Client details stay private.
My background and approach to working with data.
As a kid, my friends and I had a contest: whoever texted “Happy Birthday” first at midnight won two chocolates. Everyone else got one.
I didn’t want to win by staring at a clock, so I wrote a script that sent the message at exactly 12:00 AM. It was my first real code, and it taught me something I still believe: the best work makes the right thing happen reliably, every time, without anyone having to remember. Years later, that is still how I think about data. A number only helps if it shows up correct, on time, every time.
My first two jobs were on small teams where I was the person who owned the data, from the raw spreadsheets to the decision in the room.
At Avanthi High School, I consolidated 12K+ fee records and 50K+ expense records into reporting tables in Python and SQL, then used them to find 10–15% in cost savings. I designed an A/B test of two admission-marketing channels that lifted admissions by 18%. I built a scholarship system with XGBoost and a fine-tuned GPT-2, and walked the principal and correspondent through it, one user story at a time, until they backed the change.
At Sree Nirman, a construction startup in Hyderabad, I joined as the second employee. I standardized 50K+ project records, which made reporting 30% more reliable. I built a bid-pricing model from fewer than 200 real records, owned the bidding tool from specs to user testing, and cut bid analysis time in half. Along the way I helped hire 8 engineers and 2 interns, and grew the company YouTube channel to 60K+ subscribers, which brought in 12 construction deals.
In my FanHouse case study, members spent 22.3% more after a membership launched. It looked like a clear win. It wasn’t that simple.
The customers who later joined already spent 40.6% more before the program existed. So I matched 12,153 member and non-member pairs on their history, then compared how each pair changed. Product value rose by about $0.14 per customer per day, but higher net payments were not established once discounts and rewards came out. I kept the pretrend warning and sensitivity checks on the page instead of hiding them. Since then, I ask a harder question of every result: not “does this look convincing?” but “what evidence would let me defend it?”
I finished my M.S. in Computer Science, Data Science track, at UMKC in May 2026 with a 3.97 GPA, and I’m looking for my next team.
I’m applying for Data Analyst, Business Analyst, Data Scientist, Analytics Engineer and Applied AI roles. I’m open to roles anywhere in the US. Between applications, I write about causal inference and how language models work, and I keep building: a live job-market pipeline with its own MCP server, a forecasting backtest, and a photo-curation tool that runs on your own machine.
The real value of data is not in the dashboard or the number, it is in the decision it improves.
Narrative-style technical writing on data, machine learning, LLMs, and applied AI.
Causal Inference · 2026 · 4 min read
What Chapter 4 of Causal Inference in Python taught me about an old friend.
I thought I knew linear regression until a bank dataset showed higher credit limits "causing" fewer defaults. The article walks through confounding, why comparing similar customers breaks down with too many variables, the Frisch-Waugh-Lovell theorem as debias-and-denoise, extrapolation, how regression weights effects by treatment variance, and why not every variable deserves a seat in the model.
Filed under Causal Inference · Linear Regression · Confounding
Causal Inference · 2026 · 7 min read
Finding the hidden coin flip inside messy, non-random data.
I used a corporate manager-training program, where people skip sessions and others sneak in, to explain why naive comparisons lie when attendance is not random. The article introduces the propensity score as the probability of getting treated, matching as a dating app for data and why it can be biased, and how adjusting for who showed up changes the story.
Filed under Causal Inference · Propensity Score · Matching
LLMs · 2026 · 6 min read
A personal journey into tokenization, probability, and next-token prediction.
I wrote this as a learning trail through LLMs, starting from the first question that bothered me: how does a model even see text? The article walks through tokenization, Byte Pair Encoding, next-token probabilities, inference, and how a base model behaves like a compressed memory of internet text.
Filed under LLMs · Tokenization · Inference
AI Fundamentals · 2026 · 6 min read
A story-style introduction to how neural networks read text.
I used a bedtime-story format to explain why neural networks cannot directly read words and why text must become numbers first. The article introduces tokens, vocabularies, encoding, and the strange little bridge between human language and machine-readable input.
Filed under Tokenization · Neural Networks · Storytelling
NLP · 2026 · 7 min read
The story of Byte Pair Encoding.
This article explains Byte Pair Encoding through a story where characters, fragments, and frequent pairs slowly become a vocabulary. I wanted to show how BPE helps models handle unfamiliar words by breaking language into reusable pieces instead of memorizing every possible word.
Filed under BPE · Tokenization · NLP
LLM Internals · 2026 · 8 min read
How embeddings and position help models understand context.
I built this article around a simple misunderstanding between Arjun and Meera: “I need space.” From there, I explain input-target pairs, token embeddings, positional embeddings, and why the same word can mean different things depending on where it stands and what surrounds it.
Filed under Embeddings · Context · Transformers
Attention · 2026 · 10 min read
A bedtime story about how machines learned to remember.
I used a story between a father and a little girl to explain why attention became such an important idea in AI. The article starts with old encoder-decoder models, memory, vectors, and the problem that eventually made attention feel less like a feature and more like a rescue mission.
Filed under Attention · Transformers · Storytelling
Tools and the things I used.
Turning numbers into decisions.
Tools I use to turn messy business data into decision-ready reporting.
Making messy data trustworthy.
Cleaning, validating, reconciling, and preparing reliable datasets.
Finding patterns worth predicting.
Building predictive models for risk, pricing, operations, and outcomes.
Checking what really caused the change.
Testing whether an observed effect is real before trusting it.
Giving models a useful voice.
Fine-tuning, evaluating, and building AI-assisted decision systems.
Taking experiments into production.
Moving models from notebooks into reproducible and deployable systems.
Building products around the data.
Building full-stack data products, apps, and cloud-backed ML systems.
Always learning.
For data roles, applied AI conversations, collaborations, referrals, or project discussions, these are the easiest ways to reach me.
If you feel I’d be a good fit for your role or team, I’d love to hear about it.
Find me at linkedin.com/in/sree1704
GitHub
Notebooks, pipelines, and the source behind every case study in this paper.
Find me at github.com/Sreekaran1704
For collaborations, project discussions, or anything that needs more than a message.
Find me at sreekaran.2021@gmail.com