DevOps Engineer Interview Experience at Meesho – 2025
Meesho
General SRE Pattern
No specific, verified real Meesho DevOps candidate account was found. Built from generally reported real DevOps loop patterns.
Application Story
Candidates are often approached via LinkedIn by a recruiter, and the process moves through an online assessment, two technical rounds, and an HR round over about ten days.
Preparation Journey
Preparation should focus on cost-efficient infrastructure design, since Meesho's business model as a value-focused marketplace means engineering conversations reportedly emphasize cost awareness alongside reliability.
Why Selected / Rejected
Being able to talk concretely about trade-offs between reliability and infrastructure cost, not just pure uptime, tends to matter more here than at other product companies.
Resume Tips
For infra roles at cost-sensitive marketplace companies, quantify infrastructure cost savings you have driven. Understand cost optimization triggers in AWS.
Online — MCQ + Coding
This round includes MCQs on Linux fundamentals, basic networking, and AWS core services, plus a scripting problem asking for parsing a CSV of order records and computing total order value grouped by city.
Technical
This round covers Kubernetes Horizontal Pod Autoscaler configuration for a service with highly variable, sale-event-driven traffic, and AWS cost optimisation strategies specifically - when Spot instances are appropriate (stateless, interruption-tolerant batch workloads) versus when On-Demand or Reserved capacity is necessary (anything customer-facing where an interruption is directly visible). Interviewers typically push for rough cost numbers, not just conceptual tradeoffs, for a hypothetical fleet running mixed Spot and On-Demand.
Technical
This round covers a CI/CD pipeline design discussion for a service with frequent deploys, and a monitoring and alerting setup question specifically for handling a 10x traffic spike during a flash sale event - a strong approach proposes pre-warming caches and scaling infrastructure ahead of known sale windows rather than relying purely on reactive autoscaling, since reactive scaling alone is often too slow for a sudden, scheduled spike.
HR Round
This is a standard closing discussion on compensation expectations and current notice period.
Questions Asked at Meesho in the DevOps Engineer Interview
Online — MCQ + Coding Round
This round includes MCQs on Linux fundamentals, basic networking, and AWS core services, plus a scripting problem asking for parsing a CSV of order records and computing total order value grouped by city.
Technical Round
This round covers Kubernetes Horizontal Pod Autoscaler configuration for a service with highly variable, sale-event-driven traffic, and AWS cost optimisation strategies specifically - when Spot instances are appropriate (stateless, interruption-tolerant batch workloads) versus wh …
Technical Round
This round covers a CI/CD pipeline design discussion for a service with frequent deploys, and a monitoring and alerting setup question specifically for handling a 10x traffic spike during a flash sale event - a strong approach proposes pre-warming caches and scaling infrastructur …
HR Round Round
This is a standard closing discussion on compensation expectations and current notice period.
Prepare for this Role
At a Glance
DevOps Engineer at Other Companies
Have your own story?
Share it and help the next candidate prepare.
Comments
Loading comments...