GitLab Solutions Architect Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 16 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at GitLab.
GitLab
Solutions Architect
Entry Average Neutral experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral
HR Screening via Phone, General questions about you and what you are looking for a job, are you actively interviewing and asking about prefered start date. I stopped at the screening because I have not graduated as the job need to be filled before my graduation.
Confirmed questions2 questions
- What kind of company are you targeting?
- Tell me about yourself and your project.
GitLab
Solutions Architect
Mid Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Background check Offer
Interview formats
Behavioral Technical
Applied online and got a recruiter call that was supposed to be 30 mins but went for an hour cause the recruiter didn't know what she was doing. She kept asking about my experience, and I answered, but she had more questions. It felt like an interview. Then, I had a call with the hiring manager, who was arrogant and was smirking and laughing at my responses. He asked ridiculous questions like, "What does teamwork mean to you?". He then said that they have candidates in the final stages and he plans to move forward with one of them, so he wanted me to be aware so they don't waste each other's time. I received a generic rejection email.
Confirmed questions1 question
- In your own words, what is teamwork?
GitLab
Solutions Architect
Mid Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Panel Offer
Interview formats
Behavioral Technical Presentation
The interview process at GitLab was really good. First, HR did a screening interview, then I interviewed with the hiring manager. After that, I met with a peer Solutions Architect. The final stage was a demo to a panel. Everyone was super friendly and made me feel welcome. GitLab gave me lots of helpful info and system access to get ready for the demo. The whole thing took about 2.5 months and they were always quick to respond and gave me good feedback. I was happy to get an offer at the end, which I accepted. Big thanks to everyone I talked to for making it a great experience!
Confirmed questions1 question
- Can you tell me if GitLab integrates with other DevOps tools?
GitLab Solutions Architect Interview Questions
Quoted word for word from GitLab interview reports.
“What is the definition of value?”
Read reports →“If a customer adopts GitLab, can they still use some of their current tools?”
Read reports →“What is the value proposition of CI/CD toolchains, like GitLab?”
Read reports →“Can you describe the difference between Continuous Deployment and Continuous Delivery?”
Read reports →“Can you tell me if GitLab integrates with other DevOps tools?”
Read report →“Could you explain what CI/CD is?”
Read report →“In your own words, what is teamwork?”
Read report →“What are the GitLab values you believe in?”
Read report →“Can you do a demo?”
Read report →Formats, difficulty and experience
Across all 16 GitLab interview reports.