Software Engineer, Backend Interview Experience - United States
Process
Applied in the second week of January and didn't hear from a recruiter until the end of February. The recruiter showed up 6 minutes late and did not apologize for it.
For the next 15 minutes, they were disingenuous, disinterested, and condescending. They failed to expand on the details of the position or the team. When asked further about the role, they sent me a link to the GitLab CI/CD documentation.
This company can't even tell a solid Software Engineer from a Rails coder. Here's a piece of advice for Gitlab: RoR IS NOT A TECH STRATEGY.
Questions
Have you used GitLab before?
What is your Rails experience?
Have you used GitLab before?
Are you familiar with Agile?
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
- 5.0Great remote-first companySenior Software Engineer • Current EmployeeNovember 11, 2025Pros: Good WFB, competitive pay, and remote.Cons: Management is not that great.
- 4.0Good company, solid cultureSolutions Architect • Current EmployeeNovember 8, 2025Pros: Solid and powerful product, friendly collaborative team members, and overall a pretty good work culture that allows for a healthy work-home life balance.Cons: Sales motion can be challenging, and some internal company turbulence as GitLab matures as a company and goes through some growing pains.
- 5.0Very good place to workSolution Architect • Current EmployeeLondon, England, United KingdomOctober 30, 2025Pros: Flexible work with manageable shiftsCons: Career progression paths can be hard to achieve.
