Process
Answer some questions (2 hrs), HR Screening call (30 min), then a pairing session (2 hr).
Was told they'd get back to me in a few days, but haven't heard back, and it's been a few weeks.
I really wish they'd just say no if they're going to reject you, rather than leave you in complete silence for months.
This has been a huge time investment with nothing, not even feedback, in return.
Questions
How does a request travel through the browser?
Was this helpful?
Interview Statistics
The following metrics were computed from 5 interview experiences for the GitLab Software Engineer, Backend role in United States.
Success Rate
GitLab's interview process for their Software Engineer, Backend roles in the United States is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having negative feelings for GitLab's Software Engineer, Backend interview process in United States.
GitLab Work Experiences
- 3.0Good Pay, Awful SexismSoftware Engineer • Current EmployeeMelbourne, Victoria, AustraliaNovember 30, 2024Pros: Great pay and benefits for Australia. Incredibly flexible.Cons: Probably the worst sexism I have experienced in my decade-long career. The promotion process is unclear. Yes, there is a table in the handbook, but it's just vague corporate language.
- 5.0Great Docs, Remote FocusBackend Engineer • Current EmployeeMumbai, Maharashtra, IndiaMay 21, 2019Pros: Flexible work hours A high-quality and efficient team. Everything you need to know is documented!Cons: Work only if you enjoy a remote (virtual) setup!
- 5.0Simply a great employerSenior Backend Engineer • Current EmployeeBern, SwitzerlandMarch 10, 2025Pros: Remote work Asynchronous communication No time-tracking (we measure results, not hours) Unlimited time-off policy Great projects to work on Amazing colleagues to grow withCons: Remote work is probably not for everyone.
