Contact

Software Engineer • Full Stack • Systems

DesignDevelopDeploy

I build backend systems, cloud infrastructure, and full-stack products that scale in production.

Get in Touch

Dashboard

Contribution Graph

 
Latest Log

Understanding React Compiler

2026-01-25
→
Location

Bengaluru

Open to Work

Obsidian Graph

shivamjain.dev@gmail.com

Click to Copy

Experience

GoQuant

Software Development Engineer

▼

Jan 2025 - Mar 2026

  • •Saved $10K+ annually by building a cross-platform build pipeline for the OEMS C++ trading engine using Conan + OSXCross, eliminating developer VMs and enforcing deterministic builds across architectures.
  • •Deployed and served Qwen MoE 27B on on-prem multi-GPU infrastructure using vLLM, enabling low-latency inference workflows for internal developers and traders.
  • •Built a production-grade GenAI trading copilot enabling natural-language workflows across 100+ trading APIs using RAG pipelines, semantic reranking, and human-in-the-loop systems.
  • •Built post-trade analytics infrastructure with real-time ingestion and reconciliation pipelines enabling slippage analysis, execution validation, and mismatch detection across exchanges.
  • •Enabled multi-exchange trading support by integrating margin and leverage APIs while handling exchange-specific edge cases and execution nuances.
  • •Engineered high-frequency systems handling 300+ websocket messages/min using efficient rendering and bounded queues to eliminate lag and memory issues.
  • •Reduced symbol registry latency by 60% (5s → 2s) for 3,000+ assets/exchange using Redis rolling caches and pagination for latency-sensitive systems.

Spencers

Infrastructure & Cloud Optimization Consultant

▼

Calix

Software Engineer Intern (Cloud & Automation)

▼

DMP (MeitY)

Open Source Contributor

▼

Techvestors India

Full Stack Developer Intern

▼

SwiftRide

Full Stack Developer Intern

▼

Devlog

dev-0032026-01-25

Understanding React Compiler

↓

The new React Compiler is a game changer. It uses an intermediate representation to analyze data flow and automatically inserts memoization.

This means useMemo and useCallback are largely obsolete. I tested it on a heavy visualization component and saw a 30% reduction in re-renders without manual optimization.

Key Changes

  • Automatic Memoization: No more dependency array hell.
  • Granular Updates: Only the changed parts of the DOM update.
// Before
const heavy = useMemo(() => compute(data), [data]);

// After (Compiler)
const heavy = compute(data); // Auto-memoized
dev-0022026-01-22

WebGL Shader Performance

↓

Learned about optimizing fragment shaders for 60fps on low-end devices. Fragment shaders run for every pixel, so they are the bottleneck.

Optimization Strategy

The key optimization was moving vector calculations from the fragment shader to the vertex shader. This interpolation happens in hardware and is much faster.

// Fragment Shader (Bad)
void main() {
  vec3 light = normalize(uLightPos - vPos);
  // ...
}

// Vertex Shader (Good)
vLightDir = normalize(uLightPos - pos);

Projects

Cloud / DevTools

Intui

Secure online code execution platform with Docker sandboxing.

AI / RAG

PaperLM

RAG-based PDF Chatbot built with LangChain and Pinecone.