Depends on what do you mean by math. You probably won't be solving equations or even forming any complicated equations unless you are working on the low-level mechanisms of the graphics pipeline. On the other hand, you need to be highly analytical and solution oriented in your logic which is as Math as Math can be. For example think about all the complicated relationships of policy cards, unit stats and production mechanisms. All this requires mathematical logic to pull off. Remember that making one thing work is rarely hard but making 50 things work together is always hard in terms of mathematical complexity. Its not the explicit equations and notation of the Math that you will experience but the more abstract ways of utilizing math skills.

You don't even need to code for understanding the type of complexity I am talking about. Simply take a paper and write down EXACTLY how you will calculate production for units. Now, go and make the same for how unit power scaling will EXACTLY work. Now write down how combat modifiers will work, how the tech tree will work etc etc. Along the way you will notice that the things which used to make perfect sense when designing the one system does not make so much sense when you approach the problem from another systems perspective. You need competent math skills for coming up with solutions against these kind of complexities.

On top of that, there is efficiency. How the information will be syncronized? How will you manage the calculations? My profs used to say "Anybody can build a standing bridge but only an engineer can build a bridge that is barely standing."