[ Team 04 — Onboarding Cohort 2026 ]

We are Team JSA.
Three students,
one feedback loop.

A team of three from BITS Pilani Hyderabad. We work across machine learning, quantitative systems, and applied engineering. We are here to ship things, break things, and learn out loud.

members
03
campus
BITS HYD
focus
ML · QUANT · SYS
status
shipping
scroll ↓
01 / team

Three initials, one team.

why the name — JSA stands for the initials of our three members: Jayaditya, Shreyas, and Arrya. No cipher needed — just three people who work better together.

fun fact — our combined caffeine intake during exam week could power a small server rack.

AS

Arrya Sridhar

BITS Pilani, Hyderabad

focus
Machine Learning · Agentic AI · Computer Vision
wants to learn
LLM fine-tuning & MLOps
off-screen
Building autonomous systems, exploring agent architectures
PythonCJavaMATLAB
JK

Jayaditya Kushwah

BITS Pilani, Hyderabad

focus
Quantitative Research · Backend · Probability
wants to learn
Stochastic calculus for quant systems
off-screen
Guitar, Minecraft, competitive programming
PythonC++JavaDocker
SG

Shreyas Ghosh

BITS Pilani, Hyderabad

focus
Embedded Systems · Simulation · Process Modeling
wants to learn
Full-stack web & deployment workflows
off-screen
Arduino tinkering, football, cultural events
CC++PythonMATLAB
02 / skills map

What we already bring to the table.

A snapshot of our current coverage. Bars show how many of us actively work in each area — gaps are exactly where we plan to grow during the internship.

Machine Learning

3/3

Arrya, Jayaditya, Shreyas

Backend / Systems

2/3

Jayaditya, Arrya

Quantitative & Math

2/3

Jayaditya, Arrya

Computer Vision

1/3

Arrya

Embedded / Hardware

1/3

Shreyas

Simulation & Modeling

2/3

Shreyas, Arrya

Frontend

1/3

learning together

DevOps / Docker

1/3

Jayaditya

03 / learning goals

What we want to walk out knowing.

01

Technologies to explore

Production ML pipelines, agentic frameworks (LangGraph, MCP), modern backend stacks, cloud deployment (AWS, GCP), and the React + TypeScript side of the web we keep avoiding.

02

Problems that excite us

Autonomous decision-making under uncertainty, market microstructure & anomaly detection, and the boring-but-hard problem of making research code actually run in production.

03

What we hope to leave with

A shared sense of how real teams ship software — version control discipline, code review reflexes, writing intent before writing code, and shipping something we'd put our name on without a disclaimer.

04 / how we work

Lightweight process. Heavy on shipping.

[01]

Async stand-ups

Short written update every morning. No 9am meetings, no theater.

[02]

Weekly demo

Friday — each of us shows working code or a written breakdown. No slides.

[03]

Pair programming

Whenever someone is stuck for more than 30 minutes. Switch driver every 25.

[04]

Code review on every PR

At least one approval. Comments are about the code, never the person.

[05]

Decisions in writing

Anything bigger than a small fix gets a short doc before the code.

[06]

Blocked? Ship a draft

Default to opening a draft PR with the problem rather than waiting.

05 / open source

The repos we read on weekends.

We want to move from consumers to contributors this year — starting with good first issues, docs, and small bug fixes before working up to features.

problems we want to solve
  • — Making research-grade ML usable by non-ML teams.
  • — Better tooling for reproducible quantitative backtests.
  • — Reducing the gap between agent prototypes and production agents.
  • PyTorch
    Honest defaults, readable internals.
  • FastAPI
    The standard for shipping Python APIs without ceremony.
  • LangChain / LangGraph
    Where agentic patterns are being figured out in public.
  • Polars
    What pandas would be if rewritten today.
  • Hugging Face
    The community we want to contribute models and datasets to.
06 / contact

Want to build something together?

Arrya Sridhar