Satya Prakash Tiwari
4+ years exp
5+ projects
JavaScript
Node JS
UI Component Architecture: 4/10
Responsive & Cross-browser: 4/10
UX & Visual Polish: 4/10
Active 4 days ago
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
React-focused UI engineer at a Middle level specializing in component-driven styling and visual polish. The strongest proven skill is building componentized, styled React UIs as shown by the styled-components files and presentational components in src/components/Navbar/NavbarStyledComponent.js and src/components/HeroSection/HeroStyle.js. There is little public evidence of automated tests, advanced server-state handling (cancellation, optimistic updates), performance measurement, or accessibility auditing.
Technical skills
JavaScript• Junior • 4y+
Node JS• Senior • 5+ projects
Databases
PostgreSQL• 5+ projects
MongoDB• 4 projects
Frontend
React.js
styled-components
Material UI
Framer Motion
React Router
Ant Design• 5+ projects
Formik• 4 projects
npm• 4 projects
DevOps
Rest API
AWS• 4 projects
Design
Figma• 4 projects
Timeline
senior software engineer
•
Senior
wesoftek solutions
•
Full-Time
Senior Software Engineer with 2.5+ years of experience building scalable web applications and backend systems using React.js, Node.js, NestJS, PostgreSQL, and MongoDB.
Experienced in high-impact FinTech, Digital Lending, Enterprise HRMS, and AI SaaS platforms, including a lending platform serving 20K–30K+ daily users and supporting ₹300Cr+ loan disbursals.
Skilled in TypeScript, REST APIs, Microservices, WebSockets, JWT, AWS, database optimization, and clean architecture. Strong focus on performance optimization, scalable system design, API development, and building reliable, maintainable products.
React.js
JavaScript
Node JS
Nest.JS
loan lending platform
Backend
Senior Software Engineer with 2.5+ years of experience building scalable web applications and backend systems using React.js, Node.js, NestJS, PostgreSQL, and MongoDB.
Experienced in high-impact FinTech, Digital Lending, Enterprise HRMS, and AI SaaS platforms, including a lending platform serving 20K–30K+ daily users and supporting ₹300Cr+ loan disbursals.
Skilled in TypeScript, REST APIs, Microservices, WebSockets, JWT, AWS, database optimization, and clean architecture. Strong focus on performance optimization, scalable system design, API development, and building reliable, maintainable products.
Nest.JS
Node JS
React.js
Middle Frontend Developer
Confidence: Medium UI Engineer
React-focused UI engineer at a Middle level specializing in component-driven styling and visual polish. The strongest proven skill is building componentized, styled React UIs as shown by the styled-components files and presentational components in src/components/Navbar/NavbarStyledComponent.js and src/components/HeroSection/HeroStyle.js. There is little public evidence of automated tests, advanced server-state handling (cancellation, optimistic updates), performance measurement, or accessibility auditing.
UI Component Architecture
4/10
How interface parts are built
Component-driven UI with styled-components and clearly separated presentational components; good composition but no evidence of a custom design system, tokens, or advanced component APIs.
Responsive & Cross-browser
4/10
Works on all screens and browsers
Responsive behavior is implemented via media queries and adaptive layout patterns; mobile menu and layout adjustments are present but no advanced feature-detection or RTL/i18n scaffolding was found.
Performance Optimization
2/10
Speed of the interface
Minimal performance work: attractive animations and an SVG background exist but there is no evidence of measurement, code-splitting, bundle analysis, virtualization, or deliberate load optimizations.
Accessibility & Semantics
2/10
Usable for everyone
Some accessibility-aware bits (aria on Avatar, form labels) but many missing a11y best practices for custom widgets, focus management, and consistent alt text; no automated a11y tooling found.
State Management & Data Flow
3/10
Managing data in the app
Basic client-side state and server interactions using React context and axios with straightforward try/catch error handling; no advanced server-state discipline, cancellation, optimistic updates or state machines observed.
UX & Visual Polish
4/10
Look and feel quality
Strong visual polish and UX touches such as animated hero SVGs, motion transitions and success/error UI (Snackbar, inline messages); loading and empty states are limited or not consistently implemented.
Expertise
React• Middle
Technologies
React.js
Material UI
styled-components
Framer Motion
React Router
Recommendations
- Assign to build polished marketing sites, portfolio pages, or small-to-medium SPA frontends that need strong visual design and component-based styling.
- Pair with a senior on a project to add server-state best practices: request cancellation, optimistic updates, and systematic error/loading states.
- Work on test coverage (unit and integration) and introduce basic performance measurement (Lighthouse / bundle analysis) and CI a11y checks to raise craft to the next level.
- Convert repeated visual patterns into a small design token system or component library to increase reusability and cross-project consistency.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Backend Developer
Confidence: Medium Generalist
Junior full-stack web developer focused on building React user interfaces and simple REST integrations. Proven strength in client-side React components and form-based interactions, demonstrated by Blog-Website1/client/src/pages/write/Write.js and satya-prakash-portfolio/src/components/Contact/index.js. There is little evidence of production-grade backend architecture, schema evolution, resilience patterns, or observability in the human-authored code.
API Design
2/10
How well APIs are designed
Minimal API design evidence; client-side REST calls exist but there is no versioning, idempotency, pagination, or consistent error contract visible.
Evidence
Blog-Website1/client/src/pages/write/Write.js: axios.post to /api/posts/createpost
Blog-Website1/client/src/pages/settings/Settings.js: axios.put to http://localhost:5000/api/users/update/:id
satya-prakash-portfolio/src/components/Contact/index.js: emailjs.sendForm usage (client-side integration with external service)
Data Layer & Database
1/10
Working with databases
Almost no data-layer artifacts in human-authored files; no migrations, transaction boundaries, isolation considerations, or hand-tuned queries are visible.
Evidence
Blog-Website1/client/src/pages/write/Write.js: client-side creation of posts via /api/posts/createpost
Blog-Website1/client/src/pages/settings/Settings.js: client-side upload and PUT to /api/users/update (interaction with DB-backed API)
Scalability & Performance
1/10
Handling load and speed
No demonstrated scalability or performance engineering; there is only basic client-side file upload and image preview logic and no caching, queues, or rate limiting.
Evidence
Blog-Website1/client/src/pages/write/Write.js: FormData-based file upload and client-side image preview
satyaprakash-web/satya-prakash-portfolio/src/components/Skills/index.js: client-side rendering of many UI items (no caching or optimization evident)
System Architecture
2/10
Overall system structure
Simple, sensible frontend module boundaries and componentization are present, but there is no evidence of deliberate service decomposition, config/secret management, or graceful degradation patterns.
Evidence
satyaprakash-web/satya-prakash-portfolio/src/components/Navbar/index.js: component separation, responsive behavior and useContext(UserContext)
Blog-Website1/client/src/components/navbar/Navbar.js: clear foldered components and routing usage
Security & Auth
1/10
Protecting data and access
Minimal security controls in human-authored code; authentication and secret handling are naive on the client and secrets are exposed in source.
Evidence
satyaprakash-web/satya-prakash-portfolio/src/components/Contact/index.js: emailjs.sendForm with visible service/template/user keys
Blog-Website1/client/src/pages/settings/Settings.js: password included in PUT payload without visible token-based auth handling
Reliability & Observability
1/10
Stability and monitoring
Very limited reliability and observability practices; errors are largely console.logged and there are no retries, backoff, structured logs or timeouts.
Evidence
Blog-Website1/client/src/pages/write/Write.js: try/catch blocks that only console.log errors
satyaprakash-web/satya-prakash-portfolio/src/components/Contact/index.js: promise error handling with console.log and only a Snackbar for success
Expertise
Databases & Vector Storage• Junior
Node.js• Junior
Recommendations
- Develop responsive React UI features and single-page application front ends, including polished forms and media uploads.
- Build and maintain small end-to-end CRUD services with clear API contracts and token-based authentication to strengthen backend experience.
- Improve robustness by adding client-side and server-side error handling, explicit timeouts, and retry/backoff semantics for network calls.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior QA Engineer
Confidence: High Generalist
Front-end JavaScript developer at a junior level focused on building React single-page applications and UI for small web projects. The strongest proven skill is integrating UI with REST endpoints and handling client-side form flows, evidenced by settings/Singlepost/write components that perform axios uploads, fetches, edits, and deletes. There is little to no evidence of automated tests, CI integration, contract/schema testing, or performance/load testing in the public code.
Test Automation Frameworks
1/10
Building automated tests
Minimal test automation evidence: test dependencies are declared but there are no authored test suites, fixtures, or any test infra in human-authored code.
Test Coverage & Strategy
1/10
What and how to test
No visible test coverage strategy, risk-based tagging, or negative-path/property tests; only test-related dependencies appear in package.json without authored test files.
API & Integration Testing
1/10
Testing how parts work together
API and integration usage is present with axios calls and REST endpoints, but there is no contract/schema validation, no idempotency/retry handling, and no integration test harness.
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
Technologies
JavaScript• Junior • 4y+
Rest API
Recommendations
- Add unit and component tests with Jest and React Testing Library for key components (Settings, Singlepost, Write) and cover negative/error paths.
- Introduce API contract/schema validation and integration tests (e.g., JSON Schema checks, Schemathesis or Pact) for endpoints used by axios calls.
- Add a CI pipeline (GitHub Actions) to run linting, tests and build on push and to catch regressions during PRs.
- Remove hard-coded secrets and API keys from source and use environment variables or a secrets service; add retry and timeout/error handling for network calls.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: