In today’s rapidly evolving software landscape, the role of engineering delivery is more critical than ever. To gain a deeper understanding of what it takes to deliver high-quality software solutions in such a competitive environment, we sat down with Baldev Singh, an Engineering Delivery Manager at a world-renowned software company. With years of experience overseeing complex engineering projects, Baldev shares his insights on the intricacies of software delivery, the challenges he faces, and how the role of delivery managers has evolved over time.
Interviewer: Thank you for joining us today, Baldev. To start, could you give us an overview of what an Engineering Delivery Manager does in a software company?
Baldev Singh: Absolutely. The role of an Engineering Delivery Manager, or EDM, is essentially about ensuring that software projects are delivered on time, within scope, and with the highest possible quality. It’s a combination of project management, team leadership, and technical strategy. As an EDM, I work closely with cross-functional teams, including developers, designers, product managers, and quality assurance, to make sure that the project meets the business goals and the expectations of the client. But it’s also about problem-solving—finding solutions to the technical and organizational challenges that arise along the way.
Interviewer: That sounds like a lot of responsibility! What do you think are the most important skills an EDM needs to have to be successful?
Baldev Singh: It’s definitely a multifaceted role. First and foremost, communication is key. As an EDM, you’re the bridge between the technical teams and business stakeholders, so it’s important to translate complex technical details into something that everyone can understand, and vice versa. Leadership is another crucial skill—you need to inspire and guide teams while keeping them aligned with the overall business objectives.
Another important skill is adaptability. The software world changes fast, and priorities can shift just as quickly. You need to be able to pivot and adjust the team’s focus without losing momentum. Lastly, I’d say having a solid understanding of technology is important too. While you don’t need to be coding every day, understanding the technical implications of decisions helps in managing projects more effectively.
Interviewer: You mentioned adaptability as a key skill. Could you share an example of how you’ve had to adapt to changes during a project?
Baldev Singh: Sure. In one of our recent projects, we were well into the development of a new platform when the business team approached us with a significant change in the scope. The client needed a new feature to be included, which wasn’t part of the original plan. This is where Agile methodologies really came into play. We were able to reassess, re-prioritize, and reorganize our sprints without derailing the overall project timeline. The ability to adapt, especially when it’s client-driven, is critical in maintaining the project’s momentum and delivering value without compromising quality.
Interviewer: Speaking of Agile, how has this methodology shaped the way you approach engineering delivery?
Baldev Singh: Agile has been transformative in how we approach delivery. By breaking projects into sprints, it allows teams to focus on small, incremental improvements rather than trying to deliver everything at once. This not only helps in managing risk but also allows us to respond to changes more flexibly. In my role, I see Agile as more than just a framework—it’s a mindset. We conduct regular retrospectives to review what’s working and where we can improve, which encourages continuous learning. The collaborative nature of Agile also helps bring cross-functional teams together, ensuring we’re all working toward the same goal.
Interviewer: You’ve talked a lot about collaboration. How do you ensure that diverse teams, such as developers, testers, and product managers, work together effectively?
Baldev Singh: Collaboration is at the heart of successful delivery. Each team brings a unique perspective, so it’s important to ensure that everyone’s input is valued and that there’s open communication. One of the things I’ve found helpful is setting up regular cross-functional meetings—whether it’s daily stand-ups or weekly syncs. This allows teams to share their progress, discuss any blockers, and find solutions together.
Building a collaborative culture also means creating an environment where teams feel comfortable raising issues early. The earlier you identify a problem, the easier it is to fix. Encouraging transparency and fostering a sense of shared ownership over the project goes a long way in breaking down silos.
Interviewer: You’ve also emphasized the importance of automation in engineering delivery. Can you explain how automation fits into your strategy?
Baldev Singh: Automation is crucial, especially when it comes to maintaining quality at scale. In fast-paced development environments, you can’t rely on manual processes alone—they’re time-consuming and prone to error. We’ve implemented automation in various parts of our development cycle, particularly in testing and deployment. For example, automated testing ensures that each build is validated for bugs and issues before it moves to the next stage. Our CI/CD pipeline allows us to push changes quickly and confidently, reducing the lead time between development and production.
Automation doesn’t just speed up delivery; it also improves the overall quality of the product. It frees up engineers from repetitive tasks, allowing them to focus on more creative and complex problem-solving.
Interviewer: Risk management is another area that delivery managers often deal with. How do you handle risks during a project?
Baldev Singh: Risk management is one of the trickier parts of the job, but it’s also one of the most critical. It’s not about avoiding risks altogether—it’s about identifying them early and mitigating them before they become bigger problems. I always keep an eye on potential issues, whether it’s resource constraints, integration challenges, or changing client requirements. Regular risk assessments and having contingency plans in place help us stay proactive.
One approach I use is maintaining a risk log for each project. It’s a simple but effective tool to track risks, assign ownership, and document the mitigation steps. This way, the team knows exactly what to focus on, and we can act quickly if something goes wrong.
Interviewer: Finally, looking ahead, how do you see the role of engineering delivery evolving in the future?
Baldev Singh: The role of engineering delivery will only become more strategic as software continues to drive business transformation. As technology becomes more complex, the need for effective delivery management will grow. We’ll see an increased emphasis on automation, data-driven decision-making, and cross-functional collaboration. Engineering delivery managers will need to stay ahead of emerging trends, from AI to DevOps, while maintaining a strong focus on quality and agility.
At the same time, the human element will remain crucial. Even with all the tools and processes in place, successful delivery comes down to managing people—motivating teams, fostering innovation, and creating an environment where everyone can contribute their best work.
Interviewer: Thank you for sharing your insights, Baldev. It’s clear that engineering delivery is both an art and a science, and your experience sheds light on the intricacies of this role.
Baldev Singh: Thank you—it was a pleasure to share my experiences. Engineering delivery is definitely challenging, but it’s also incredibly rewarding. Every project teaches you something new, and that constant evolution is what makes the role so exciting.
Baldev Singh’s experiences and insights highlight the complexities and rewards of engineering delivery. As the software industry continues to evolve, leaders like him play a vital role in ensuring that businesses can deliver innovative, high-quality products efficiently, while navigating the challenges that come with complex software development.