SDET-QA

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 runs on async event chains, shared inventory ledgers, and dozens of services calling each other in real time. Team: Lenskart Platform Engineering. Experience: Substantial hands-on backend automation. A bug caught here isn't a UI glitch; it's a misship, a wrong invoice, or a SKU oversold across a live channel. Lenskart delivers across multiple geographies simultaneously, each with different tax regimes, couriers, and cutoff rules running through the same platform.

Responsibilities

End-to-end automation across the fulfillment chain (picking → QC → packing → manifest → dispatch) spanning 30+ services; Event-contract testing on Kafka, validating producer/consumer correctness across async hops; Data-consistency and reconciliation testing across the shared inventory ledger and the consolidated inventory layer; Scaling the automation framework (distributed/parallelized test execution, containerized test runners, CI/CD integration); API and contract testing across REST/Feign inter-service calls, plus failure-injection testing for the exception-management state machine; Performance/load testing for peak-demand periods; Chaos testing for blast radius; Partnering with engineering leads on quality gates and shift-left practices, and sitting in architecture reviews for new services as a design-time voice; Mentoring to raise the automation bar across the SDET function

Requirements

2+ years in automation/SDET roles, with real depth in backend API automation (REST + message-driven systems), not primarily UI automation; Strong Java + a test framework (TestNG/JUnit, RestAssured or equivalent); Hands-on experience testing event-driven/Kafka-based architectures; Strong SQL and comfort reasoning about data consistency across distributed services; CI/CD experience (Jenkins/GitLab CI) and experience scaling test execution (parallelization, containerization); Solid grasp of microservices failure modes (idempotency, retries, eventual consistency, partial failure)

Nice to have

Experience testing warehouse, OMS, or logistics/supply-chain platforms; Load-testing tools (JMeter/locust/gatling/k6); Exposure to Elasticsearch, Redis, and observability tooling; Chaos-engineering or fault-injection experience