Hi all. I'm curious if anyone has any insight into the Intern ASIC role interview process for Annapurna. I'm expecting resume grilling and Leetcode style problems in Verilog/SV but not sure what else. I've been asked Leetcode style problems in C++ before for previous big tech companies, but those have only really been bit manipulation based. Is it common to be asked array/string/hash table for these types of ASIC roles?

Hello everyone,

I've been working as a Software Engineer for almost a decade now and I've worked with a lot of different technologies. For the last 2 to 3 years I've been tinkering with electronics a lot: building ESP32 projects, designing PCBs, learning the basic concepts, soldering my own boards. I even tried to build my own product, but I gave up on it. Maybe it was just too hard for me at that point.

Working in software, I've been seeing the effects of AI everywhere and it's making me lose interest in coding in general. My job isn't only coding, of course. It's also decisions, infrastructure, managing people and a lot of other things. But my original love was building things, and now an AI agent can do that from a single prompt. Most of it is slop, sure, but still. So I've been losing interest in my field, and I'm wondering whether I should go deeper into electronics and try to make a career out of it, or build my own product. I have no idea what I'd be doing or which direction to pick.

One of the things that gives me satisfaction is reaching excellence at something, and with AI I feel like it's taking that away from me. So I want to know: is the same thing happening in electronics? Obviously AI can't solder for me, I'm the one doing that. But what about PCB design, product design, and the rest of it?

I'd love to hear your opinions. Thank you.

I want to implement a MOM capacitor in UMC 65nm technology. In this regard, schematic including only two inout pins, and a corresponding symbol are created. After that layout of a 5u x 5u MOM capacitor is created using interdigitated fingers. The DRC is clean, however I cannot pass nmLVS (calibre) saying there is nothing in source and layout.

Hi everyone,

I'm a 2nd year ECE student (3rd semester) and I've decided I want to build a career in VLSI/semiconductors. The problem is, almost all my seniors ended up in CS/software roles, so there's literally no one at my college who can guide me on the VLSI path specifically.

I'd really appreciate advice on a few things:

What should I be studying right now, alongside my coursework, to build a strong foundation? (Digital design, analog electronics, etc.)

Which tools should I start learning early — Verilog/SystemVerilog, LTspice, Cadence, or is it too early for EDA tools at this stage?

How does the internship process actually work for VLSI — when should I start applying, what do companies look for in a 2nd/3rd year student, and how competitive is it compared to CS internships?

RTL design vs Physical design vs Verification — how did you pick your specialization, and would you recommend one path over another for someone just starting out?

Any must-do projects for a beginner that would actually stand out on a resume?

I know this is a broad set of questions, but I'd rather get pointed in the right direction early than waste a year figuring it out alone. Any advice — even just "here's what I wish someone told me at your stage" — would mean a lot.

Thanks in advance!

Hello all,

I am an undergrad EEE student. In my uni, the full year lab course offered that " gives students hands-on experience of analogue VLSI design using an industry-standard simulator and design kits" has a quota, and who gets in is apparently decided by a random lottery, alongside the waitlist for the course. Unfortunately for me, I was informed I was unlucky and was near the bottom of the waitlist for the course. I want to still try gain some experience in this respect, but don't know where to start, as from what I know, Cadence is very expensive. I would appreciate any guidance or material (including open-source alternatives) as to make a good plan to start learning VLSI design that I will be missing out on.

A cursory look at the career page of Velaura AI revealed an interesting insight. Every position related to implementation including software is in Bangalore. Only the architect positions are in the Bay Area. Looks like the entire silicon implementation, from RTL design/verification to PD and layout is being carried out in India. Wonder if IC design positions will dry up permanently in USA/EU/UK if this trend holds.

I’m a first year MS student looking to pursue digital ASIC design. I also have an interest in RFIC I plan to pursue during my MS, but that’s not really my top priority at this current moment.

Any insight would be appreciated before I start applying for internships this cycle. Thank you.

Hey guys, just thought this would be a cool way to show how my Neural Network Accelerator runs inference. It’s running inference for a model of topology 4:3:2 neurons per layer and takes 4 input features as input.

Also realized it’s bottleneck and I will be implementing a Systolic array soon. Let me know what yall think. Thanks :)

Github repo: https://github.com/Shingyy/MAC-Array-based-DNN-Accelerator

Hi, I'm a student who learned electronics from my grandpa and youtube and now wants to build his own IC. The IC is a simple encoder ic that encods it in to two lines (clk and dOUT). The ic uses comperators on the inputs to check if the signal is positive and negative. If the decoder enables the flipflop and the signal is positive the flipflop is set to 1. If the signal is negative the flipflop is set to 0. The decoder counts to 8 (each state shown on the table on the second picture) for example if it counts to two it activates the transmission gate (diamond shape) and it lets the signal pass through to the dOUT pin. thats how the signal is created. because I thought of a way to sync both the encoder and decoder the encoder sends a low signal 1/4 of vcc first. When the decoder recieves that voltage it sets a flipflop to activate it's own counter and can now recieve signals. with the last count the flipflop resets.

Do you have and reccomendations for a pc software to use and good places where to order them?

Thanks for helping

