Vishak TV
Software Developer
5+ years exp
Dart
TypeScript
JavaScript
Node JS
Responsive & Cross-browser: 4/10
UX & Visual Polish: 4/10
Active 2 days ago
+91 (6238) 060766
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Frontend UI Engineer (junior-to-middle) focused on building interactive web UIs with React and vanilla DOM code; strongest proven skill is implementing realtime UI flows with Firebase and DOM rendering as shown in chatbaseApp/js/db.js. The most concrete artifact supporting this is chatbaseApp/js/db.js which contains Firebase auth, Firestore snapshot listeners, file upload to storage and dynamic DOM rendering (renderCafe) for messages. There is little evidence of systematic testing, accessibility-first design, request cancellation/race handling, or measured performance work in the public code.
Technical skills
Dart
TypeScript
JavaScript• Middle • 5y+
Node JS• Middle • 4y+
Databases
MongoDB
Frontend
Material UI
Redux
Tailwind CSS
PostCSS
Redux Toolkit
React Router
Chart.js
Angular• 4y+
Next.js• 4y+
React.js• 4y+
DevOps
CI/CD
Rest API
AWS• 4y+
Docker• 4y+
Git• 4y+
Design
Figma• 4y+
Mobile
Firebase
Flutter• 4y+
PWA• 4y+
QA
Postman
Jest• 4y+
Timeline
Software Engineer
•
Middle
Caytm Technologies
•
Full-Time
Developed mobile and web features across the full delivery cycle, from requirements to deployment. Built workflows using Next.js, created a scalable Angular admin interface, and implemented secure REST APIs with Node.js including cashback functionality. Designed and developed a production debugging and internal administration app using Flutter with BLoC and UI design in Figma. Improved performance and accessibility by shipping a PWA and increased reliability via automated testing.
Next.js
Angular
React.js
Node JS
Figma
Flutter
PWA
Jest
AWS
Docker
Git
Middle Frontend Developer
Confidence: Medium UI Engineer
Frontend UI Engineer (junior-to-middle) focused on building interactive web UIs with React and vanilla DOM code; strongest proven skill is implementing realtime UI flows with Firebase and DOM rendering as shown in chatbaseApp/js/db.js. The most concrete artifact supporting this is chatbaseApp/js/db.js which contains Firebase auth, Firestore snapshot listeners, file upload to storage and dynamic DOM rendering (renderCafe) for messages. There is little evidence of systematic testing, accessibility-first design, request cancellation/race handling, or measured performance work in the public code.
UI Component Architecture
3/10
How interface parts are built
Component boundaries exist (React components + vanilla DOM modules) but architecture is mostly view-layer glue without a design-system or advanced composition patterns.
Evidence
food-order-app/src/component/index.js: homepage composed from ./coarousel/Carousel, ./featureSctn/FeatureSection, ./Header/Header, ./NavBar/Navbar
chatbaseApp/js/db.js: renderCafe function and DOM-based render logic for message items
Responsive & Cross-browser
4/10
Works on all screens and browsers
Responsive CSS with media queries and mobile adjustments are present; basic responsive breakpoints and layout tweaks are implemented in handcrafted styles.
Evidence
chatbaseApp/scss/style.scss: multiple @media queries and responsive modal/side-section rules
chatbaseApp/css/style.css: mobile and tablet @media blocks adjusting layout and input/footer positioning
Performance Optimization
2/10
Speed of the interface
Little evidence of deliberate performance engineering beyond using standard build tooling; some large built chunks are present but appear to be compiled output rather than custom optimizations.
Evidence
Admin_Dashboard/static/js/2.40cc3c7c.chunk.js: built webpack chunk (shows code-splitting / bundling artifacts)
food-order-app/package.json: react-scripts build tooling present (standard bundler pipeline)
Accessibility & Semantics
2/10
Usable for everyone
Minimal explicit accessibility work observed; markup is reasonably semantic in places but custom widgets lack ARIA/focus management and there is no sign of axe/CI a11y testing.
Evidence
chatbaseApp/index.html: semantic structure (forms, nav) and viewport meta but no ARIA usage on custom controls
chatbaseApp/js/script.js: interactive controls (modal toggle, user search) manipulated without explicit focus management
State Management & Data Flow
3/10
Managing data in the app
Uses server-state (Firebase) with realtime listeners and a basic Redux store in the React app, but no advanced patterns (request cancellation, optimistic rollback or state machines).
Evidence
chatbaseApp/js/db.js: Firebase auth.onAuthStateChanged, firestore.onSnapshot with docChanges and renderCafe/delete flow
food-order-app/src/store/store.js: imports cartAdder slice and integrates a Redux store (react-redux / @reduxjs/toolkit present)
UX & Visual Polish
4/10
Look and feel quality
Good visual polish and UX touches (modals, spinners, overlays, delete confirmation); flows are implemented with feedback but lack deeper UX features like undo, accessibility-first interactions, or measured perceived-performance.
Evidence
chatbaseApp/css/style.css: delete-message-overlay, input-section and spinner styling; polished card and message styles
chatbaseApp/scss/style.scss: modal animations, responsive adjustments and various UI skeleton/spinner states
Expertise
React• Middle
Frontend Architecture & Build Tools• Junior
Industries
Food & Beverages• Middle
Technologies
JavaScript• Middle • 5y+
TypeScript
Dart
Node JS• Middle • 4y+
Redux
Tailwind CSS
Next.js• 4y+
Chart.js
Figma• 4y+
Angular• 4y+
CI/CD
Git• 4y+
AWS• 4y+
Docker• 4y+
React.js• 4y+
Material UI
PostCSS
Redux Toolkit
React Router
Recommendations
- Harden and migrate the Firebase front-end code: move config out of index.html, add environment handling and server-side rules, and centralize auth/state into a small React module for reuse.
- Improve state discipline and edge states: consolidate server-state flows (onSnapshot) into a predictable pattern or small custom hook with request cancellation, loading/empty/error states and rollback handling.
- Invest in accessible, testable components: add ARIA/focus management for custom widgets, and add automated a11y checks and unit/interaction tests for critical flows (auth, messaging, cart).
- Clean up build artifacts and source control: avoid shipping compiled chunks in source, commit source files only and add a simple CI build step to run linting and tests before deploy.
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 Node.js backend developer focused on building simple REST APIs with Express and MongoDB. The strongest proven skill is implementing user registration with input validation, password hashing and token issuance as shown in src/controllers/userController.ts and src/models/User.ts. There is limited evidence of production practices such as secret management, token lifecycle (expiry/refresh), automated tests, migrations, scalability patterns, or observability instrumentation.
API Design
3/10
How well APIs are designed
Basic REST API design with route versioning and a consistent JSON response contract, but no idempotency, pagination, or advanced versioning strategy.
Data Layer & Database
2/10
Working with databases
Simple Mongoose schema with field validators and unique constraint; no migration history, transactions, or explicit performance tuning.
Evidence
vishakvenu/food-app-backend/src/models/User.ts: Mongoose schema with validators, unique email and password rules
vishakvenu/food-app-backend/src/controllers/userController.ts: uses User.findOne and new User(...).save() patterns
vishakvenu/food-app-backend/src/utils/utils.ts: handleValidationErrors parses mongoose ValidationError
Scalability & Performance
1/10
Handling load and speed
No caching, queuing, connection-pooling or measured performance optimizations are present; single-process Express app only.
System Architecture
2/10
Overall system structure
Basic modular folder structure (routes, controllers, models) indicating separation of concerns, but no multi-service decomposition or config/secret management.
Security & Auth
3/10
Protecting data and access
Some security awareness: password hashing and input validation are implemented, but secrets management and token lifecycle are incomplete and risky.
Evidence
Reliability & Observability
2/10
Stability and monitoring
Basic try/catch error handling and helper functions for validation errors, but limited observability, no structured logging, no retries/backoff or graceful shutdown handling.
Evidence
vishakvenu/food-app-backend/src/controllers/userController.ts: try/catch around registerUser with error branching
vishakvenu/food-app-backend/src/utils/utils.ts: handleValidationErrors and handleErrors functions
vishakvenu/food-app-backend/src/server.ts: connectDB().catch used to log DB connection errors
Expertise
Node.js• Junior
Technologies
MongoDB
Rest API
Recommendations
- Assign to implement and extend CRUD REST endpoints and authentication flows using Express and Mongoose.
- Have the developer improve security by moving secrets to environment configuration, adding JWT expiry/refresh and removing hardcoded secrets.
- Task them with adding automated tests for controllers and model validation and a migration strategy for schema changes.
- Ask them to implement basic observability and reliability features such as structured logging, health checks, and graceful shutdown.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: