Developer Advocacy
We inspire and enable developers to be more productive with GitLab. We bring our technical expertise to demos, content, and collaboration with field teams, customers, and developer communities to adopt Agentic AI and DevSecOps use cases in practice. Our hands-on experience informs product feedback and contributes to product and go-to-market strategy.
QuickLinks
Content and projects
- Content Library: Find demos, presentations, and other technical content.
- Content creation: Learn about the content we create.
- Team Projects: Explore our demos, research, and automation projects.
Events and speaking
- Team Calendar: Speaking engagements, events, and CFP dates.
- Event planning and reporting: Evaluate events, prepare content, and share results.
- Call for Papers and speaking resources: Find opportunities and prepare proposals and talks.
Tools and shared resources
- Tools and Platforms: Community platforms, access, automation, and moderation.
- Team Development Environments: Set up environments for demos and technical work.
- Team Shared Drive: Shared team documents and resources.
Want to work with the team?
Explore collaboration
Submit a request
- Request Developer Advocate support
- Request community response support
- Request content
- Request competitive research
Strategy
Developer advocacy is an evolving, complex field.
Our team focuses on areas aligning with the company’s areas of interest including:
- AI: enable teams to achieve success adopting agentic AI. By leveraging speed with security across the SDLC, we help teams accelerate software delivery.
- DevSecOps: We want our work to speak to not only developers but all team members involved in the DevSecOps lifecycle to deliver working code to production: Product Managers, software engineers, system and DB administrators, designers, test engineers, security engineers, operations engineers, platform engineers, SREs, development managers and executives, etc.
- Enterprise: Developers and DevSecOps professionals in the enterprise have special constraints and needs. Often these are glossed over with easy “throw out your architecture and use this new shiny thing” - we won’t do that, we’ll acknowledge real-world challenges, legacy code, and enterprise constraints and help people solve those problems as well. When applicable, we switch roles into consulting and support.
KPIs
The KPIs metrics we use to measure our impact are:
- Number of developer engagements (i.e. community members who react, post, or respond to our posts) per month vs. goal & Year-over-Year trend
- Percentage of positive sentiment per month vs. goal & Year-over-Year trend
We recognize these KPIs and metrics don’t capture the impact of the diverse range of work that our team does but understand that tradeoffs can be necessary to effectively communicate our impact within GitLab.
What fits in our strategy
When we are reviewing opportunities or requests for support, we must be able to answer yes to each of these questions to move forward with the work:
- Will this work support, grow, and/or engage GitLab customers and community members?
- Is there a measurable impact against one of our team’s KPIs?
- Has an issue been created to define the work and assign a DRI?
If the answer to any of the above questions is “no”, we ask the requestor to take one of the following actions:
- Make adjustments so we can take on the work.
- Find another team that is better suited to deliver the work.
- Come to an agreement that the work should not be done.
Team members and focus areas
We are members of the Developer Advocacy team.
| Team member | Focus areas | Languages | Projects | Technologies | Resources |
|---|---|---|---|---|---|
| Colleen Lake Developer Advocate |
Embedded Systems, GitLab Duo, Community Engagement | English | Event Support, Sales Enablement, Demo Videos, Webinars | Javascript, C++, Embedded | |
| Daniel Helfand Developer Advocate |
DevSecOps | English | CI/CD, Kubernetes, Go | ||
| Fatima Sarah Khalid Lead Developer Advocate |
Community Engagement, DevSecOps | English | LinkedIn Live, Community Engagement | CI/CD, C++, PHP, JavaScript | |
| Fernando Diaz Principal Developer Advocate |
DevSecOps with a focus on Security and Compliance | English, Spanish | GitLab demos on YouTube, Analyst relations demos, event support, Security and Governance tutorials | Security, Kubernetes, CI/CD, Python | |
| Itzik Gan-Baruch Staff Developer Advocate |
DevSecOps with a focus on CI/CD, CI/CD Catalog, Security | English, Hebrew | Product tours, Click-through demos, CI/CD components | Remote Development, CI/CD, Value Stream Management | |
| John Coghlan Senior Director, Developer Advocacy |
Strategy and Planning in Developer Advocacy | English | Website | ||
| Michael Friedrich Principal Developer Advocate |
DevSecOps with a focus on Agentic AI modernization, AI SME | English, German | maintained talks, event strategy, competitive research | DevSecOps, AI, Embedded, Python, C/C++, Rust | README, Talks, Portfolio |
| William Arias Staff Developer Advocate |
DevSecOps with a focus on AI/ML, Sec and Data | English, Spanish | Support Ticket Sentiment Analysis, Competitive Research, Analyst relations demos, End-to-end DevSecOps Platform | CI/CD, AI/ML, Kubernetes, Security, Python, C |
What we do
Our developer advocate team can be summarized by the “Three Cs”:
- Content creation: This is what many often think of when thinking of the traditional role of developer relations: writing blog posts, delivering technical talks, participating in podcasts or panels, and sharing ideas and thoughts on social media. Content creation also includes assets co-created with other GitLab teams, inside and outside of Marketing.
- Customer and community engagement: Our team regularly engages with GitLab customers and the wider GitLab community when they have questions, concerns, and feedback. This happens during in-person and virtual events, webinars, and meetings and online via GitLab issues, the GitLab Forum, Hacker News, and other social media sites.
- Consulting: Within GitLab, our team represents the voice of the community. When other teams are working on changes or decisions that will impact customers and the community, we will educate them on our customers and community, advocate for their interests, and work to ensure that any potential impacts are clearly understood and addressed when communicating such changes. Our team also shares our knowledge of industry trends, emerging tools, social media strategy, and other skills to support our teammates in achieving their goals in alignment with GitLab’s Cross-functiona Optimization subvalue.
Content creation
We build out content to help educate developers around best practices related to DevOps, GitLab, remote work, and other topics where we have expertise. Content includes presentations, demos, workshops, blog posts, and media engagements. Content creation also includes assets co-created with other GitLab teams, inside and outside of Marketing.
Please read the Content handbook to learn more about the content workflow, library and distribution with UTM tracking.
Customer and Community Engagement
Our team regularly engages with GitLab customers and the wider GitLab community on the GitLab Forum, Reddit, and Discord. Developer Advocacy is the DRI for questions and strategy on these platforms, and uses Common Room to review community insights.
See the Tools and Platforms handbook for platform guides, access, and operational workflows. For moderation and escalation guidance, follow the Code of Conduct enforcement process.
Consulting
Developer Advocates serve as consultants and subject matter experts (SMEs), leveraging their expertise and experience to support teams and customers with product features, new SKUs, and other topics.
Please read the Consultancy handbook to learn more about consultancy requests, decision matrix, and examples with GitLab Duo / AI adoption.
Other activities
Community Response
Given the Developer Advocate team’s understanding of our community and broad knowledge of GitLab, we will engage in the response of situations that require intervention to address urgent and important concerns of our community members. We have a documented process for how we manage these situations.
Event support
The Developer Advocate team plays a key role in supporting events. We work closely alongside Corporate Event Marketing to provide strategic content and assistance for both corporate and third-party sponsored events. This collaboration ensures the success and seamless execution of various gatherings. To learn more please refer to the Events page.
Developer Advocates submit proposals and speak at events as part of their role. See the CFP handbook and speaking resources to find events, track proposals, and request help with a submission or presentation.
We also help team members prepare for speaking opportunities at local tech events and meetups. If you’d like help preparing for such an event, please reach out to us in the #developer-advocacy Slack channel or create an issue using the Developer Advocate Request template.
Release Advocacy
Developer Advocates should always be prepared to promote our monthly release and engage in community response on release days given the historical performance of release posts on Hacker News.
Social media
We build our thought leadership and distribute our content on social media. See Developer Advocacy on Social Media to learn more about our strategies and become a GitLab advocate yourself.
Spokespersons
Developer Advocates are subject matter experts (SMEs) in their focus areas, and collaborate with the Corporate Communications team to provide media coverage in the form of interviews, podcasts, content by-lines, etc. Developer Advocates are GitLab spokespersons and are required to take relevant training as determined by the Corporate Communications team.
Projects
Our team maintains projects to provide GitLab use cases for content creation (demos, recordings, blog posts, workshops, talks, etc.), help showcase technical concepts and research to customers, and automate our team processes. We work in public by default, so that everyone can learn and contribute. See Developer Advocate Projects for a list of all of those projects.
How we work
See the team workflow handbook for internal issue templates, issue boards, and how we track our work.
Find us on Slack
GitLab team members can reach us in the #developer-advocacy Slack channel.
We use #developer-advocacy-updates for content shares and other updates that don’t warrant generating noise in the larger channel. Many updates are automated using Workato workflows.
Community insights are automated in #community-pulse, including posts from the forum, Reddit and Hacker News.
Team touchpoints
- Dev Advocacy team meeting (weekly) - Agenda: search for
Developer Advocacy Weeklyin GDrive. - Dev Advocacy Showcase (monthly) - Agenda: search for
Developer Advocacy Showcase [monthly]in GDrive. - 1:1 meeting between each team member and their manager (weekly)
Reporting
Most of our results reporting is automated through triage bots and metrics collection.
We report on our key metric in the Marketing Exec Scorecard and discuss what is influencing the metric in the Marketing Leadership Team (MLT) Metrics weekly meeting.
Calendar
The Developer Advocate calendar provides insights into speaking engagements, important events, CFP timelines, and other dates. Learn more in our CFP handbook.
Developer Advocacy Community Response Process
Consultancy workflows for Developer Advocates
Content library and workflows for Developer Advocates
Development Environments for Developer Advocates
Developer Advocacy Events
Hacker News
Learn Developer Advocacy
Developer Advocacy: Mentoring and Coaching
Projects
Developer Advocacy on Social Media
Developer Advocate Team Workflow
Developer Advocacy Tools and Platforms
8863af2f)
