Solutions Architect Interview Experience - London, England
Process
The interview process at GitLab typically begins with the submission of an application, followed by an initial screening.
Candidates may then undergo a technical assessment and interview with the hiring manager.
Subsequently, a team interview and culture fit assessment may take place.
A reference check is conducted, and if successful, an offer is extended.
Finally, the onboarding process ensures a smooth transition for new hires joining the GitLab team.
Questions
Talk more on what you did in your current role.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the GitLab Solutions Architect role in London, England.
Success Rate
GitLab's interview process for their Solutions Architect roles in London, England is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for GitLab's Solutions Architect interview process in London, England.
GitLab Work Experiences
- 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.0Wonderful People, Many ChangesSolutions Architect • Former EmployeeApril 14, 2025Pros: A great place to work, surrounded by wonderful people.Cons: There have been a lot of changes recently.
- 5.0Work-life balance is the golden handcuffsSolutions Architect • Current EmployeeAugust 2, 2023Pros: Completely async organization. You work when you need to. Results are the only thing that matter. I truly believe it is as close as it will get to a meritocratic organization. Focus Fridays with no meetings pretty much means it's a 4-day work week. I'd say probably closer to a 4.5-day work week. Unlimited PTO without question. Within my first year, I took 2.5 months off, and my manager told me to take more.Cons: If you're not from a developer background or not technical generally, you have a super rough time onboarding and getting up to speed. Async work styles benefit some individuals more than others.
