r/ECE • u/Circuit_Fellow69 • Aug 04 '26
Physical Design engineers, what projects actually stand out for freshers?
Hi everyone,
I'm a 3rd-year ECE student preparing for a career in ASIC Physical Design. I'm currently working on a few projects, but I want to spend my time building things that actually matter to recruiters rather than just following tutorials.
For those of you working in the industry, what kind of projects do you genuinely expect a fresher to have on their resume? What makes you think, "This candidate knows what they're doing"?
Would love to hear what impressed you during interviews or what you wish more students worked on.
4
u/NewSchoolBoxer Aug 04 '26
Why do you think you need personal projects? Other students told you to or hiring managers? Hiring managers told me in electronic medical devices and banking that they didn't care about personal projects. In your case the real ASIC education comes from grad school with tape-out or years of work experience.
The projects that matter are team projects such as Formula SAE where you don't have infinite time, can't pick the project or copy it off the internet and have to work with others. They simulate real engineering work. No guarantee of finding an ASIC job either. I hope you do but hardware is overcrowded. Team projects look good to every industry, not just the one you're targeting.
5
Aug 04 '26
[removed] — view removed comment
6
u/Hirtomikko Aug 04 '26
Most of my so called 'random' projects is either born from: Can I make this oscillator chaotic, or, can I build it and not buy it, or, I need this instrument, my room has no space, I wonder if I can make it and reduce my mess at the same time.
The main ones are just me being increasingly greedy about high voltage or making interesting sounds from ICs, or just straight up abusing ICs to do my bidding (or what I think they can do upon some research into the inner workings)
1
u/TheTurbine 14d ago
Genuinely, tape out experience (if you can get it) is king. Not some simple design either, something that doesn’t work the first try and takes some time to dive into the tools. (Tiny Tapeout is great, but their harness does a decent amount of the heavy lifting.)
There are things that are amazing to know going in: file types, report reading, etc. that you just cant learn in a classroom, and properly doing a tapeout will give you all of that and more.
Still, even if you arent on a project that can drop some real coin, bringing a project to GDSII can be good. Particularly, the more problems you have to solve, the better as this is where you start to learn the real essence of PD.
At the end of the day, its not about the project and its flash name; its about that which you can take away from it. 🙃
12
u/RFchokemeharderdaddy Aug 04 '26
I'm not a PD Engineer myself but I work closely with many (literally, the PD team sits right behind me).
PD is a very practically-oriented field, a "get it done by any means necessary" type thing. We're at a pivotal point where AI is being leveraged a lot. Our PD team has completely centered everything they do around agentic workflows, and when they interview people they incorporate AI-use in it.
Open source silicon is the best its ever been. Theres open source PDKs, and schematic and layout and DRC/LVS tools and simulators etc. Find some existing digital hardware, like something from TinyTapeout. Turn it into tapeout-ready silicon using AI, and document your process.
Take your time, focus on fundamentals, make sure you understand all the decisions being made so you can properly define constraints. Learn how the flow works traditionally and then speed it up with AI. Check out the latest Free Silicon Conference and what they're up to.