At work, you may spend 80% of your time doing what 80% of your peers can do, but it is that 20% that reflects value. For example, if you suddenly find that the project can't run, you should find out which code has gone wrong in the previous 10 code submission. Ordinary people may check every submitted record and even reset it to run again. But if you have a strong problem-solving ability, you may use dichotomy to find problems, which will be much more efficient and give you more time.

Many times the interviewer asks you about the algorithm, not the algorithm. Because many of these things can be washed out through a day or two of hard work, it depends more on your thinking and attitude to solve problems. To put it bluntly, it is the ability to solve problems. You spend less time and get good results, and you win.

When it comes to the requirements of front-end Web development for mathematics, to be honest, it won't be used much in actual coding, and junior high school level is enough. Except that a matrix in CSS3 is used in linear algebra, I haven't encountered more advanced mathematics for the time being (of course, if I focus on vision and animation, that's another matter).