Spoorthi Shetty
Software Developer
JavaScript
Node JS
TypeScript
C++
Python
C
Responsive & Cross-browser: 5/10
UI Component Architecture: 4/10
State Management & Data Flow: 4/10
Active 9 days ago
Download CVCV
Overview
Technical skills
Projects
Timeline
Roles
Overview
Frontend app engineer (approx. middle level) focused on React-based single-page applications and site frontends with a strength in building booking and admin flows; the strongest proven skill is building SPA features and flows using React + Redux with concrete implementations in the ticket-booking pages (Shows, TheatersList, BookShow) that include API integration, form flows, modals and payment token handling; there is limited evidence of automated tests, advanced performance engineering, accessibility depth or large-scale architecture decisions in publicly visible code.
Phone
Technical skills
Languages
6
JavaScript
Node JS
TypeScript
C++
Python
C
Node JS
4
Axios
Express
Mongoose
Bcrypt
Frontend
8
Angular
RxJS
Next.js
React.js
Redux
Redux Toolkit
Ant Design
React Router
Other
9
Claude
Bootstrap
GitHub
Rest API
Git
Postman
Dotenv
Copilot
State Management
Projects
Developed a movie ticket booking app with backend REST APIs for movies, shows, seat availability, and bookings using JWT-based authentication. Implemented API endpoints and designed the data flow to support client-side consumption. Built the client-side integration to consume the developed APIs for booking-related user actions.
Timeline
Software Engineer
·
Middle
Saranyu Technologies
·
Full-Time
Worked on production OTT and CMS web applications supporting high monthly active user traffic. Built and optimized Angular feature loading using lazy loading and route-level performance techniques. Implemented resilient REST API error handling using RxJS, providing graceful fallbacks and preventing user-flow interruptions. Mentored junior engineers from project setup through delivery and contributed to subscription/entitlement-related logic and UI component development.
Angular
RxJS
Next.js
Trainee Software Engineer
·
Junior
Saranyu Technologies
·
Full-Time
Software Engineering Intern
·
Junior
Saranyu Technologies
·
Internship
Middle Frontend Developer
Confidence: Medium App Engineer
Frontend app engineer (approx. middle level) focused on React-based single-page applications and site frontends with a strength in building booking and admin flows; the strongest proven skill is building SPA features and flows using React + Redux with concrete implementations in the ticket-booking pages (Shows, TheatersList, BookShow) that include API integration, form flows, modals and payment token handling; there is limited evidence of automated tests, advanced performance engineering, accessibility depth or large-scale architecture decisions in publicly visible code.
UI Component Architecture
4/10
How interface parts are built
Component-based React organization with small reusable components but no in-house design system or advanced composition patterns.
Evidence
Movie-Ticket-Booking-frontend/src/components/Button.js
Movie-Ticket-Booking-frontend/src/components/ProtectedRoute.js
Movie-Ticket-Booking-frontend/src/components/PageTitle.js
Responsive & Cross-browser
5/10
Works on all screens and browsers
Responsive CSS and media-query based breakpoints present in the static site; layout adjusts across a range of sizes but no explicit RTL/i18n or feature-detection logic.
Evidence
Leaf-Now-build-0.0.1/assets/css/styles.css
Leaf-Now-build-0.0.1/index.html
Performance Optimization
2/10
Speed of the interface
Little evidence of measured performance work or advanced optimizations; standard SPA patterns without code-splitting or virtualization for large lists.
Evidence
Movie-Ticket-Booking-frontend/src/pages/Theater/TheatersList.js
Movie-Ticket-Booking-frontend/src/pages/TheatersShow/index.js
Accessibility & Semantics
2/10
Usable for everyone
Basic semantic HTML and form labels exist, but no ARIA on custom widgets, no focus management on custom controls, and no a11y tooling visible.
Evidence
Leaf-Now-build-0.0.1/index.html
Leaf-Now-build-0.0.1/donate.html
State Management & Data Flow
4/10
Managing data in the app
Server-state calls are centralized via apicalls and Redux is used for global state with loading indicators and try/catch error flows; no advanced cache invalidation, request cancellation or optimistic rollback patterns observed.
Evidence
Movie-Ticket-Booking-frontend/src/redux/store.js
Movie-Ticket-Booking-frontend/src/pages/Theater/Shows/index.js
Movie-Ticket-Booking-frontend/src/pages/BookShow/index.js
UX & Visual Polish
4/10
Look and feel quality
Good surface-level UX: seat-selection UI, modal flows, success/error toasts and static-site polish; lacks skeletons, measured perceived-performance improvements, or undo patterns.
Evidence
Movie-Ticket-Booking-frontend/src/pages/BookShow/index.js
Leaf-Now-build-0.0.1/assets/css/styles.css
Leaf-Now-build-0.0.1/donate.html
Expertise
React· Middle
HTML & CSS· Middle
Industries
Commerce· Middle
Media & Entertainment· Middle
Technologies
JavaScript· since 2023 · Middle
TypeScript
Redux
Next.js· since 2025
RxJS· since 2025
Angular· since 2025
Bootstrap
Git
React.js
Axios
Ant Design
Redux Toolkit
React Router
GitHub
Recommendations
- Build and iterate single-page applications that require form-heavy workflows, admin dashboards and CRUD flows (booking, theater/movie management).
- Implement front-end features that integrate with REST APIs and third-party payments (payment token handling and booking flows).
- Develop user-facing admin tools and modal-driven management UIs using Ant Design and Redux.
- Polish component boundaries and add CI-driven a11y checks, automated tests and measured performance improvements as part of feature work.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Backend Developer
Confidence: High API Engineer
A backend API engineer (roughly middle level) focused on Node.js/Express services with a practical strength in implementing end-to-end REST features such as user auth and booking/payment flows. The strongest proven skill is building REST endpoints with MongoDB models and auth/payment integration, evidenced by usersRoute.js (bcrypt + JWT) and bookingsRoute.js (Stripe integration and nested Mongoose populate). Public code lacks input validation, transactional seat-booking safeguards, tests, structured logging, and production readiness features like pagination, versioning, or metrics.
API Design
3/10
How well APIs are designed
Basic REST endpoints and auth flows are implemented but there is no versioning, no idempotency handling, no consistent error status codes, and no pagination/filtering patterns; API design is functional but minimal and lacks production-grade contracts.
Evidence
server/routes/usersRoute.js: POST /register and POST /login endpoints with simple success/failed response objects
server/routes/bookingsRoute.js: POST /book-show and GET /get-bookings endpoints with nested Mongoose population but no versioning or pagination
Data Layer & Database
3/10
Working with databases
Uses Mongoose schemas and nested populate calls showing knowledge of relationships, but there is no migration history, no transaction boundaries around multi-step updates, and updates (seat booking) are non-atomic.
Evidence
server/models/showModel.js: showSchema defines refs to movies and theaters and bookedSeats array
server/routes/bookingsRoute.js: GET /get-bookings uses .populate with nested populate('movie') and populate('theater')
server/routes/bookingsRoute.js: POST /book-show reads show then calls findByIdAndUpdate to append seats without transactional safeguards
Scalability & Performance
2/10
Handling load and speed
No caching, no queueing, and no explicit connection/configuration for pooling or rate limiting; some operations (seat updates) are written in a way that will not scale without concurrency controls.
Evidence
server/routes/bookingsRoute.js: POST /book-show appends to bookedSeats by reading show and then updating, exposing a race condition under concurrent bookings
server/routes/bookingsRoute.js: payment flow (stripe) executed inline with no async job/queue decoupling
System Architecture
3/10
Overall system structure
Monolithic Express + Mongoose structure with clear separation of routes and models demonstrates basic modularization, but there is no evidence of considered service decomposition, config/secret management beyond dotenv, or graceful degradation strategies.
Evidence
server/routes/usersRoute.js: router used to separate user-related endpoints
server/models/showModel.js: models folder with Mongoose schemas indicating conventional module boundaries
Security & Auth
4/10
Protecting data and access
Shows basic security awareness: bcrypt for password hashing and JWT for authentication using an environment secret, but lacks input validation, explicit auth error codes, token lifecycle management (refresh/revoke) and has potential information leakage in error messages.
Evidence
server/routes/usersRoute.js: password hashing via bcrypt.genSalt and bcrypt.hash in POST /register
server/routes/usersRoute.js: jwt.sign({ userId: user._id }, process.env.jwt_secret, { expiresIn: '7d' }) in POST /login
Reliability & Observability
2/10
Stability and monitoring
Basic try/catch error handling is present, but there is no structured logging, correlation ids, timeouts, retries/backoff, circuit breakers, or health/metrics instrumentation to indicate production-grade reliability and observability.
Evidence
server/routes/usersRoute.js: try/catch blocks returning generic responses without structured logging
server/routes/bookingsRoute.js: try/catch in payment and booking flows but no retries, timeouts, or metrics
Expertise
Node.js· Junior
Microservices & API Architecture· Junior
Industries
Media & Entertainment· Middle
Events & Ticketing· Junior
Technologies
Node JS· Middle
Rest API
Express
Bcrypt
Mongoose
Dotenv
Recommendations
- Develop small to medium REST APIs in Node.js/Express that require user auth and payment integration, such as ticketing or e-commerce microsites.
- Work on improving data integrity for concurrent flows by implementing transactions or optimistic locking for seat booking and adding input validation schemas (e.g., Joi) and tests.
- Harden production readiness by adding structured logging, request timeouts, retries where appropriate, and simple observability (health checks and basic metrics).
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: