Engineering org
Current organization
- Nick Snyder, VP Engineering
- Jean du Plessis, Director of Engineering
- Elzanne Wentzel, Engineering Manager - Content Platform
- Katy Juell, Full Stack Engineer
- Brett Hayes, Software Engineer
- Becca Steinbrecher, Software Engineer
- Tim Zielonko, Software Engineer
- Jordan Plahn, Engineering Manager
- Ryan Slade, Software Engineer
- Asdine El Hrychy, Software Engineer
- Indradhanush Gupta, Software Engineer
- Molly Weitzel, Software Engineer
- Alexander Ostrikov, Software Engineer
- Idan Varsano, Software Engineer
- Jason Gornall, Engineering Manager, Frontend Platform
- Tom Ross, Software Engineer
- Valery Bugakov, Software Engineer
- Oleg Gromov, Software Engineer
- Laura Hacker, Frontend Engineer, Frontend Platform
- Kristen Stretch, Engineering Manager, Developer Experience
- Dave Try, Software Engineer
- Robert Lin, Software Engineer
- Marek Zaluski, Software Engineer, Engineering Education Lead
- JH Chabran, Software Engineer
- Michal Vrtiak, Software Engineer
- Elzanne Wentzel, Engineering Manager - Content Platform
- Virginia Ulrich, Director of Customer Support
- Nonso Obiano, Customer Support Manager
- Giselle Northy, Application Engineer
- Stompy Mwendwa, Application Engineer
- Amber Furbush, Application Engineer
- Ben Gordon, Application Engineer
- Donavon Ellison, Application Engineer
- Jason Harris, Application Engineer
- Alex Jean-Baptiste, Application Engineer
- Brielle Collins, Customer Support Manager
- Warren Gifford, Application Engineer
- Gabe Torres, Application Engineer
- Michael Bali, Application Engineer
- Kelvin Lee, Application Engineer
- Mariam Adedeji, Application Engineer
- Riana Shahid, Application Engineer
- Quinlan Sparks, Application Engineer
- Shawnteé Harris, Program Manager
- Sarah Briggs, Program Manager
- Nonso Obiano, Customer Support Manager
- Bill Creager, Director of Engineering
- Stephen Gutekanst, Internal Contributor / Software Engineer
- Virginia Ulrich, (Interim) Engineering Manager, Delivery
- Crystal Augustus, Software Engineer, Delivery
- Kevin Wojkovich, Software Engineer, Delivery
- Michael Lin, Software Engineer, Delivery
- Murat Sutunc, Engineering Manager, Growth and Integrations
- Tharuntej Kandala, Software Engineer
- Beatrix Woo, Software Engineer
- Erzhan Torokulov, Software Engineer
- Philipp Spiess, Full-Stack Engineer, Growth and Integrations
- Taras Yemets, Software Engineer
- Naman Kumar, Software Engineer
- Rafal Leszczynski, Engineering Manager, Cloud SaaS
- Joe Chen, Software Engineer
- Milan Freml, Software Engineer
- Rafal Gajdulewicz, Software Engineer
- Pietro Rosa, Software Engineer
- Petri-Johan Last, Software Engineer
- Michelle Veronese, Software Engineer
- Diego Comas, Security Engineering Manager
- André Eleuterio, Security Engineer
- Mohammad Umer Alam, Security Engineer
- Lauren Chapman, Security Engineer
- Feroz Salam, Security Engineer
- Jennifer Mitchell, Engineering Manager - DevOps
- Dax McDonald, Software Engineer
- Manuel Ucles, Software Engineer
- Filip Haftek, Software Engineer DevOps
- Daniel Dides, Cloud DevOps
- Sander Ginn, Cloud DevOps engineer
- David Veszelovszki, Software Engineer, Growth and Integrations
- Yink Teo, Director of Engineering, Global Code Graph
- Loïc Guychard, Engineering manager, search
- Rijnard van Tonder, Software Engineer
- Juliana Peña, Software Engineer
- Rok Novosel, Software Engineer
- Camden Cheek, Software Engineer
- Felix Kling, Software Engineer
- Felix Becker, Engineering Manager
- Vova Kulikov, Software Engineer, Frontend
- Coury Clark, Software Engineer, Backend
- Justin Boyson, Software Engineer, Frontend
- Cristina Birkel, Software Engineer, Backend
- Leo Papaloizos, Software Engineer
- Chris Warwick, Software Engineer
- Chris Pine, Engineering Manager, Batch Changes
- Erik Seliger, Software Engineer
- Adam Harvey, Software Engineer
- Adeola Akinsiku, Software Engineer
- Kelli Rockwell, Software Engineer, Batch Changes
- Bolaji Olajide, Full Stack Engineer - Batch Changes
- Owen Convey, Engineering Manager
- Eric Fritz, Software Engineer
- Thorsten Ball, Software Engineer
- Noah Santschi-Cooney, Software Engineer
- Ólafur Páll Geirsson, Software Engineer, Code Intelligence
- TJ DeVries, Software Engineer
- Chris Wendt, Software Engineer on Code Intelligence
- Cesar Jimenez, Software Engineer on Code Intelligence
- Varun Gandhi, Software Engineer
- Jeff Warner, Engineering Manager for Search Core
- Keegan Carruthers-Smith, Software Engineer
- Tomás Senart, Software Engineer
- Geoffrey Gilmore, Software Engineer
- Stefan Hengl, Software Engineer
- Loïc Guychard, Engineering manager, search
- Michal Sennett, Strategic Projects Manager, Engineering
- Jean du Plessis, Director of Engineering
Helpful links:
- VP Eng team docs
- Engineering team and hiring plan (internal doc)
Philosophy
Our engineering organization is divided into mission based teams that contain the necessary cross-functional skillsets to achieve the desired mission. The leader of each team (at every layer) is responsible for ensuring appropriate cross-team collaboration happens when necessary.
Minimum viable team
A minimum viable team contains:
- A product manager
- An engineering manager
- Appropriate product design support depending on the work of the team
- Four engineers, with a minimum of two per skillset (examples: 2 backend + 2 frontend, 4 backend, 4 frontend)
New teams will not be created until/unless we have committed headcount in the plan to staff them to a minimum viable team within 3 months of forming the team, or to whatever is necessary to make the new team successful, whichever is larger.
We want each team to have sufficient engineering capacity to not only be able to deliver on their roadmap but so that teammates feel:
- they can take PTO without worrying about the team’s commitments
- teammates have ample time to experiment with new ideas or improvement that exist outside the team’s roadmap.
The number of teammates that allows teams to achieve these objectives should be considered their minimum team size.
Optimal team size
The optimal engineering team size is somewhere between minimum and maximum size, and depends on the team’s scope, the engineering manager’s capacity, and teammate capabilities. We trust engineering managers to make the right decision for their team.
Maximum viable team
We expect engineering managers to not manage more than 8 people directly.
If a team is approaching capacity and we need to continue to grow, the manager of the team should work with their manager to create a plan to grow and divide the team. This involves identifying a new engineering manager (either internally or hiring), which can take ~3 months, so it is important to plan ahead. In advance of identifying a new manager, the manager of the team at capacity should already start organizing the team’s work as if they were managing two separate teams. This eases the team into the transition before we actually have a new engineering manager onboard.
When teams grow and divide, we prefer to grow the org horizontally, not vertically. This means the new engineering manager would be a peer to the existing engineering manager, not report to the existing engineering manager, as long as the engineering manager’s manager has capacity. If the engineering manager’s manager doesn’t have the capacity, then we need to make a higher-level decision about how to adjust our org structure to support the growth we need.
Transferring teams
If you are already at Sourcegraph and see a current or future opportunity that you’re interested in, please tell your manager to figure out next steps. If you don’t feel comfortable talking to your current manager for any reason, please reach out to your manager’s manager, or someone in people ops. See also the process for switching teams.