Just because you think Perl is the best answer to every problem, does not mean that it is the right solution for that company right now. You should always be willing to learn other languages, learn how the established code base operates, and how the team uses the tools they have to work together using the languages that they know. That will be vital in winning confidence and respect with your collegues.

Do not concern yourself with trying to get Perl everywhere. It will go where it fits best, when it is ready. Once you have attained oneness with the programming team, they will naturally "think for themselves" that Perl is the best way to go, where it is.

If you do not keep this willingness to understand your collegues' viewpoint, you will only add to the masses of Perl enthusiasts who are so blindly bashing Perl that they miss the opportunity to learn from established code bases, that have solved programming problems in new and interesting ways.

Ways that will work in Perl too, once you have ported them to CPAN for all of the Perl community to enjoy.