Syed Aman Rukhsar
Software Developer
Node JS
TypeScript
JavaScript
SQL
API Design: 4/10
Data Layer & Database: 4/10
System Architecture: 4/10
Active 6 days ago
+91 (9581) 420274 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
AI-integrated Full-Stack Engineer with 3+ years delivering production LLM applications. Specialised in building and scaling
React + Node.js/Python SaaS products with LangChain, RAG pipelines, and GPT-4/OpenAI integrations. Delivered a
40% backend latency reduction and >85% accuracy AI features in production. Seeking product engineering roles where
reliable AI systems and backend scalability drive business outcomes.
Technical skills
Node JS• Middle
TypeScript• Middle
JavaScript• Middle
SQL
Node JS
Prisma
Express
Axios
Databases
PostgreSQL
MongoDB
Frontend
React.js
Vite
Zustand
Recharts
Zod
Tailwind CSS
DevOps
Rest API
Docker Compose
AWS
QA
Vitest
QA
AI/ML
Claude
Cursor
Claude Code
Timeline
Haldia Institute of Technology
Bachelor's Degree •
Computer Science & Engineering
Middle Backend Developer
Confidence: Medium API Engineer
A Middle-level backend API engineer focused on TypeScript/Node.js services with a strength in schema-driven validation and modular service boundaries. The strongest proven skill is robust data validation and transformation with Zod and comprehensive unit tests as demonstrated in packages/shared/src/data-transformers.ts and data-transformers.test.ts. There is limited public evidence of production operations work such as distributed system design, migration history, advanced observability, or coordinated resilience patterns.
API Design
4/10
How well APIs are designed
API design shows schema-driven validation, idempotency handling, and consistent route structure, but lacks explicit versioning, pagination conventions beyond simple query params, and no documented error contract standard across services.
Evidence
Syed-98/expense-tracker/backend/index.ts: POST /api/expenses implements idempotency-key handling and Zod validation
Syed-98/mini-crm-opportunity-tracker/backend/src/routes/opportunityRoutes.js: express-validator usage and route declarations
Syed-98/mini-crm-opportunity-tracker/backend/src/controllers/authController.js: JWT token generation and auth endpoints
Data Layer & Database
4/10
Working with databases
Data layer includes typed validation and two different persistence approaches (Prisma + relational, Mongoose + MongoDB) with model-level constraints and sensible use of populate to avoid naive N+1, but no migration history or explicit transaction/isolation handling is present.
Evidence
Syed-98/expense-tracker/backend/index.ts: PrismaClient usage and findUnique/create for idempotency
Syed-98/mini-crm-opportunity-tracker/backend/src/models/Opportunity.js: Mongoose schema with validation and enums
Syed-98/mini-crm-opportunity-tracker/backend/src/controllers/opportunityController.js: use of .populate to load owner relation
Scalability & Performance
2/10
Handling load and speed
Some attention to simulated latency and responsiveness in test/mock code, but there is little evidence of caching, queue-based decoupling, rate limiting, or measured performance optimizations for production scale.
System Architecture
4/10
Overall system structure
Project exhibits deliberate modular structure (monorepo with shared package, clear frontend/backend separation, widget registry and typed shared schemas) showing sensible boundaries, but system-level architecture (multi-service contracts, graceful degradation) is not explored in depth.
Evidence
Syed-98/Dashboard-builder/packages/shared/src/data-transformers.ts: shared schema-driven transformation library
Syed-98/Dashboard-builder/packages/frontend/src/engine/store.ts: widget store and registry usage indicating component/service boundaries
Syed-98/Dashboard-builder/packages/backend/package.json and packages layout: monorepo with shared package
Security & Auth
4/10
Protecting data and access
Good basic security practices are present such as bcrypt for password hashing, JWT for auth, input validation, and configurable CORS, but there is no evidence of token refresh/revocation, WAF/SSRF mitigations, secrets rotation, or dependency auditing automation.
Evidence
Syed-98/mini-crm-opportunity-tracker/backend/src/controllers/authController.js: bcrypt hashing and jwt token issuance with 2h expiry
Syed-98/mini-crm-opportunity-tracker/backend/server.js: CORS configuration driven by environment variable
Syed-98/mini-crm-opportunity-tracker/backend/src/routes/opportunityRoutes.js: express-validator based input validation
Reliability & Observability
3/10
Stability and monitoring
There is unit test coverage for data transformation logic and some defensive rehydration logic on the client, plus basic error handling in endpoints, but production-grade observability, structured logging, timeouts, backoff/retry policies, and graceful shutdowns are not evidenced.
Evidence
Syed-98/Dashboard-builder/packages/shared/src/data-transformers.test.ts: comprehensive unit tests for transformer logic
Syed-98/Dashboard-builder/packages/frontend/src/engine/store.ts: onRehydrateStorage handler that resets corrupted localStorage state
Syed-98/expense-tracker/backend/index.ts: try/catch blocks with console.error in endpoints
Expertise
Node.js• Middle
Microservices & API Architecture• Middle
Databases & Vector Storage• Middle
Industries
Data & Analytics• Middle
Sales & Marketing• Middle
Technologies
Node JS• Middle
MongoDB
PostgreSQL
Docker Compose
Prisma
Express• mentioned only
Stack• mentioned only
Recommendations
- Develop API-first Node.js services that require strong input validation and clear data contracts using Zod and TypeScript.
- Build analytics dashboards and data-transformation pipelines where typed transformers and unit testing are important.
- Implement small-to-medium backend systems for SMBs such as CRM or expense-tracking services that need secure auth and idempotent operations.
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-focused app engineer (middle level) who builds data-driven single page applications and widgetized dashboards. The strongest proven skill is implementing reliable data transform and charting pipelines, as shown by packages/shared/src/data-transformers.ts and its tests in packages/shared/src/data-transformers.test.ts. Public code does not show deep performance instrumentation, advanced a11y for custom widgets, or large-scale system-design responsibilities.
UI Component Architecture
4/10
How interface parts are built
Reasonable component/registry architecture and clear separation between shell, widget definitions and widget runtime state, but not a bespoke design system or unusually deep component patterns.
Responsive & Cross-browser
5/10
Works on all screens and browsers
Responsive CSS and sensible layout rules with media queries and fluid grid areas used in multiple shells; not heavy on advanced browser feature-detection or RTL support.
Performance Optimization
2/10
Speed of the interface
Some practical perf-conscious choices (persist partialize, limited DOM work), but no measured perf artifacts, bundle analysis, virtualization or advanced code-splitting evidence.
Accessibility & Semantics
2/10
Usable for everyone
Basic accessibility and focus styles are present (focus outlines, visible focus states) but no evidence of custom widget keyboard/focus management, ARIA strategies or CI a11y checks.
State Management & Data Flow
4/10
Managing data in the app
Clear SPA state design with a persistent zustand store, rehydrate/error handling and server-side idempotency in backend endpoints showing attention to server-state discipline.
UX & Visual Polish
4/10
Look and feel quality
Good UX polish in CSS with explicit loading, error and empty states and test coverage for data-transform behavior, supporting a solid perceived-UX baseline.
Verified artifacts
Expertise
React• Middle
Frontend Architecture & Build Tools• Middle
Industries
Commerce• Middle
Data & Analytics• Middle
Financial Services• Middle
Technologies
Zustand
Tailwind CSS
Express
React.js
Vite
Axios
Zod
Recharts
Recommendations
- Develop data-centric dashboard interfaces and widget platforms that consume server-side time series and relational payloads.
- Implement mid-sized SPA features with complex client-state flows, offline persistence and simple idempotent backend endpoints.
- Build and maintain product UIs that integrate Recharts/visualizations and rely on a widget registry pattern for composition.
- Work on feature teams improving API reliability, input validation (Zod) and end-to-end data contracts between frontend and backend.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: High SDET
Middle-level engineer focused on building testable TypeScript React and Node-based dashboards and backend services. The strongest proven skill is implementing robust data transformation and validation logic with explicit unit tests as evidenced by packages/shared/src/data-transformers.ts and packages/shared/src/data-transformers.test.ts. There is limited evidence of CI pipeline automation, contract testing, or any performance/load testing in the public human-authored code.
Test Automation Frameworks
3/10
Building automated tests
Basic test automation artifacts and unit test framework usage are present (Vitest configs, unit tests, and small mock engine) but there is no advanced fixture framework, sharding, or CI-integrated test orchestration.
Test Coverage & Strategy
4/10
What and how to test
Tests include negative-path and edge-case checks (schema rejection, error throwing, ordering/time assertions, unknown-type error), showing conscious negative-path design and boundary testing, but there is no property-based testing, mutation testing, or deliberate risk-based test stratification.
API & Integration Testing
2/10
Testing how parts work together
There is schema-driven validation (Zod) and idempotency handling in server code and tests validate schema conformance, but no contract testing tooling, no integration testcontainers, and no explicit retry/idempotency scenarios under failure injected in tests.
Performance & Load Testing
Testing speed under load
Not evidenced in public code
Bug Reporting & Analysis
2/10
Finding and describing bugs
Some test assertions exercise failure paths and explicit error expectations which supports basic bug detection and root-cause narrowing, but there are no reproducible bug reports, issue-to-fix links, or documented flaky-test investigations.
CI Test Integration
2/10
Running tests automatically
Project contains per-package test configuration and npm scripts for running tests (Vitest configs and package.json scripts), but there is no CI workflow, matrix, selective/diff-based test runs, or quarantine/retry policy visible in human-authored files.
Expertise
SDET & Test Engineering• Middle
API Testing & Contract Validation• Middle
Industries
Commerce• Middle
Software• Middle
Technologies
QA
JavaScript• Middle
TypeScript• Middle
Rest API
Vitest
Recommendations
- Develop data-heavy dashboard components and data-transform pipelines where schema validation and determinism is important.
- Build and extend test harnesses and mock data engines for API and frontend integration tests to improve contract confidence.
- Own backend validation and idempotency features for API endpoints and write integration tests that exercise failure and retry scenarios.
- Contribute test automation improvements such as CI workflows, per-test retries, and property-based tests for key invariants.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: