Regarding working on a team, communication, handling criticism, and admitting ignorance, I think most of those are really properties of junior employees, rather

Regarding working on a team, communication, handling criticism, and admitting ignorance, I think most of those are really properties of junior employees, rather than junior engineers, specifically. I know I had a few issues in my first couple years, but I worked it out. I'm definitely a much more effective team member now than when I first started. As math, I also have a pure math background, with an undergrad degree and some graduate study. Other than having that certain rigor of thought, and a problem solving mentality, I haven't really found a lot of use for it specifically in my work. For example, I probably know a lot more about graphs than any of my colleagues, because I took several graduate level courses in graph theory, but, in actual code, not much of that matters as long as you can recognize when a problem is a graph problem and find the correct algorithm (usually some variant of BFS or DFS). Every so often, I know some random fact that helps with a problem that comes up at work due to that math background, but it's not frequent. The last one I remember is that we needed a good way to compute the area of an arbitrary polygon. Other than that, I can't think of much that I've used in work that was directly applicable. I wouldn't even say the derivative/integral concept is specific to a math background, since a lot of STEM majors require at least a 2 semester calc sequence. CS typically requires linear algebra. Stuff beyond that doesn't seem to get a lot of use, unless you're in the exact right specific field (e.g. writing graphics or other math-heavy software) from what I've seen.