Operations Engineer Interview Experience - San Francisco, California
Process
The process began with a standard call from the recruiter, followed by a handover to Engineering Managers. The hiring manager was arrogant and asked me questions unrelated to the job role. For example, they asked, "How would you architect this application?" I thought I had applied for an Operations Engineer position, not an Enterprise Architect role.
I received the standard rejection email within hours.
Questions
Recruiter: Why Slack?
Describe past job responsibilities (all listed on resume).
Challenges you have faced.
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the Slack Operations Engineer role in San Francisco, California.
Success Rate
Slack's interview process for their Operations Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having mixed feelings for Slack's Operations Engineer interview process in San Francisco, California.
Slack Work Experiences
- 4.0Slack is good. But worse than beforeSoftware Engineer • Current EmployeeSan Francisco, CAJuly 10, 2024Pros: - Challenging work and interesting problems - Great work culture - Smart peopleCons: Comp decreased after the acquisition.
- 4.0Smart colleagues, but many projects never launchedSoftware Engineer • Former EmployeeSan Francisco, CAMay 10, 2026Pros: Got to work with a lot of smart people.Cons: A lot of the project that I worked on never shipped.
- 5.0Great cultureSoftware Engineer • Current EmployeeSan Francisco, CAMarch 1, 2024Pros: Great people who are trying to hold the line.Cons: Salesforce now has the reins.
