Vivek Singh
Software Developer
5+ years exp
TypeScript
Node JS
JavaScript
Security & Auth: 4/10
Active 2 days ago
+91 (8707) 794910
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Backend engineer focused on Node.js microservices at a middle level with a strength for pragmatic API and auth implementations. The strongest proven skill is building small service-oriented Node.js systems with an API gateway, request-id logging and Redis caching as shown in api-gateway/index.js and order-service/src/services/order.service.js. Public code does not show advanced resilience, DB migrations, performance benchmarking or automated test coverage.
Technical skills
TypeScript
Node JS• Senior • 5y+
JavaScript• Middle
Node JS
Bcrypt
Express• 5y+
Databases
MySQL
MongoDB
Redis
Frontend
Material UI
Sass
Webpack
PostCSS
Vite
JQuery
Bootstrap
Next.js• 5y+
Tailwind CSS• 5y+
React.js• 5y+
Redux
DevOps
CI/CD
Git
Rest API
QA
Jest
Mobile
React Native
Cybersecurity
Checkmarx
Snyk
Timeline
System Engineer
•
Middle
Tata Consultancy Services
•
Full-Time
Developed and optimized scalable UI components using React and Redux to improve performance and user experience. Applied frontend security best practices by remediating vulnerabilities identified via Snyk and Checkmarx. Collaborated with designers, backend developers, and QA to deliver user-focused solutions, and worked on backend features with Node.js and Express. Implemented ARIA-compliant accessibility components to improve accessibility.
React.js
Redux
Node JS
Express
Checkmarx
Snyk
Software Developer
•
Middle
SAS ONE Pvt. Ltd.
•
Full-Time
Built scalable web and mobile applications using React, Next.js, and Tailwind CSS. Developed backend services with Node.js and Express, integrating REST APIs and improving frontend performance via lazy loading and code splitting. Monitored and optimized Core Web Vitals and delivered SEO-friendly experiences using SSR and SSG. Maintained code quality through Git workflows and code reviews.
React.jssince 2021
Next.js
Tailwind CSS
Node JSsince 2021
Expresssince 2021
Middle Backend Developer
Confidence: Medium API Engineer
Backend engineer focused on Node.js microservices at a middle level with a strength for pragmatic API and auth implementations. The strongest proven skill is building small service-oriented Node.js systems with an API gateway, request-id logging and Redis caching as shown in api-gateway/index.js and order-service/src/services/order.service.js. Public code does not show advanced resilience, DB migrations, performance benchmarking or automated test coverage.
API Design
3/10
How well APIs are designed
Basic REST API design with consistent error codes and a simple gateway proxy, but no versioning, idempotency, or advanced pagination patterns.
Evidence
microservices-nodejs/api-gateway/index.js - createProxy and header/request-id handling
microservices-nodejs/order-service/src/controllers/order.controller.js - list/get/create endpoints and auth checks
microservices-nodejs/user-service/src/controllers/auth.controller.js - register/login/me endpoints with error handling
Data Layer & Database
3/10
Working with databases
Uses MongoDB repositories and Redis caching with TTL and basic cache invalidation, but no migration history, transactions or advanced query optimization shown.
Evidence
microservices-nodejs/order-service/src/services/order.service.js - repo.findAll and redis get/set with TTL and invalidation
microservices-nodejs/order-service/src/repositories/order.repository.js - repository layer functions (findAll, findById, create)
microservices-nodejs/user-service/src/services/auth.service.js - repo.create and findByEmail patterns
Scalability & Performance
3/10
Handling load and speed
Includes Redis caching and an API gateway proxy for decoupling, but lacks rate limiting, request timeouts, backpressure or load-test artifacts.
Evidence
microservices-nodejs/order-service/src/services/order.service.js - caching with TTL and invalidation
microservices-nodejs/order-service/src/cache/redis.client.js - redis client init/get/disconnect
microservices-nodejs/api-gateway/index.js - proxying requests to service URLs
System Architecture
3/10
Overall system structure
Monorepo with small service decomposition and an API gateway shows intentional separation, but the design is simple and there is little evidence of inter-service contracts or graceful degradation strategies.
Evidence
microservices-nodejs/package.json - workspaces for api-gateway, user-service, order-service
microservices-nodejs/api-gateway/index.js - gateway routing to service URLs
microservices-nodejs/user-service/index.js - standalone service entrypoint
Security & Auth
4/10
Protecting data and access
Authentication implemented with bcrypt and JWT plus Joi validation at model layer, demonstrating security awareness, though secrets fallback and missing hardening reduce the score.
Evidence
microservices-nodejs/user-service/src/services/auth.service.js - bcrypt hashing and jwt.sign/verify usage
microservices-nodejs/user-service/src/middleware/auth.middleware.js - JWT token verification
microservices-nodejs/user-service/src/models/user.model.js - Joi input validation
Reliability & Observability
3/10
Stability and monitoring
Structured logging and request-id propagation are implemented for observability, and controllers use explicit error responses, but resilience patterns like retries, timeouts and graceful shutdown are not present.
Evidence
microservices-nodejs/api-gateway/index.js - request-id assignment and logger.info with duration on response finish
microservices-nodejs/user-service/src/controllers/auth.controller.js - logging on attempts and failures
microservices-nodejs/order-service/src/controllers/order.controller.js - explicit status handling and try/catch
Expertise
Microservices & API Architecture• Middle
Node.js• Middle
Industries
Financial Services• Middle
Technologies
MySQL
MongoDB
Redis
Rest API
Bcrypt
Recommendations
- Lead development of small to medium REST microservices in Node.js, including API gateway routing and auth flows.
- Implement resilience improvements such as request timeouts, retries with backoff, and circuit breakers around inter-service calls.
- Add database migration tooling and transactional patterns for MongoDB workloads and document schema evolution.
- Improve observability and SRE practices by adding structured traces, metrics (Prometheus/OpenTelemetry) and request-level timeouts for service calls.
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
A middle-level front-end developer specializing in JavaScript for mobile and web applications with practical experience building consumer-facing UIs. The strongest proven skill is front-end state management and integration with platform APIs, demonstrated by the Redux Toolkit slice and async product fetching in Shopping-Cart/redux/cartSlice.js and the MapView/geolocation integration in SpeedRider/src/screens/Home.js. There is little to no evidence of low-level systems work such as graphics shaders, physics engines, deterministic simulation, performance profiling, or automated CI and test coverage.
Gameplay Systems & Mechanics
2/10
How game logic works
Simple gameplay-style logic exists (captain selection, OTP generation, ride pricing) but no non-trivial state machines or decoupled gameplay systems.
Graphics & Rendering
1/10
Drawing game visuals
Uses platform rendering APIs (MapView, Markers, Polyline) and icon fonts but no authored shaders or custom render pipeline work.
Physics & Math
2/10
Game physics and math
Basic spatial/math usage for distances and coordinate handling; no custom physics or deterministic simulation.
Engine Proficiency
3/10
Skill with the game engine
Practical use of frameworks (React Native, Next.js) and state management (Redux Toolkit) beyond copy-paste but no editor tooling or engine-level customization.
Performance & Frame Budget
1/10
Keeping the game smooth
No measured optimizations or profiling evidence; normal patterns used but some attention to UX responsiveness (fitToCoordinates/animateToRegion).
Content Pipeline & Tooling
2/10
Tools for game content
Standard front-end content pipeline practices and dependency setup (Next.js, Tailwind, package.json) but no automation, CI, or asset import tooling.
Industries
Commerce• Middle
Technologies
JavaScript• Middle
Recommendations
- Develop consumer mobile features that require maps and geolocation (route drawing, nearest-entity selection, ETA) using React Native and map SDKs.
- Build e-commerce frontends with Redux Toolkit and Next.js, focusing on robust async flows, error handling and UX edge cases.
- Add unit and integration tests and set up a CI pipeline to raise confidence for production releases.
- Invest in performance practices: profile hot paths, avoid allocations in render loops, and introduce pooling or throttling where needed
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Intern Frontend Developer
Confidence: Low App Engineer
Frontend developer at a junior level focused on building microfrontend-style PWAs and static portfolios with basic service worker integration. The strongest proven artifact is a service worker implementing naive network-first caching located at tomervivek/Microfrontend-PWA/host/src/service-worker.js. There is limited evidence of custom component architecture, structured client state management, accessibility engineering or automated tests in the public code.
UI Component Architecture
2/10
How interface parts are built
Minimal component architecture; mostly static HTML/CSS and included third-party UI scripts rather than a custom design system or component library.
Responsive & Cross-browser
2/10
Works on all screens and browsers
Basic responsive scaffolding is present (meta viewport), but no advanced layout strategies, RTL/i18n patterns or feature-detection logic.
Performance Optimization
3/10
Speed of the interface
Shows awareness of PWA caching via a service worker, but the implementation is a simple network-first cache-then-fallback and lacks measured optimizations, cache versioning and stale-while-revalidate patterns.
Accessibility & Semantics
2/10
Usable for everyone
Very limited accessibility work evident; basic semantic HTML and lang attribute are present but no ARIA on custom widgets or CI a11y tooling.
State Management & Data Flow
1/10
Managing data in the app
No evidence of structured client state management, request cancellation, optimistic updates or state machines; only a service worker fetch handler touches async flow.
UX & Visual Polish
2/10
Look and feel quality
Visual polish relies on copied third-party libraries and animation CSS; there are no custom loading/empty/error UX patterns or undo/rollback flows implemented in app code.
Expertise
React• Intern
PWA & Web APIs• Intern
Industries
Financial Services• Middle
Technologies
TypeScript
Node JS• Senior • 5y+
Redux
Webpack
Tailwind CSS• 5y+
Next.js• 5y+
Express• 5y+
CI/CD
Bootstrap
Git
React.js• 5y+
JQuery
Vite
Material UI
Sass
PostCSS
Recommendations
- Build small microfrontend prototypes that integrate remote components while keeping each app lightweight - expand the existing host/service-worker work into robust caching and update strategies.
- Refactor vendor JS/CSS into package-managed dependencies and create a small component library with clear boundaries and tests to demonstrate component architecture skills.
- Add explicit async-state discipline: request cancellation, optimistic updates with rollback, and documented race-condition handling for nontrivial flows.
- Improve accessibility and UX by adding ARIA to custom widgets, keyboard focus management, and CI a11y checks like axe or eslint-plugin-jsx-a11y.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: