Intervu is in beta — feedback welcome at support@intervu.io

GitLab Sales Development Representative (SDR/BDR) Interview Questions

30 real practice questions for the entry-level Sales Development Representative (SDR/BDR) role at GitLab (Developer Tools), spanning behavioral, problem solving, role knowledge, situational, and stakeholder. Open the sales funnel: prospect, qualify, run outreach and discovery, and book meetings for account executives. The first 3 questions below include what GitLab interviewers actually listen for, plus likely follow-ups.

Questions
30
Categories
Behavioral (6), Problem Solving (6), Role Knowledge (6), Situational (6), Stakeholder (6)
Difficulty mix
10 easy · 10 medium · 10 hard
Avg. answer time
~4 min

Behavioral Questions (6)

  1. 1.Tell me about a time you wrote something down — a process, a how-to, a set of steps — so that someone else could do it without asking you. What did you write and why?

    easy~3 min

    What interviewers look for

    • Candidate identified a recurring question or bottleneck and proactively created documentation to eliminate it — showing Handbook First instincts even without being asked.
    • The documentation was specific enough to be actionable by someone with no prior context, not just a vague summary.
    • Candidate made the documentation visible and accessible to others — shared it in a common location, linked to it, or updated it over time.

    Likely follow-ups

    • Did anyone actually use what you wrote? How did you know it was helpful?
    • If you were onboarding a new teammate to your current role today, what's the first thing you'd write down for them?

    Company context

    GitLab operates as an all-remote company with over 2,000 team members across 60+ countries, and its public handbook is foundational to how the company functions. The Handbook First principle means that if a process isn't documented, it effectively doesn't exist. For an SDR at GitLab — who may be onboarding fast, running sequences, and handing off to AEs — the ability to document outreach cadences, objection-handling scripts, or qualification criteria in a shared, findable format is a core job skill, not a bonus one.

  2. 2.Describe a time when you had a problem to solve and you went with the simplest, most obvious approach instead of something more complicated. Why did you choose that path?

    easy~3 min

    What interviewers look for

    • Candidate deliberately evaluated a more complex or exciting option and consciously chose the simpler one — not just defaulted to simple out of laziness or ignorance.
    • Candidate articulates a clear reason for the choice — faster to ship, easier to maintain, less risk, good enough to solve the problem — rather than just saying 'it was easier.'
    • The simpler solution actually worked and delivered the intended outcome, validating the pragmatic choice.

    Likely follow-ups

    • Was there any pressure — from peers, a manager, or yourself — to do something more sophisticated? How did you handle that?
    • In an SDR role, where would you apply this kind of thinking — what's one thing about prospecting or outreach that you'd keep dead simple?

    Company context

    GitLab explicitly values 'Boring Solutions' — the idea that the best tool for a job is often the most proven, least exciting one. For an entry-level SDR, this maps directly to prospecting: candidates who immediately reach for the most complex multi-touch AI sequence tool, or who overthink personalization to the point of paralysis, often underperform compared to reps who send clear, direct, well-timed emails using basic tooling. GitLab wants SDRs who default to what works over what impresses.

  3. 3.Tell me about a time you spotted a problem or gap outside your direct job and did something about it anyway. What was the situation and what did you actually do?

    medium~4 min

    What interviewers look for

    • Candidate identified a real gap that wasn't theirs to fix — in a process, a communication breakdown, a teammate's onboarding — and took a concrete action rather than just flagging it.
    • Candidate did this without being asked and without waiting for permission, demonstrating initiative consistent with GitLab's 'Everyone Can Contribute' principle.
    • Candidate describes the impact of their contribution — what improved, what was saved, what teammate benefited.
    • Candidate shows awareness that stepping outside their lane was appropriate and constructive, not territorial or overstepping.

    Likely follow-ups

    • Did anyone push back on you getting involved? How did you navigate that?
    • In an SDR role at GitLab, what areas outside pure pipeline generation do you think SDRs could contribute to — and would you?

    Company context

    GitLab's 'Everyone Can Contribute' principle is not a slogan — it means team members at every level are expected to propose and drive improvements, even in areas they don't own. For an SDR, this might mean improving a shared sequence template, flagging broken messaging in a campaign, updating a stale ICP definition, or writing up objections they're hearing so marketing can act on them. GitLab looks for SDRs who treat their role as broader than their job description.

  4. 4.Tell me about a time a colleague, manager, or someone from another team stepped into something you considered your responsibility. How did you react, and what happened?

    medium~4 min
  5. 5.You're the first SDR on a new prospecting motion — maybe a new vertical or a new ICP — and there's no playbook yet. How would you approach building and documenting a repeatable process from scratch so the next SDR who joins can ramp in days, not months?

    hard~5 min
  6. 6.You're getting low reply rates on your outreach sequences. Your manager suggests trying a new AI personalization tool everyone's buzzing about. What's your process for deciding whether to use it or stick with what you have?

    hard~5 min

