Operations Engineer Interview Experience - San Francisco, California
Process
Phone screen with the recruiter, 30 minute phone screen with the department manager, 30 minute coding challenge.
The people I spoke with made it seem like what they needed was someone with a strong background in managing systems through automation, but then gave me a test directed specifically at someone with a programming background. The person conducting the technical portion of my interview didn't even work in the department that I was interviewing for. As a result the coding challenge didn't appear to be all that relevant to the job I was interviewing for. I was expecting a technical interview focused on server administration and automation.
Under these circumstances I was caught off guard and as a result performed far worse than I would have under normal conditions. Not really happy about that, but I think it comes down to the poor definition of "DevOps" rather than my skills or the position they were looking to fill at the company. If presented with a more appropriate technical interview, I have no doubt they would have made an offer.
Questions
Write a script which generates an array of all number pairs from a set which uniquely add to a specified sum.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the PagerDuty Operations Engineer role in San Francisco, California.
Success Rate
PagerDuty's interview process for their Operations Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for PagerDuty's Operations Engineer interview process in San Francisco, California.
PagerDuty Work Experiences
- 5.0Great Work EnvironmentOperations Engineer • Current EmployeeSan Francisco, CaliforniaSeptember 8, 2014Pros: This has been the best place I've worked at so far. Everyone cares about each other and the work we are doing. When mistakes are made, we acknowledge and collectively address it. I also feel like all layers of management care about the individuals who work here. There is daily catered lunch, regular social evenings at the office, ping pong, foosball, and good quality beer (we do have PBR also if you're more in to water). The work to life balance is good. Being on-call you are expected to be available once a week every few weeks. Even then, these shifts are usually quiet. And when on call, there is plenty of breathing room to allow you to get plenty of rest after a rough night. To reuse something that was said to me by someone here: "Every day of my life I get to work with the smartest people I know."Cons: There are not any that I can think of.
- 5.0Best workplace i have worked till nowOperations Engineer • Current EmployeeSan Francisco, CaliforniaJuly 2, 2014Pros: - Leadership team is technical - Compensation is on par with market - Product is getting better every day, which gives motivation to the entire organization - No restrictions on opensource adoption and contribution (as long as it does not involve core products) - Ability to take risk (in terms of new technology, tools, stacks, people etc) and iterate quickly and learn from failure. And internalizing the same as a company culture, it's just awesome - Attitude to embrace remote working, this is crucial if you have family and you stay outside SF (somedays commute is just horrible, due to games, road closures, public commute issues etc)Cons: - Rapidly growing mid-management layer, which creates silos and information loss between hops. - Being in SF, it's becoming increasingly difficult to commute.
- 5.0great companySoftware Engineer • Current EmployeeSan Francisco, CaliforniaMarch 22, 2024Pros: Friendly people, good perks, and top product in the marketCons: Leadership sometimes doesn't seem to know how to make the product better.
