Developer Productivity Engineering Meetup/Webcast Sponsored by Gradle and DoorDash Engineering

How DoorDash Does Developer Productivity Engineering

Register nowThursday, January 27th (10am San Francisco | 1pm NY | 6pm London | 7pm Berlin)



You can’t do Developer Productivity Engineering (DPE) without collecting and analyzing data from developer behaviour and your software production tools. You also need the right tools to make sense of all this data to prioritize opportunities for improvement and to take action. In this upcoming DPE meetup we talk to Adam Rogal from the Developer Productivity team at Doordash. For the last 2 years, Adam has been building out the DoorDash Developer Productivity team, and previously he was a member of the DPE teams at Uber and Google. In this webcast we’ll explore with Adam the platform they built to improve the productivity of their engineers to ultimately ship new and better features to DoorDash users.



Topics and questions for Adam:

  • What was the impetus for establishing a DPE team at DoorDash?
  • How have the productivity engineering priorities evolved at DoorDash relative to your  past experience at Uber?
  • How did you get executive sponsorship to push DPE as a practice at DoorDash?
  • What are the DPE deliverables (KPIs, OKRs) and expectations from the executives you report to? What do they care about and what do they want to see?
  • How often do you have a DPE sync with your VP level folks and what things do you discuss with them?
  • How does that air cover from executives lead to more success with your DPE implementation?
  • Tell us about your Developer Platform organization? How is it structured and how many members does your team have?
  • What data are you looking at and what tools and processes do you use to collect and analyze that data?
  • What was the biggest productivity engineering win your team had in the last few years where you learned something new and took actions that led to a great result?
  • What’s your DPE moonshot?
  • What’s your advice for newer software teams that want to ship software at scale by improving build and test speed and troubleshooting efficiency?