Problem Solving Questions (6)

  1. 7.You have 50 accounts to work this week and no guidance on where to start. How do you figure out which ones to call first?

    easy~3 min
  2. 8.Estimate how many outbound emails you'd need to send in a month to book 15 meetings. Walk me through your math.

    easy~3 min
  3. 9.You're tasked with building a cold outreach sequence for a new segment GitLab hasn't targeted before — say, healthcare software companies navigating HIPAA compliance. You don't have messaging, you don't have case studies, and there's no prior playbook. What do you do?

    medium~4 min
  4. 10.Your AE tells you that three of the last five meetings you booked all had the same problem — the prospects didn't know what GitLab actually does beyond version control. What does that tell you, and how do you fix it going forward?

    medium~4 min
  5. 11.GitLab's total addressable market includes hundreds of thousands of software companies globally, but an SDR can only realistically work a few hundred accounts. How would you make the case to your manager that your specific account list is the right slice of that market — and how would you defend it if they pushed back?

    hard~5 min
  6. 12.Imagine GitLab launches a major product update — say, significant new AI features in GitLab Duo — and marketing sends you 200 inbound leads who responded to the launch campaign. When you start working the leads, you notice about 60% are from companies that are way too small to ever buy, and another 20% are existing customers. How do you handle this, and what do you tell your manager?

    hard~5 min

Role Knowledge Questions (6)

  1. 13.An SDR's core job is converting outreach into booked meetings. Walk me through the key metrics you'd track every week to know if your pipeline is healthy.

    easy~3 min
  2. 14.You're prospecting into a mid-market software company to sell GitLab's DevSecOps platform. Who are the people you'd try to reach, and how would you decide who to contact first?

    easy~3 min
  3. 15.You've sent 150 outbound emails this week across three different sequences and got a 2% reply rate. How do you figure out whether the problem is the list, the message, or the sequence timing?

    medium~4 min
  4. 16.A prospect you've been working replies to your email and says, 'We already use GitHub — why would we switch to GitLab?' How do you handle that in your response?

    medium~4 min
  5. 17.You've just finished a discovery call and the AE tells you the prospect was actually a poor fit — wrong company size, no active initiative. What does that tell you about your qualification process, and how do you fix it upstream?

    hard~4 min
  6. 18.You're asked to prioritize your outreach across 200 accounts in your territory. Some are large enterprises, some are mid-market, and a few are flagged as 'intent data' accounts showing research activity on DevSecOps topics. How do you sequence your effort?

    hard~5 min

Situational Questions (6)

  1. 19.You've booked a meeting with a VP of Engineering at a 300-person SaaS company. Two hours before the call, the AE emails you saying they can't make it and asks you to run the discovery solo. What do you do?

    easy~3 min
  2. 20.A prospect replies to your outreach saying they love what they've heard about GitLab Duo but their security team will never approve a cloud-based AI tool. They ask if there's a self-managed option. You're not sure. What do you do next?

    easy~3 min
  3. 21.It's the 20th of the month. You're two meetings short of your quota, your best prospect just pushed their timeline to next quarter, and your manager is asking for a realistic forecast. What do you tell them, and what do you do for the next ten days?

    medium~4 min
  4. 22.You've been assigned a named account list that includes a Fortune 500 company. You research it and find out they're a major GitHub Enterprise customer — and there's a public news story from last month where their CTO praised GitHub. How do you approach this account?

    medium~4 min
  5. 23.You're three weeks into a new outbound sequence targeting platform engineering teams. The sequence is getting replies but your manager tells you the meetings booked from it aren't converting past the first AE call — the AEs keep saying the prospects aren't actually qualified. How do you figure out what's broken and fix it?

    hard~5 min
  6. 24.You notice a teammate on your SDR team is booking significantly more meetings than you, and when you look at their sequence, you realize they're targeting smaller companies that are easier to book but rarely convert to revenue. Your numbers look worse but your meetings are with better accounts. Your manager hasn't noticed the difference yet. What do you do?

    hard~5 min

Stakeholder Questions (6)

  1. 25.Tell me about a time you needed help from someone who wasn't your boss — a peer, a teammate from another group, or someone senior to you — to get something done. How did you get them on board?

    easy~3 min
  2. 26.Tell me about a time you had to communicate bad news — a missed deadline, a mistake you made, something that didn't go as planned — to someone who was counting on you. How did you handle it?

    easy~3 min
  3. 27.You've booked a promising meeting with a DevOps lead at a target account. Two days before the call, the AE you're paired with sends you a Slack message saying they want you to requalify the account using a completely different set of criteria than what you've been using — and their criteria would likely disqualify this prospect. How do you handle it?

    medium~4 min
  4. 28.Imagine marketing runs a campaign that sends hundreds of leads into your queue, but when you work them, you quickly realize they don't match the ICP your AEs care about at all. How do you raise that with marketing without burning the relationship?

    medium~4 min
  5. 29.You send a cold outreach sequence to a senior director of engineering at a target company. They reply — but instead of setting up a meeting, they push back hard, saying they've heard GitLab's security scanning creates too much noise and slows down their developers. You've never dealt with this objection before and you're not sure if it's true. What do you do?

    hard~5 min
  6. 30.Your manager asks you to give feedback on the outbound sequence a more experienced SDR on your team has been running. You think two of the steps are off — they're contacting the wrong persona and the messaging undersells GitLab Duo compared to what prospects are actually asking about. How do you share that feedback without it feeling like an attack?

    hard~5 min

More GitLab interview questions