Skip to main content
⚙️

DevOps / SRE Interview Prep — Linux, Kubernetes, CI/CD — for engineers in Tashkent and Central Asia

DevOps interviews lean heavily on Linux fundamentals, container orchestration, and incident-response stories. Practice the questions Tashkent IT Park residents and EU remote employers actually ask, with real-time AI scoring on communication, technical depth, problem-solving, and cultural fit.

DevOps and SRE roles in Tashkent are hired by IT Park residents at scale, by fintechs who can no longer treat infra as “the developers' problem,” and by remote EU employers who pay a real premium for someone who can debug a production cluster in English on a Friday night.

The interview format is consistent: Linux fundamentals screen, one networking deep-dive, a Kubernetes troubleshooting question, a CI/CD or IaC design task, and incident-history behavioral questions. The questions below cover all five.

Core skills tested

  • Linux fundamentals: processes, signals, file descriptors, /proc
  • Networking: TCP, DNS, TLS, load balancers, Linux iptables / nftables
  • Containers and Kubernetes (pods, services, ingress, RBAC)
  • One IaC tool deeply: Terraform, Pulumi, or CloudFormation
  • CI/CD: GitHub Actions, GitLab CI, or Jenkins
  • Observability: Prometheus, Grafana, OpenTelemetry, log aggregation
  • One cloud deeply: AWS, GCP, or DigitalOcean
  • Incident response and writing useful postmortems

Salary ranges in Tashkent (2026)

Approximate. Remote-first European roles typically pay 30–50% above local rates.

Junior

10–15M UZS / month

Mid-level

20–32M UZS / month

Senior

40M+ UZS / month (or EUR remote)

What you will actually be asked

Pulled from real interviews recorded on NextSuhbat. Each item is a question you should expect, plus what the interviewer is really testing.

  1. 1

    Recruiter screen

    Walk me through the most painful production incident you helped resolve.

    Why it is asked: Two minutes. Symptom, suspect list, what you tried, root cause, and the change you shipped after.

  2. 2

    Technical

    What does it mean when df shows 0% free but du shows plenty of space?

    Why it is asked: Tests Linux internals — open file descriptors holding deleted inodes. Senior bar.

  3. 3

    Technical

    Walk me through what happens when a Pod fails to start in Kubernetes.

    Why it is asked: Cover image pull, init containers, readiness vs liveness, ImagePullBackOff vs CrashLoopBackOff, kubectl describe.

  4. 4

    Technical

    You see latency spike on a service. Walk me through the investigation.

    Why it is asked: Network → DB → app → upstream. Cover dashboards, percentile vs average, recent deploys, capacity, and rollback decision.

  5. 5

    Technical

    Explain the difference between rolling updates, blue-green, and canary deploys.

    Why it is asked: Tradeoffs in cost, risk, rollback speed. Tie each to when you would actually use it.

  6. 6

    Coding

    Write a shell pipeline that finds the top 10 IPs hitting an Nginx access log.

    Why it is asked: awk, sort -n, head. Tests basic Unix fluency.

  7. 7

    Coding

    Write a Terraform module that provisions an S3 bucket with versioning, lifecycle, and a least-privilege IAM role.

    Why it is asked: Tests real IaC habits — variables, outputs, no hardcoded ARNs.

  8. 8

    System design

    Design the deployment pipeline for a service that ships 10x a day across staging and prod, with zero-downtime rollouts.

    Why it is asked: CI stages, gating tests, canary, rollback, observability hooks. Cover the bad-deploy detour.

  9. 9

    Behavioral

    Tell me about a time you said no to a developer asking for prod access.

    Why it is asked: Tests judgment without sounding territorial. Frame as protecting the developer too.

  10. 10

    Behavioral

    Tell me about a postmortem you wrote that changed how the team operates.

    Why it is asked: Concrete change with a date and a metric. Vague answers signal you have not led one.

Practice these questions out loud — for free

Reading is not practice. Run a 20-minute AI mock interview in English, Russian, or Uzbek and get a scorecard against communication, technical depth, problem-solving, and cultural fit.

Start free mock interview

Built in Tashkent for Central Asia. All practice sessions support English, Russian, and Uzbek voice.