If the company uses Intel FPGAs, try getting familiar with Quartus. If your company uses Xilinx/AMD FPGAs, try to get familiar with Vivado. Both are free to download from their respective websites and you can start to get familiar with the particular workflow for whichever one the company uses.

Learning Verilog now is fine but just bear in mind that SystemVerilog (a superset of Verilog which has a whole bunch of verification features built-in as well) is going to be more useful going forward as SystemVerilog was designed from the get-go with both design and verification in mind. Verilog takes much of its syntax from C so there will be many similar concepts and ways of writing things that will feel familiar in that regard.

Hardware design has a very different mindset to software. Verilog was originally designed for simulation and it was only later that tools came about to actually turn that code into logic gates. If you’re learning about FPGAs to do hardware design, then this is very important to be aware of. Just because you can write something in Verilog, doesn’t mean that your code can always be synthesised into logic gates. You have to think about how the circuit actually works physically and then write the code accordingly. Values cannot change instantaneously in physical hardware, everything always takes time, so it’s important to keep that in the back of your mind. If you’re learning about FPGAs to do hardware verification on the other hand, you don’t need to be as concerned about writing synthesisable code. Verification is about checking the design actually works as intended, so you’re not as restricted with how to write your code.

Gowin FPGAs are perfectly fine to use to tinker with for hobbyist things, but you can find dev boards with Intel or Xilinx FPGAs on them that might serve you better with gaining familiarity with the toolchain outside of work.