Manoranjan Behera

Backend • Middle • Management: Under a year • Bengaluru, India • UTC+05:30 • In office, Fully remote • Work permits: India • Citizenship: India • English: B2 • Available now

Software Developer

Management: Under a year

Node JS

JavaScript

API Design: 4/10

Data Layer & Database: 4/10

System Architecture: 4/10

Active 3 days ago

Invite to interview

Download CVCV

Overview

Technical skills

Projects

Timeline

Roles

Overview

Full-stack web engineer (middle level) focused on building production MERN applications and interactive frontends with strong UI polish. Proven strength is crafting polished client-side experiences and integrations - for example the portfolio hero (three.js scene, typewriter, toasts) and the Quiz app frontend with ProtectedRoute wiring (frontend/src/App.js and Manoranjan8170.github.io/index.html). Public code shows solid CRUD APIs and UX work but limited evidence of advanced system design, formal test coverage, or rigorous server-state/cache strategies.

Phone

Technical skills

Node JS

JavaScript

Node JS

Express

Mongoose

Axios

Bcrypt

Dotenv

Python

Django

Frontend

React.js

Three.JS

React Router

npm

DevOps

Rest API

GitHub

Git

Databases

MySQL

Postman

Projects

Sagara Mitra

May 2025 to Jul 2026 1 Year 2 Months

Developed React.js frontend features for an Online Examination and Proctoring System, including the candidate dashboard, exam interface and system-check modules. Integrated REST APIs with the backend team and coordinated frontend tasks as Team Lead.

Urban sense

Oct 2025 to Dec 2025 2 Months

Timeline

Software Developer Intern (Team Lead) • Lead

PyGeniarc • Full-Time

Feb 2026 to May 2026 3 Months Bengaluru In office

Developed the frontend for an online examination and proctoring system using React. Built key UI modules such as dashboards, exam interfaces, and system-check components. Coordinated with the backend team to integrate REST APIs and align frontend delivery with backend timelines while leading the frontend work stream.

Django

PostgreSQL

React.js

Middle Backend Developer Confidence: Medium API Engineer

Backend API engineer (middle level) with practical Node.js experience and a strength for building role-based REST services and domain-specific business logic. The strongest proven skill is designing and implementing API controllers and a modular AI analysis service as seen in the issue creation, department detection, and aiAnalysisService modules. The codebase lacks production-grade operational features such as structured observability, token lifecycle management, migrations, and load/scale testing evidence.

API Design

4/10

How well APIs are designed

Solid REST API patterns and consistent error responses are present, with role-based route protection, but there is no API versioning, idempotency keys, or advanced pagination strategy.

Evidence

quiz-application/backend/controllers/authController.js: JWT generation (generateToken) and consistent JSON success/error responses

urbansense/backend/controllers/issueController.js: role-based access checks and HTTP status usage in getIssueById/createIssue/updateIssue

quiz-application/frontend/src/App.js: ProtectedRoute usage to enforce route-level authorization

Data Layer & Database

4/10

Working with databases

Uses Mongoose features (populate, countDocuments, aggregates) and handles duplicate-key errors, but there is no migration history, explicit transaction usage, or advanced indexing documented.

Evidence

urbansense/backend/controllers/issueController.js: aggregation pipelines in getIssueStats and use of mongoose.Types.ObjectId

quiz-application/backend/controllers/quizController.js: Quiz.find().populate and Question.countDocuments per quiz (Promise.all pattern)

urbansense/backend/controllers/adminController.js: duplicate key (11000) handling on create/update and department existence checks

Scalability & Performance

3/10

Handling load and speed

Some attention to performance (parallel Promise.all, aggregation queries) exists, but no caching, queueing, connection-tuning, or load-testing artifacts are present.

Evidence

quiz-application/backend/controllers/quizController.js: Promise.all used to compute question counts for quizzes

urbansense/backend/controllers/issueController.js: use of MongoDB aggregation for stats to reduce application-side computation

System Architecture

4/10

Overall system structure

Clear module separation (controllers, services, models) and a dedicated AI analysis service show deliberate boundaries, but the system is a single monolith without multi-service contracts or secret/config management beyond dotenv.

Evidence

urbansense/backend/services/aiAnalysisService.js: separate service module for media analysis

