Taro Logo

Devops Engineer Interview Experience

January 1, 2015
Positive ExperienceGot Offer

Process

I interviewed with Udemy, and while I am rating it as “easy,” I do not mean to say that it was not thorough.

To begin, there was an initial phone screen with the person who would then go on to become the main point of contact. There were then two interviews.

The first was a phone interview—kind of a “technical lite.” Most of the questions were both open-ended and about skills and technologies that I had listed on my resume, or were reasonable to be inferred from the position I was applying for (like the other Software Engineer review, I also got some Memcache and Redis related questions).

There were no arcane or obscure questions that so many interviewers seem to favor.

There was also a small coding portion to the phone interview.

The second interview was at their headquarters. It was on the longer side (5 hours), but broken up into reasonable time chunks (30-60 minutes) where I was interviewed by either one or two people per session.

The first two sessions did not have any whiteboarding, only questions about projects I had worked on. I find that type of question to be much less stressful to answer.

Only a couple of the sessions asked to straight-out solve problems (only one of which was the traditional whiteboard coding).

The reviewers were a pretty diverse set, from a couple of different teams and also different levels of experience working with the company. Most of the questions were targeted to my strengths.

There were a couple of questions asked about areas that are outside my skill set, and my interviewers explained to me what I was missing to be able to answer the question. So, I learned something new.

I would describe most of the interview time as very conversational. Not just grilling about the candidate's knowledge, but more like using the questions to start conversations about technical, business, and team-related things.

At the end, there was a debriefing interview, which was a sort of wrap-up, things to come, and let me know roughly what to expect moving forward.

Overall, I got feedback after every step of the process very quickly, and it is apparent that Udemy has put a lot of effort into figuring out what makes the interview process go well.

Questions

A couple of questions about HTTP headers. But it was pretty good motivation to sit down with Wikipedia and close that knowledge gap.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Udemy Devops Engineer role in United States.

Success Rate

100%
Pass Rate

Udemy's interview process for their Devops Engineer roles in the United States is incredibly easy as the vast majority of engineers get an offer after going through it.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for Udemy's Devops Engineer interview process in United States.

Udemy Work Experiences