Manish Rajak
Software Developer
JavaScript
Node JS
TypeScript
Python
C
C++
Security & Auth: 5/10
API Design: 4/10
Data Layer & Database: 4/10
Active 1 day ago
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Full-stack web developer (middle level) specializing in pragmatic Next.js front ends and Express back ends with a focus on auth and realtime features. The strongest proven skill is secure authentication and session handling as demonstrated by refresh-token hashing, cookie options, and rotation in StudyNest/backend/src/controllers/auth.controller.js. There is limited public evidence of automated test coverage, measured front-end performance work, or advanced accessibility engineering.
Technical skills
JavaScript
Node JS• Middle
TypeScript
Python
C
C++• Middle
Node JS
Express
Nodemailer
Axios
Ioredis
Mongoose
Bcrypt
C++
STL
Databases
MySQL
PostgreSQL
Redis
MongoDB
Frontend
JQuery
Next.js
React.js
Socket.IO
Tailwind CSS
PostCSS
Framer Motion
Recharts
DevOps
AWS
Azure
Docker
Git
Rest API
WebRTC
WebSockets
AI/ML
Claude
QA
Postman
Timeline
A production-ready Smart Attendance System built with Python, Flask, OpenCV, and face_recognition. Features real-time webcam-based attendance marking, anti-spoofing via blink detection, role-based dashboards, analytics, Excel export, and email alerts.
Node JS
MongoDB
Express
React.js
Next.js
Python
Flask
OpenCV
Software Development Engineer Intern
•
Junior
Bluestock Fintech
•
Internship
Built and designed IPO listing and registration workflows used by large user groups. Implemented and integrated RESTful APIs across multiple endpoints to support end-to-end features. Worked on improving the overall application experience using backend integration and API development practices.
AWS
Node JS
Express
Rest API
Bangalore Institute of Technology (BIT)
Bachelor's Degree •
Electronic Instrumentation
Middle Backend Developer
Confidence: Medium API Engineer
A backend-focused API engineer (middle level) with clear practical experience building secure REST endpoints and user-account flows. The strongest proven skill is secure authentication and session handling with refresh-token rotation and hashed refresh storage as implemented in StudyNest/backend/src/controllers/auth.controller.js. The public code lacks production-grade operational artifacts such as migration history, structured observability, scaling infrastructure and automated tests.
API Design
4/10
How well APIs are designed
API endpoints show deliberate auth and error-handling choices, idempotent upserts and consistent status codes, but there is no visible versioning strategy, documented pagination, or formal API contract.
Evidence
StudyNest/backend/src/controllers/auth.controller.js - token rotation, cookie options and generic error responses
StudyNest/backend/src/controllers/room.controller.js - join/leave endpoints with ON CONFLICT upsert and validation
ComplaintFrom-website/src/app/api/complaints/route.ts - POST/GET handlers with status codes and non-blocking email notification
Data Layer & Database
4/10
Working with databases
Data layer uses parameterized SQL queries, JOINs and COUNT FILTER and stores hashed refresh tokens, and the Mongo schema is defined for complaints; however there is no visible migration history, transaction boundary handling, or explicit indexing strategy in the provided files.
Evidence
StudyNest/backend/src/controllers/room.controller.js - parameterized queries, JOIN and COUNT(...) FILTER usage
StudyNest/backend/src/controllers/auth.controller.js - storing refresh_token_hash and DB interactions
ComplaintFrom-website/src/models/Complaint.ts - Mongoose schema with fields and defaults
Scalability & Performance
2/10
Handling load and speed
Little evidence of deliberate scalability engineering such as caching, queues, connection tuning or rate-limiting configuration; a sensible LIMIT is used on listing and client-side timers exist but no production scaling artifacts are present.
Evidence
StudyNest/backend/package.json - lists express-rate-limit as a dependency (rate limiting dependency present but configuration not shown)
StudyNest/backend/src/controllers/room.controller.js - LIST query with LIMIT 50
StudyNest/frontend/pages/rooms/[id].js - client-side Pomodoro timer implementation
System Architecture
3/10
Overall system structure
Code is organized with controllers, middleware and utils separated, and frontend/backend clearly split; overall it is a monolithic web application structure without multi-service contracts, secret management, or advanced service decomposition.
Evidence
StudyNest/backend/src/controllers/ - clear controller files for auth, room, session
StudyNest/backend/src/middleware/auth.js - middleware boundary for protected routes
ComplaintFrom-website/src/middleware.ts - Next.js edge middleware protecting admin routes
Security & Auth
5/10
Protecting data and access
Strong practical security choices are visible - bcrypt password hashing with reasonable rounds, refresh-token rotation with hashed storage, httpOnly secure cookies, input sanitization and parameterized queries - showing security awareness at input boundaries.
Evidence
StudyNest/backend/src/controllers/auth.controller.js - bcrypt usage, SALT_ROUNDS, refresh token hashing and secure cookie options
StudyNest/backend/src/controllers/room.controller.js - sanitizeInviteCode input sanitization
StudyNest/backend/package.json - inclusion of helmet as a dependency
Reliability & Observability
3/10
Stability and monitoring
Basic reliability patterns appear - try/catch with next(err), console.error logging and defensive logout cleanup - but structured logging, retries/backoff, timeouts and graceful shutdown patterns are not present in the surfaced code.
Evidence
StudyNest/backend/src/controllers/auth.controller.js - try/catch flows and defensive invalidation on refresh-token mismatch
ComplaintFrom-website/src/app/api/complaints/route.ts - console.error usage and non-blocking email send
StudyNest/backend/src/controllers/room.controller.js - try/catch with next(err) propagation
Expertise
Node.js• Middle
Databases & Vector Storage• Middle
Industries
Education• Middle
Technologies
Node JS• Middle
MongoDB
PostgreSQL
Express
Bcrypt
Axios
Recommendations
- Ship and document database migrations and schema evolution scripts so schema changes are auditable and reproducible - add a visible migrations/ directory and migration_chain artifacts.
- Harden production readiness: add structured logging, metrics, graceful shutdown, request timeouts and retry/backoff for external calls.
- Add caching or queue-based decoupling for heavier work (email notifications, reporting) and show explicit rate-limiting configuration for auth endpoints.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: Medium Fullstack
Full-stack web developer (middle level) specializing in pragmatic Next.js front ends and Express back ends with a focus on auth and realtime features. The strongest proven skill is secure authentication and session handling as demonstrated by refresh-token hashing, cookie options, and rotation in StudyNest/backend/src/controllers/auth.controller.js. There is limited public evidence of automated test coverage, measured front-end performance work, or advanced accessibility engineering.
UI Component Architecture
3/10
How interface parts are built
Modular React pages and small components with Context are used, but there is no custom design system or advanced component composition beyond typical Next.js page-level patterns.
Evidence
StudyNest/frontend/pages/rooms/[id].js: RoomContent component with local state and composed UI
StudyNest/frontend/pages/rooms/index.js: RoomsContent with form, filters and room cards
Queue-Management-system/frontend/src/App.js: Router and route-level composition of pages and guards
Responsive & Cross-browser
3/10
Works on all screens and browsers
Responsive design is implemented with Tailwind utility classes and breakpoints, but there is no evidence of advanced fluid layout techniques, RTL/i18n readiness, or feature-detection fallbacks.
Evidence
StudyNest/frontend/pages/rooms/[id].js: uses md:grid-cols and responsive utility classes
StudyNest/frontend/tailwind.config.js: custom theme tokens and content globs
Portfolio/tailwind.config.ts: Tailwind content config for app/pages/components
Performance Optimization
2/10
Speed of the interface
Some backend performance patterns are present (Redis for queues, LIMIT in SQL), but there is little evidence of measured front-end performance work, bundle analysis, virtualization, or targeted optimizations.
Evidence
StudyNest/backend/src/controllers/room.controller.js: SQL query with LIMIT 50 in listRooms
Queue-Management-system/backend/controllers/queueController.js: Redis used to track queue lengths and emit minimal socket updates
Queue-Management-system/backend/controllers/appointmentController.js: Redis usage with a MongoDB fallback for resilience
Accessibility & Semantics
2/10
Usable for everyone
Basic semantic HTML and form labels are used and focus rings defined in CSS, but there is no clear evidence of ARIA on custom widgets, keyboard focus management, or an a11y test/linter in CI.
Evidence
StudyNest/frontend/pages/rooms/[id].js: labelled input and semantic main/aside structure
StudyNest/frontend/pages/index.js: uses semantic sections and headings
Queue-Management-system/frontend/src/index.css: input focus ring and accessible focus styles
State Management & Data Flow
4/10
Managing data in the app
Server-state discipline and defensive auth patterns are visible on the backend and frontend state flows include cleanup and error handling; there are no advanced state machines or request-cancellation patterns but token rotation and refresh handling are implemented sensibly.
Evidence
StudyNest/backend/src/controllers/auth.controller.js: hashed refresh tokens, secure cookie options, and rotation logic
StudyNest/frontend/pages/rooms/[id].js: timer with ref, cleanup on unmount and API calls on join/leave
Queue-Management-system/backend/controllers/queueController.js: separation of queue service and socket emission showing deliberate data flow
UX & Visual Polish
3/10
Look and feel quality
The UI shows careful visual polish and helpful error messages with fallbacks in the backend, but loading skeletons, optimistic updates with rollback, and undo patterns are not broadly implemented.
Evidence
StudyNest/frontend/pages/rooms/[id].js: joinError messaging and camera-mode toggles for clear UX feedback
Queue-Management-system/backend/controllers/appointmentController.js: Redis fallback to MongoDB preserving UX when Redis is unavailable
Queue-Management-system/frontend/src/index.css: rich design tokens and animation utilities supporting visual polish
Expertise
React• Middle
Modern Web Frameworks• Middle
Frontend Architecture & Build Tools• Middle
Industries
Education• Middle
Health Care• Middle
Technologies
JavaScript
TypeScript
Rest API
Tailwind CSS
Next.js
Socket.IO
WebRTC
WebSockets
Azure
Git
AWS
Docker
React.js
JQuery
Mongoose
PostCSS
Nodemailer
Ioredis
Framer Motion
Recharts
Recommendations
- Develop full-stack Next.js + Express applications that require secure auth and session management, especially refresh-token rotation and httpOnly cookie flows.
- Implement realtime features and queueing with Redis and Socket.IO where responsiveness and low-latency updates are required.
- Build dashboards and UX for productivity or education products where stateful timers, streaks, and room membership flows are central.
- Iterate on frontend performance and accessibility: add measured LCP/INP improvements, skeleton loading states, ARIA on custom widgets, and automated tests.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Game Developer
Confidence: Medium Generalist
C++-capable full-stack generalist at a Middle level with a strong emphasis on algorithmic problem solving and small web services. The strongest proven skill is algorithm design and performance-minded C++ implementation, demonstrated by the pmr-based memory-pool and set usage in DSA-Streaks/2213-longest-substring-of-one-repeating-character/2213-longest-substring-of-one-repeating-character.cpp. Public code does not evidence game-engine work such as rendering shaders, physics simulation, deterministic networked simulation, or large-scale engine tooling.
Gameplay Systems & Mechanics
1/10
How game logic works
Minimal gameplay-style logic present; primarily algorithmic problem solutions rather than authored gameplay systems.
Evidence
Manish6232/DSA-Streaks/3734-lexicographically-smallest-palindromic-permutation-greater-than-target/3734-lexicographically-smallest-palindromic-permutation-greater-than-target.cpp
Manish6232/DSA-Streaks/2213-longest-substring-of-one-repeating-character/2213-longest-substring-of-one-repeating-character.cpp
Graphics & Rendering
Drawing game visuals
Not evidenced in public code
Physics & Math
2/10
Game physics and math
Algorithmic and number-theory work present (GCD, modular reasoning, graph DP) but no physics engine, deterministic simulation or custom integrators.
Engine Proficiency
3/10
Skill with the game engine
Shows practical engine/framework proficiency for web apps: API routes, middleware, DB connectivity and environment-aware configuration.
Performance & Frame Budget
3/10
Keeping the game smooth
Attention to performance in algorithmic code (sparse table RMQ, pmr memory resource) and careful complexity choices; no profiler captures or cross-platform frame-budget work.
Content Pipeline & Tooling
2/10
Tools for game content
Basic content pipeline and tooling setup for web projects (Next/Tailwind config and package manifests); CI, import automation or large-scale asset pipelines not present.
Technologies
C++• Middle
STL
Recommendations
- Develop performance-sensitive C++ modules or algorithm libraries where low-level memory control and STL expertise matter (e.g., game server utilities, native plugins).
- Implement and maintain backend API features and operational code (authenticated API routes, DB connection management, email notifications) similar to ComplaintFrom-website where reliability and clear error handling are required.
- Contribute algorithm-heavy systems or gameplay-prototype tools that benefit from careful complexity analysis and low-level optimization (pathfinding utilities, procedural content helpers).
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: