- Location
- Bengaluru, Karnātaka, India
- Workplace
- Onsite
- Type
- Full-time
- Department
- Technology
- Seniority
- Senior
- Source
- Recruitee
Description
Role: SDET / Senior SDET — Backend & Scalable Automation
Team: Lenskart Platform Engineering
Experience: Substantial hands-on backend automation
About the team
Lenskart's warehouse management platform is a Kafka-driven ecosystem of roughly 40 microservices spanning procurement, receiving, the inventory ledger, picking, quality control, packing, manifesting, and dispatch. It's the system that decides how a pair of glasses moves from a vendor shipment to a customer's doorstep, across every geography Lenskart serves. It runs on async event chains, shared inventory ledgers, and dozens of services calling each other in real time — which makes testing it a genuinely different problem from testing a typical CRUD app.
What you'll own
· End-to-end automation across the fulfillment chain — picking → QC → packing → manifest → dispatch — spanning 30+ services, not a single app.
· Event-contract testing on Kafka — validating producer/consumer correctness across async hops (order hand-off, QC-pass events, manifest-close events, exception routing) where a broken contract fails silently until it doesn't.
· Data-consistency and reconciliation testing across the shared inventory ledger and the consolidated inventory layer — this is the class of bug that doesn't crash anything, it just quietly oversells stock across channels.
· Scaling the automation framework itself — distributed/parallelized test execution, containerized test runners, and CI/CD integration so suites stay fast as the service count keeps growing.
· API and contract testing across REST/Feign inter-service calls, plus failure-injection testing for the exception-management state machine (retries, dead-letter topics, escalation paths).
· Performance/load testing for peak-demand periods.
· Chaos testing for Blast radius.
· Partnering directly with engineering leads on quality gates and shift-left practices and sitting in architecture reviews for new services as a design-time voice, not a post-release gate.
· Mentoring — raising the automation bar across the SDET function, not just your own output.