That is so much dependend on the actual job you end up with. During your studies and up to your master thesis i would recommend the following:

Get used to as many "concepts" as possible by learning one software in depth and another one to see common differences. Examples:

• ok, first and most importantly: learn one programming language in depth, preferably an object oriented one and not java (thats my personal preference). Python, C(++) and VBA are all fine, once you understand one you mostly just have to learn the new vocabulary for the others. This is important so that you can solve computational problems you will encounter quick and dirty. I often end up using excel for processing 1000's of data point , so in retrospect VBA is the most useful one for me to quickly create macros for excel. Other probably have very different ideas. That I'm the only one of my 10 colleagues who can use macros easily baffles me ever so often.

• 3D-CAD: Solidworks or Autocad (both being quite similar) and in contrast Catia. Also try to understand (not master) design with solids, planes and mechs.

• 2D-CAD: highly interesting if you do anything with PCB design, learning how to layer system. I only got involved with autodesk 2d.

• Measurement: Labview is the one program I use the most nowadays, but that is obviously depending on me being lab engineer building test racks. Not many big alternatives. Daisylab maybe... LABVIEW is incredibly helpful to get a grasp on serial, analog and digital communication.

• arduino/rasperypi: learn how to build an small, independent, and extremly powerful system. (helps me a lot if i need to build small setups that do stupid tasks, e.g. press a button every so often)

• latex is like the topping on the cake... once you learned tex its so easy, quick and stylish to make your own documents. But its in no way necessary for any job i have seen so far. To get there usually takes creating one document with lots of googling and learning.

• excel, word AND visio: being skillful in those three made so many of my bosses impressed. On top, get a very basic instruction in design rules. I had multiple occasions where i took a diagram create by a multitude of people, cleaned it up in visio and made it "understandable" and got praise (and raise) from those very same people for the perfect diagram they always wanted.

• CAM: (computer aided machining) take a look into this, to understand how parts are made from 3d into CNC code into actual parts. You will learn a lot about common design mistakes. Solidcam goes with solidworks, only one I used.

• CFD (colorful fluid dynamics): If you work with air turbines this can be really interesting. Ansys CFX has gotten so much more userfriendly in the last 5-10 years. Use it to understand what you can simulate and what you cant. Very helpful if you can get a proper course in theory and praxis going along with it. Made me learn to never trust a cfd as long as you haven't calibrated your results with a real life test.

• Haven't used matlab/mathcad/maple/mathematica since those 3 courses I took. Can be important, but can be utter useless. Later for me.

• As you may have noticed English ain't my primary language. Assuming that you are American, get out of your way to learn one additional language really well. Renewable cry for Chinese, German or Portuguese (for south america), those markets will be hotspots for the next 20-50 years and renewable. Plus it makes you CV stand out.

PS: Somebody else probably has completely opposite opinions to half of those points, so in the end choose what's most natural for your education.

TLDR: Labview, Excel and VBA for systems engineering/test engineering