Simran Chaurasia
Frontend Developer
5+ years exp
JavaScript
TypeScript
Node JS
Invite to interview
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Frontend React engineer at a middle level specializing in client-side state and UX for SPA-style product and test-management experiences. The strongest proven skill is application state and async data handling as shown by simransia/test-management/src/stores/test-store.ts and simransia/e-commerce/src/hooks/useProductDetail.ts. There is little public evidence of automated tests, formal accessibility audits, measured performance reports or backend/SSR work.
Phone
Technical skills
Languages
3
JavaScript
TypeScript
Node JS
Frontend
11
React.js
Tailwind CSS
Zustand
Next.js
GraphQL
Storybook
shadcn/ui
Recharts
Sass
Zod
React Router
Other
31
React Native
Playwright
Expo
Axios
WebSockets
Express
React Hook Form
Firebase
D3.js
Material UI
Three.JS
Radix UI
Jest
Rest API
Cloudflare
styled-components
React Three Fiber
Vite
Figma
drei
Sentry
CI/CD
Git
Docker
Claude Code
Cursor
PostCSS
Lighthouse
State Management
Zeplin
Sketch
Timeline
Frontend Engineer
•
Middle
GoQuant
•
Full-Time
Built real-time trading user interfaces that consume live market data and render low-latency visualizations across multiple venues. Owned key frontend modules including orderbook, swap trading, analytics dashboards, wallet integrations, and order execution flows. Added automated cross-browser regression testing with Playwright and improved accessibility using semantic HTML and keyboard-friendly navigation. Implemented live data pipelines and synced spreadsheet-style views for market updates.
Next.js
TypeScript
Tailwind CSS
Playwright
React.js
shadcn/ui
WebSockets
Recharts
Zustand
Frontend Engineer
•
Middle
Articuno Coding LLP
•
Full-Time
Developed high-performance web applications using Next.js, React, TypeScript, Tailwind CSS, and GraphQL for multiple clients. Created mobile-first experiences with React Native (Expo) and optimized frontend workflows using Storybook and TDD practices. Improved accessibility and Core Web Vitals by addressing Lighthouse findings, including LCP reduction and layout stability enhancements, with monitoring via Sentry. Strengthened UI security by validating inputs and securely handling authentication tokens.
Next.js
React.js
TypeScript
Tailwind CSS
React Native
GraphQL
Storybook
Zustand
Playwright
Expo
Web Development Intern
•
Junior
Full Creative
•
Internship
Converted design assets into responsive, pixel-accurate UI using HTML and CSS tooling. Implemented JavaScript and CSS animations to improve engagement and visual polish. Delivered frontend pages based on provided mockups and ensured layout consistency across supported viewports.
Chhatrapati Shahu Ji Maharaj University (Kanpur University)
Bachelor's Degree •
Physics
Indira Gandhi National Open University
Non-Degree Program •
Computer Science
Middle Backend Developer
Confidence: Medium Generalist
A middle-level front-end generalist specializing in typed React applications and client-side data handling. The strongest proven skill is building resilient client API integrations and state management, exemplified by fetch wrappers and AbortController usage in simransia/e-commerce/src/services/api.ts and the hook logic in simransia/e-commerce/src/hooks/useProductDetail.ts. There is little to no evidence of server-side development, database schema evolution, production observability, or backend security and auth lifecycle handling.
API Design
3/10
How well APIs are designed
Client-side API surface is consistently typed and wrapped, with basic error handling but no evidence of API versioning, pagination conventions, idempotency keys, or a formal error contract beyond ApiResponse shapes.
Data Layer & Database
1/10
Working with databases
No server-side data layer or migration history is present; only client-side TypeScript interfaces model API payloads and no transaction or DB concerns are implemented.
Scalability & Performance
2/10
Handling load and speed
Some attention to performance and network resilience on the client is visible, such as AbortController usage and image proxying, but there is no evidence of caching strategies, queueing, load testing, or server-side optimizations.
System Architecture
3/10
Overall system structure
Code is modular with clear boundaries between hooks, stores, services, and API layers, showing deliberate frontend architecture; however the scope is single-process frontend apps without multi-service decomposition or runtime resilience patterns across services.
Security & Auth
2/10
Protecting data and access
Minimal security-specific controls are visible; basic error checks and input sanitation assumptions exist but there is no explicit auth lifecycle, token handling, or defensive input validation at API boundaries in the provided human-authored files.
Reliability & Observability
3/10
Stability and monitoring
Reliable client behavior is reasonably handled with try/catch, AbortController, and explicit loading/error state patterns; there is no structured logging, metrics, retry-with-backoff, or circuit breaker logic shown.
Technologies
Node JS• Middle
Rest API
Axios
Recommendations
- Build robust API client libraries and SDKs that include retry/backoff, idempotency, and clear error contracts to bridge front-end and back-end concerns.
- Implement end-to-end integration with a simple backend service (Node or other) to gain experience with migrations, transactions, and token-based auth flows.
- Add structured logging and lightweight observability (correlation ids, metrics) to critical flows such as product fetch and bulk question uploads.
- Work on backend features for e-commerce like inventory reservation or idempotent order creation to learn concurrency and consistency patterns.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle Frontend Developer
Confidence: Medium App Engineer
Frontend React engineer at a middle level specializing in client-side state and UX for SPA-style product and test-management experiences. The strongest proven skill is application state and async data handling as shown by simransia/test-management/src/stores/test-store.ts and simransia/e-commerce/src/hooks/useProductDetail.ts. There is little public evidence of automated tests, formal accessibility audits, measured performance reports or backend/SSR work.
UI Component Architecture
5/10
How interface parts are built
Component boundaries and state separation are reasonable: custom hooks, a central Zustand store and modular API layer are used, but there is no evidence of a bespoke design system or advanced composition patterns beyond conventional separation.
Evidence
simransia/test-management/src/stores/test-store.ts: useTestStore with clear actions and derived helpers (makeLocalId, createEmptyQuestion)
simransia/test-management/src/hooks/use-tests.ts: useTests / useTest hooks separating data fetching and state
simransia/e-commerce/src/hooks/useProductDetail.ts: product detail hook encapsulating UI state and URL sync
Responsive & Cross-browser
4/10
Works on all screens and browsers
Responsive styling is implemented with media queries, grid layouts and mobile adaptations, but there is no sign of advanced feature-detection, container queries or explicit RTL/i18n handling.
Performance Optimization
4/10
Speed of the interface
Some practical performance and perceived-performance techniques are present (skeletons, request cancellation), but there are no measured optimizations, bundle analysis artifacts or advanced SSR/bundling strategies shown.
Accessibility & Semantics
3/10
Usable for everyone
Basic accessibility signals exist in styles (focus-visible outlines) and overlay patterns, but there is little evidence of ARIA on custom widgets, keyboard focus management in JS, or automated a11y tooling in CI.
State Management & Data Flow
5/10
Managing data in the app
Server-state and client-state are cleanly separated with an API layer and hooks; there is solid error handling, reload functions and a central store for complex UI flows, but no advanced optimistic-updates with rollback or formal state machines.
Evidence
simransia/test-management/src/api/test.ts: thin API wrapper returning typed ApiResponse objects
simransia/test-management/src/hooks/use-test-metadata.ts: hooks with loading/error/reload patterns
simransia/test-management/src/stores/test-store.ts: structured Zustand store for wizard and question management
UX & Visual Polish
5/10
Look and feel quality
UX polish is visible: skeletons, loading/error states, toasts and thoughtful variants/empty states exist, showing attention to perceived performance and edge states, though some behavior is only in styles without runnable example code proving interactions.
Verified artifacts
Expertise
React• Middle
HTML & CSS• Middle
Frontend Architecture & Build Tools• Middle
Industries
Commerce• Middle
Education• Middle
Technologies
Zustand• since 2022
GraphQL• since 2022
Tailwind CSS• since 2022
Next.js• since 2022
Express
D3.js
WebSockets• since 2025
Figma
Three.JS
Sketch
Git
React.js• since 2022
Vite
Radix UI
Storybook• since 2022
Zeplin
Material UI
Sass
PostCSS
Zod
styled-components
shadcn/ui• since 2025
Recharts• since 2025
React Three Fiber
React Hook Form
React Router
Lighthouse
drei
Recommendations
- Build and own medium-sized React SPAs that require complex client state, forms and content authoring (admin dashboards and test-creation flows).
- Implement e-commerce product and cart flows where URL-sync, request cancellation and stock state are important, leveraging the existing hooks and store patterns.
- Add automated tests and accessibility checks (unit + integration + axe in CI) and capture simple performance metrics (LCP/TTI) to raise confidence for production readiness.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: Medium Generalist
A middle-level front-end developer specializing in TypeScript React single-page applications with solid state-management patterns. The strongest proven skill is building typed API wrappers and consumer hooks with clear error handling, demonstrated in src/api/test.ts and src/hooks/use-tests.ts. There is little to no evidence of automated test suites, CI pipelines, contract testing or performance/load testing in the human-authored code.
Test Automation Frameworks
1/10
Building automated tests
Minimal test automation tooling is declared in package manifests but there is no real test suite, fixtures or automation framework present in human-authored code.
Test Coverage & Strategy
1/10
What and how to test
Some input validation and error-surface points exist in application code but there is no structured test strategy, risk-based tagging, property-based tests or mutation testing artifacts.
API & Integration Testing
2/10
Testing how parts work together
Well-typed API wrapper functions and centralized error handling show basic API testing awareness but there are no contract tests, schema validation suites or integration test containers.
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
1/10
Finding and describing bugs
Code includes mechanisms that help reproduce state and observe errors but there are no documented bug reports, RCA artifacts or flaky-test investigations in the analyzed code.
CI Test Integration
1/10
Running tests automatically
Build and test scripts exist in manifests but there are no CI workflows, matrix runs, artifact collection or quarantine mechanics in human-authored content.
Industries
Education• Middle
Technologies
JavaScript• since 2021 • Middle
TypeScript• since 2022 • Middle
Playwright• since 2022
CI/CD
Sentry
Recommendations
- Develop production-grade React admin dashboards and internal tooling that require typed API integration and state management.
- Build and own API client libraries and their contract tests (OpenAPI/pact/schemathesis) to raise integration confidence.
- Implement a CI pipeline with test automation, artifact collection and selective test runs to harden delivery flows.
- Add unit and component tests (testing-library/ vitest / jest) and migrate some critical paths to property-based or contract tests for robustness.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: