/docs/introduction.md

⚡ Senior Backend Engineer 🗓 2+ years experience 📦 2 open-source pkgs 📍 Bengaluru, India

Vishal Teotia

Senior Backend Engineer with 2+ years building systems that handle real money. Fintech, blockchain infrastructure, and the kind of backend work where a bug is not just a bug.

This is a docs-style breakdown of my work, technical stack, and the projects I've built. Structured like the open-source projects I spend time on.

💡

Quick navigation

Jump to Stack for tools and languages, Projects for things I've shipped, or Experience for the full timeline.

python

vishal = {
    "name": "Vishal Teotia",
    "title": "Senior Backend Engineer",
    "experience": "2+ years",
    "location": "Bengaluru, India",
    "languages": ["Python", "Go", "C/C++"],
    "github": "github.com/vashuteotia123",
    "contact": "tovishalteotia1@gmail.com"
}

/docs/stack.md

Stack

Languages, frameworks, and tools I work with regularly. Most of this has been used in production.

How I work

A few things that define how I approach engineering:

Systems should be fault-tolerant by design, not patched into it later
Ownership means following something from first commit to production incident
Data correctness is not negotiable, especially in financial systems
Understand the problem fully before touching the keyboard

Tech Stack

Languages

Python Go TypeScript C/C++ Solidity

Frameworks

Django FastAPI Flask Celery gRPC Web3

Databases

PostgreSQL MongoDB Redis

Messaging & Queues

Kafka RabbitMQ

DevOps & Infra

Docker AWS Jenkins GitHub Actions

Observability

Grafana DataDog

💡

On picking up new tools

Picking up new languages and frameworks on the job is part of the work. The problem shapes the tool choice, not the other way around.

/docs/skills.md

Skills

A structured breakdown of my technical and professional capabilities, built from 2+ years of hands-on fintech and blockchain engineering.

Core Competencies

python

skills: SkillMap = {
    "languages": {
        "expert": ["Python"],
        "proficient": ["Go", "TypeScript", "C/C++", "Solidity"],
    },
    "backend": {
        "expert": ["Django"],
        "proficient": ["FastAPI", "gRPC", "Kafka", "Flask", "Celery", "RabbitMQ"],
    },
    "soft_skills": [
        "Reads error logs for fun",
        "Breaks prod, fixes prod, tells no one",
        "Writes commit messages people actually read",
        "Asks why before writing a single line",
    ],
}

🔭

Currently exploring

How to convince a language model it has feelings. Also some systems programming stuff, but mostly the feelings thing.

/docs/projects/

Projects

Open-source tools and side projects problems I found interesting enough to build a solution for and ship publicly.

hypermind

AI / LLM Infra open source 🟠 Show HN

A production-grade LLM memory proxy that sits between your app and any provider OpenAI, Anthropic, Groq, Google. Implements human-like short-term + long-term memory with relevance scoring, recency tracking, and Ebbinghaus context decay. Under <700ms overhead.

Problem

LLMs are stateless they forget everything between sessions, making persistent agents impossible.

Solution

Universal proxy with RAG, vector search, and knowledge graph. Same API your LLM now remembers.

Stack

TypeScript Cloudflare Workers D1 Vectorize R2

Reach

Featured on Hacker News (Show HN) · Live playground available

bash

# Instead of calling providers directly:
curl https://api.openai.com/v1/chat/completions

# Call HyperMind same API, but with persistent memory:
curl https://your-hypermind.workers.dev/router/v1/chat/completions
# ✓ Your AI now remembers across sessions

Live Playground GitHub Show HN

pytest-culprit

stable open source ⭐ 2 stars

A CLI tool that walks backward through N Git commits running your test at each one, stops when it passes, and prints the exact failing commit. Pass the number of commits to scan and the test command that's it.

Problem

When a test breaks in CI, pinpointing which commit caused it means hours of manual bisecting.

Solution

One command: pytest-culprit 15 pytest tests/... walks back N commits and prints the culprit.

Stack

Python pytest Git CLI

Impact

Saves 30–60 min per flaky test incident · 2 stars · 1 fork

bash

# Install
pip install pytest-culprit

# Usage: pytest-culprit <num_commits> <test_command>
pytest-culprit 15 pytest tests/test_rewards.py::test_logic

# 📌 Starting from branch: main
# ▶️  Running test at commit 0a45b22 [3/15]
# ✅  Test started passing here.
# ❌  Last failing commit was:
# 
# commit f87d098
# Author: Vishal Teotia
# Date:   2025-05-15
#     break: tests
# 
# 🧪 This commit broke: pytest tests/test_rewards.py::test_logic

GitHub PyPI

/docs/experience.md

Experience

All three roles are at the same company. The scope changed with each one.

Senior Product Engineer (Backend)

Multipli.fi · Bengaluru

Jul 2025 → Present

Owned the v2 redesign and migration of Multipli's core backend
Re-architected from a tightly coupled L3-dependent system to a modular, protocol-driven design
Planned and executed production migration with parallel v1/v2 operation
Maintained 99.9% user-facing SLA throughout the migration rollout
Enabled $18M+ in customer-deposited assets within 3 weeks post-migration
Reduced long-term custody and governance risk through standards-aligned asset architecture
Acted as backend owner during releases and incidents, coordinating validation and rollback strategies
Mentored and onboarded 3 junior backend engineers via design reviews and production-readiness walkthroughs

Python Go Kafka PostgreSQL gRPC Docker

Product Engineer (Backend)

Multipli.fi · Bengaluru

Jul 2023 → Jun 2025

Owned the full development lifecycle of the Multipli platform from ideation to testnet launch, with 1M+ pre-signed users
Scaled staking and unstaking workflows on mainnet systems to support 1k+ concurrent user transactions
Developed automated disbursal pipelines managing $100M+ in assets
Enforced exactly-once semantics across pub-sub based financial workflows
Developed core primitives like stop-limit and bulk order execution flows
Built fault-tolerant internal transfer systems with at-least-once guarantees, enabling reuse across 7 core services
Implemented CI/CD automation with test reporting and PR tagging, reducing development cycle time by 40% and PR review time by 50%

Django FastAPI Celery Redis RabbitMQ Web3 Solidity

Product Engineer Intern (Backend)

Multipli.fi · Bengaluru

Jan 2023 → Jun 2023

Built production backend services from inception to deployment and maintained trading and transaction-processing APIs
Reduced blockchain transaction update latency from 10 minutes to sub 5 seconds
Stabilized airdrop automation pipelines, reducing automation failure rates from 60–70% to 1–5%
Identified and fixed cache and database inconsistency issues, improving correctness of leaderboards and transaction histories
Replaced reconciliation-based flows with real-time webhooks, reducing operational complexity

Python PostgreSQL MongoDB Redis Webhooks

B.Tech – Mechanical Engineering

Vellore Institute of Technology · Chennai

Aug 2019 → May 2023

Graduated with CGPA 8.8/10. Taught myself software engineering alongside the degree through open-source work and personal projects. Joined Multipli as a backend intern in the final semester.

Python C/C++ CGPA: 8.8/10

/docs/faq.md

FAQ

Some questions worth answering about how I think and work.

Why Mechanical Engineering if you're a backend engineer?

Spent four years studying how physical things break under stress, which turns out to be great preparation for watching servers do the same thing. Somewhere between thermodynamics and fluid mechanics I started writing Python, liked it more than both, and quietly switched careers while still attending the wrong classes. Graduated with an 8.8 GPA and a degree that has never once been relevant to anything I've done professionally. No regrets. The systems thinking stayed. The wrenches did not.

Python or Go?

Python for getting things done quickly, Go for when you want things to stay done. I don't have strong feelings either way, which probably means I've been burned by both at some point.

How do you debug something you don't understand yet?

Read the logs until they stop making sense, then read them again. Add more logs. At some point the system starts telling you where it hurts. The trick is not to guess before you have enough data, even when guessing feels faster.

Tabs or spaces?

Whatever the linter says. I have no interest in dying on that hill.

What's your test coverage target?

High enough that I can sleep at night, low enough that I'm not writing tests for tests. The number matters less than whether the tests actually catch real failures. 100% coverage on a broken system is just expensive decoration.

/docs/changelog.md

Changelog

My career as a version history. Each release represents a meaningful level-up in scope, ownership, or technical depth.

v3.2.0

Jul 2025

Promoted to Senior · v2 backend ownership

ADD Owned v2 core backend redesign & production migration
ADD Enabled $18M+ customer-deposited assets within 3 weeks
ADD Mentored and onboarded 3 junior backend engineers
ADD Maintained 99.9% SLA during full migration rollout
CHG Architecture: tightly coupled → modular protocol-driven

v2.0.0

Jul 2023

Full-time Product Engineer · Mainnet scale

ADD Led platform from ideation to testnet with 1M+ pre-signed users
ADD Built $100M+ automated disbursal pipelines
ADD Scaled staking/unstaking to 1k+ concurrent user transactions
ADD Enforced exactly-once semantics on pub-sub financial workflows
ADD Published pytest-culprit to PyPI
FIX CI/CD: development cycle time −40%, PR review time −50%

v1.0.0

Jan 2023

Initial release · Intern → production

ADD First production backend services shipped end-to-end
FIX Blockchain tx latency: 10 min → sub-5 seconds
FIX Airdrop automation failure rate: 60–70% → 1–5%
FIX Cache/DB inconsistencies in leaderboards + tx histories
REM Removed reconciliation flows; replaced with real-time webhooks

v0.1.0

Aug 2019

Bootstrap · VIT Chennai

ADD B.Tech Mechanical Engineering (CGPA: 8.8/10)
ADD Self-taught Python, C/C++ alongside coursework
CHG Career trajectory: mechanical → software engineering

/docs/contact.md

Contact

Feel free to reach out for collaborations, questions about my work, or anything else worth a conversation.

⚡

Best way to reach me

Email is the most reliable. LinkedIn works for a quick intro.

📧

Email

tovishalteotia1@gmail.com

💼

in/vishalteotia