There are good reasons for having unit tests, however, unit tests do not make a good product. It is the same automated tests, source control, etc... It could be said about most development paradigms. They are just tools in the toolbox. How you use those tools and the information they provide is what makes the difference. I've seen many cases of an urge to implement the latest & greatest "THING" in the internet, only to have it fall flat because it was complete overkill, wrong tool for the job, or simply poorly timed execution (you cant implement the "perfect world" overnight, it takes several iteration for the people and processess to catch up).
When you get there, if you think it would benefit them based off of their work style / processes / product, I would come up with a plan to start using unit tests and use this as an opportunity to climb the ladder.
When you get there, if you think it would benefit them based off of their work style / processes / product, I would come up with a plan to start using unit tests and use this as an opportunity to climb the ladder.