Prajwal Bhange
Fullstack
2years in tech
4repositories checked by code analysis
3projects
3roles confirmed by code
Overview
Full stack developer with ~2.5 years of experience building and running production e-commerce platforms, admin dashboards and business websites with React, Next.js, Node.js, NestJS, GraphQL (Hasura), PostgreSQL and MongoDB.
Highlights:
- Cut search load time from 21s to ~2s and category pages from 9.5s to under 0.5s on a 1 lakh+ product catalogue through query optimisation.
- Built secure checkout (HDFC, PayPal, Yes Bank, COD) with server-side price recalculation, plus shipping integrations (Shiprocket, FedEx, UPS).
- Built an internal admin panel with barcode stock scanning, bulk Excel uploads and admin-managed business rules.
- Own features end to end, from data model and APIs to UI and Docker deployment.
- Earlier: React and Three.js UIs for AI chatbot platforms.
Live work: silverandgem.co.in, desmoderm.in. Open to remote and onsite full stack / MERN roles.
Phone
Timeline
Full Stack Developer
·
Middle
Gosbfy
·
Full-Time
Nest.JS
Next.js
React.js
Node JS
Redux
GraphQL
PostgreSQL
Postman
Tailwind CSS
JavaScript
TypeScript
Savitribai Phule Pune University (University of Pune)
Bachelor's Degree ·
Computer Science
React Developer Intern
·
Junior
Easysearch-ai
·
Internship
Built interactive, high-performance React interfaces for chatbot platforms across different business domains. Integrated and tested APIs, and helped automate personalized PDF report generation. Created quiz and interactive modules aimed at improving user engagement.
React.js
Redux
Three.JS
Projects
Built and maintained an end-to-end jewellery e-commerce platform with a storefront, NestJS backend, and a GraphQL data layer. Implemented B2B/B2C functionality including multi-currency pricing, volume discounts, coupons, and a large product catalogue. Optimized search and category performance and integrated shipping and payment fee calculations to keep totals consistent before checkout.
My Own React
Implemented a React-like frontend library featuring a virtual DOM and a diffing/reconciliation approach. Focused on reducing rendering overhead by updating only what changes. Evaluated and reported improved average render performance as part of the project goals.
Delivered an end-to-end clinic website with a structured UI and a production deployment using Docker. Organized treatment content by skin concern, and included doctor profiles, video patient stories, and testimonial sections. Focused on publishing a clear information architecture and maintaining a responsive frontend experience.
Technical skills
Languages
6
JavaScript
TypeScript
Node JS
C++
SQL
C
Node JS
6
Nest.JS
Bcrypt
BullMQ
Express
Axios
Ioredis
Frontend
8
React.js
Three.JS
Next.js
Redux
Apollo Client
Vite
Tailwind CSS
Jotai
Other
14
PostgreSQL
Vitest
GitHub
Rest API
Docker
Git
ESLint
Prettier
Swagger
Webpack
PostCSS
GraphQL
QA
DNS
Junior Backend Developer
Confidence: Medium API Engineer
Backend API engineer (Middle) focused on building queue-driven Node.js services for document ingestion and small public APIs; the strongest proven skill is designing queue-based processing pipelines and worker handlers using NestJS and BullMQ as shown in worker/src/resume.processor.ts and api/src/resumes/resumes.service.ts; the public codebase lacks evidence of advanced schema migration history, transaction/isolation design, or production-grade observability and tracing pipelines.
API Design
5/10
How well APIs are designed
API design shows sensible validation, Swagger docs, API-key guard and rate limiting but lacks formal versioning/idempotency headers or a documented error contract across services.
Evidence
textkit-api/src/main.ts: ValidationPipe + SwaggerModule setup and API key scheme
textkit-api/src/text/text.controller.ts: small, well-formed endpoints (slugify, word-count, reading-time) with DTO usage
textkit-api/src/app.module.ts: ThrottlerModule + APP_GUARD registration (rate limiting)
Data Layer & Database
3/10
Working with databases
Uses Prisma client for straightforward CRUD; no visible migration history or explicit transaction/isolation-level handling in human-authored code.
Evidence
api/src/resumes/resumes.service.ts: prisma.resume.create/findMany/findUnique/update usage
worker/src/resume.processor.ts: prisma.resume.update calls in processing and failure handlers
Scalability & Performance
4/10
Handling load and speed
Good use of queue-based decoupling and concurrency controls; lacks explicit caching, measured tuning, or advanced connection-pool tuning in application code.
Evidence
api/src/resumes/resumes.service.ts: queue.add('process-resume', ..., { jobId: resume.id }) to decouple ingestion
worker/src/resume.processor.ts: @Processor('resume-processing', { concurrency: 2 }) controlling parallelism
System Architecture
4/10
Overall system structure
Reasonable module decomposition (api worker separation, PdfParser, status publisher) and monorepo layout; overall architecture is conventional rather than novel.
Evidence
package.json (root): workspace layout (api, worker, web)
worker/src/resume.processor.ts & api/src/resumes/resumes.service.ts: clear separation between enqueueing and worker processing
worker/src/pdf/pdf-parser.service.ts (service boundary implied) and worker/src/events/status-publisher.service.ts usage
Security & Auth
5/10
Protecting data and access
Shows practical boundary security: API-key guard, input validation, rate limiting, and file-type check on upload; however token lifecycle, refresh/revocation, and secrets management are not shown.
Evidence
textkit-api/src/text/text.controller.ts: ApiSecurity('api-key') + ApiKeyGuard usage
textkit-api/src/main.ts: ValidationPipe used globally for input validation
api/src/resumes/resumes.service.ts: file buffer magic-bytes check to validate PDF uploads
Reliability & Observability
5/10
Stability and monitoring
Reliability patterns present: worker retry/failure handlers, logging, and status publishing; missing are broad observability integrations, distributed tracing or explicit backoff/jitter configuration.
Evidence
worker/src/resume.processor.ts: logger usage, OnWorkerEvent('failed') handles retry vs final failure and updates DB status
api/src/resumes/resumes.service.ts: removes existing dead job before re-adding to ensure idempotent retry behavior
textkit-api/test/app.e2e-spec.ts and app.controller.spec.ts: presence of tests and e2e scaffolding
Expertise
Microservices & API Architecture· Junior
Node.js· Junior
Messaging & Real-time· Junior
Industries
Education· Junior
Technologies
Node JS· Junior
Rest API
Nest.JS
GraphQL
Express
Bcrypt
Axios
BullMQ
Ioredis
Recommendations
- Develop production-grade ingestion pipelines that add exponential backoff + jitter and explicit retry policies in the worker (make backoff parameters configurable and instrumented).
- Add a concise migration history and transactional tests for critical DB flows using Prisma migrations and explicit transaction options to demonstrate schema evolution and isolation choices.
- Improve observability: add structured request/job correlation ids, metrics (Prometheus), and distributed tracing hooks so worker and API traces can be correlated for incidents.
- Harden auth and secrets: add token lifecycle (refresh/revoke) for API keys and integrate secrets into a secrets manager rather than environment files for production deployments.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Frontend Developer
Confidence: Medium Fullstack
Fullstack engineer (Middle) specializing in building Node/NestJS APIs and background job pipelines for document processing. The strongest proven skill is backend dataflow and reliable job orchestration demonstrated by api/src/resumes/resumes.service.ts and worker/src/resume.processor.ts. There is little evidence of advanced frontend architecture, measured web performance work, or comprehensive accessibility engineering in authored code.
UI Component Architecture
2/10
How interface parts are built
Basic component and shared-UI packaging exists but there is no evidence of a custom design system, advanced composition patterns, or non-trivial component lifecycle logic authored by the developer.
Evidence
paytm/packages/ui/package.json
01-Prajwal/paytm/apps/merchant-app/app/page.module.css
Responsive & Cross-browser
4/10
Works on all screens and browsers
Responsive layout techniques and media queries are applied in authored CSS with attention to reduced-motion and hover/pointer capability, showing awareness of cross-device UX.
Performance Optimization
2/10
Speed of the interface
Limited frontend-focused performance work; some backend-side performance/concurrency considerations are evident (queue concurrency and narrow selects) but no measured frontend optimizations, bundle reports, or virtualization patterns are present.
Evidence
01-Prajwal/ resume-pipeline/worker/src/resume.processor.ts - @Processor('resume-processing', { concurrency: 2 })
01-Prajwal/resume-pipeline/api/src/resumes/resumes.service.ts - findAll() uses select to limit returned fields
Accessibility & Semantics
1/10
Usable for everyone
Minimal accessibility-specific engineering authored; there is a prefers-reduced-motion media query but no ARIA, focus management, or accessibility testing artifacts authored by the developer.
State Management & Data Flow
4/10
Managing data in the app
Clear server-state and async discipline on the backend: job queue usage, retry/idempotency handling, status publishing, and guarded create/update flows; frontend state management evidence is minimal.
UX & Visual Polish
3/10
Look and feel quality
Visual polish and UX attention are present in authored CSS with responsive and reduced-motion rules, but there is little evidence of complete UX flows (skeletons, loading/error/undo) or measured perceived performance improvements.
Expertise
React· Junior
Frontend Architecture & Build Tools· Junior
Technologies
JavaScript· since 2024 · Junior
Redux· since 2024
Webpack
Tailwind CSS
Next.js· since 2025
Three.JS· since 2024
Git
Docker
React.js· since 2024
Vite· since 2025
Apollo Client· since 2025
PostCSS
ESLint
Prettier
Jotai
GitHub
DNS
Recommendations
- Build and maintain backend-first fullstack features: APIs, worker pipelines, and background job orchestration using NestJS, BullMQ, and Prisma-style clients.
- Develop document ingestion and processing pipelines, including PDF parsing, retry logic, status events, and durable storage.
- Implement small-to-medium Next.js frontends that pair with the existing APIs and add explicit loading/error/undo UX and accessibility improvements.
- Own monorepo build and CI tasks, leveraging Turborepo/Next.js workspaces and lint/test automation.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior QA Engineer
Confidence: Medium API QA Engineer
Backend developer (Senior, tier_score 5.0) focused on building reliable API and background-processing pipelines with job queues and database integration. The strongest proven skill is designing resilient queue-based resume processing and retry/failure handling as shown in api/src/resumes/resumes.service.ts and worker/src/resume.processor.ts. There is limited public evidence of advanced QA infrastructure such as contract testing, property-based tests, CI test engineering, or performance/load testing.
Test Automation Frameworks
3/10
Building automated tests
Basic test framework setup is present (Vitest, supertest e2e), but lacks advanced fixtures, factories, isolated mock servers, or parallelization/sharding config.
Evidence
resume-pipeline/api/vitest.config.ts
textkit-api/test/app.e2e-spec.ts
resume-pipeline/api/package.json:test and test:e2e scripts
Test Coverage & Strategy
2/10
What and how to test
Some unit and e2e tests exist (happy-paths), but there is little evidence of risk-based tagging, explicit negative-path/property-based tests, or mutation/fuzz coverage.
Evidence
textkit-api/src/app.controller.spec.ts
textkit-api/test/app.e2e-spec.ts
API & Integration Testing
3/10
Testing how parts work together
API integration testing is exercised via Supertest e2e tests and Vitest configuration, but there is no contract testing or schema-validation tooling (pact/schemathesis) visible.
Evidence
textkit-api/test/app.e2e-spec.ts
resume-pipeline/api/vitest.config.ts
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
Finding and describing bugs
Not evidenced in public code
CI Test Integration
2/10
Running tests automatically
Local test scripts and test configs exist, but there is no CI workflow, selective test-on-diff logic, or quarantine mechanics for flaky tests visible.
Evidence
resume-pipeline/api/package.json (test/test:e2e scripts)
resume-pipeline/api/vitest.config.ts
Expertise
API Testing & Contract Validation· Junior
Unit & Component Testing· Junior
Technologies
QA
TypeScript· Junior
Swagger
Vitest
Recommendations
- Build and harden backend services that require job queues, retry semantics, and durable processing (BullMQ/ioredis + Prisma stacks).
- Author API integration and contract tests (schemathesis or Pact) and expand the existing e2e suite into negative-path and boundary tests.
- Implement CI test pipelines with selective runs, per-test retry policies, and artifact collection (traces/screenshots/log bundles).
- Develop monitoring and SLO-driven load tests (k6 or Gatling) for the worker throughput and queue backpressure scenarios.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Job preferences
- Work permits
- India
- Citizenship
- India
- Employment type
- Full-Time
- Company size
- 51-200
Open to AI agents: they read this profile and start a dialog through Alion
alion.io/@sunny-bhange/mcpAlion · People, companies and AI agents in one graphalion.io/@sunny-bhange