How to Structure Your Engineering Team to Scale

In this episode, Jeremy Eastwood, the Head of Engineering at DroneDeploy, talks about velocity and adding processes as your team grows. Key Takeaways: Metric to measure velocity Reconciling struggles Experimenting while using guardrails Devote an engineer to reliability during each sprint Making sure there is an expected result when experimenting When to sit back and let the team execute Definition of done and compliance Seeing the whole field and providing feedback to your managers About today’s guest: Jeremy Eastwood is the Head of Engineering at DroneDeploy. Jeremy oversees the talented engineering org at DroneDeploy and aspects of its core product offering, including mobile applications, cloud platform and infrastructure, computer vision engine, and 3rd party ecosystem. He was one of the first hires at DroneDeploy and has been a part of the growth from a seed-stage startup to the market leader in digital reality capture, with over 250 employees and offices worldwide. Before DroneDeploy, Jeremy worked in research on the design of jet engines and holds a Ph.D. in aerodynamics from the University of Cambridge. Outside work, he enjoys hiking around the Bay Area with his family. LinkedIn: https://www.linkedin.com/in/jeremy-eastwood/ ___ Thank you so much for checking out this episode of The Tech Trek, and we would appreciate it if you would take a minute to rate and review us on your favorite podcast player. Want to learn more about us? Head over at https://www.elevano.com Have questions or want to cover specific topics with our future guests? Please message me at https://www.linkedin.com/in/amirbormand (Amir Bormand)