Taro Logo

Senior Build/Release Engineer Interview Experience - San Diego, California

February 1, 2013
Negative ExperienceNo Offer

Process

Interviews:

  • Two phone interviews (1 hour each)
  • Two onsite interviews (2 hours each)

Process:

I applied for the role and was called approximately a week later by the hiring manager. I was asked fairly basic questions relevant to the role of a build/release engineer. HR requested a 4-5 hour interview (which was way too long), so we decided to split it into two interviews.

The first interview, I met with a developer and QA engineer. Overall, they had good attitudes about the importance of build engineers on a development team. I had another interview with an existing build engineer who had a major chip on their shoulder. There seems to be a huge disconnect between the build/release engineer and the development team. The last in-house interview was with a "platform" developer who preferred to brag about their accomplishments as opposed to asking questions pertinent to the interview.

Questions

Given a set of tests in two lists – expected and actual – write some code to output all tests that are different from or additional to those expected.

What is the algorithmic complexity of your solution?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the ServiceNow Senior Build/Release Engineer role in San Diego, California.

Success Rate

0%
Pass Rate

ServiceNow's interview process for their Senior Build/Release Engineer roles in San Diego, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for ServiceNow's Senior Build/Release Engineer interview process in San Diego, California.

ServiceNow Work Experiences