Gitlab Customer Success Engineer at GitLab providing technical product expertise and best practice guidance post-sale. Role includes delivering enablement through webinars, labs, and on-demand engagements to support GitLab adoption.
Responsibilities
Engage with customers via Zoom calls and email as a technical consultant during the post-sales journey, providing product, solution, and best-practice guidance.
Partner with Customer Success Managers to go deep on GitLab use case implementation (for example: source code management, continuous integration, continuous delivery, DevSecOps, and Agile Planning).
Deliver practical, customer-specific enablement through webinars, hands-on labs, office hours, and on-demand engagements in a pooled support model (not dedicated to a single account)
Provide technical and architectural guidance that helps customers adopt GitLab capabilities and connect technical decisions to the outcomes they care about.
Align with Account Executives and Renewals Managers to share customer-facing subject matter expertise that supports customer business objectives
Develop and deliver workshops, demos, and other reusable enablement content in collaboration with cross-functional partners.
Build and maintain specialty competency in one or more technologies aligned to GitLab's market focus through training, certification, and creating working examples for internal and customer use.
Contribute to customer-facing learning resources, including GitLab documentation, YouTube content, and enablement programs such as the Digital Journey.
What you'll bring
Experience supporting one or more GitLab use cases (source code management, continuous integration, continuous delivery, DevSecOps, or Agile Planning) and enabling customers with practical, in-depth guidance.
Proficiency with DevSecOps tools or adjacent highly technical tooling, with the ability to translate tool capabilities into customer outcomes.
Technical background in software development or systems engineering, including comfort discussing architecture, workflows, and implementation tradeoffs.
