Kamlesh Sahu
Software Developer
5+ years exp
Python
TypeScript
JavaScript
Node JS
Active 2 days ago
+91 (7977) 311551
Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Backend developer at a Middle level focusing on modular Python automation and job-matching services with a practical strength in integrating scraping, resume parsing, and simple agent logic. The strongest proven skill is building parsing and aggregation pipelines as shown by app/services/resume_parser.py and app/services/job_scraper.py. There is little public evidence of production-grade datastore migrations, distributed systems patterns, formal API versioning, or automated test coverage.
Technical skills
Python• Middle
TypeScript• 5y+
JavaScript• Junior • 4y+
Node JS• Middle • 4y+
Python
Requests
Beautiful Soup
Pydantic
Node JS
Express
Axios
Frontend
Bootstrap
Material UI
Redux
Tailwind CSS
PostCSS
ESLint
Prettier
autoprefixer
React Router
Next.js• 5y+
React.js• 5y+
styled-components• 5y+
GraphQL• 4y+
React Query• 4y+
Webpack• 4y+
DevOps
AWS
Git
CI/CD• 4y+
GitHub Actions• 4y+
Grafana• 4y+
Prometheus• 4y+
Rest API• 4y+
Design
Figma
QA
Jest
AI/ML
Claude
Copilot
Timeline
Technology Analyst
•
Middle
Infosys
•
Full-Time
Developed production-ready full-stack modules using React, Node.js, and TypeScript, including third-party integrations with strong type safety. Built a GraphQL BFF layer and integrated it with REST APIs using React Query to streamline frontend data fetching. Owned issues across Stage, QA, and Production using monitoring, and supported end-to-end release cycles with independent deployments after PR merges. Implemented secure in-app payments via a payment gateway iframe and improved PR documentation automation with an AI-assisted GitHub Actions workflow.
TypeScript
Node JS
React.js
GraphQL
Rest API
React Query
Webpack
Prometheus
Grafana
GitHub Actions
AI Agents
CI/CD
Trainee → Software Developer (React)
•
Junior
Trantor Pvt Ltd
•
Full-Time
Built features for a spreadsheet-like web application as part of a MERN-focused training, working in a Dockerized development environment. Developed UI functionality with Next.js and TypeScript, resolving styling and component issues using styled-components for consistent user experience. Transitioned from trainee to React-focused development while following team standards and collaboration workflows.
Next.js
TypeScriptsince 2021
styled-components
Docker
React.jssince 2021
Middle Backend Developer
Confidence: High API Engineer
Backend developer at a Middle level focusing on modular Python automation and job-matching services with a practical strength in integrating scraping, resume parsing, and simple agent logic. The strongest proven skill is building parsing and aggregation pipelines as shown by app/services/resume_parser.py and app/services/job_scraper.py. There is little public evidence of production-grade datastore migrations, distributed systems patterns, formal API versioning, or automated test coverage.
API Design
2/10
How well APIs are designed
Minimal API design: a single naive Express endpoint and client calls exist but there is no versioning, idempotency strategy, or consistent error contract.
Evidence
travel-ai-planner/backend/src/main.js: POST /ask handler (simple completion endpoint)
Job-ai-agent/scripts/streamlit_app.py: client-side fetch to backend and usage of service functions (fetch_jobs, send_email)
Data Layer & Database
2/10
Working with databases
Data layer is file-backed JSON and in-memory objects with no migration history, transactional boundaries, or tuned queries; a Pydantic model exists but no demonstrated schema evolution.
Evidence
Job-ai-agent/app/services/scheduler_service.py: _init_files, _load_schedules, file-based schedules/users JSON storage
Job-ai-agent/app/models/job_model.py: presence of Job Pydantic model
Scalability & Performance
2/10
Handling load and speed
Basic performance practices only: request timeouts and simple de-duplication; no caching/invalidation, no queue-based decoupling, no load-test evidence or rate limiting.
Evidence
Job-ai-agent/app/services/job_scraper.py: requests.get(..., timeout=8) and deduplication by title in fetch_jobs
Job-ai-agent/scripts/streamlit_app.py: UI-side limits (trimming shown jobs) and spinner usage
System Architecture
3/10
Overall system structure
Clear modular structure (agents, services, models, utils) showing deliberate separation of concerns within a monolith, but not a distributed microservices architecture.
Evidence
Job-ai-agent/app/agents/grok_agent.py: agent orchestration and tool execution design
Job-ai-agent/app/services/scheduler_service.py: dedicated scheduler service with API used by UI
Security & Auth
2/10
Protecting data and access
Some security awareness (dotenv usage, basic input checks) but also problematic practices like checked-in client credentials and placeholder/hardcoded API keys; no token lifecycle or dependency audit shown.
Evidence
Job-ai-agent/app/agents/grok_agent.py: OpenAI/Grok client constructed with api_key placeholder in code
project-hack/src/firebase.js: Firebase configuration object with API key and appId committed
Reliability & Observability
3/10
Stability and monitoring
Reasonable reliability patterns: logger usage, try/except fallbacks and graceful fallback flows; however there are no structured metrics, retry/backoff policies with jitter, or graceful shutdown/health checks.
Evidence
app/utils/logger.py referenced across modules via get_logger
Job-ai-agent/app/services/job_scraper.py and app/agents/grok_agent.py: try/except with fallback logic and explicit fallback job lists
Expertise
Python• Middle
Backend AI & LLM• Middle
Node.js• Junior
Technologies
Python• Middle
Node JS• Middle • 4y+
Rest API• 4y+
Express
Beautiful Soup
Pydantic
Requests
Recommendations
- Harden backend services for production by replacing file-backed JSON with a real database and add schema migrations and tests for schema evolution (e.g., use Alembic or similar).
- Add operational resilience: implement retries with exponential backoff and jitter for external calls, background queue workers for scraping, and caching with invalidation for frequently-read data.
- Improve security and secrets hygiene: remove checked-in credentials, load all secrets via environment or secret manager, and add input sanitization and dependency vulnerability scanning.
- Add automated tests and CI/CD: unit and integration tests around parsing, scheduler logic, and LLM integrations plus a simple pipeline to run them on each push.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Frontend Developer
Confidence: Medium App Engineer
A front-end focused app engineer (approximately junior-to-middle level) who builds small end-to-end React apps with simple backend integrations. The strongest proven skill is building client-server UI flows with React Context and Firebase auth, as shown by the AuthContext provider in project-hack/src/AuthContext.js. The public code shows limited evidence of testing, measured performance work, advanced state discipline like request cancellation or optimistic updates, and formal accessibility practices.
UI Component Architecture
4/10
How interface parts are built
Component boundaries are basic but deliberate; uses React Context to avoid prop drilling and composes small components rather than large monoliths.
Evidence
project-hack/src/AuthContext.js: React Context provider encapsulating auth state
travel-ai-planner/Client/src/App.js: form component with local state and controlled inputs
Responsive & Cross-browser
4/10
Works on all screens and browsers
Responsive layout is present using Tailwind-style classes and a mobile menu, and a Tailwind config is included for responsive content targeting.
Evidence
portfolio/index.html: responsive Tailwind classes and mobile navigation markup
project-hack/tailwind.config.js: Tailwind content configuration for project files
Performance Optimization
1/10
Speed of the interface
No measured performance work or advanced optimizations; only boilerplate hints at performance measurement and build tooling are present.
Evidence
travel-ai-planner/Client/src/index.js: comment about measuring performance (reportWebVitals)
project-hack/package.json: devDependencies include build tooling (tailwindcss, autoprefixer) but no targeted perf artifacts
Accessibility & Semantics
2/10
Usable for everyone
Basic semantic HTML and form labels exist, but there is no explicit ARIA, focus management, keyboard handling or a11y testing in code.
Evidence
travel-ai-planner/Client/src/App.js: uses <label> elements for form inputs
portfolio/index.html: semantic <nav> and structural markup for navigation
State Management & Data Flow
3/10
Managing data in the app
Shows basic client-server state flow and auth state management using Context and Firebase; lacks cancellation, optimistic updates, offline handling or advanced cache invalidation.
Evidence
project-hack/src/AuthContext.js: onAuthStateChanged handling and Firestore getDoc to hydrate user info
travel-ai-planner/Client/src/App.js: POST fetch to backend /ask endpoint and basic try/catch error logging
travel-ai-planner/backend/src/main.js: Express endpoint that calls OpenAI and returns JSON
UX & Visual Polish
3/10
Look and feel quality
Visual polish and UX are present in the static portfolio and basic form flows, but there are few explicit loading/error/empty states or undo/rollback patterns.
Evidence
portfolio/index.html: styled hero, responsive CTA and mobile menu pattern
portfolio/script.js: mobile menu open/close interaction
project-hack/src/components/PasswordLogin/RegisterPage.css: styling for login/register UI
Expertise
React• Junior
Frontend Architecture & Build Tools• Junior
Technologies
TypeScript• 5y+
Redux
Webpack• 4y+
GraphQL• 4y+
Tailwind CSS
Next.js• 5y+
GitHub Actions• 4y+
Prometheus• 4y+
Figma
CI/CD• 4y+
Bootstrap
Git
AWS
Grafana• 4y+
React.js• 5y+
React Query• 4y+
Axios
Material UI
PostCSS
ESLint
Prettier
styled-components• 5y+
React Router
autoprefixer
Recommendations
- Build a small production SPA with protected routes and form flows that include loading, error and empty states and add tests to cover the flows.
- Improve backend robustness by returning explicit error responses, sanitizing and validating incoming requests, and moving API keys to secure server-side storage.
- Add accessible interactions: ARIA attributes for custom widgets, keyboard focus management after actions, and include axe/eslint-plugin-jsx-a11y in CI.
- Introduce basic performance and observability: add simple bundle splitting, measure LCP/TTI with reportWebVitals, and run a bundle analyzer during builds.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior QA Engineer
Confidence: Medium Generalist
Junior front-end engineer specializing in component-driven React UIs and simple client-side integrations. The strongest proven skill is building client-side UI and auth flows as shown by AuthContext.js (firebase auth state handling) and Navbar.js (Apollo useLazyQuery GraphQL integration). There is no evidence of automated test suites, CI test integration, contract testing or performance/load testing in the authored code.
Test Automation Frameworks
1/10
Building automated tests
Minimal test automation artifacts; only testing-related devDependencies and starter test scripts are present with no authored test suites, fixtures or selector discipline.
Evidence
project-hack/package.json: contains @testing-library/react and test script 'react-scripts test'
cgraphql/package.json: contains @testing-library/jest-dom and test script
Test Coverage & Strategy
1/10
What and how to test
No risk-based test strategy or meaningful negative-path/boundary tests found; only default test scripts exist indicating basic setup without a deliberate coverage strategy.
Evidence
project-hack/package.json: test script 'react-scripts test'
cgraphql/package.json: test script 'react-scripts test'
API & Integration Testing
1/10
Testing how parts work together
Application integration code exists (GraphQL client and Firebase init) but there are no contract tests, schema validation, retry/idempotency tests or testcontainers-based integration artifacts.
Evidence
cgraphql/src/components/Navbar/Navbar.js: useLazyQuery(GET_COVID_DATA) showing client-side GraphQL usage
project-hack/src/firebase.js: firebase initialization exporting db and auth objects
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
Expertise
Unit & Component Testing• Junior
Technologies
JavaScript• Junior • 4y+
Jest
Recommendations
- Develop interactive React component work and client-side features such as auth flows and GraphQL-driven dashboards.
- Add unit and component tests with React Testing Library and Jest focused on negative paths and boundary conditions for key components like AuthContext and Navbar.
- Introduce a CI pipeline that runs tests, records artifacts and fails builds for regressions to reduce risk of shipping regressions.
- Start small contract tests for GraphQL endpoints and basic API error-path tests to catch integration regressions early.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: