Divyanshu Bisht
Software Developer
5+ years exp
JavaScript
TypeScript
Node JS
Python
API Design: 5/10
Data Layer & Database: 4/10
Scalability & Performance: 4/10
Active 8 hours ago
Invite to interview
Download CVCV
Overview
Technical skills
Projects
Timeline
Roles
Overview
Backend Node.js engineer at a middle level focused on building REST APIs and validation-heavy server logic. The strongest proven skill is robust input validation and test coverage as shown by backend/src/validation/ticketValidation.js and the corresponding unit and integration tests in backend/src/validation/__tests__/ticketValidation.test.js and backend/tests/integration/*.test.js. There is limited public evidence of advanced distributed systems design, schema migrations, production-grade observability or explicit retry/backoff and circuit breaker patterns.
Phone
Technical skills
Languages
4
JavaScript
TypeScript
Node JS
Python
Node JS
10
Axios
Express
Mongoose
Bcrypt
Multer
Sequelize
Nodemailer
Joi
Winston
Helmet
Frontend
13
React.js
Redux
GraphQL
Next.js
Sass
Tailwind CSS
React Router
React Query
Bootstrap
Chart.js
Material UI
Redux Toolkit
Zustand
DevOps
3
GitLab
GitLab CI
AWS
Other
25
Jest
SonarQube
Vitest
Cursor
Claude
MySQL
Vite
GitHub
GitHub Actions
Dotenv
Sentry
CI/CD
Docker
Git
Rest API
Model Context Protocol
Twilio
npm
Storybook
Webpack
PostCSS
AI Agents
RAG
State Management
PWA
Projects
Astro Sooka
Developed React-based features for an OTT streaming platform, including custom leaderboard ad units and hybrid SSAI/CSAI ad insertion. Implemented cross-device AirPlay casting support for video playback. Integrated analytics and monitoring (Conviva, CleverTap, Sentry, Google Analytics) to track playback quality and production issues.
OISASS
Developed a BI tool that enables users to upload Excel/CSV files and visualize the results. Implemented a data processing workflow that renders uploaded datasets as real-time charts. Built the frontend with Next.js, Redux, and Chart.js.
Cornea Care
Created a responsive consultation web app where users describe eye symptoms and receive tailored treatment recommendations. Implemented authentication and communication features using OAuth and Twilio. Built the UI with Next.js and Redux to manage state across the user flow.
AISmart
Built a mobile-responsive React application to support monitoring and management of critical flight operations. Focused on improving operational visibility for functions such as on-time departures through a frontend interface. Implemented state handling with Redux and typed components using TypeScript.
Timeline
Senior Software Engineer
•
Senior
To The New
•
Full-Time
Reduced SonarQube technical debt and improved unit test coverage using Jest to raise maintainability and release confidence. Delivered ad monetization and playback reliability features using React and Redux, including hybrid SSAI/CSAI and AirPlay casting. Automated npm audit reporting via GitLab CI/CD and led Next.js/React knowledge sharing and mentorship through code reviews.
SonarQube
Jest
React.js
Next.js
Redux
TypeScript
GitLab CI
GitLab
Cursor
Software Engineer
•
Middle
Cynoteck Technology Solutions
•
Full-Time
Built a consultation portal using React with a component-based architecture and Redux state management. Integrated REST APIs and GraphQL using TypeScript to render dynamic data in responsive web and mobile-friendly screens. Improved frontend performance via lazy loading, code splitting, and React hook optimization while collaborating with UI/UX and backend teams.
React.js
Redux
TypeScript
GraphQL
Axios
Web Developer
•
Middle
Reosys Smart Solutions
•
Full-Time
Developed and maintained JavaScript-based frontend applications, including admin and end-user panels. Worked on web performance improvements and accessibility compliance to enhance overall user experience. Supported client demos, gathered requirements, and incorporated feedback to align solutions with business goals.
JavaScript
Uttarakhand Open University
Bachelor's Degree
Middle Backend Developer
Confidence: Medium API Engineer
Backend Node.js engineer at a middle level focused on building REST APIs and validation-heavy server logic. The strongest proven skill is robust input validation and test coverage as shown by backend/src/validation/ticketValidation.js and the corresponding unit and integration tests in backend/src/validation/__tests__/ticketValidation.test.js and backend/tests/integration/*.test.js. There is limited public evidence of advanced distributed systems design, schema migrations, production-grade observability or explicit retry/backoff and circuit breaker patterns.
API Design
5/10
How well APIs are designed
API design shows deliberate pagination, filter building, consistent error shapes and integration tests, but lacks explicit versioning and idempotency controls.
Evidence
support-ticket-management/backend/src/services/ticketService.js: listTickets with pagination and filter building (buildListFilter, pagination in response)
support-ticket-management/backend/src/validation/ticketValidation.js: structured validation and normalization for create and update endpoints
support-ticket-management/backend/src/validation/__tests__/ticketValidation.test.js: unit tests asserting validation behavior and error shapes
Data Layer & Database
4/10
Working with databases
Data layer uses Mongoose with population, countDocuments and aggregation work in other services; validation guards references, but there is no evidence of migration history or explicit transaction/ isolation handling.
Evidence
support-ticket-management/backend/src/services/ticketService.js: use of Ticket.find(...).populate(...), Ticket.countDocuments and Promise.all for concurrent queries
support-ticket-management/backend/src/validation/ticketValidation.js: validateUserReference calls User.findById to enforce referential integrity
KRPH/src/krphapi/sla/slaController.js: complex MongoDB aggregation pipelines and explicit index creation (IndexsForSla)
Scalability & Performance
4/10
Handling load and speed
Shows practical performance patterns: cache usage, pagination, parallel queries and aggregation pipelines, but no queue-based decoupling, explicit connection pooling tuning, or measured performance artifacts.
Evidence
KRPH/src/krphapi/sla/slaController.js: NodeCache usage with cacheKey logic for SLA reports
support-ticket-management/backend/src/services/ticketService.js: pagination + Promise.all to fetch page and count concurrently
System Architecture
4/10
Overall system structure
Reasonable modular structure with clear service, validation and middleware separation appropriate for a single-service API; architecture is monolithic and there is no evidence of multi-service contracts or advanced degradation strategies.
Evidence
support-ticket-management/backend/: folder layout separating services, validation, middleware and tests
support-ticket-management/backend/src/middleware/asyncHandler.js and src/middleware/errorHandler.js: separation of concerns for request handling and error handling
Security & Auth
4/10
Protecting data and access
Good input validation and some sanitization helpers are present and tests exercise invalid inputs; authentication and token lifecycle logic appear in other projects but token revocation, secrets management and hardened SSRF/SQL-injection countermeasures are not fully evidenced here.
Evidence
support-ticket-management/backend/src/validation/ticketValidation.js: input normalization, enum and user reference validation
support-ticket-management/backend/src/validation/__tests__/ticketValidation.test.js: tests validating bad object ids and missing users
KRPH/src/krphapi/auth/authService.js: uses jwt and bcrypt for auth flows (evidence of auth handling in code)
Reliability & Observability
3/10
Stability and monitoring
Basic reliability patterns exist such as error handler middleware and tests; advanced observability, retry-with-backoff, circuit breakers and graceful shutdown patterns are not clearly present in human-authored code.
Evidence
support-ticket-management/backend/src/middleware/errorHandler.js: dedicated error handler (signature present)
support-ticket-management/backend/tests/integration/*.test.js: integration tests exercising API endpoints and error shapes
KRPH/src/krphapi/support-ticket/supportTicketService.js: loggingApi usage indicates some logging/observability integration
Expertise
Node.js• Middle
Microservices & API Architecture• Middle
Messaging & Real-time• Middle
Industries
Farming & Agriculture• Middle
Technologies
Rest API
GraphQL• since 2022
Bcrypt
Joi
Winston
Multer
Mongoose
Helmet
Dotenv
Nodemailer
Recommendations
- Develop REST APIs that require strong input validation, clear error contracts and automated unit/integration tests.
- Implement operational reporting and aggregation endpoints that need careful MongoDB aggregation, caching and pagination.
- Integrate third-party services and backend stores (SQL stored procedures + Sequelize and MongoDB) with attention to error handling and retry policies.
- Harden security and observability: add structured logs, metrics, retry-with-backoff, secrets handling and documented migration history
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
Fullstack developer (mid-level) focused on building reliable backend APIs and coordinating a conventional React frontend with pragmatic validation and testing. The strongest proven skill is backend API and data work, demonstrated by the SLA/report aggregation and caching code (KRPH/src/krphapi/sla/slaController.js) and the support-ticket validation and integration tests (backend/src/validation/ticketValidation.js and backend/tests/integration). There is limited evidence of advanced frontend performance engineering, comprehensive accessibility on custom widgets, or sophisticated client-side state machines and optimistic UI patterns.
UI Component Architecture
3/10
How interface parts are built
Component boundaries and reuse exist but are modest; frontend shows custom hooks and utility modules rather than a bespoke design system.
Evidence
support-ticket-management/frontend/src/hooks/useUsers.js
support-ticket-management/frontend/src/api/client.js
support-ticket-management/frontend/src/utils/validation.js
Responsive & Cross-browser
3/10
Works on all screens and browsers
Responsive layout uses grid and media queries and there is basic responsive consideration, but no advanced fluid/RTL or feature-detection work.
Evidence
support-ticket-management/frontend/src/index.css (responsive grid and @media (max-width: 640px))
support-ticket-management/frontend/src/index.css (grid-template-columns: repeat(auto-fit, minmax(200px, 1fr)))
Performance Optimization
2/10
Speed of the interface
Some performance work is present mainly in backend/reporting (caching, aggregation); frontend performance-specific work (virtualization, measured LCP/INP tuning) is not evidenced.
Evidence
KRPH/src/krphapi/sla/slaController.js (NodeCache usage and caching logic)
KRPH/src/krphapi/support-ticket/supportTicketService.js (appCache token caching and external API call caching pattern)
Accessibility & Semantics
2/10
Usable for everyone
Basic accessibility and semantics are present (focus styles, form-control focus outline), but no evidence of ARIA on custom widgets, keyboard management, or CI a11y tooling.
Evidence
support-ticket-management/frontend/src/index.css (.form-control:focus outline rule)
support-ticket-management/frontend/src/index.css (semantic class names: .alert, .loading-indicator, .empty-state)
State Management & Data Flow
3/10
Managing data in the app
State and data flow show custom API client, organized API modules and hooks; server-state discipline is manual (no React Query/SWR) and there is validation and request parsing on backend.
Evidence
support-ticket-management/frontend/src/api/tickets.js (query builder and CRUD API functions)
support-ticket-management/frontend/src/api/client.js (ApiError, parseResponse, apiRequest)
support-ticket-management/backend/src/validation/ticketValidation.js (server-side validation and normalizeTicketInput)
UX & Visual Polish
4/10
Look and feel quality
UX details are thoughtfully implemented: empty states, loading indicators, form error patterns and integration tests that assert edge states and error displays.
Evidence
support-ticket-management/frontend/src/index.css (loading-indicator, empty-state, field-error classes)
support-ticket-management/backend/tests/integration/tickets.crud.test.js (integration tests validating errors, pagination and edge cases)
support-ticket-management/backend/tests/integration/tickets.comments.test.js (tests for comment behaviors and updatedAt edge case)
Expertise
React• Middle
Frontend Architecture & Build Tools• Middle
Industries
Farming & Agriculture• Middle
Government• Middle
Technologies
TypeScript• since 2022 • Senior
Node JS• Middle
Zustand
Redux• since 2022
Webpack
Tailwind CSS
Next.js• since 2025
Express
GitHub Actions
Chart.js
GitLab CI• since 2025
Bootstrap
Git
AWS
Docker
React.js• since 2022
Vite
React Query
Storybook
npm
Sequelize
Axios• since 2022
Material UI
Sass
PostCSS
Redux Toolkit
React Router
GitHub
GitLab• since 2025
Recommendations
- Develop fullstack internal tools and support-ticket workflows where server-side validation, aggregation and integration with external APIs are required.
- Implement backend-heavy reporting pipelines and cron-driven data processing and caching (SLA/reporting and token-caching patterns are a fit).
- Extend the React frontend with clearer client-state patterns (introduce React Query or similar) and component-level tests to improve UX edge-state handling.
- Work on integrations that require robust error handling and stored-procedure / SQL orchestration for enterprise systems.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: Medium SDET
Middle-level SDET focused on backend API validation and integration testing with a practical emphasis on input validation and end-to-end API flows. The strongest proven skill is robust input validation and negative-path testing as implemented in backend/src/validation/ticketValidation.js and its corresponding unit tests in src/validation/__tests__/ticketValidation.test.js. There is limited evidence of CI pipeline automation, contract testing, performance/load testing or large-scale system design in public code.
Test Automation Frameworks
6/10
Building automated tests
Reasonable test automation infrastructure with in-memory DB setup, global lifecycle hooks, test helpers and fixtures, but no advanced parallelization or sharding configuration.
Evidence
support-ticket-management/backend/jest.config.js
support-ticket-management/backend/tests/helpers/testDb.js
support-ticket-management/backend/tests/helpers/testApp.js
Test Coverage & Strategy
5/10
What and how to test
Balanced unit and integration test coverage including negative-path validation checks and helpers for asserting validation failures, but no property-based tests, mutation testing or explicit risk-tagging/priority classification.
Evidence
support-ticket-management/backend/src/validation/__tests__/ticketValidation.test.js
support-ticket-management/backend/tests/integration/tickets.crud.test.js
support-ticket-management/backend/tests/helpers/expectValidationError.js
API & Integration Testing
5/10
Testing how parts work together
Good API integration testing with Supertest and in-memory MongoDB usage covering status codes and response shapes, but no contract testing tools (pact/schemathesis) or explicit idempotency/retry scenario tests.
Evidence
support-ticket-management/backend/tests/integration/tickets.crud.test.js
support-ticket-management/backend/tests/integration/tickets.comments.test.js
support-ticket-management/backend/package.json
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
2/10
Finding and describing bugs
Some debugging and test-result notes exist but there are no reproducible bug reports, linked fixes, or documented root-cause analyses tied to tests.
Evidence
support-ticket-management/debugging-notes.md
support-ticket-management/test-results.md
CI Test Integration
2/10
Running tests automatically
Local test scripts and jest global setup/teardown are present indicating CI awareness, but there are no CI workflow configurations, matrix runs or curated failure artifact retention documented.
Evidence
support-ticket-management/backend/jest.config.js
support-ticket-management/package.json
Expertise
SDET & Test Engineering• Middle
Industries
Information Technology• Middle
Technologies
JavaScript• since 2021 • Middle
Jest• since 2025
CI/CD
Sentry
Vitest
Recommendations
- Develop backend API validation libraries and negative-path test suites for new or existing services, leveraging the current validation patterns and test helpers.
- Build and maintain integration test harnesses that use in-memory databases and fixture seeding to validate end-to-end flows for REST APIs.
- Extend testing practice into CI by adding workflow definitions with selective job matrices, artifact capture and per-test retry/quarantine rules.
- Introduce contract testing (PACT or Schemathesis) and mutation or property-based tests to increase confidence in API contracts and edge-case behavior.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: