Hacker News new | ask | show | jobs
by magicsmoke 2140 days ago
Specializing in hardware design is really a poison pill despite how interesting the field is. You spend more than a decade in school to gain the skills needed to work at the chip level, which often requires a PhD. Then it turns out that there's only a handful of companies in the world with the equipment or supporting personnel needed for the field, and your skills are worthless outside of these specialized environments. No wonder pay is so low despite the years of schooling needed. After going through those considerations, I ended up dropping out of a PhD in RFIC design and fell back to embedded systems. More companies hiring and versatile enough to slide into general software or web programming if necessary. Chip design is still fascinating, but all traps look nice on the outside.

Also, for any aspiring undergrads wandering this way that thought RFIC design was fascinating because they picked up a copy of Razavi's "RF Microelectronics" or something similar and couldn't help but read it cover from cover, the textbooks lie. The analytical equations in a chip design textbook are not reflective of what the actual process is like. While you're still in college, try and get a professor to give you a student addition of Keysight ADS or Microwave Office AWR, along with an SDK from a fab. Then spend a few months of simulation time to see for yourself how much simulated results diverge from analytical models and how painstakingly slow it is to optimize those simulations especially once you start moving into EM simulations. And keep in mind these are simulations, chances are the physical chip will diverge even more due to process variations, unknown parasitics, or even bad simulation models from the fab. If the lack of precision, simulation time, and general drudgery doesn't kill your enthusiasm when compared to your textbook learning, then by all means proceed.

It's still a fascinating subject. Every so often when I need a break from code I'll take out my old RFIC textbooks and read a chapter or two. But you really don't want to know how this sausage is actually made.

3 comments

Close to what I experienced myself.

I spent my teens looking up to microelectronics career, and actually self-studied a year, or two ahead for entrance to Nanyang, or NTU semi.eng. programs.

I almost accidentally met two ex-TSMC engineers who worked for Chang almost since his first days at ITRI, and they were very good mentors, and seriously warned me about "a decade+ grind ahead." In the end it were my parents who stonewalled the idea, and sent me to a business degree mill in Canada. And this is all was when I had 2 early admission letters from both Nanyang, and NTU on my desk...

are you earning more than a TSMC engineer now?
Easily, and I am just doing EEng101/MEng101 level work in an engineering consultancy. The work I do now has nothing to do with actual IC fabrication.
That's too bad. Working on the cutting edge sounds much more exciting.
> If the lack of precision, simulation time, and general drudgery doesn't kill your enthusiasm when compared to your textbook learning, then by all means proceed.

Exactly why I stopped, this hits close to home

> But you really don't want to know how this sausage is actually made.

Please tell me about some quick nasty bits!!!!! I need a joke or entertaining story to share during my friday sprint review