Ido Rabinovitch

Strategic Practices Leadership and Technical Evangelist

Ido is a software quality engineering executive with extensive experience helping companies and software organizations develop and continuously roll out high-quality products and features. His blend of professional and personal leadership skills assists him in guiding organizations to follow modern engineering practices with attention to the ultimate customer experience and digital journey. He currently works as a Senior Director at Applause leading strategic practices. Ido is also the Applause Technical Evangelist and blog contributor.

Ido has years of experience building and leading multiple quality engineering organizations and strategic practices for top-tier enterprises, driving exceptionalism across all team members. He particularly enjoys inspiring others to constantly improve and attain their full potential. He is skilled in evolving development, product and quality organizations into modern software engineering shops, influencing all levels of the company with a Lean-Agile and DevOps mindset and principles.

Prior to working at Applause, Ido was Director of Software Engineering at AT&T; Sales Director and Director of Software Quality Engineering at Amdocs; and Director of Quality Engineering at Tescom. Ido is also a certified Project Management Professional and a certified SAFe Agilist.

Ido has a passion for cultivating and driving exceptional software quality practices with specialties in test automation, continuous improvements, built-in-quality, test-driven development and shift-left methodologies.

When he is not working, Ido enjoys spending weekends with his wife watching their sons play soccer, snowboarding during the winter, cooking special meals, listening to live music, and traveling globally.

See What Ido Rabinovitch Has Written:

Why Low-Code/No-Code Development Increases the Need for Testing

Low-code/no-code development has merit, but teams using it must weigh the pros and cons

Is QA in Software Development Redundant?

Why some software product development teams think so