Skip to content
Edition
Late EditionM.S. Computer Science · 3.97 GPA
The Sreekaran Reddy Portfolio
Breaking
Open to work: Data Analyst & Data ScientistARIMA beat XGBoost and LightGBM on 5 of 5 loan-delinquency seriesFanHouse study: 40,000 synthetic customers, 12,153 matched pairs50% rise in school revenue at Avanthi High SchoolMarket Pulse: a live job-market pipeline with its own MCP serverM.S. Computer Science, 3.97 GPA

Sreekaran Reddy

Data Analyst & Data Scientist

I make data trustworthy with SQL and Python, readable with Tableau, and defensible with causal inference.

  • Causal Inference
  • LLM Fine-Tuning
  • SQL · Python · Tableau
Sreekaran Reddy
“Every dataset has a story it isn't telling yet. I enjoy the process of finding it.”
Open to work

“Every dataset has a story it isn't telling yet. I enjoy the process of finding it.”

Top stories

5/5ForecastingARIMA outperformed XGBoost and LightGBM across five loan series in this backtestRead the story 40.6%Causal inference · Synthetic dataMembers already spent more before the membership existedRead the case study LiveData engineeringMarket Pulse turns daily job postings into market intelligenceSee how it works All 12 projects · continued on Page B1
Section B · InvestigationsPage B1

Projects & Case Studies

Questions I explored, things I built, and what the evidence taught me.

Showing 12 of 12

No. 01Time-Series Forecasting5 of 5

Loan delinquency forecasting

Can modern machine learning beat a classical forecast on five U.S. loan-delinquency series?

Key finding

ARIMA beat both ML models after data leakage was fixed.

  • Python
  • statsmodels (ARIMA)
  • XGBoost
  • LightGBM
No. 02Causal Inference+$0.1367/day

FanHouse: more product value, more payments?

I followed 40,000 synthetic customers to separate who joins a membership from what the program changes.

Key finding

Net-payment 95% interval: −$0.0232 to +$0.0027 per customer/day. Higher payments were not established.

  • Python
  • pandas
  • NumPy
  • scikit-learn
No. 03Mobile App120 Hz

LookBack

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.

Key finding

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%.

  • React Native
  • Expo
  • TypeScript
  • SQLite
No. 04Hardware Hacking2 apps, 1 seat

Connect Head

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.

Key finding

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.

  • Swift
  • SwiftUI
  • IOBluetooth (RFCOMM)
  • CoreAudio
No. 05Hardware Hacking1/16 per click

DialHack

Turn the Smart Dial on the CMF Buds Pro 2 case into a Mac input device, and learn how I fidget along the way.

Key finding

Measured before building: each click is one volume step, capped at about 3 steps per second; long and triple presses never reach the Mac.

  • Swift
  • SwiftUI
  • CoreAudio
  • MPRemoteCommandCenter
No. 06Computer Vision82.76% F1

PhotoCull

Privacy-first computer vision for duplicate detection, event grouping, and explainable photo curation.

Key finding

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.

  • Computer Vision
  • Ranking
  • Clustering
  • Local ML
No. 07Data AnalyticsDaily

Market Pulse

Turn scattered daily job postings into searchable, explainable market intelligence.

Key finding

An automated pipeline turns job postings into computed statistics and AI summaries; generated text needs verification.

  • Python
  • FastAPI
  • PostgreSQL
  • Docker
No. 08Applied AI39.8%

Genre-controlled story generation

Adapt a small language model to write fantasy, romance, and science-fiction stories.

Key finding

Validation perplexity fell 39.8%, but the adapted model scored lower than the base model on a small LLM-judged writing sample.

  • Python
  • PyTorch
  • Hugging Face
  • PEFT
No. 09Data ScienceXGBoost + RAG

MedPredicts

An academic prototype combining hospital records and environmental context to predict 30-day readmission.

Key finding

Risk predictions paired with generated explanations and example follow-up rules. Clinical validation and real-world use are not documented here.

  • Python
  • Pandas
  • XGBoost
  • Data Cleaning
No. 10MLOpsMLOps

Vehicle insurance MLOps

Take an insurance eligibility model from an experiment to a reproducible prediction service.

Key finding

Versioned data, validation, and CI/CD support the deployed API.

  • Python
  • Pandas
  • NumPy
  • MongoDB
No. 11Cloud ApplicationCloud SaaS

RecommenderX

Help movie lovers discover their next watch through personalized recommendations.

Key finding

Recommendations, watchlists, ratings, and AI review summaries in one app.

  • Python
  • Django
  • PostgreSQL
  • Cloud Deployment
No. 12Data AnalyticsLogistic regression

Student success prediction

