Taro Logo

Devops Engineer Interview Experience - Amsterdam, Netherlands

March 1, 2021
Negative ExperienceNo Offer

Process

  1. HR call.

  2. Technical test. They asked to write Terraform/Ansible code to deploy frontend, backend, AWS LoadBalancer, and RDS with separated subnets. In my opinion, that's disrespectful at this point already. After the HR call, you know nothing about the company, their stack, and the team, but you have to spend some hours on the task.

  3. Technical interview. Just the same as people wrote before - very unprofessional:

  • The interviewers were unfriendly and just tried to punish with questions.
  • Too many useless questions about syntax.
  • It wasn't a discussion; it was just like an exam – they never tried to prove their point when they disagreed, so I always had to ask for their opinion.
  • The interviewer from Russia had really bad English skills; no complaints about the one from the Netherlands.

A big waste of time.

Questions

Here's a list of topics for review:

  • AWS (VPCs, Load Balancers, Autoscaling Groups)
  • Kubernetes (core services, EBS volumes for StatefulSets in different Availability Zones)
  • Terraform (common questions such as "what are three ways to reduce code," and "pros/cons of Terraform workspaces")
  • Python Concepts (data types, mutability vs. immutability, decorators)
  • Linux Debug Tools (name and describe specific tools)

Was this helpful?

Interview Statistics

The following metrics were computed from 4 interview experiences for the Miro Devops Engineer role in Amsterdam, Netherlands.

Success Rate

0%
Pass Rate

Miro's interview process for their Devops Engineer roles in Amsterdam, Netherlands is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Miro's Devops Engineer interview process in Amsterdam, Netherlands.

Miro Work Experiences