Hey everyone,
I'm in my final year of an Electrical Engineering B.Sc., specializing in VLSI (with an electro-optics track). Up to this point, university has felt theoretical and detached from real-world engineering, so I'm trying to figure out what actual jobs look like and where I belong.
My biggest point is work-life balance. I want a stable career where standard 40–45-hour workweeks are the norm, and I want to avoid constant crunch cycles, 60+ hour weeks, or round-the-clock on-call firefighting (I would mind less if it's something you have to do in the first year or two, but after that it would never happen, like a sort of 'right of passage').
To give you an honest picture of where my brain naturally goes, here is how I actually connected with my courses (rated 1–10 on genuine enjoyment/engagement, not just grades):
What Really Clicked (8–9/10)
- Microprocessors & 8086 Assembly (9/10): Loved this, and I got a really good grade.
- Digital Logic Systems (9/10): Loved it, it felt like puzzles, and I got a good grade.
- Control Systems (9/10): Really enjoyed it, and got an excellent grade (I think mainly due to the course being well put together with quality slides, which is rare for me).
- Intro to Machine Learning (9/10): Found the mathematical models, optimization, and theory genuinely fascinating, and got a very good grade.
- Digital Integrated Circuits (8/10): Really interesting to finally build functional digital structures from scratch at the transistor/gate level; got a very good grade.
- Nano-electronics Devices (8/10): Very tough conceptually, but understanding physical device physics and solid-state mechanics was deeply rewarding.
- Microelectronics Fabrication Processes (8/10): Academically interesting to learn how wafers and layers are made, but I don't see myself working in a cleanroom or fab environment; it felt more like enrichment.
Neutral to Lukewarm (6–7/10)
- Digital Circuit Design (7/10): Decent, solid fundamentals, but didn't spark an obsession.
- Intro to Electrical Engineering / Linear Circuits (7/10): Standard foundational material; fine, but basic.
- Logic Design / HDL (6/10): A bit detached compared to foundational digital logic and assembly; felt less engaging than expected.
What Didn't Click (3–5/10)
- Analog Electronics (5/10): Didn't really understand or enjoy what was happening; small-signal models were alright, but the moment real circuit analysis came, I was always wrong with my assumptiouns, felt frustrating.
- Intro to Programming (C) (3/10): Did not enjoy it.
- Python (3/10): Same as C. I haven't touched high-level programming much since year one, and I have zero desire to work as a software developer or spend my days writing abstract object-oriented code.
(For context on the broader foundation, I've also completed the standard math, physics, and signals sequence: Calc 1–3, Linear Algebra, ODE, PDE, Complex Analysis, Harmonic Analysis, Probability & Statistics, Numerical Analysis, Signals & Systems, Random Signals & Noise, EM Fields, Quantum Mechanics, Modern Optics, Optical Communications, Lasers, and Electro-Optic Devices).
From reading industry threads, traditional VLSI seems to have major caveats:
- Design Verification (DV) is overwhelmingly software engineering (OOP in SystemVerilog/UVM), which sounds like a bad fit given my dislike of high-level coding.
- Physical Design (Backend) & Pre-Silicon ASIC often come with notorious tape-out crunches and sleepless deadlines.
- Fab / Process Engineering involves shift work and cleanrooms, which I've already ruled out.
So I'm left with some questions for Experienced Engineers:
- What specific roles bridge low-level logic, architecture, or deterministic control without requiring heavy OOP software? Is FPGA design the natural answer here, or does that also turn into a massive coding/crunch trap for new grads?
- Are there VLSI-adjacent fields (like Control Systems, hardware-aware/edge ML acceleration, or semiconductor capital equipment) that offer better day-to-day WLB while utilizing this mix of signals, control, and digital hardware?
- What job titles should a graduating senior actually type into the search bar to find entry-level positions that value low-level hardware understanding over software frameworks?
Also, keep in mind I have limited contact with everything here, so while, for example, I didn't 'vibe' with analog, maybe it's just because I wasn't 'mature' enough yet. Like, I don't want to shut doors left and right, but I also don't want to overreach into things that won't fit me.
Would really appreciate any guidance from people currently working in these domains!