Use academic and enrollment data to classify dropout, enrolled, and graduate outcomes.

Key finding

The strongest tested model on accuracy and F1-score.

  • Python
  • Data Analysis
  • Feature Engineering
  • Exploratory Data Analysis
Section C · The RecordPage C1

Experience

Roles, responsibilities, and results, most recent first.

  1. Technical Support · Lab Operations · Student Data Support

    Information Services Lab Assistant

    University of Missouri-Kansas City

    tickets resolved per semester
    75+
    student projects coached
    20+
    • Owned technical support for student-facing computer labs, resolving 75+ tickets per semester across hardware, printer, login, and workstation issues, alongside Python, SQL, R, and notebook-based coding support.
    • Drove analytics coaching across 20+ student academic and research projects in Python and R, strengthening EDA rigor, statistical validation, and assumption-checking in peer analysis.
  2. Construction Analytics · Machine Learning · Growth Analytics

    Data and ML Intern → Data Scientist

    Sree Nirman, Hyderabad, India

    records standardized
    50K+
    lift in reporting reliability
    30%
    gain in operational efficiency
    15%
    • Standardized 50K+ construction records using SQL and Pandas, improving reporting reliability by 30%.
    • Delivered bi-weekly Tableau dashboards to the CEO and client board, supporting a 15% operational efficiency gain.
    • Deployed the pricing model with the engineering team in an internal bidding-support tool, reducing bid analysis time by 50%.
  3. Financial Analytics · Education Data · ML Decision Support

    Data Science Intern

    Avanthi High School

    rise in school revenue
    50%
    rise in admissions
    18%
    MAE predicting final marks
    0.8
    • Designed and measured a two-channel A/B test of admission marketing, recording an 18% rise in admissions.
    • Launched the winning admission marketing strategy, contributing 15 percentage points of a 50% rise in school revenue.
    • Trained XGBoost with leave-one-cohort-out cross-validation, beating mean and running-average baselines at 0.8 MAE on a 10-point scale.

Special reports

One case from each role, told the way it happened.

Special report · Construction pricing

The price that history got wrong

A construction startup with fewer than 200 past bids, a pricing tool it could trust, and the obvious approach we threw out first.

20192019201920192019NEW CITYNEW CITYNEW CITYNEW CITYNEW CITYHISTORYHISTORYHISTORYHISTORYHISTORY₹29L2019 RATE₹29L2019 RATE₹29L2019 RATE₹29L2019 RATE₹29L2019 RATE₹36–42L+ cost drivers₹36–42L+ cost drivers₹36–42L+ cost drivers₹36–42L+ cost drivers₹36–42L+ cost driversIn my day this plotcost ₹29L!In my day this plotcost ₹29L!In my day this plotcost ₹29L!In my day this plotcost ₹29L!In my day this plotcost ₹29L!Let’s price the groundwe’re standing on.Let’s price the groundwe’re standing on.Let’s price the groundwe’re standing on.Let’s price the groundwe’re standing on.Let’s price the groundwe’re standing on.శ్రీ
History, still quoting last year’s prices.
  1. 01

    Fewer than 200 bids to learn from

    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.

    Exhibit A The record
    BidZonePlot, sq ydBuildQuoted
    B-041Zone A2409 mo₹38.6L
    B-057Zone C1807 mo₹29.1L
    B-063Zone B30011 mo₹47.9L
    B-078Zone A1506 mo₹24.3L
    B-092Zone D2208 mo₹35.0L

    150–200 real bids on record

  2. 02

    Last year’s price pointed the wrong way

    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.

    Exhibit A Why history failed
    Past bids implyTerrain cost todayThe lines cross: history now misprices
  3. 03

    Today’s costs, checked against the market

    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.

    Exhibit A Real bids, plus synthetic ones
    BidZonePlot, sq ydBuildQuoted
    B-041Zone A2409 mo₹38.6L
    B-057Zone C1807 mo₹29.1L
    B-063Zone B30011 mo₹47.9L
    S-001Zone B2108 mo₹33.4L
    S-002Zone D26010 mo₹41.7L
    S-003Zone A1707 mo₹27.8L
    • Material cost
    • Labor
    • Location
    • Duration
    • 20+ features

    Checked against market rates, supplier pricing and procurement costs

  4. 04

    A plain line, then Ridge and Lasso

    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.

    Exhibit A The benchmark
    ModelR²MSEMAE
    Linear baseline
    Ridge
    Lasso

    MLflow Every run logged; the selected version registered for reuse.

  5. 05

    A range, not a guess

    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.

    Exhibit A What the tool returns

    Bid B-104 · estimated price

    ₹36.2L₹42.4L

    A 10 to 20% range, not a single number

    1. 1. Material cost
    2. 2. Labor
    3. 3. Location
    4. 4. Project duration

    50% less time per bid

