
GitLab Sales Development Representative Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 19 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at GitLab.
SDR Manager
The hiring process included three steps: First, a screening call with a US-based HR Talent. Second, a meeting with the Hiring Manager, which was productive, relevant, and direct. Third, a panel presentation for SD/BD Leadership that focused on SDR Leader Experiences, Impact, and Value Add. However, it's worth noting that the Sales and Business Development Leadership team had a strategic restructuring overnight, which was a bit of a red flag. During the panel interview, which involved a presentation, the product functional leader on the panel was asked a lot of questions about hiring and collaboration with her team and product teams. This was concerning, showing a lack of clarity and communication internally. It also came out that the original Hiring Manager was no longer in that role. When asked if there were any concerns after all the discussions, he didn't have any comments, which was also a red flag.
- What are some examples of how SDR and Product teams work together?
Sales Development Representative
The recruiter reached out and was really fast to reply to my message. A few days later, I had a screening interview with the recruiter over Zoom. It was a well-run interview, and the recruiter was professional. I didn't get past the screening interview though.
- Can you give me a brief overview of yourself?
- What prompted your departure from your most recent job?
- What is your understanding of our company?
Sales Development Representative
Applied about 2.5 months back. The site said 4-5 business days between steps, but scheduling took way longer than that for me and others. It started with a screening call where I had to explain why I left all past jobs. Then, I waited 10 days to hear back and schedule the next call with the team lead. I really should have prepped more on Git, how Gitlab is different, and the distinctions between Atlassian and Github. They seem to want money-driven, competitive sales folks. After that, I had a call with the Director of Sales and Marketing. It was a pretty intense interview, and they really pushed me on technical details. A few days later, they let me know I didn't make it. The recruiter's emails were all generic, just for scheduling, and she never answered my questions about the process or my status, especially since it dragged on longer than advertised. The website mentioned getting feedback, but again, no reply to my email. While I think Gitlab could be a cool place to work and I did like the people I talked to, their hiring process needs to be more in line with what they post online.
- Can you explain what Git is, how Gitlab stands out, and what its features are? Also, what ideas do you have for improving Gitlab?
- Tell me about Git, how Gitlab is different, and the differences between Atlassian and Github.
- Can you explain more about these technical questions?
GitLab Sales Development Representative Interview Questions
Quoted word for word from GitLab interview reports.
“What is your understanding of developer tools?”
Read reports →“What are 3 things you've learned about GitLab?”
Read reports →“How would you handle a call with a very rude customer after it ends?”
Read reports →“Tell me about Git, how Gitlab is different, and the differences between Atlassian and Github.”
Read reports →“What are some examples of how SDR and Product teams work together?”
Read report →“Can you explain what Git is, how Gitlab stands out, and what its features are? Also, what ideas do you have for improving Gitlab?”
Read report →“Can you share an instance where you converted a customer objection into a new lead?”
Read report →“Can you describe what a typical day looks like for you?”
Read report →“What do you do outside of work to keep yourself motivated?”
Read report →Formats, difficulty and experience
Across all 19 GitLab interview reports.