Sandeep Srivastav Bandikatla
Software Developer
6+ years exp
JavaScript
TypeScript
Node JS
Python
Go
Rust
Data Layer & Database: 4/10
Active 13 days ago
+1 (425) 5207009 Invite to interview
Message
Download CVCV
Overview
Technical skills
Timeline
Roles
Overview
Backend API engineer at a middle level with a practical focus on lightweight web services and concurrency patterns. The strongest proven skill is implementing a Mongoose-level Redis query cache and cache invalidation as shown in services/cache.js and its integration with routes/book.js. There is little evidence of production-grade testing, formal API versioning, auth mechanisms, or schema migration history in public code.
Technical skills
JavaScript
TypeScript
Node JS• Middle
Python• 6y+
Go• Middle • 4y+
Rust• Junior • 3y+
Node JS
Express
Dotenv
Databases
MongoDB
Redis
Azure Cosmos DB
DevOps
Kubernetes
Docker Compose
Rest API
Containers
AWS• 4y+
CI/CD• 3y+
gRPC• 3y+
Azure
Azure AKS
Docker
Git
Timeline
Software Engineer II
•
Middle
Microsoft
•
Full-Time
Built ingestion and query capabilities for Azure Resource Graph using Azure services and APIs to handle large-scale cluster metadata workloads. Re-architected a query service from a single global dependency to regional microservices, improving availability and reducing query latency for high-volume requests. Optimized ARG performance by reducing garbage-collection overhead and improved cost via cleanup work in Cosmos DB to improve response times.
Azure
Azure AKS
Azure Cosmos DB
Software Development Engineer
•
Middle
Amazon Web Services
•
Full-Time
Worked on a high-throughput distributed SaaS system implemented in Rust, dispatching large numbers of function executions to isolated micro-VMs. Designed a consistent hashing change to improve fleet utilization and reduced operational overheads. Migrated communication from HTTP/1-based custom protocols to gRPC for better robustness, and integrated automation to terminate high-latency nodes using internal monitoring signals. Delivered a Slack webhook tool to tag code reviewers and surface CI/CD failures.
Rust
gRPC
Slack
CI/CD
Arizona State University
Master's Degree •
Computer Science
Software Development Engineer Intern
•
Junior
Amazon Web Services
•
Internship
Designed and implemented leader node snapshot creation using AWS S3 to improve follower catch-up performance. Contributed to improving overall distributed system responsiveness for new nodes joining the cluster.
AWS
Founder and Backend Developer
•
Executive
AdGain Tech
•
Cofounder
Founded a company focused on improving ad engagement and built an interactive web application with backend REST APIs. Drove early user growth and supported business integrations, including partnership development with advertisers. Coordinated a merge with a tech incubator while continuing backend feature delivery.
Python
Indian Institute of Technology Patna (IITP)
Bachelor's Degree •
Computer Science
Middle Backend Developer
Confidence: Medium API Engineer
Backend API engineer at a middle level with a practical focus on lightweight web services and concurrency patterns. The strongest proven skill is implementing a Mongoose-level Redis query cache and cache invalidation as shown in services/cache.js and its integration with routes/book.js. There is little evidence of production-grade testing, formal API versioning, auth mechanisms, or schema migration history in public code.
API Design
3/10
How well APIs are designed
Basic REST design and filtering present but no versioning, no consistent error contract, no idempotency or pagination; routes are simple and mostly CRUD.
Evidence
books-docker-API-master/routes/book.js: GET /api/books with optional author filter and POST /api/books
books-docker-API-master/index.js: express app wiring and route registration
Data Layer & Database
4/10
Working with databases
Shows deliberate data-layer work including a query-level Redis cache and cache invalidation, but lacks migration history, schema evolution, and robust validation.
Evidence
books-docker-API-master/services/cache.js: monkey-patched mongoose.Query.exec with Redis hget/hset and expire
books-docker-API-master/models/Book.js: Mongoose schema definition
books-docker-API-master/routes/book.js: clearKey(Book.collection.collectionName) cache invalidation on write
Scalability & Performance
3/10
Handling load and speed
Some performance thinking: query caching with Redis and a concurrent Go sorting implementation, but no documented load strategies, cache invalidation policies beyond simple clears, or measured optimizations.
Evidence
books-docker-API-master/services/cache.js: Redis-backed query cache logic with configurable TTL
multithreaded-sort-as-a-service/api/controllers/sort_controller.go: concurrent goroutine-based sorting using buffered channel and WaitGroup
System Architecture
3/10
Overall system structure
Clear separation of API, controllers and models and small service structure, but no evidence of service decomposition trade-offs, config/secret management beyond env files, or production orchestration.
Evidence
books-docker-API-master/: project structure with models, routes and services
multithreaded-sort-as-a-service/api/server.go and api/controllers/base.go: beego-based router and server initialization
Security & Auth
1/10
Protecting data and access
Minimal security posture: no auth/authz, minimal input validation and no explicit protection against injection or other boundary threats.
Evidence
books-docker-API-master/routes/book.js: request body used directly when creating Book without validation
multithreaded-sort-as-a-service/api/controllers/sort_controller.go: isValid(nums) returns true and no validation implemented
Reliability & Observability
2/10
Stability and monitoring
Light observability via console.debug and minimal reliability handling; basic env loading and a Redis retry_strategy are present but there is no structured logging, timeouts, backoff with jitter, or graceful shutdown handling.
Evidence
books-docker-API-master/services/cache.js: console.debug logging and redis.createClient with retry_strategy
multithreaded-sort-as-a-service/api/server.go: godotenv.Load with fatal log on error but no graceful shutdown
Expertise
Node.js• Middle
Go Development• Middle
Technologies
Python• 6y+
Rust• Junior • 3y+
Node JS• Middle
MongoDB
Redis
Rest API
gRPC• 3y+
Express
Azure
CI/CD• 3y+
AWS• 4y+
Kubernetes
Dotenv
Azure Cosmos DB
Azure AKS
Recommendations
- Develop small-to-medium REST services that need caching and fast read paths, using the existing Mongoose+Redis cache pattern and expanding it with metrics and invalidation policies.
- Build concurrent Go microservices or CLI tools where goroutines, channels and WaitGroup patterns are required, and harden them with input validation, edge-case handling and graceful shutdown.
- Improve production readiness by adding structured logging, health checks, timeout and retry policies with backoff, and automated tests and migration scripts for the data layer.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
Middle DevOps Engineer
Confidence: Medium Generalist
Go developer at a middle level specializing in small concurrent web services. The strongest proven skill is implementing Go concurrency patterns, demonstrated by api/controllers/sort_controller.go which uses goroutines, sync.WaitGroup and a buffered channel to implement a timing-based sort. There is no evidence of production CI/CD pipelines, infrastructure-as-code, observability, tests, or cloud architecture in the public code, and the runtime Docker setup uses a development server rather than a compiled production binary.
CI/CD Pipelines
1/10
Automated build and deploy
Minimal CI/CD evidence; only Dockerfile and docker-compose present, no pipelines, reusable workflows, or deploy gates.
Evidence
multithreaded-sort-as-a-service/Dockerfile
multithreaded-sort-as-a-service/docker-compose.yml
Infrastructure as Code
Managing servers with code
Not evidenced in public code
Containerization & Orchestration
2/10
Working with containers
Basic containerization using a Dockerfile and docker-compose; no multi-stage builds, non-root user, resource requests, or orchestration configuration.
Evidence
multithreaded-sort-as-a-service/Dockerfile
multithreaded-sort-as-a-service/docker-compose.yml
Observability & Monitoring
Watching system health
Not evidenced in public code
Reliability & Incident Response
1/10
Keeping systems up
Some concurrency patterns and basic synchronization are implemented in code, but there is no production reliability engineering, graceful shutdown, deploy strategy or runbooks.
Evidence
multithreaded-sort-as-a-service/api/controllers/sort_controller.go
Cloud & Cost Optimization
Smart use of the cloud
Not evidenced in public code
Technologies
Containers
Go• Middle • 4y+
Docker Compose
Recommendations
- Build containerized, production-ready Go services that compile to a single binary and include a Dockerfile multi-stage build and a non-root runtime user.
- Add CI pipelines (GitHub Actions or similar) with build, test and image-publish stages and a caching strategy for Go modules.
- Introduce basic observability: structured logs, Prometheus metrics and a simple dashboard, plus at least one alert and a small runbook.
- Replace timing-based sorting with deterministic algorithms or add input validation and edge-case handling (divide-by-zero when min==max), and add unit tests for core functions.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories: