DevOps Engineer Interview Experience at Lenskart – 2026

This recruiter screen covers infrastructure background and specifically probes for multi-cloud experience, since the team actively works across more than one cloud provider rather than being consolidated onto a single vendor.

This round covers configuration management specifically, asking how to manage consistent server configuration across a mixed fleet using both Ansible and Chef, relevant when a team is mid-migration from one to the other. A sound approach runs both in parallel scoped to distinct, non-overlapping host groups during migration rather than a risky big-bang cutover, with a clear tracked list of which hosts have migrated to avoid configuration drift between the two systems during the transition period.

Candidates are asked to design infrastructure for handling a large seasonal sale event where e-commerce traffic spikes dramatically while retail-store POS traffic stays roughly constant, and both share some backend inventory services. A strong approach proposes traffic-source-aware autoscaling that scales the e-commerce-facing tier aggressively while keeping the POS-facing tier's scaling more conservative, plus a shared inventory service with a read-replica layer specifically to prevent e-commerce read load from degrading POS transaction latency during the sale, since a POS failure at checkout in a physical store has a much more immediate, visible customer impact than a slow e-commerce page load.

This standard closing HR round covers why Lenskart specifically, notice period, and a couple of situational questions about handling conflicting priorities - a strong example describes pushing back on a request to skip a staging deployment step under deadline pressure, explaining the tradeoff rather than silently complying.