Video Streaming Service
Backend / APIsBackend-focused service: ingestion pipelines, storage layout, manifest generation, stream preparation, and secure delivery contracts for players—designed for scale and clear integration points.
APIs & services
Node · REST
Express, auth, integrations
Data stores
Mongo · Redis
Document store + cache
Quality bar
Jest · Selenium
Unit, integration, E2E where it pays
Production
~4 yrs
Agile delivery, on-call style fixes
I spend a large share of time on APIs, persistence, and production behavior: clear request/response contracts, auth rules, caching, and the kind of debugging you do when traffic and data shape are both non-trivial. I am used to owning features across the boundary—database and service changes land together with the UI that consumes them.
On the client, I ship React / Next.js experiences where state, performance, and accessibility matter (including complex modules like timelines and players). I work the way modern product teams expect: small PRs, tests where they earn their keep, and close collaboration with product and design in Agile delivery.
Dense, interview-style signal—aligned with how senior IC roles are scoped today (services + data + quality, with UI as the product surface).
Design and ship HTTP APIs and service logic that other teams and clients can rely on.
Deepest day-to-day: Node/Express REST, MongoDB/Redis, and React/Next/TypeScript for implementation.
Grouped how recruiters and hiring managers typically scan profiles—filter by lane, tap to pin a skill.
Ordered to foreground backend and full-stack work first—then client-heavy modules that sit on top of real service contracts.
Backend-focused service: ingestion pipelines, storage layout, manifest generation, stream preparation, and secure delivery contracts for players—designed for scale and clear integration points.
Full-stack product surface: authentication, persistence for assets, async job-style generation flows, and guarded API routes so the UI stays thin and the server owns business rules.
Cross-cutting library work: shared error model for Node and browser clients, normalization utilities, and predictable rendering hooks—reduces drift between services and UI error handling.
Content domain with RBAC, server-rendered pages for SEO, and performance-conscious delivery—good example of balancing auth rules, caching, and publish workflows.
Client-heavy module with adaptive streaming, buffering and error states, and tight coupling to backend manifests—shows API consumption discipline under real network conditions.
Professional product work: synchronized playback, clip graph operations, and state-heavy UI backed by stable service contracts—representative of complex client + API interplay.
Pulled live from DEV— new posts appear here automatically (checks every 5 minutes while this tab is open).
Open to full-stack roles and collaborations. Prefer email with a short context and what you are hiring for.
Master of Computer Applications — Integral University, Lucknow
Bachelor of Computer Application — Swami Vivekanand Subharti University, Meerut