Qdrant India Site Reliability Engineer Interview: Rounds, Questions and Preparation

What the job involves

Site Reliability Engineers at fast-growing global tech companies like Qdrant India ensure that vector databases and AI infrastructure stay fast, available, and scalable. Day to day, they automate deployments, monitor latency and error rates, respond to incidents, and improve system reliability through code. Freshers in this role typically start with observability, scripting, and basic distributed systems work.

Role and technical knowledge

1. 1

   What is the difference between a Site Reliability Engineer and a DevOps Engineer?

   Explain that SRE applies software engineering to operations, with error budgets and SLOs, while DevOps is a broader culture and practice. Mention that SRE often owns reliability targets and on-call.

2. 2

   How would you monitor a vector database service to ensure low latency for search queries?

   Cover metrics like p99 latency, query throughput, CPU and memory usage, and disk I/O. Mention Prometheus for collection and Grafana for dashboards, plus alerting on latency spikes.

3. 3

   Explain what a service level objective (SLO) is and why it matters for a fast-growing AI company.

   Define SLO as a target for reliability, like 99.9 percent availability. Explain that it helps balance feature velocity with user trust and guides alerting.

4. 4

   What is Infrastructure as Code, and how would you use it in a small team?

   Describe tools like Terraform or Ansible to define servers and networks in version control. Highlight repeatability, faster onboarding, and fewer manual errors.

Practical scenarios

1. 5

   A production database is returning high latency during peak hours. How do you troubleshoot?

   Start with dashboards and logs to find the bottleneck. Check CPU, memory, disk I/O, slow queries, and network. Suggest short-term fixes like caching or scaling, then long-term tuning.

2. 6

   You need to deploy a new version of a service with zero downtime. What steps do you take?

   Use rolling updates or blue-green deployment with health checks. Mention Kubernetes, canary releases, and rollback plans. Emphasize testing in staging first.

3. 7

   How would you set up alerting for a service that must not exceed 1 percent error rate?

   Define an error rate metric, use Prometheus alert rules, and set thresholds with a short duration. Include runbooks and avoid alert fatigue by tuning severity.

4. 8

   A disk on a production server is filling up quickly. What do you do?

   Identify large files or logs, rotate or compress logs, and clean temporary files. Add monitoring and automated cleanup. Investigate root cause to prevent recurrence.

Behavioural and situational

1. 9

   Tell me about a time you fixed a technical problem under time pressure.

   Use the STAR method. Focus on how you stayed calm, prioritized, and communicated. Highlight the outcome and what you learned.

2. 10

   How would you handle a disagreement with a senior engineer about a reliability fix?

   Show respect and data-driven discussion. Suggest running a small experiment or reviewing metrics together. Emphasize team goals over being right.

3. 11

   Describe a situation where you had to learn a new tool quickly for a project.

   Pick a real example, like learning Docker or a monitoring tool. Explain your learning approach, resources used, and how you applied it successfully.

4. 12

   Are you comfortable being on-call and responding to incidents at odd hours?

   Be honest but positive. Mention you understand the responsibility, value clear runbooks, and are willing to learn incident management. Show you can manage stress.

HR and company fit

1. 13

   Why do you want to work as a Site Reliability Engineer at a fast-growing AI infrastructure company?

   Connect your interest in reliability and automation to the company's need for scalable AI systems. Mention learning opportunities and impact.

2. 14

   Where do you see yourself in three years in this role?

   Show growth from junior SRE to owning critical services or mentoring. Align with the company's growth, like specializing in distributed systems or observability.

3. 15

   What do you know about our company's product or technology?

   Research the company's focus, such as vector databases or AI search. Mention a specific product or open-source project and why it interests you.

4. 16

   How do you prioritize your work when multiple tasks are urgent?

   Explain a method like impact versus effort or using a simple matrix. Mention communicating with stakeholders and focusing on customer impact first.