Senior DevOps Engineer Interview Experience - Remote, Oregon
Process
The solitary most disrespectful and disorganized interview process I have ever experienced. To begin with, the recruiter really likes to string together big words and use them improperly. I think this is her way of making up for being a disorganized space cadet with zero sense of respect or professionalism.
She would e-mail me, we would talk on the phone or exchange emails, and promise a response the next day. Two weeks later I would follow up, get told "tomorrow," and then I would forget about her for another week or two.
For at least 10 calls and 2 dozen emails, it resulted in two brief phone interviews:
- With someone who didn't seem to understand what position they were interviewing for.
- And someone without the technical knowledge to do the technical interview.
The inmates are running the insane asylum.
Questions
A few basic tech questions, which anybody with 2 years of experience could have answered.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Wikimedia Foundation Senior DevOps Engineer role in Remote, Oregon.
Success Rate
Wikimedia Foundation's interview process for their Senior DevOps Engineer roles in Remote, Oregon is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Wikimedia Foundation's Senior DevOps Engineer interview process in Remote, Oregon.
Wikimedia Foundation Work Experiences
- 5.0Great Team, Remote WorkFull Stack Web Developer • Current EmployeeFebruary 19, 2024Pros: Good team, possibility to work remotely.Cons: I don't see a single flaw.
- 4.0Good culture, with listening earsTest Engineer • Current EmployeeNovember 12, 2023Pros: Allowance for growth and improvementsCons: No direct promotion path per se.
- 2.0Great org goal, good place for solo work, bad place for collaborationSoftware Engineer • Current EmployeeParis, FranceJuly 27, 2021Pros: Awesome goal Very well known product Non-profit with a tech side Good life/work balance Open source, and community focused Ok salary RemoteCons: Surprisingly, in the tech department, collaboration is extremely hard and painful, to the point of being avoided. Due to the lack of collaboration, all work is individualized: you do your work, don't touch anybody's. The same lack of collaboration, and a layered org/responsibilities, make any work that requires more than a layer extremely painful. That means that any meaningful work is either not done, or slow and painful, so there's an increasing pile of tech debt that nobody wants to tackle (and is encouraged not to). The focus on individual and hand-over-the-fence type of work also ends up with little project management knowledge in the org; one-person projects don't need it. This also creates a very damaging "us vs them" culture. Little learning opportunities. Limited progression opportunities. So, if you only want to do small things by yourself, it's a great place to be. If you want to do anything else, you will probably not last much.