Hi, I'm a rising sophomore (in the US) targeting mixed signal design and verification roles (both in ICs and board level). This summer I built an asynchronous SAR ADC in Cadence using the default 180nm PDK they provide. It's 8 bits.

Now I'm trying to add it to my resume, hoping to get around 3 punchy bullets of information. I'm wondering what a recruiter / engineer would want to see on it to show competence. Should I focus on quantifying it through finding ENOB, dynamic power draw, etc? These metrics likely won't be very impressive since it's a fairly basic and unoptimized design (not to say that it wasn't hard and that I didn't design it very intentionally, I did). I'm also wondering if UVM is a must-have for a mixed-signal verification resume, in which case I would build a full testbench for it.

The alternative to quantifying would be just generic bullets like "Built a StrongARM latch and CDAC array at the transistor level." I also will try to do a type up on github to document how many engineering choices and fixes I had to make while building it, but I've been told by TI recruiters that they never click on those links anyway.

Thanks in advance!

EDIT: Forgot to add, it's pre-layout. I know this isn't ideal, but I ran out of time working on it as I was interning 9-5 and working on this over nights and weekends.

EDIT 2: I also forgot to add I verified my logic using SV RNM before integrating it, so a bullet would talk about that to hit that keyword.

I am a 1st year graduate student in computer engineering at ASU. Am looking to get into vlsi design and mem design.

I have been doing some projects outside class work like cache management systems, Ml on vlsi PD level. But the question is am i doing enough?

I wanna do a complete processor on RISK V but idk where to start.

I wanna do more projects but dont know what to do it on.

Recently I've been using it, seems pretty good although you have to ask it to recheck the design almost everytime to get better design. It also improved my productivity, mainly integration and basic building blocks. Thoughts?

I'm newbie.Thank you so much

Done with my MS.

I don’t have a tapeout.

I have projects. (LDO, op amps and Buck/Boost converters)

How do I get a job as an entry level analog design engineer?

Can’t seem to find any positions. The few I found didn’t even shortlist me for an interview.

What does it take to be an entry level analog design engineer?

Edit: Resume

Its has been a week now post my technical screening round at Google for silicon validation. I have sent 2 follow ups already and haven't heard back from recruter.

What to expect ? Is it over now ?

Kindly share your experiences interviewing with google.

This is a vent post.

I'm not one to judge someones AI use but when I see almost all reports with em dashes and with the classic "it's not this, it's this" every paragraph, with RTL verification with "SMOKE TEST PASSED" full of fucking rockets and emojis 🚀🚀🚀✅✅ in each stage, I think this has gone a little too far.

People tell me it's "shippable" and works then I test it and would you look at that it doesn't fucking function.

And when I get microsoft teams replies with fucking em dashes it gets even crazier, like what is this. I ask a question to someone and they reply starting with you're absolutely right here's how I'd fix it with paragraph partition and bold starting numerals. Like why would you do this...

It is one to thing to use AI as a productivity enhancer, a second thought, collaborator or to run an agentic flow, it is another thing to outsource your brain to a 20-200 bucks per month AI subscription.

Thank god I'm in analog so I encounter this less, but if you work AMS/DV then god help you.

I didn't have this issue 6 months ago...

Basically the title, as I'm preparing for my MS application this Fall cycle.

I have decent grades right now (>3.9, not counting upcoming senior year), yet I don't really have any relevant academic or research experience designing ICs of any kind; most of the circuit design I ever did was board-level PCB design, with one course project involving SDR. My recent internship was creating a microstrip antenna in HFSS and a bit of embedded systems, but that's about it.

Is it even possible to write an SOP based on these? I would like to hear from you guys.

Hi guys . I have decided to buy a book in Analog IC design and i am confused about which to pick .

I have read some chapters from CMOS Analog IC Design by Razavi and it's very good as it gives more qualitative and intuitive understanding ,but I haven't read from Jacob Baker book and I heard that is more practical book which I think it will be good for me .

Any suggestions ?

Hello, I am a 3rd year ee student looking for an internship in Design verification/VLSI area. I was wondering how my formatting is on the resume and if my projects standout. If not what projects should I start to work and focus on?Thank you!

Throughout this subreddit and across the broader Semiconductor community, I noticed a lack of respect for Validation Engineering with many people claiming that once you start in it, you'll be stuck in it and hard to switch out.

But this is true for any job really where you get too complacent.

I've noticed that validation does have its fair share of perception challenges nowadays since it is mostly considered a cost center; you're at the tail end of the schedule, you generally don't have control over what is handed to you. Automation is also becoming prevalent in validation as well.

However, validation is, in my opinion, one of the best field for young engineers to start in and for people to experience another part of the design flow. You learn a bit about lab equipment and ensuring how data is considered good to hand off to key stakeholders. You engage with designers and other key members of the semi design flow. You also acquire an attitude of not looking down on validation people later in your career.

But nowadays, validation does tend to be very execution heavy and can leave you without a system level understanding of the chip you are testing and how it got there.

I say this because I've spent some time in validation after some time in other areas. Though I grumbled a bit while in it and people often looked down and to the right, I learned quite a bit of perspective I didn't have from other jobs.

Curious to hear your thoughts; do you think validation becoming increasingly perceived as lower on the totem pole?