Exhibit A The record
BidZonePlot, sq ydBuildQuoted
B-041Zone A2409 mo₹38.6L
B-057Zone C1807 mo₹29.1L
B-063Zone B30011 mo₹47.9L
B-078Zone A1506 mo₹24.3L
B-092Zone D2208 mo₹35.0L

150–200 real bids on record

Bids, zones, prices and driver weights in the exhibit are illustrative. Client details stay private.

Section D · ProfilePage D1

About

My background and approach to working with data.

construction records made trustworthy at Sree Nirman
50K+
rise in school revenue at Avanthi High School
50%
rise in admissions, checked with an A/B comparison
18%
GPA, M.S. Computer Science
3.97

It started with two chocolates

The first script

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.

Small teams, real stakes

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.

The project that changed my thinking

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?”

What I’m looking for

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.

Section E · Opinion & EssaysPage E1

A few things I wrote

Narrative-style technical writing on data, machine learning, LLMs, and applied AI.

Causal Inference · 2026 · 4 min read

The Unreasonable Effectiveness of Linear Regression

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

Read on LinkedIn →

Causal Inference · 2026 · 7 min read

Propensity Score

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

Read on LinkedIn →

LLMs · 2026 · 6 min read

How I Slowly Understood What’s Really Happening Inside LLMs like ChatGPT

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

Read on LinkedIn →

AI Fundamentals · 2026 · 6 min read

Bedtime Story: How Text Became Magic

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

Read on LinkedIn →

NLP · 2026 · 7 min read

Chapter 6: When Words Became Pieces

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

Read on LinkedIn →

LLM Internals · 2026 · 8 min read

The Space Between Words

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

Read on LinkedIn →

Attention · 2026 · 10 min read

The Night Before Attention Was Born

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

Read on LinkedIn →
Section F · ClassifiedsPage F1

Skills

Tools and the things I used.

Analytics & BI

Turning numbers into decisions.

Tools I use to turn messy business data into decision-ready reporting.

  • SQL
  • Python
  • Excel
  • Tableau
  • Tableau Stories
  • KPI Reporting
  • Dashboard Design
  • Stakeholder Reporting

Data Engineering & Quality

Making messy data trustworthy.

Cleaning, validating, reconciling, and preparing reliable datasets.

  • Pandas
  • NumPy
  • Data Cleaning
  • Data Validation
  • Source-to-Report QA
  • ETL Workflows
  • dbt Core
  • BigQuery
  • DuckDB

Machine Learning

Finding patterns worth predicting.

Building predictive models for risk, pricing, operations, and outcomes.

  • Scikit-learn
  • XGBoost
  • CatBoost
  • Regression
  • Classification
  • Feature Engineering
  • Model Evaluation
  • Computer Vision
  • Error Analysis

Experimentation & Causal Inference

Checking what really caused the change.

Testing whether an observed effect is real before trusting it.

  • Causal Inference
  • A/B Testing
  • Hypothesis Testing
  • Propensity Score Matching
  • Difference-in-Differences
  • OEC & Guardrail Metrics

Applied AI & LLMs

Giving models a useful voice.

Fine-tuning, evaluating, and building AI-assisted decision systems.

  • Hugging Face
  • PyTorch
  • LoRA
  • QLoRA
  • RAG
  • FAISS
  • LLM-as-Judge
  • Prompt Engineering
  • Model Context Protocol (MCP)

MLOps & Deployment

Taking experiments into production.

Moving models from notebooks into reproducible and deployable systems.

  • MLflow
  • DVC
  • FastAPI
  • Docker
  • Kubernetes
  • AWS EKS
  • AWS EC2
  • AWS S3
  • GitHub Actions
  • Prometheus / Grafana

Cloud & Data Products

Building products around the data.

Building full-stack data products, apps, and cloud-backed ML systems.

  • Django
  • PostgreSQL
  • MongoDB
  • Streamlit
  • Google Cloud SQL
  • Google Cloud Storage
  • Clerk Authentication
  • Groq API

Always learning.

Section G · LettersPage G1

Connect with me

For data roles, applied AI conversations, collaborations, referrals, or project discussions, these are the easiest ways to reach me.

LinkedIn

Talk about a role

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

Connect on LinkedIn →

GitHub

Read the code

Notebooks, pipelines, and the source behind every case study in this paper.

Find me at github.com/Sreekaran1704

Browse repositories →

Email

Write a letter

For collaborations, project discussions, or anything that needs more than a message.

Find me at sreekaran.2021@gmail.com

Send an email →