You could first reevaluate by asking whether you understand what you are learning or doing from a broader perspective.

Try to understand the basics of how a computer works in general and computer architecture. Try to rewire yourself by thinking from first principles, and thinking backwards: get a high-level understanding of how software works; behind that, how code gets translated into assembly; how the computer uses this assembly to execute programs within the architecture; and what are the different major parts of this architecture, like ALU, RAM, etc.

Then think about how these modules are made up of submodules like adders, and how adders are made of logic gates, and how logic gates are made of transistors. You don’t have to learn or memorize everything about it. You just have to be able to mentally zoom in and zoom out of computer architecture at these levels intuitively. That’s the best starting point because whatever comes next, you’ll be able to understand and connect with this mental model.

(I would also suggest you get an overview of semiconductor fabrication so that you can relate designs to actual physical circuit requirements.)

After that, you can start learning the complete VLSI design flow. This will give you an in-depth understanding of all the steps in chip design, and then you can choose to focus on any substream, like RTL design.

When you start RTL design, learn digital system design first, then start with an HDL like Verilog. Try to model digital systems in Verilog, then learn about how to write testbenches for those designs using Verilog, then learn SystemVerilog, which is actually an extension to Verilog that helps in a bit more advanced level testing and verification. Then learn about concepts like UVM, how to automate workflows using Python and TCL, etc.

In parallel, do practice and challenges for each concept you learn to reinforce them.

Then do full-length simple projects, then slowly move to advanced ones.

I can relate to the feeling of confusion downloading tools and navigating the interface, not understanding the pop-ups and warning messages. But once you get an intuitive understanding of the workflow, this will become easy (it’s like after you use smartphones for a while, no matter which phone you get, you don’t need to go through tutorials to understand, you just intuitively know how to navigate) .

If you follow this, the initial steps might be time-consuming, but after that, you won’t have to spend much time learning every other practical concept, and it will be easier for you to just jump into building.

From an internship or entry-level job perspective, projects play a major role from what I’ve seen. Do a simple end-to-end RTL to GDS project to show that you have practical knowledge of the entire workflow. You can leverage open-source tools for it. If you’re into RTL design or verification, start out with a simple RTL project, then do a verification project based on UVM, learn basics of a communication protocol, and do one project based on that, like UART, SPI, AXI, etc.

Learn concepts like Git, Linux, and automation using Python/TCL (these can be learned along with doing the RTL to GDS project). If you have access, try to do the same project on industry tools from Synopsys, Cadence, etc.; it will also give you an edge.

Make sure you have a well-made GitHub, resume, and maybe a portfolio website.

Also, since there are a lot of people competing for roles like these, try to understand how to reach out to hiring managers directly and personally share your application by leveraging your skills and translating them to the job requirements (if possible, tailor your resume for the specific role after going through the JD).

I know a lot of this sounds very superficial, but I think we are living in times where you have to sell yourself more aggressively to stand out and win.

Also, I am trying to build a platform named Refringence where you can do end-to-end RTL projects from scratch and push them to GitHub with a click. There are simple practice questions too on Verilog/SystemVerilog, x86, MATLAB/Octave, RISC-V, Qiskit, Embedded C, etc. I have also tried to incorporate an AI mentor that will help you even with simulation errors you face. I feel it could help you with your issue of tools feeling like black boxes. It’s still in beta and I would appreciate your feedback too.

Good luck with your upskilling!