Mohit Purohit
Frontend Developer
5+ years exp
4+ years ML exp
Node JS
SQL
Go
JavaScript
TypeScript
Active 9 days ago
+91 (6375) 202913 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Middle-level frontend app engineer specializing in building React single-page applications with conventional routing and global state management. This strength is proven by a Redux/MobX/Vite-based food-ordering app wiring Provider and Router and by the semcart project configuration (examples: hungerFeast/app.js and semcart/vite.config.ts). There is limited evidence of production-grade performance measurement, advanced accessibility beyond role-based tests, or sophisticated server-state flows and security hardening in the public code.
Technical skills
Node JS• Middle
SQL
Go• Junior
JavaScript• Junior • 5y+
TypeScript• Senior • 4y+
Node JS
Express
Go
Gorilla
Databases
Apache Kafka
PostgreSQL
RabbitMQ
Redis
Frontend
ESLint
Next.js
Prettier
Redux Toolkit
Storybook
React Router
Tailwind CSS
Vite
Socket.IO
GraphQL• 4y+
Lighthouse• 4y+
React Query• 4y+
React.js• 4y+
Redux• 4y+
DevOps
Amazon EC2
AWS
Blue-Green Deployment
CI/CD
Docker
Git
Kubernetes
SLI/SLO/SLA
Terraform
WebSockets
Rest API
GitHub Actions• 4y+
QA
Playwright
Sentry
Vitest
Cypress• 4y+
Jest• 4y+
AI/ML
LLM
Copilot• 4y+
Claude• 3y+
Cursor• 3y+
Mobile
PWA
State Management
Timeline
Senior Frontend Engineer
•
Senior
Tata Consultancy Services
•
Full-Time
Designed and led a React-based feature frontend monorepo using micro-frontend patterns, reducing duplication and enabling independent squad releases. Improved UI performance by profiling and removing redundant renders, and implemented resilient UI error handling with retries and graceful fallbacks. Integrated REST and GraphQL APIs with safer rollout approaches, set up CI/CD with Lighthouse checks and canary deployments, and used AI coding assistants to accelerate verified refactors and testing.
React.js
TypeScript
Redux
React Query
GraphQL
GitHub Actions
Jest
Cypress
Lighthouse
Claude
Copilot
Cursor
University of Rajasthan
Bachelor's Degree •
Computer Applications
Middle Frontend Developer
Confidence: Medium App Engineer
Middle-level frontend app engineer specializing in building React single-page applications with conventional routing and global state management. This strength is proven by a Redux/MobX/Vite-based food-ordering app wiring Provider and Router and by the semcart project configuration (examples: hungerFeast/app.js and semcart/vite.config.ts). There is limited evidence of production-grade performance measurement, advanced accessibility beyond role-based tests, or sophisticated server-state flows and security hardening in the public code.
UI Component Architecture
3/10
How interface parts are built
Basic component composition and routing with conventional React components and Provider usage; no evidence of a custom design system or advanced component APIs.
Evidence
hungerFeast/app.js: AppLayout component composing Header, Outlet and Footer with Provider
hungerFeast/src/pages/ContactUs.js: self-contained form component with local markup and Tailwind classes
hungerFeast/__test__/Header.test.js: unit tests targeting Header component behaviors
Responsive & Cross-browser
3/10
Works on all screens and browsers
Uses Tailwind with a custom tailwind.config and responsive classes in components; basic viewport and responsive patterns are present but no advanced fluid type or container queries.
Evidence
hungerFeast/tailwind.config.js: custom screens and spacing configuration
hungerFeast/src/pages/ContactUs.js: Tailwind utility classes for responsive layout
semcart/index.html: meta viewport present
Performance Optimization
2/10
Speed of the interface
Some awareness of code-splitting and lazy loading via React.lazy and Suspense and custom Vite config, but no measurement artifacts or advanced bundle/perf work.
Evidence
hungerFeast/app.js: lazy(()=>import("./src/pages/About")) with Suspense fallback
semcart/vite.config.ts: custom Vite plugin usage (tailwindcss, babel)
Learning-chat-app/frontend/vite.config.ts: custom plugin configuration
Accessibility & Semantics
3/10
Usable for everyone
Practical semantic markup and basic a11y testing patterns (getByRole); labels are linked to inputs, but no advanced ARIA or focus-management for custom widgets.
Evidence
hungerFeast/src/pages/ContactUs.js: label and input associations and required attributes
hungerFeast/__test__/Contact.test.js: tests using getByRole and getAllByRole to assert inputs and heading
hungerFeast/__test__/Header.test.js: getByRole assertions for buttons
State Management & Data Flow
3/10
Managing data in the app
Uses global state libraries (Redux/Redux Toolkit and mentions of MobX/React Query) and wires Provider into the app, but no advanced server-state handling, optimistic updates, or cancellation patterns shown.
Evidence
hungerFeast/app.js: Provider wrapping AppLayout with appStore
hungerFeast/package.json: dependency on @reduxjs/toolkit and react-redux
semcart/package.json: includes @tanstack/react-query and mobx (indicates awareness of different state approaches)
UX & Visual Polish
2/10
Look and feel quality
Basic visual polish and user-facing flows (styled forms, loading fallback in Suspense) but no skeleton screens, undo patterns, or documented perceived-performance improvements.
Evidence
hungerFeast/src/pages/ContactUs.js: styled form with focus states
hungerFeast/app.js: Suspense fallback for lazy-loaded About
semcart/src/App.css and src/index.css: Tailwind imports showing styling approach
Expertise
React• Middle
Frontend Architecture & Build Tools• Middle
Industries
Commerce• Middle
Food & Beverages• Middle
Internet Services• Middle
Technologies
TypeScript• Senior • 4y+
Node JS• Middle
Terraform
Redux• 4y+
GraphQL• 4y+
Tailwind CSS
Next.js
Express
Socket.IO
GitHub Actions• 4y+
WebSockets
CI/CD
Git
AWS
Docker
Kubernetes
React.js• 4y+
Vite
React Query• 4y+
Storybook
ESLint
Prettier
Blue-Green Deployment
Amazon EC2
SLI/SLO/SLA
Redux Toolkit
React Router
Lighthouse• 4y+
Recommendations
- Develop feature-complete consumer SPAs (catalog, cart, checkout) using the existing React + Redux/Vite skillset and add server-state via React Query with cancellation/optimistic-update patterns.
- Expand test coverage and CI by adding unit and integration tests for critical flows and add lint/a11y checks to CI to raise overall QA standards.
- Focus on measured performance work: add bundle analysis, LCP/INP measurements, code-splitting budgets and skeleton screens to improve perceived performance.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Backend Developer
Confidence: Medium API Engineer
Junior backend engineer specializing in simple Go REST APIs and learning-focused Go projects. The strongest proven skill is implementing HTTP handlers and basic routing in Go as shown by movies-crud/main.go. There is no evidence of production-grade data persistence, migrations, authentication, scaling strategies, or observability in the public code.
API Design
2/10
How well APIs are designed
Basic REST routing and handler structure is present but lacks versioning, idempotency, pagination, consistent error contract, or documented API contracts. The design is functional for learning/demo use but not production-ready.
Evidence
movies-crud/main.go: router.HandleFunc("/movies", getMovies).Methods("GET") and other route handlers
movies-crud/main.go: createMovie/updateMovie/getMovie handlers implementing basic CRUD over HTTP
Data Layer & Database
1/10
Working with databases
No persistent data layer or migrations; data is an in-memory slice with no transaction boundaries, constraints, or tuned queries. This demonstrates only transient state suitable for demos or learning.
Evidence
movies-crud/main.go: var movies []Movie and append-based in-memory storage
Scalability & Performance
1/10
Handling load and speed
No caching, queueing, connection pooling, or documented scalability strategies. The code is single-process and unsharded without capacity planning or performance measurements.
Evidence
movies-crud/main.go: in-memory slice usage with no caching or pooling
web-server/main.go: simple http.FileServer without scaling-related configuration
System Architecture
1/10
Overall system structure
Small, monolithic examples with minimal module boundaries and no service decomposition, graceful degradation, or config/secret management. Architecture appears educational rather than production-engineered.
Evidence
movies-crud/main.go: all handlers and models defined in a single file
web-server/main.go: single-file HTTP server and route handling
Security & Auth
1/10
Protecting data and access
Almost no security controls are present: no auth/authz, no input validation beyond naive decoding, and no secrets handling. There is minimal defensive coding for HTTP method/path errors.
Evidence
web-server/main.go: method and path checks returning http.Error for unsupported requests
movies-crud/main.go: json.Decoder used without input validation or schema checks
Reliability & Observability
1/10
Stability and monitoring
Minimal observability and reliability patterns: basic log.Fatal usage, no structured logging, no timeouts, retries, or graceful shutdown handling. Test coverage exists for frontend components but not for backend handlers.
Evidence
movies-crud/main.go: log.Fatal(http.ListenAndServe(...)) and fmt.Printf for startup logging
hungerFeast/__test__/Header.test.js: frontend unit tests showing testing practice (not backend)
Expertise
Go Development• Junior
Node.js• Junior
Technologies
Go• Junior
Rest API
Gorilla
Recommendations
- Build a small production-style REST service that includes a real database, migrations, and schema evolution (e.g., Go + PostgreSQL + migration tool) to demonstrate transactional boundaries and data integrity.
- Add input validation, authentication/authorization, and secure secrets handling to show security at service boundaries.
- Introduce observability and reliability: structured logging with request correlation ids, timeouts, graceful shutdown, and basic health/readiness endpoints.
- Add backend unit and integration tests plus a simple CI pipeline to demonstrate test-driven hardening and deployment practices.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior QA Engineer
Confidence: Medium Automation Engineer
Frontend React developer (junior) focused on building component-driven web apps with an emphasis on component testing. The strongest proven skill is component-level automated testing using React Testing Library as shown in hungerFeast/__test__/Header.test.js and hungerFeast/__test__/Contact.test.js. There is limited evidence of CI integration, E2E Cypress specs, contract testing, or performance/load testing in public code.
Test Automation Frameworks
2/10
Building automated tests
Basic component-level automated tests using React Testing Library and test runners are present, but there is no evidence of test fixtures, data factories, mock servers with logic, parallelization, or a deliberate selector strategy beyond basic getByRole/getByText.
Evidence
hungerFeast/__test__/Header.test.js
hungerFeast/__test__/Contact.test.js
UserMangement/vitest.config.ts
Test Coverage & Strategy
2/10
What and how to test
Test suite is focused on happy-path UI assertions; coverage collection is enabled but there is little evidence of risk-based test stratification, negative-paths, boundary tests, or property-based invariants.
Evidence
hungerFeast/__test__/Contact.test.js
hungerFeast/__test__/Header.test.js
hungerFeast/jest.config.js (collectCoverage: true)
API & Integration Testing
1/10
Testing how parts work together
Light integration hints exist (dev proxy and axios dependency) but there are no contract tests, schema validation, idempotency checks, or containerized integration test setups.
Evidence
UserMangement/vite.config.ts (proxy -> reqres.in)
UserMangement/package.json (axios dependency)
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
Running tests automatically
Not evidenced in public code
Expertise
Unit & Component Testing• Junior
Industries
Commerce• Middle
Food & Beverages• Junior
Technologies
JavaScript• Junior • 5y+
Cypress• 4y+
Playwright
Jest• 4y+
Sentry
Vitest
Recommendations
- Expand test coverage with negative-path and boundary tests and assert exact failure states and status codes where applicable.
- Add end-to-end Cypress suites and integrate them into a CI pipeline to capture regression risk across the full stack.
- Introduce test fixtures/data factories and simple mock server or contract tests (e.g., schemathesis or Pact) for API-backed features.
- Add CI configuration with per-job test artifacts and a reasoned retry/quarantine policy for flaky tests.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: