Brian Henrich
About Brian Henrich
Brian Henrich is a Lead Software Engineer at Thomson Reuters, where he has worked since 2010. He specializes in Agile coaching, scrum leadership, and software architecture, with extensive experience in Java, SQL, and UNIX systems.
Current Role as Lead Software Engineer
Brian Henrich serves as the Lead Software Engineer at Thomson Reuters, a position he has held since 2010. In this role, he oversees software and content releases, ensuring that development processes align with organizational goals. His responsibilities include managing the analysis of audits for both legacy and migrated systems, which is essential for maintaining software integrity and performance.
Experience at Thomson Reuters
Brian Henrich has a long tenure at Thomson Reuters, having worked there in various capacities since 2003. He initially joined as a Software Engineer, progressing to Senior Software Engineer from 2006 to 2010. His experience in these roles has equipped him with a deep understanding of software development and project management, contributing to his current leadership position.
Expertise in Agile Coaching and Scrum Leadership
Brian specializes in Agile coaching and scrum leadership, focusing on enhancing the efficiency of development teams. His expertise in these methodologies allows him to implement best practices that improve team collaboration and project delivery timelines. This skill set is vital in today's fast-paced software development environment.
Technical Skills and Software Architecture
Brian possesses advanced skills in Java and SQL development, which are critical for backend and database management. He also has expertise in software architecture, enabling him to enhance the structural design of software systems. His experience with UNIX systems further supports robust software testing and design processes.
Previous Experience at Accenture
Before joining Thomson Reuters, Brian worked as a Consultant at Accenture from 1998 to 2001. In this role, he gained valuable experience in assessing production and pre-production support issues, which involved communicating their impact to the business. This foundational experience contributed to his development as a software engineer.