Process
I had two interviews, one with a technical engineer and one with one of the directors.
Then I had to chase the internal recruiters for 6 weeks and send 5 emails to ask for a yes or no answer. They didn't even bother to answer my emails.
Six weeks later, I got rejected with one of those no-reply automated emails sent to me with no feedback.
I found it extremely unprofessional and disrespectful.
It's not a very difficult task to answer your candidate's emails or give them feedback.
Questions
Usual interview questions.
Linuxy questions and some design questions.
What's SRE, etc., etc.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the GitLab SRE role in Remote, Oregon.
Success Rate
GitLab's interview process for their SRE roles in Remote, Oregon is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for GitLab's SRE interview process in Remote, Oregon.
GitLab Work Experiences
- 5.0Great Job, Toxic CultureSoftware Engineer • Current EmployeeNoida, Uttar Pradesh, IndiaJune 20, 2024Pros: Everything good about this and our jobs.Cons: Very toxic things are there.
- 5.0Finally, a company that lives up to their valuesSoftware Engineer • Current EmployeeJanuary 17, 2021Pros: Lives up to their valuesCons: Cannot think of any, honestly.
- 5.0Transparent, Great Product, Remote Isn'tSolution Architect • Current EmployeeNovember 4, 2019Pros: Company continually lives up to CREDIT values. * Transparency: How many other companies are there where the community can see full, collaborative conversations between employees at all levels of the organization? * Contribute is a huge perk! The product itself is great and growing rapidly.Cons: - Remote work isn't for everyone. - Unsure of raise/promotion structure.