urbansense/backend/controllers/*.js: separation of concerns across adminController, issueController, authController, chatbotController

Security & Auth

4/10

Protecting data and access

Basic authentication and authorization are implemented correctly (bcrypt hashing, JWT, role checks and selective field projection), but token lifecycle (refresh/revocation), rate limiting, and input validation libraries are not present.

Evidence

quiz-application/backend/controllers/authController.js: bcrypt password hashing and jwt token creation with process.env.JWT_SECRET

urbansense/backend/controllers/issueController.js: role-based access checks when returning or modifying issues

urbansense/backend/controllers/adminController.js: selective .select('-password') and duplicate key handling

Reliability & Observability

3/10

Stability and monitoring

Controllers use try/catch and there are console logs and defensive fallbacks in the AI service, but structured logging, correlation ids, timeouts/retries, graceful shutdown and metrics/alerts are not implemented.

Evidence

urbansense/backend/controllers/issueController.js: verbose console.log statements and try/catch around createIssue with error stack output in development

urbansense/backend/services/aiAnalysisService.js: defensive error returns and fallback behavior when analysis fails

Expertise

Node.js• Middle

Backend AI & LLM• Middle

Databases & Vector Storage• Middle

Industries

Education• Middle

Government• Middle

Technologies

Node JS• Middle

Rest API

Express• since 2025

Bcrypt

Django• since 2026

Mongoose

Axios

Dotenv

Stack• mentioned only

Recommendations

Build REST APIs and admin dashboards that enforce role-based access and analytics (API endpoints, aggregation pipelines, admin controllers).
Implement and productionize AI-assisted backend features (refactor aiAnalysisService to call a real ML model, add timeouts and retries, and ensure safe fallbacks).
Harden services for production: add structured logging, correlation ids, metrics, graceful shutdown, and request timeouts with retries where appropriate.
Improve data engineering practices: add a migration history, consider transactions for multi-document updates, and document indexes and query plans for heavy aggregates.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

quiz-application urbansense

Middle Frontend Developer Confidence: Medium App Engineer

UI Component Architecture

3/10

How interface parts are built

Component boundaries are present (React pages, ProtectedRoute) but there is limited evidence of a purpose-built component library, design-system tokens authored by the developer, or advanced composition patterns; most UI work is page-level and handcrafted HTML/CSS with some React pages.

Evidence

quiz-application/frontend/src/App.js: routing + ProtectedRoute pattern showing page/component boundaries

quiz-application/frontend/src/services/api.js: dedicated API service file (service abstraction)

Manoranjan8170.github.io/index.html: CSS variables and repeated UI patterns indicating ad-hoc design system work

Responsive & Cross-browser

4/10

Works on all screens and browsers

Responsive layouts and sensible breakpoints are implemented with CSS media queries and prefers-reduced-motion handling; pages include RTL/locale hooks only implicitly, no multi-lingual assets found.

Evidence

Manoranjan8170.github.io/index.html: responsive @media rules and prefers-reduced-motion block

sagara-mitra/src/main/resources/static/index.html: responsive hero and carousel styles

sagara-mitra/src/main/resources/static/boats.html: layout and modal responsive rules

Performance Optimization

3/10

Speed of the interface

Developer shows practical performance awareness (clamping devicePixelRatio, reduced-motion handling, limiting particle counts) but lacks measured optimization artifacts, CI bundle analysis, or code-splitting evidence.

Evidence

Manoranjan8170.github.io/index.html: three.js renderer.setPixelRatio clamp and prefers-reduced-motion guard

Manoranjan8170.github.io/index.html: particle count and simple background particle updates rather than heavy DOM operations

Accessibility & Semantics

4/10

Usable for everyone

Several accessibility-minded details are present - aria attributes, focus-visible focus rings, aria-live regions and prefers-reduced-motion - showing pragmatic a11y attention, though there is no evidence of automated axe checks or a11y test suites.

Evidence

Manoranjan8170.github.io/index.html: accessible focus-visible styles, aria-labels on navigation and hero elements

sagara-mitra/src/main/resources/static/profile.html: role="main" and aria-live usage

State Management & Data Flow

3/10

Managing data in the app

Standard server-client state patterns are used (JWT auth, APIs, Mongoose models). There is little evidence of advanced client-side server-state discipline (no request cancellation, no optimistic updates or cache-invalidation strategy), but backend demonstrates sensible CRUD and validation patterns.

Evidence

quiz-application/backend/controllers/authController.js: JWT generation, password hashing and auth endpoints

quiz-application/backend/controllers/quizController.js: server-side quiz creation, question seeding and submission handling

quiz-application/frontend/src/App.js: use of ProtectedRoute indicating client-side auth gating

UX & Visual Polish

5/10

Look and feel quality

UX polish is strong for static/marketing pages - typewriter, toast notifications, 3D hero, scroll-reveal and well-crafted modals; production UX features in apps (error states, skeletons, undo) are present but not comprehensive across the codebase.

Evidence

Manoranjan8170.github.io/index.html: typewriter, toast, scroll-reveal, modal and 3D hologram interactions

sagara-mitra/src/main/resources/static/boats.html: booking modal, custom confirmation popup and availability flow

sagara-mitra/src/main/resources/static/login.html: OTP generation UI and user-friendly popups

Expertise

React• Middle

HTML & CSS• Middle

Web Performance & Optimization• Junior

Industries

Education• Middle

Travel & Tourism• Middle

Technologies

JavaScript

Three.JS

Git

React.js• since 2026

npm

React Router

GitHub

Frontend• mentioned only

Recommendations

Develop interactive single-page applications and client-heavy web experiences where polished UI/UX and component-to-page wiring matter (SPA development with React).
Implement end-to-end features for education platforms - quizzes, scoring and user dashboards - leveraging existing quiz controllers and React pages.
Build booking and transactional flows (booking UI, availability checks and payment integration) for travel or ticketing applications where you already have domain code.
Contribute frontend improvements in teams that need strong craftsmanship on animations, accessibility fixes and responsive design rather than low-level infra work.

Repositories

The developer's experience in this domain has been verified based on AI analysis of the following repositories:

Manoranjan8170.github.io quiz-application sagara-mitra