Software Engineer, Backend Interview Experience - Remote, Oregon
Process
Multiple stages, exactly what they described on the website, but a little bit slower. Difficulty increases in each stage. They test everything, including your skills, personality, technical knowledge, and your overall approach to engineering. Some of the questions were open-ended, perhaps for checking our viewpoint.
Questions
On what kind of timeline are you looking for a new job?
Do you have remote working experience?
Do you have an open source project that you own or contributed to that you feel particularly proud about? Could you provide a link to it or send a code sample?
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the GitLab Software Engineer, Backend role in Remote, Oregon.
Success Rate
GitLab's interview process for their Software Engineer, Backend roles in Remote, Oregon is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for GitLab's Software Engineer, Backend interview process in Remote, Oregon.
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.
