Shraddha Kesarwani
Software Developer
Python
Go
JavaScript
Node JS
Ruby
API Design: 4/10
Reliability & Observability: 4/10
Active 4 days ago
Invite to interview
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Backend API engineer applying solid API design and test-driven development practices at a middle level with a focus on small, maintainable services - strongest at building REST endpoints and storage integrations with concrete tests. The most proven skill is building a test-covered FastAPI service that cleanly separates routes, storage, and HTTP client logic as demonstrated by app/routes.py, app/storage.py, app/weather_client.py and their tests. There is limited evidence of production-grade operational tooling such as distributed architecture, robust auth/token lifecycle, migrations, or advanced scalability patterns.
Phone
Technical skills
Languages
5
Python
Go
JavaScript
Node JS
Ruby
Python
4
FastAPI
Pydantic
HTTPX
Asyncio
Databases
3
Redis
Apache Kafka
MySQL
DevOps
3
Docker
AWS
AWS Lambda
AI/ML
3
Model Context Protocol
Claude Code
Claude
Other
19
Express
Pytest
Vitest
React.js
Tailwind CSS
Ruby on Rails
Sidekiq
GitHub
Dotenv
Uvicorn
Git
Rest API
Postman
Vite
CI/CD
Jenkins
AI Agents
autoprefixer
SigNoz
Timeline
Software Development Engineer
•
Middle
Vegrow
•
Full-Time
Built a Python payment-recovery pipeline that integrates Gmail Pub/Sub to automate multiple bank-email routes using idempotent deduplication, concurrent processing, and failure alerting with manual replay support. Developed modular Go APIs integrating Zoho data for payments, invoices, and CRM to reduce reconciliation incidents. Optimized production endpoints by resolving N+1 queries and adding targeted caching to significantly cut response latency. Architected an internal orchestration harness that runs multiple Claude Code agents in isolated Docker sandboxes using MCP-based tool servers.
Python
Go
Gmail
Redis
Docker
Claude Code
Model Context Protocol
Pune University
Bachelor's Degree •
Computer Applications
Software Engineer Intern
•
Junior
Vegrow
•
Internship
Implemented a role-based customer onboarding system to replace a third-party CRM tool, consolidating multiple verification and onboarding steps into a single flow and reducing recurring tooling cost. Built a Kafka-backed Go SMS/OTP delivery integration supporting multiple notification workflows and channels. Centralized template processing, priority routing, provider integration, and delivery logging for reliable message delivery.
Apache Kafka
Go
Middle Backend Developer
Confidence: High API Engineer
Backend API engineer applying solid API design and test-driven development practices at a middle level with a focus on small, maintainable services - strongest at building REST endpoints and storage integrations with concrete tests. The most proven skill is building a test-covered FastAPI service that cleanly separates routes, storage, and HTTP client logic as demonstrated by app/routes.py, app/storage.py, app/weather_client.py and their tests. There is limited evidence of production-grade operational tooling such as distributed architecture, robust auth/token lifecycle, migrations, or advanced scalability patterns.
API Design
4/10
How well APIs are designed
Clear REST API design with explicit error mapping and response models, but no versioning, pagination, or idempotency strategy; mixes a small, well-tested FastAPI service with an Express monolith that implements basic RBAC simulation.
Evidence
weather-explorer/backend/app/routes.py: FastAPI endpoints with response_model and HTTPException mapping
bug-tracker/backend/server.js: /bugs CRUD endpoints with requireUser and requireRole middleware
shraddha-999/bug-tracker/test-api.js: end-to-end tests exercising create/update/delete and verifying audit logs
Data Layer & Database
3/10
Working with databases
Lightweight data layer abstractions and storage integration are present with some attention to API of the storage client, but there is no relational schema, migrations, or complex transactional logic.
Evidence
weather-explorer/backend/app/storage.py: WeatherStorage wrapper that lazy-initializes Supabase client and enforces content-type on upload
weather-explorer/backend/tests/test_storage.py: tests verifying upload content-type and list() options override
Scalability & Performance
2/10
Handling load and speed
Minor operational considerations are present (bucket list options, client lazy-init, polling), but there is no deliberate scaling, caching invalidation, rate limiting, or queue-based decoupling.
Evidence
weather-explorer/backend/app/storage.py: list_files overrides limit and sort order to handle large buckets
bug-tracker/frontend/src/hooks/useBugs.js: polling every 5s for fresh data
bug-tracker/backend/server.js: in-process SLA check using setInterval (periodic escalation)
System Architecture
3/10
Overall system structure
Reasonable separation of concerns in the FastAPI project (routes, storage, client, schemas) and test fixtures indicate modular thinking, but the overall architecture is small-scale and monolithic in parts.
Evidence
weather-explorer/backend/app/: separation into routes.py, storage.py, weather_client.py, schemas.py
bug-tracker/backend/server.js: single-file monolith for the bug-tracker API
Security & Auth
3/10
Protecting data and access
Basic authentication/authorization checks and input validation are implemented, but auth is simulated via a header and there is no token lifecycle, secrets management, or hardened boundary controls.
Evidence
bug-tracker/backend/server.js: requireUser and requireRole enforce role-based access from x-user-id header
weather-explorer/backend/app/schemas.py: Pydantic-based request validation used for input constraints and date-range checks
Reliability & Observability
4/10
Stability and monitoring
Good test coverage and explicit error handling across modules improve reliability; the code maps upstream errors to appropriate HTTP statuses and has unit tests for client, storage, and routes, but lacks operational patterns like retries with backoff, circuit breakers, or graceful shutdown hooks.
Evidence
weather-explorer/backend/tests/test_weather_client.py: tests cover network errors and non-200 handling for the external API client
weather-explorer/backend/tests/test_routes.py: tests assert HTTP status mapping for upstream failures and storage errors
shraddha-999/bug-tracker/test-api.js: integration script validating idempotency and audit logging
Expertise
Python• Middle
Microservices & API Architecture• Middle
Technologies
Go• since 2024 • Junior
Ruby
Node JS• Middle
Rest API
Express
FastAPI
Ruby on Rails
Apache Kafka• since 2024
Asyncio
Sidekiq
Dotenv
Recommendations
- Develop small to medium REST APIs and integrations that require clear surface contracts and tests, focusing on external API clients and storage adapters.
- Implement backend features where Pydantic validation, typed request/response models, and unit/integration tests are required.
- Work on storage-backed data ingestion or ETL tasks that need careful error mapping and test fixtures for upstream failure modes.
- Improve operational robustness by adding retries with exponential backoff, graceful shutdown, and simple deployment observability (metrics/log correlation).
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle QA Engineer
Confidence: High API QA Engineer
API-focused QA engineer at a middle level specializing in backend service testing and isolation. The strongest proven skill is building isolated backend tests with pytest and monkeypatch, demonstrated by tests such as backend/tests/test_routes.py and backend/tests/test_storage.py that use Fake clients and TestClient to validate success and failure paths. There is little public evidence of CI integration, formal contract testing, performance/load testing, or large-scale system design.
Test Automation Frameworks
6/10
Building automated tests
Solid evidence of test automation frameworks and isolation: pytest-based unit tests, TestClient integration, and hand-rolled fake clients/fixtures demonstrate deliberate test scaffolding and dependency injection. Missing advanced infra like testcontainers, sharding/parallelization config, or a dedicated mock server with programmable behavior prevents a higher score.
Evidence
weather-explorer/backend/tests/test_routes.py: FakeStorage fixture and monkeypatch usage to replace storage and fetch functions
weather-explorer/backend/tests/test_storage.py: FakeSupabaseClient and FakeBucket classes used to validate upload/list/download behavior
bug-tracker/test-api.js: standalone HTTP integration script executing end-to-end CRUD and audit checks
Test Coverage & Strategy
5/10
What and how to test
Good negative-path and boundary testing is present (validation edge cases, upstream failure handling, missing-file behavior). There is no evidence of risk-based tagging, mutation testing, or property-based tests, so strategy and coverage maturity are moderate.
Evidence
weather-explorer/backend/tests/test_validation.py: latitude/longitude and date-range boundary tests
weather-explorer/backend/tests/test_routes.py: tests for upstream failure returning 502 and invalid input returning 400
API & Integration Testing
6/10
Testing how parts work together
Strong API and integration testing coverage for backend components: explicit contract-like checks of status codes and payloads, dependency isolation via monkeypatch/fake clients, and storage-layer unit tests. Lacks formal contract tooling (Pact/Schemathesis) and no testcontainer-backed integration with real services.
Evidence
weather-explorer/backend/tests/test_routes.py: TestClient exercises FastAPI routes with fake storage and fake upstream responses
weather-explorer/backend/tests/test_storage.py: unit tests validating Supabase storage interactions via FakeSupabaseClient
bug-tracker/test-api.js: sequential integration assertions for create/update/delete/log audit
Performance & Load Testing
1/10
Testing speed under load
No dedicated performance or load testing artifacts; only a small SLA-checking timer in the bug-tracker server simulates operational behavior but does not constitute performance/load testing.
Evidence
bug-tracker/backend/server.js: setInterval-based SLA escalation logic (application-level timer)
Bug Reporting & Analysis
3/10
Finding and describing bugs
Some attention to auditability and reproducible verification is visible (file-based activity log and tests that assert audit events), but there are no external bug reports, linked issue analysis, or recorded flaky-test investigations.
Evidence
bug-tracker/backend/server.js: appendLog and addHistory helpers that write activity to ACTIVITY_LOG.md
bug-tracker/test-api.js: verifies logs include CREATED/UPDATED/DELETED to validate audit trail
CI Test Integration
Running tests automatically
Not evidenced in public code
Expertise
SDET & Test Engineering• Middle
Manual & Exploratory Testing• Middle
Technologies
Python• since 2024 • Middle
JavaScript• Middle
Postman
Pytest
Vitest
Pydantic
HTTPX
Uvicorn
Recommendations
- Expand and formalize CI pipelines (GitHub Actions / GitLab CI) to run the existing pytest suite, collect artifacts, and gate deployments.
- Introduce contract testing or schema-based validation (e.g., schemathesis or OpenAPI-driven tests) for clearer API guarantees and regression protection.
- Add integration environments using testcontainers or ephemeral cloud mocks and add a small performance smoke test suite (k6/locust) for critical endpoints.
- Harden automation by adding test tagging (smoke/critical/regression), per-test retry/quarantine rules, and artifact retention for flaky test triage.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Junior Frontend Developer
Confidence: Medium Fullstack
Full-stack developer (Middle) focused on practical end-to-end features and API-driven UI patterns. The strongest proven skill is building small full-stack flows and API integrations, evidenced by the Express backend with RBAC and audit logging (bug-tracker/backend/server.js) and the React client hooks that encapsulate polling, error handling, and CRUD flows (bug-tracker/frontend/src/hooks/useBugs.js). The public code does not show large-scale distributed systems, comprehensive frontend accessibility work, or explicit measured performance engineering.
UI Component Architecture
2/10
How interface parts are built
Limited component architecture evidence; the code uses custom hooks to encapsulate API/state logic but there are no original component libraries, design-system tokens, or multi-layer composition patterns visible in the human-authored frontend files.
Evidence
bug-tracker/frontend/src/hooks/useBugs.js
bug-tracker/frontend/src/hooks/useCurrentUser.js
Responsive & Cross-browser
2/10
Works on all screens and browsers
Basic responsive setup using Tailwind and standard meta viewport; no advanced responsive techniques, container queries, or explicit RTL/i18n hooks are present in the human-authored files.
Evidence
bug-tracker/frontend/tailwind.config.js
bug-tracker/frontend/index.html
Performance Optimization
2/10
Speed of the interface
Minimal performance work visible: pragmatic use of useCallback to avoid unnecessary re-renders and a Vite build/dev setup, but no measured optimization artifacts, bundle analysis, virtualization, or concurrency-focused optimizations in the human-authored code.
Evidence
bug-tracker/frontend/src/hooks/useBugs.js
weather-explorer/frontend/vite.config.js
Accessibility & Semantics
1/10
Usable for everyone
Very little accessibility evidence beyond basic HTML lang and viewport; no ARIA on custom widgets, no focus management or keyboard handling present in the human-authored UI code.
Evidence
bug-tracker/frontend/index.html
weather-explorer/frontend/index.html
State Management & Data Flow
3/10
Managing data in the app
Clear server-state discipline for small apps: encapsulated API logic in hooks, error parsing, polling, and coherent update flows; backend shows simple RBAC, audit logging, and SLA escalation logic. There is no advanced request cancellation, optimistic rollback patterns, or complex state machines.
Evidence
bug-tracker/frontend/src/hooks/useBugs.js
bug-tracker/backend/server.js
UX & Visual Polish
3/10
Look and feel quality
UX attention at the feature level: loading and error state variables in hooks and unit tests that assert graceful handling of missing data; however there are few UI-level skeletons, undo patterns, or comprehensive empty-state designs in the human-authored UI code.
Evidence
bug-tracker/frontend/src/hooks/useBugs.js
weather-explorer/frontend/src/weatherData.test.js
Expertise
React• Junior
Frontend Architecture & Build Tools• Junior
Technologies
Tailwind CSS
React.js
Vite
autoprefixer
Recommendations
- Develop internal admin tools, dashboards, and lightweight CRUD apps that require RBAC, auditing, and simple background jobs.
- Implement and extend client-side state encapsulation patterns (custom hooks) into reusable component libraries and documented UI primitives.
- Build production prototypes of API-integrated features and expand automated integration tests to cover concurrency and error scenarios.
- Focus on adding request cancellation, optimistic updates with rollback, and a11y improvements to existing hooks/components to raise frontend quality.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: