Netomi logo

Netomi Devops Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 5 interview experiences · FREE TO READ

2.8 Rounds average
Difficult Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Netomi.

Showing 3 of 5
Netomi logo
Netomi

DevOps Engineer

Engineering · a year ago

Mid Difficult Positive experience Accept offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical System Design

The interview process was awesome. The interviewer was really professional and prepared, and they made it feel welcoming, so I felt comfortable talking openly and thinking through stuff. The questions were relevant, challenging but fair, and they really checked my technical and problem-solving skills. What was cool was how structured the interview was, they were clear about what they wanted and focused a lot on real-world situations. The interviewer was engaging and gave me good info about the job and company culture, which made it feel like a real conversation, not just a test. All in all, it was a super positive experience and gave me a great vibe about the company's hiring and culture. I'd totally recommend this process!

Confirmed questions5 questions
  • Can you describe how you'd optimize a Kubernetes cluster for both performance and cost?
  • What distinguishes Horizontal Pod Autoscaler (HPA) from Vertical Pod Autoscaler (VPA)?
  • What's your approach to implementing network policies in Kubernetes?
Netomi logo
Netomi

Devops Engineer

Engineering

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Technical Behavioral Other

There is no structured process. Whatever comes to mind. First, they should learn how to treat people. They themselves say you don't join the company as ours is a small company and we get out salary if the application. or else we won't. I would like to ask them why they have opened the position. Worst interview process I never had my life.

Confirmed questions6 questions
  • Questions about Terraform?
  • Questions about Docker?
  • Questions about shell scripting?
Netomi logo
Netomi

DevOps Engineer

Engineering

Staff Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Technical System Design

So the job description they sent over didn't really match up with what we talked about. They said it was for someone with 3-5 years of experience, but the questions they asked were more for like a 10-12 year senior person. It felt kinda all over the place, not really a consistent vibe.

Confirmed questions1 question
  • Can you tell me about system scheduling in Linux?

Netomi Devops Engineer Interview Questions

Quoted word for word from Netomi interview reports.

What distinguishes Horizontal Pod Autoscaler (HPA) from Vertical Pod Autoscaler (VPA)?

Read reports

Could you write out the Terraform code for an IAM user module? This module should default to associating a "ReadOnly" policy with the user. However, it needs to be flexible enough to accept variables for permissions sets and policy names, allowing for a custom inline policy to be created and attached to the IAM user, overriding the default.

Read reports

Imagine two VPCs: VPC A contains a private subnet with an RDS database. VPC B has multiple private subnets and uses autoscaling to launch EC2 instances. If a certain number of instances fail to launch due to JDBC timeout errors, what are the potential reasons for this issue?

Read reports

How does Kubernetes manage stateful applications, and in what scenarios would you opt for a StatefulSet?

Read reports

Could you explain Kubernetes networking, covering ClusterIP, NodePort, and LoadBalancer services?

Read report

Can you help resolve a shell script execution issue on a machine?

Read report

Formats, difficulty and experience

Across all 5 Netomi interview reports.

Interview formats

Technical 41.7%
System Design 16.7%
Coding 16.7%
Behavioral 16.7%
Other 8.3%

Interview difficulty

Easy 0%
Average 40%
Difficult 60%

Candidate experience

Negative 60%
Positive 40%