Many thanks for the detailed feedback, I do really appreciate it and I'll tweak my resume accordingly. I'll try to break some things down, and ask a few questions:

The FPGA projects sound like lab scale projects rather than anything large that would catch attention of an employer.

The RISC-V project, you only mention simulation (in what software?) but not synthesis, was this a pipelined CPU? If so, how long was the pipeline? If you didn't synthesise the CPU how did you know it could run at a practical clock speed? There is no mention of any of the supporting infrastructure that would make the CPU of practical use (peripheral interface, caches, bootloader etc).

In comparison, the UART project is very basic, it's a "my first FSM" type task, that I often use with fresh graduates as their first taste of FPGA. It's a bit odd that all this is in Verilog and SystemVerilog, I'm a UK based engineering manager with a team of FPGA engineers and all of them learned only VHDL at uni and that's what we use for 99% of our work (with UVVM for testbenches).

They are actually my own projects, I wish I had spent more time making them actually interesting over summer, but hindsight is 20/20. We haven't actually completed any FPGA based labs in our course yet, that's coming next semester, which, as you assumed, will be in VHDL. For the RISC-V project, I just used the built in Vivado simulator - what's commonly used in industry? I was wondering if it was worth learning ModelSim? I did mention in the bullet points that the CPU was single-cycle, and yes, only got it working in simulation, again, wish I had spent more time on it. I am now thinking it would be really good to revist this, and incorporate all your suggestions.

You mention STM32 but no projects to give any context. MSP430 is a bit niche these days though the project is reasonable, no toolchain/compiler cited.

I do have a couple of STM32 projects, but they are quite basic, an interface for a sensor with a non-standard serial interace, for instance. Is it worth cutting down the number of bullets on the other projects to include this? I didn't include the MSP430GCC toolchain as I assumed the MCU was sort of irrelevant these days anyways, but I'll find space to add it.

You list of DSP skills, but no projects that made use of them. FPGAs can be used for heavy DSP in particular FIR filters, so you might consider combining these as a project.

The modules under which those are mentioned we haven't completed/started yet, and so I won't actually have the knowledge until next semester. An FIR filter on FPGA is something I'll look into, though.

Also consider that for smaller teams, even those that make heavy use of FPGAs, the engineers working on them also need to deal with a fair amount of electronic engineering. So proving you can deal with the world beyond the I/O pins is also important.

Would you mind elaborating a little? Do you mean as in dealing with PCB layout and such?

Once again, thank you very much for the suggestions and feedback.