PORTFOLIO DOC :: ID: JN-2026BACKEND ENGINEERSYSTEMS & INFRASTRUCTUREPORTFOLIO DOC :: ID: JN-2026BACKEND ENGINEERSYSTEMS & INFRASTRUCTUREPORTFOLIO DOC :: ID: JN-2026BACKEND ENGINEERSYSTEMS & INFRASTRUCTUREPORTFOLIO DOC :: ID: JN-2026BACKEND ENGINEERSYSTEMS & INFRASTRUCTURE

SUBJECT :: SAMARTH NAGAR

SYSTEMSENGINEER

ROLE

Backend Developer · DevOps Engineer · Systems Architect

ORIGIN

Indore, India

STATUS

Open for opportunities

DOC IDSN-RESUME-2026
CLASSIFICATIONPUBLIC

01 :: ABOUT RECORD

COLLECTED

Backend-focused developer obsessed with systems, infrastructure, performance, and browser-native tech.

INTELLIGENCE SYSTEM

SUBJECT NAME

Samarth (Sam) Nagar

DOCUMENT ID

SN-ABT-001

EDUCATION

SAGE University Indore
B.Tech Computer Science
Expected 2026 · CGPA 7.8/10

LOCATION

Indore, India
UTC+05:30

SUMMARY

Started with Harvard's CS50, then spent years exploring operating systems, network protocols, distributed systems, and now diving deep into WebAssembly, Local LLMs, and API design. I learn through building.

02 :: FIELD REPORT

Experience

Deployment logs from live systems I helped ship, secure, or automate.

EXP-01Jan 2026 – mar 2026

Backend Engineering Intern

@ Brand Collabs

Next.jsDockerSupabaseAudit
  • Built static code generation pipeline automating asset workflows
  • Deployed fully offline Supabase instance with containerized infrastructure
  • Audited API security across internal services and resolved critical vulnerabilities
  • Authored backend documentation and technical workflows

03 :: DEPLOYED SYSTEMS

Projects

Selected builds where I explored browser-native tech, local AI orchestration, and performance-first web systems.

PRJ-03→

WASM Video Editor

Browser-based video processing with WebAssembly and FFmpeg. Real-time encoding, decoding, and export pipelines — desktop-grade media processing inside the browser with zero server compute.

WebAssemblyFFmpegNode.jsClient-side
PRJ-02→

Local LLM Interface

Streaming chat interface for locally-hosted AI models. Backend APIs manage model lifecycle — load, unload, swap — reducing cold-start latency and improving runtime orchestration.

Node.jsOllamaStreaming APIsAI
PRJ-01→

Personal Blog Platform

SEO-optimized static site built with Next.js and MDX. Server-side rendering and edge caching deliver sub-200ms page loads on Vercel's edge network.

Next.jsMDXSEOEdge
PRJ-00→

Dotfiles & Dev Environment

Terminal-first Linux workflow configured with Neovim, tmux, fish, and Lazygit. Fedora-based daily driver tuned for backend and systems work.

NeovimtmuxFedoraShell

04 :: TOOLCHAIN

Stack

Technologies I use to design, deploy, and operate systems from the terminal to the edge.

Languages

JavaScriptTypeScriptPythonGoPHPLuaBash

Web & Runtime

Node.jsNext.jsReactViteHonoExpressBunDeno

Data & Storage

PostgreSQLMySQLSQLiteMongoDBRedisPlanetScale

Cloud & Infra

DockerKubernetesLinuxNginxGitCloudflareVercelAWSSupabase

APIs & Protocols

WebSocketGraphQLtRPCRESTPostmanKafka

Workflow

NeovimtmuxfishGitLazygitLazydockerFedora

05 :: CASE STUDIES

Research

Deep dives into production codebases to understand how real systems are architected, documented, and shipped.

ACTIVE INVESTIGATION

react.dev Architecture Deep Dive

Analyzed the real production codebase behind react.dev to map architecture decisions: custom MDX components, a build-time SSG pipeline, and the React Compiler already running in production.

  • No state management library needed — URL + useState + Context sufficient
  • 50+ custom MDX components behind each doc page
  • Custom SSG pipeline that serializes React tree to JSON at build time
  • Build-time eval() workarounds acknowledged as intentional hacks
Read Full Report→Detailed Notes→