NagaSaiRam Sunkara
Full Stack Developer
Node JS
Python
SQL
C++
C
JavaScript
TypeScript
Java
API Design: 5/10
Scalability & Performance: 5/10
System Architecture: 5/10
Active 5 days ago
+91 (8309) 278299 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Senior fullstack web engineer focused on browser-based recording and media processing pipelines. The strongest proven skill is designing resilient backend video processing and worker systems as evidenced by server/merge/merge.js and rivora-spring/server/workers/streamWorker.js. There is limited public evidence of comprehensive UI a11y work, formal test coverage, or measured frontend performance benchmarking.
Technical skills
Node JS• Senior
Python
SQL
C++
C
JavaScript
TypeScript
Java• Senior
Node JS
BullMQ
Express
Nest.JS
Axios
Mongoose
Ioredis
Nodemailer
C
FFmpeg
Java
Spring Boot
Databases
PostgreSQL
Redis
MongoDB
Frontend
React.js
Vite
Tailwind CSS
Redux
Redux Toolkit
Zod
Socket.IO
DevOps
AWS
CI/CD
Docker
Git
GitHub Actions
Rest API
Vercel
AI/ML
Gemini
LLM
Tesseract OCR
IoT
MQTT
QA
Jest
Postman
Mobile
JUnit
Timeline
National Institute of Technology (NIT)
Master's Degree •
computer applications
Software Development Intern, Backend Engineering
•
Junior
Antino Labs Pvt. Ltd.
•
Internship
Worked on backend features related to payments and IoT. Improved payment handling by reducing duplicate charges and supporting production stability during service issues. Coordinated with teammates to resolve issues and share implementation context where documentation was missing.
SnapStudy Ai
AI/ML
•Converts handwritten notes and 50+ page PDFs into structured flashcards using the Gemini Flash API, Tesseract OCR, and PDF.js, scheduled via the SM-2 spaced repetition algorithm.
Python
React.js
RAG
PyTorch
LLM
Tesseract OCR
Revora
Desktop app
•Designed a fault-tolerant recording engine using five-second chunked media capture with automatic retry, recovery, and re-synchronisation, holding zero data loss across 100+ sessions on unstable networks.
•Moved media processing off the request path with BullMQ worker queues and FFmpeg, reducing synchronous API response time by 40% and enabling concurrent audio rendering.
•Integrated OAuth 2.0, Redis caching, and Cloudinary storage with automatic upload recovery for large multimedia files.
Java
Spring Boot
JavaScript
Node JS
React.js
PostgreSQL
BullMQ
Redis
Senior Backend Developer
Confidence: Medium API Engineer
Backend-focused full-stack engineer (senior-level evidence) specializing in media ingestion and processing pipelines. The strongest proven skill is building resilient media processing workflows and queue-backed workers as implemented in server/merge/merge.js, rivora-spring/server/workers/streamWorker.js and server/workers/videoWorker.js. There is limited public evidence of production-grade observability (tracing/correlation ids), migration/versioning of the data schema, or comprehensive automated tests.
API Design
5/10
How well APIs are designed
Clear REST controllers and consistent error codes and role tokens, but missing explicit versioning, pagination or a documented API contract.
Evidence
Rivora/server/controllers/sessionController.js: sendInvitation / generateToken / getSessionById endpoints
rivora-spring/spring-server/src/main/java/com/rivora/service/SessionService.java: createSession, sendInvitation, generateToken, mergeVideos methods
rivora-spring/spring-server/src/main/java/com/rivora/security/JwtAuthFilter.java: request authentication filter
Data Layer & Database
4/10
Working with databases
Uses Mongo/Mongoose and Spring Data repositories with populate/findOneAndUpdate; no migration history or explicit transactional boundaries are present.
Evidence
Rivora/server/controllers/sessionController.js: Session.findById and findOneAndUpdate usage
rivora-spring/spring-server/src/main/java/com/rivora/service/SessionService.java: sessionRepository.save and findById usage
rivora-spring/spring-server/src/main/java/com/rivora/repository/SessionRepository.java: MongoRepository usage
Scalability & Performance
5/10
Handling load and speed
Good queue-based decoupling with BullMQ and Redis Streams, worker concurrency controls and offloading of concatenation work to Cloudinary/ffmpeg optimizations.
Evidence
Rivora/server/workers/videoWorker.js: BullMQ Worker with limiter and job processing
rivora-spring/server/workers/streamWorker.js: Redis Streams consumer loop with XREADGROUP and idempotency handling
Rivora/server/merge/merge.js: Cloudinary transformation-based concatenation and local ffmpeg merging
System Architecture
5/10
Overall system structure
Reasonable service decomposition for media pipeline: controllers, merge module and separate workers; uses env-driven config and includes graceful shutdown handling.
Evidence
Rivora/server/merge/merge.js: media pipeline implemented as a separate module (processSession)
rivora-spring/server/workers/streamWorker.js: clear module-level worker architecture and graceful shutdown()
Rivora/server/controllers/sessionController.js: controller layer that enqueues jobs and calls merge
Security & Auth
4/10
Protecting data and access
JWT-based auth, httpOnly cookies and a Java JwtAuthFilter show security awareness, but token lifecycles and consistent expiry/refresh handling are not fully implemented.
Evidence
Rivora/server/controllers/authController.js: JWT creation and httpOnly cookie settings
rivora-spring/spring-server/src/main/java/com/rivora/security/JwtUtil.java: JWT helper
rivora-spring/spring-server/src/main/java/com/rivora/security/JwtAuthFilter.java: request authentication filter
Reliability & Observability
5/10
Stability and monitoring
Retries, job failure handlers and graceful shutdowns are present; logging is used but structured tracing/correlation ids and advanced backoff strategies are limited.
Evidence
Rivora/server/merge/merge.js: getResourceDetailsWithRetry with MAX_RETRIES and delay
Rivora/server/workers/videoWorker.js: worker.on('failed') handling and DB update after processing
rivora-spring/server/workers/streamWorker.js: shutdown() and retry/backoff in stream loop
Expertise
Node.js• Middle
Java• Middle
Messaging & Real-time• Middle
Microservices & API Architecture• Middle
Industries
Education• Middle
Media & Entertainment• Middle
Technologies
Python
Java• Senior
SQL
MongoDB
PostgreSQL
Redis
Rest API
Nest.JS
Spring Boot
GitHub Actions
Vercel
CI/CD
Git
AWS
Docker
Cloud• mentioned only
Stack• mentioned only
Recommendations
- Implement and harden Redis Streams worker fleets for large-scale media pipelines and formalize idempotency and dead-letter strategies.
- Extend observability: add structured logs, correlation ids, metrics and traces around job lifecycle and ffmpeg steps.
- Add schema migration tooling and transactional patterns for critical DB updates and persist job states for easier recovery.
- Harden auth/token lifecycle: add explicit token expirations, refresh paths and centralized token revocation for invited role tokens.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Senior Frontend Developer
Confidence: Medium Fullstack
Senior fullstack web engineer focused on browser-based recording and media processing pipelines. The strongest proven skill is designing resilient backend video processing and worker systems as evidenced by server/merge/merge.js and rivora-spring/server/workers/streamWorker.js. There is limited public evidence of comprehensive UI a11y work, formal test coverage, or measured frontend performance benchmarking.
UI Component Architecture
3/10
How interface parts are built
Component boundaries and custom hooks exist and are pragmatic, but there is limited evidence of a bespoke component system, composition patterns or a deliberate design system beyond using libraries and passing state down from a central App.
Evidence
Map-My-Notes/src/App.js: central AppContent that loads and passes state to pages
client-rivora/src/hooks/useLocalRecorder.js: custom hook handling MediaRecorder lifecycle
Map-My-Notes/src/context/AuthContext.js: AuthProvider and useAuth context
Responsive & Cross-browser
2/10
Works on all screens and browsers
Basic responsive tooling is present (Tailwind) but there is no evidence of advanced layout strategies, RTL/i18n readiness or progressive enhancement patterns beyond standard breakpoints and font choices.
Evidence
Map-My-Notes/tailwind.config.js: theme and colors configuration
client-rivora/vite.config.js: polyfills and aliasing for cross-browser compatibility
Performance Optimization
4/10
Speed of the interface
Meaningful performance and scalability work exists on the backend (worker design, queue limits, Redis streams) and the client uses chunked uploads to avoid large payloads, but there are no measured before/after metrics or bundle analysis artifacts.
Evidence
rivora-spring/server/workers/streamWorker.js: Redis Streams consumer with idempotency and polling
Rivora/server/workers/videoWorker.js: BullMQ worker with limiter and failure handling
client-rivora/src/hooks/useLocalRecorder.js: chunked MediaRecorder upload loop and uploadProgress handling
Accessibility & Semantics
2/10
Usable for everyone
Minimal accessibility evidence; basic semantic structure and keyboard affordances are not visible, and there are no a11y tool integrations or ARIA on custom widgets.
Evidence
Map-My-Notes/src/App.js: router/pages and use of Toaster (no explicit accessibility patterns)
Map-My-Notes/tailwind.config.js: theme tokens (visual but not accessibility-specific)
State Management & Data Flow
4/10
Managing data in the app
Server-state and data flows are well thought out on the backend with job queues and worker processing; frontend state uses context and hooks with cleanup, and the recording hook shows request lifecycle discipline and cancellation patterns.
Evidence
Rivora/server/merge/merge.js: retry logic, chunk ordering and error handling in merge pipeline
rivora-spring/server/workers/streamWorker.js: processJob flow, XACK handling and idempotency
client-rivora/src/hooks/useLocalRecorder.js: recordingActiveRef, currentRecorderRef and effect cleanup
UX & Visual Polish
3/10
Look and feel quality
UX considerations such as upload progress indicators and Toaster messages exist and there are sensible defaults and warnings, but there is limited evidence of comprehensive loading/error/empty state designs or undo patterns across the UI.
Evidence
client-rivora/src/hooks/useLocalRecorder.js: isUploading and uploadProgress state and user-facing warnings
Map-My-Notes/src/App.js: central data-loading with logs and parallel Promise.all for perceived performance
Expertise
React• Middle
Modern Web Frameworks• Middle
PWA & Web APIs• Middle
Industries
Education• Middle
Media & Entertainment• Middle
Technologies
Node JS• Senior
Redux
Tailwind CSS
Express
Socket.IO
React.js
Vite
Mongoose
Axios
BullMQ
Zod
Nodemailer
Ioredis
Redux Toolkit
Cloud• mentioned only
Recommendations
- Own end-to-end remote-recording features including client chunked recording, robust uploads, and backend merge pipelines for scalable media processing.
- Implement and harden background workers and stream/queue consumers (Redis Streams or BullMQ) for fault-tolerant media jobs and retries.
- Build integrations that optimize video delivery and CDN/storage lifecycle for large media (Cloudinary/FFmpeg workflows and cleanup).
- Develop data-driven learning UIs using Google Drive integration and spaced repetition flows where you already show solid integration work
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Blockchain Developer
Confidence: Medium Generalist
Full-stack Node.js and React engineer (senior-level borderline) focusing on resilient media capture and server-side video processing pipelines. The strongest proven skill is building end-to-end media processing and background-worker pipelines, demonstrated by server/merge/merge.js and the workers/streamWorker.js worker which handle chunked uploads, ffmpeg composition, Cloudinary integration, retries and Redis stream consumer logic. There is little to no evidence of Web3/smart-contract work, formal tests, or security/audit artifacts and some operational security issues (hardcoded secrets) remain unaddressed.
Smart Contract Development
Writing smart contracts
Not evidenced in public code
Security & Audit
3/10
Checking contracts for flaws
Basic web-security patterns are present (JWTs, httpOnly cookies, input validation) and there is evident error handling, but there are also clear operational security issues (hardcoded secrets/credentials) and no formal audit/testing artifacts.
Evidence
Rivora/server/controllers/sessionController.js: getSessionById uses JWT signing and authorization checks comparing req.user._id
Rivora/server/controllers/authController.js: sets httpOnly/secure/sameSite cookie flags for JWT
TrashClash_server/auth.js: hardcoded ADMIN_USERNAME/ADMIN_PASSWORD and JWT_SECRET = 'super_secret_key'
Blockchain Protocol Understanding
Knowing how blockchains work
Not evidenced in public code
DApp & Web3 Integration
Connecting apps to blockchain
Not evidenced in public code
Tokenomics & DeFi Logic
Token and finance logic
Not evidenced in public code
Decentralization & Trust Model
1/10
Designing trust without middlemen
Minimal trust-model controls are present via JWT-based auth, but there is no documented upgrade/governance, key-rotation or multisig patterns and some secrets are hardcoded.
Evidence
Rivora/server/controllers/sessionController.js: signs guest and participant tokens with process.env.JWT_SECRET
TrashClash_server/index.js and auth.js: hardcoded JWT_SECRET and admin credentials
Industries
Media & Entertainment• Middle
Recommendations
- Harden secrets and operational security: remove hardcoded credentials, add .env checks, and implement secret rotation and vault integration (e.g., AWS Secrets Manager, HashiCorp Vault).
- Add automated tests and CI: unit tests for merge logic, integration tests for worker flows, and end-to-end tests for recording/uploading/merging pipelines.
- Improve observability and reliability: add structured logging, metrics (Prometheus), and alerting for worker failures and Cloudinary/ffmpeg errors.
- Harden auth and session security: validate token flows, handle token expiry/refresh, and explicitly export/import shared resources (fix transporter/export mismatches).
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: