Dev Experience team

The Dev Experience team, or DevX for short, is a team focused on improving the developer experience of Sourcegraph as part of the Enablement org.




This section is a work in progress.



To collaborate, we use the following:

Work allocation

We aim to allow teammates the flexibility to work on incoming requests, tackle proactive improvements, and invest in long-term efforts to further our team goals, so as a rule of thumb:

  • We aim to spend 20% to 30% (~2-3 days every 2 weeks) of our time on making proactive impact, i.e. working on things that are aligned with the team’s mission, but aren’t on our roadmap.
  • If over 50% (~5 days every 2 weeks) of our time is spent outside of planned work (i.e support requests), we opt to discuss the scope and priority of the work with the team first.


This section is a work in progress.

We currently have weekly sync meetings and biweekly retrospectives.


Support is handled through the @dev-experience-support handle in Slack. Support on-call responsibilities on this team include:

Build pipeline support

Build pipeline support pertains to our continuous integration. This responsibility can be described as that of a “build sheriff” - the goal is to have someone lead on identifying the right person to drive a fix on an issue, rather than actively fixing every issue that arises.

As a build sheriff, the on-call support teammate should monitor the pipeline through channels like #buildkite-main for flakes, and ensure issues are followed up on:

  1. Infer the owner based on the contents of the issue, e.g. through product names and other context, and reach out for assistance:
    1. If a team can be inferred, ping the @$TEAM-support handle in Slack for assistance, escalating to @$TEAM if no support handle or teammate is available.
    2. If no team is easily inferred, ping the most recent author via git blame where relevant for assistance.
  2. Guide the teammate towards a resolution for the issue by following our broken builds process (also see Continuous integration: Flakes).


The DevX team is responsible for a monthly newsletter to highlight developer experience updates (not just those lead by the team). Learn more about it and see previous issues in the newsletter archive.

To prepare a new issue of the newsletter, create a PR for the latest newsletter issue here following the conventions in the previous newsletters. Some tips:

Once the newsletter is ready and reviewed, merge the PR. Then copy and paste the rendered newsletter from the handbook (you can set this up locally with yarn dev) into a draft newsletter. You will need to remove the background color from the pasted content, but the formatting should otherwise just work.

Verify the output looks good, and email it to

Growth plan


Tech stack