Don't create top-level comments - those are for employers.
Feel free to reply to top-level comments with on-topic questions.
Reply to the top-level comment that starts with individuals looking for work.
Rules For Employers
The position must be related to electrical and computer engineering.
You must be hiring directly. No third-party recruiters.
One top-level comment per employer. If you have multiple job openings, that's great, but please consolidate their descriptions or mention them in replies to your own top-level comment.
Don't use URL shorteners. reddiquette forbids them because they're opaque to the spam filter.
Templates are awesome. Please use the following template. As the "formatting help" says, use two asterisks to bold text. Use empty lines to separate sections.
Proofread your comment after posting it, and edit any formatting mistakes.
Template
(copy and paste this into your comment using "Markdown Mode", and it will format properly when you post!)
**Company:** [Company name; also, use the "formatting help" to make it a link to your company's website, or a specific careers page if you have one.]
**Type:** [Full time, part time, internship, contract, etc.]
**Description:** [What does your company do, and what are you hiring electrical/computer engineers for? How much experience are you looking for, and what seniority levels are you hiring for? The more details you provide, the better.]
**Location:** [Where's your office - or if you're hiring at multiple offices, list them. If your workplace language isn't English, please specify it.]
**Remote:** [Do you offer the option of working remotely? If so, do you require employees to live in certain areas or time zones?]
**Visa Sponsorship:** [Does your company sponsor visas?]
**Technologies:** [Give a little more detail about the technologies and tasks you work on day-to-day.]
**Contact:** [How do you want to be contacted? Email, reddit PM, telepathy, gravitational waves?]
There have been a handful of different posts in the last few months specifically asking to address some of the low effort, low quality posts we often see on this subreddit. I think people have gotten overly fixated on the perceived influx of Indian student questions (please giv roadmap, etc.), but there have always been the same type of low-quality posts coming up from other sources:
Please suggest a capstone project
Help me with my homework
I hate my professor, recommend me a textbook
And so on. So for now, we won't be adding new flairs or filters, but instead we'll just ramp up moderation effort to remove low quality and low effort posts of this nature, and we'll keep this thread stickied for the foreseeable future.
At present, the majority of the moderators are inactive, so I need to ask for some folks to apply. My criteria at present is below:
Relatively frequent poster in /r/ece and related subs
Account age at least a few years
Must be a practicing engineer in the field or at least in your PhD program
To apply, simply submit a message to the moderators (not me personally, not a reply in this thread) with the words "positive feedback" in your first line, and describe in just a few sentences your education / professional background and what you think you'd like to see change on the subreddit. No need for a LinkedIn link or anything, but please don't bullshit. No one gets paid, and moderating isn't exactly fun.
Finally, I'd ask for everyone else to make judicious use of the report button. It's the easiest way for moderators to do their jobs, since highly reported posts simply get a big red "spam" button for us to push and remove the post. Don't abuse it for every single post you don't like, but we'll start utilizing it as well as Automod to clean things up more.
Thanks for your help and thanks for your patience.
I applied for a New Grad Wireless SoC Design Verification Engineer role at Apple in the Bay Area and cleared the first round with the hiring manager. My next round is going to be a panel interview with 4-5 senior team members, stretching to about 6-7 hours in total. This is my first interview, and I really want to give this my best shot.
If any of you have interviewed with Apple for a DV role before, please do comment and help out with the process. I could really use a couple of tips, do's and don'ts, and which topics to spend more focus on.
Also, what sort of package can a new grad expect? The pay range is shown as 120k-180k, but since I am a new grad, I expect the base to be somewhere around 130k, if I am not wrong. If I do not have any competing offers at the moment, is it recommended to negotiate (assuming I get an offer ofc)?
I am a current junior and was able to receive an offer for an internship from a notable company in the semiconductor industry. The role is for software apps and I was wondering if the transition from software apps to embedded is difficult or not. My internship project will be more firmware focused (talked to the hm) but the full time is typical swe apps work
I'm a high school student working on a project where I need to build a small bench setup and record what a DC arc looks like in the current. Basically im just wondering whats the most common thing that gets mistaken for an arc when you're measuring current on any sort of system based on your experience. Any answer i usually find online just says arcs have fast edges and then noisy current and I read some arc fault detector papers but they mostly talk about results within a controlled testing enviornment and I dont have any idea on what actually happenes when people try detection in real life. I've never really done this on a real system before, so any sort of help would mean a lot.
I'm currently in an engineering program and doing a co-op at another company for 12 months (May 2026 - May 2027), where a large part of my work involves testing in the telecom industry. It is not the most exciting work, but I cannot complain much since I am literally an intern.
However, I recently got offered a 16-month co-op term for AMD, but I'm a little conflicted about whether I should accept it. It's not a big ASIC role, and I can probably give more context about the role if asked.
The main downside is that accepting the position would mean extending my degree by roughly another year. I'd end up graduating a year later than most of my friends and the people I started university with. Going back to school, I would lose out on a good capstone project with my friends. While I understand that graduating a year later isn't necessarily a big deal in the long run, it's still something that's been on my mind. In addition, I am also not sure if the role is really worth it. Is it really worth extending my degree for a role I am not interested in, even though it's a big company like AMD?
On one hand, AMD is a well-known company, and I feel like getting 16 months of experience there could be a great addition to my resume, help me develop valuable technical skills, and potentially open up more opportunities after graduation.
On the other hand, I'm wondering whether the extra year is really worth it. I also don't want to get too caught up in chasing company names if the actual experience or long-term benefits aren't necessarily as significant as I'm imagining. I can also try targeting another company in big tech for the summer (but of course, there is nothing concrete right now).
I'd really appreciate hearing people's experiences and perspectives. I'm trying to figure out whether this is an opportunity I should take advantage of or whether I'm overvaluing the company name and should focus on applying to another company for the summer (in a role I'm more interested in) and graduating sooner.
Also, I can share what the job title is and the location as well if that helps :)
I gave the Cisco oa .It was good mixture of some analog and digital questions. It was good. More like most of the questions I know very well and I did it perfectly. For some questions in which I was stuck, I solved them and complete. It was good experience. But before Cisco, I have given many OAs, and every time my OA went well, there always no shortlisting for me. Hope I does get this time, and this will pass soon. Okay. One more thing I suspect is like the OA was of about 60 minutes, but most of the questions were easy and direct to solve, so I solved them in around 35 minutes and submitted it. What do you think? Will Cisco flag me as a cheat or discrepancy? Because I have finished in very early time, so they might think that I have cheated on this. Further, I don't know what will happen. Let's hope for the best.
Hi, I am starting as a validation engineer at a large semiconductor company but mainly due to higher pay (and more learning) I wanted to move into IC design, ideally within 2 to 3 years.
A few questions for people who've made this move or work in design:
Master's timing: should I start a part-time master's right away, or wait about a year until I'm settled and know what area I want to specialize in?
Is a master's actually required? Can someone realistically move from validation to design without one, if they learn enough on their own and perform well internally?
What to learn: what skills or tools should I focus on during my time in validation to be a strong candidate for design (analog fundamentals, Cadence, specific courses, etc.)?
Internal transfers: how do validation-to-design moves usually happen at big semi companies? Is it mostly networking with design teams, performance reviews, or applying internally?
At end I just want to have a career with high ceiling and one that can keep me interested for decades. From what i have heard validation learning curve hits a plateau.
Additionally, I was also wondering will my validation experince count as industry experience or will I start from 0 YOE when I finally make it into design.
I’m a CS grad interested in getting into embedded systems.
I studied C and C++ during my degree, though I’m a bit rusty and completely new to the hardware side of things.
I recently bought a few components (STM32 Nucleo board, OLED display, sensors) to eventually build a project, but I’d like to build a solid foundation first.
I’d really appreciate recommendations for learning resources, such as Udemy courses, YouTube channels, online courses, tutorials or websites. If you’ve followed a learning path that worked well for you, I’d love to hear about it!
I am a freshman CompE major at UIUC. Starting out, obviously I don't have a scope of everything in ECE but I find the topics interesting. However I have been repeatedly told that my presentation/commutation/management skills are top notch. It's to the point where I'm kinda thinking why I went into a field that's so technical.
I mean in the nicest way, a bunch of my peers who are undoubtedly very intelligent (and probably very nice!!!), lack communication and social skills.
With all of that said I was wondering if there was a specific niche in ECE that particularly focuses on both from the get go (like the social, communication side + technical/logistical). Professors said I would be a good manger but obviously thats not possible out of college.
I’m a high school junior planning to major in electrical engineering and I’m looking to upgrade from an old macbook pro to a windows laptop that will last me at least 3 years. I prioritize battery life, performance and portability but would also like to game if possible. I’m looking at a Lenovo Yoga 7i which is currently on sale for around $1000 off or an Asus Zenbook S14. I plan to use CAD softwares like fusion or onshape for my robotics team and personal projects, but it’s not a huge thing. That being said, I’m unsure whether paying for a dedicated gpu is the right move if I already have a desktop and will be mostly using my laptop for school and other engineering softwares that aren’t CAD softwares. Any laptop recommendations?
Hi everyone, I am studying electromagnetics now. I am using Hayt 8th edition. I have reached transmission lines but I feel like is a bit different than what my professor explained. I tried to study it from pozar but it was too compilcated even if it matched the approach of my professor.
What do you suggest?
Is hayt different?
Also, Hayt 8th edition starts with transmission lines before wave, which is a bit off.
I know it might not matter too much, but should I do my M.S. in Electrical Engineering or Computer Engineering? My university doesn't offer an M.S. in ECE, only separate EE and CE degrees.
My goal is a digital IC design role, ideally RTL design or design verification. Does the degree name make any difference to recruiters, or is it mostly about coursework and projects? Which one would you pick?
Digital is my main focus, but I'm also interested in computer architecture, AI accelerators, analog/mixed-signal design, firmware, and even AI/ML software in the side.
I’m really getting fed up with seeing the same questions pop up over and over again.
You know the ones I mean: "Hey, I’m from tier abc college and I’m in my first year. I want to get into VLSI because it seems promising, but I’m totally not into coding. What do I need to do to land a job at Intel? How can I move to the USA or Germany or wherever?"
That kind of post is fine in my book. But then you get stuff like, "What are some interview questions I should prep for?" or "Will company abc offer a PPO?" or "What’s the admission process for college 123?"
Honestly, if people in India are confused about what a PPO even is, do you really think others on this sub will have clarity? Plus, not everyone is clued in on the admission procedures for college 123 either.
Just to clarify, I’m Indian too. I’m not trying to sound racist or anything, I’m just exhausted from seeing the same old questions all the time.
I started my M.S.E. in EE at UPenn this fall (Computer Engineering concentration, graduating May 2028). I did my undergrad in EEE at UCL. Next semester I'll be taking a tapeout course, so I'll have a real chip design project under my belt before summer.
I'm hoping to land a Summer 2027 internship in digital design or DV. The problem is that my only internship so far was software-heavy (embedded Linux and AI demo work at Arm China), and my VLSI experience is all course projects: a full-custom SRAM-based MAC accelerator in a FinFET PDK, a RISC-V core in SystemVerilog, and an RTL-to-signoff project on NVDLA's CMAC that's still in progress (not on the resume yet). I have no UVM experience yet.
So far I've applied to ~30 positions (TI, AMD, ADI, Marvell, Micron, etc.) and gotten 0 interviews.
A few questions:
Is it realistic to still land a digital/DV internship applying from now through spring, or have most teams filled their slots?
I'd like to work on side projects in my spare time to fill the gaps. What kind of project would actually stand out for digital design / DV roles? For example, a small UVM testbench, an open-source RTL-to-GDS flow (OpenLane/SKY130), or something on FPGA? Or are side projects not worth much compared to coursework and tapeout?
Which of my projects should I lead with, and is the software internship helping or just taking up space?
Resume attached (anonymized). Any advice from people who've been in a similar spot would mean a lot. Thanks!
I'm considering pursuing a degree in electrical engineering, but I have colour vision deficiency. I'm concerned about whether this could limit my career opportunities or prevent me from working in certain engineering roles.
Which types of positions require a pre-employment medical examination that includes colour vision testing? Are these requirements mainly for field-based positions, such as power line technicians and electrical maintenance workers, or do they also apply to engineering positions, such as electrical engineers and power systems engineers?
I'm currently a junior studying EE at a T10 engineering school and I'm completely torn on whether to take a spring co-op or stay in school to focus on research.
For context, I've previously interned in embedded firmware at a semiconductor company, have an ASIC design internship lined up for next summer, and have been doing computer architecture research for about 1 years. I've contributed to a conference paper submission.
I recently got an offer for a spring SWE internship at a major aerospace company. It's an industry I've been wanting to explore, especially since I'm not 100% set on staying in computer architecture/silicon long term (though I do enjoy it).
The dilemma is that I'm also considering doing a research-based MS, potentially followed by a PhD. If I stay in school, I'd have three semesters to continue my research, complete a senior thesis, and potentially get a publication. If I take the co-op, I'd only have two semesters left, which is enough for a thesis but with less time for research. I'd still graduate in four years either way.
I'm leaning toward the co-op, but I'm worried about how much losing that semester of research could affect my grad school applications. Would appreciate any advice, especially from people who've gone through research-based MS or PhD admissions. Also if anyone has gone to industry for a few years then went back to do MS/PhD, I'd appreciate any insight into that as well.
Also nowadays, how much value does getting a masters add?
TL;DR: Choosing between a spring SWE co-op in aerospace and an extra semester of research. Graduation timing stays the same, but I'm worried about losing a semester research experience and potentially a publication before applying to grad school.
When I first started working in electronics, op-amps were one of those topics I thought I understood — until I actually had to use them in circuit design.
Looking back, I realized that some of the basic concepts are worth revisiting, especially the ideal op-amp model, virtual short, virtual open, and the superposition theorem.
So I decided to go back to the fundamentals, organize my notes, and share what I've learned along the way. This is the first part of my op-amp learning series. Hopefully, it can help someone who's learning the same things, and I'd also love to hear how others approach these concepts.
Definition. The operational amplifier, or op-amp for short. The figure below shows the circuit symbol commonly used for it.
An op-amp has two differential inputs, u+ (non-inverting input) and u- (inverting input), plus a single-ended output uo.
2. The three assumptions.
(1) Infinite gain. A stands for gain and OL for open loop.
(2) Infinite input impedance: Ri = ∞.
(3) Zero output impedance: Ro = 0.
3. Two concepts.
(1) Virtual open. Since Ri is infinite, there is no loading effect at the inputs, so Ip = In = 0. In other words, no current flows into either the non-inverting or the inverting terminal.
(2) Virtual short. Since Ro is zero, there is no load effect at the output, so the output relates directly to the open-loop gain:
And because Aol is infinite, ud = 0, which means up = un. The two input terminals sit at the same voltage.
4. Ideal characteristics.
(1) Zero input capacitance. (2) Infinite common-mode rejection ratio. (3) Infinite signal bandwidth. (4) Infinite slew rate. (5) Zero offset voltage. (6) Zero offset voltage drift. (7) Performance that does not change with time, temperature, humidity, or supply.
5. The superposition theorem.
(1) Definition. In a linear circuit with multiple sources, the current or voltage in any branch equals the algebraic sum of the currents or voltages produced in that branch by each source acting alone. Node voltages and branch currents are first-order functions of the source values, and each response can be seen as the superposition of the responses from individual independent sources.
(2) Three notes. First, superposition applies only to linear circuits. Second, when computing one source's contribution, set the others to zero: voltage sources short, current sources open. Third, superposition works for voltages and currents but not for power. The sum of the powers from individual sources is not the real dissipated power; get the voltages and currents first, then compute power.
One habit I picked up early: write virtual open and virtual short on the page before any algebra. Nearly everything later in this series leans on those two lines, and the conditions attached to them are what separate a quick solution from a wrong one.
People often ask what parts actually go into domestic Chinese EVs, so I tore down a Xiaomi SU7 front headlight driver module to see. The back cover looked plain compared to an all-metal Aito M7 unit I opened earlier, almost like a knockoff at first, though that is just how these are made. Heavy glue between the bottom shell and metal front cover forced me to break the back housing apart to get the single-sided PCB out, which only has one external connector on the back.
The board runs on an Infineon CYT2B75CADQ0AZEGS Arm Cortex-M4 automotive MCU for lighting logic, PWM, diagnostics, and protocol stacks, paired with two NXP CAN transceivers—an SOP8 TJA1042 for body network comms and an SOP14 TJA1043 supporting 5 Mbps CAN FD for higher-bandwidth dynamic lighting data. Power and beam control use an MPS MP2019 linear regulator for 12V transients and low quiescent current, an ON Semiconductor NCV70517 microstepping motor driver for AFS adaptive beam adjustment, and a ROHM BD42530 voltage follower with ±10mV offset to track voltage and offset cable drops.
TI chips handle the LED drivers across primary and auxiliary circuits: a TPS92682Q dual-channel constant-voltage LED driver with PWM dimming paired with Diodes Incorporated DMPH4015SPSQ MOSFETs and Good-Ark AMBRP10H100 Schottky diodes for main LED strings, plus three 1.6A TI TPS92520Q dual synchronous buck LED drivers for auxiliary lights like DRLs. There is also another DMPH4015SPSQ P-channel MOSFET and an unidentified SOP8 chip marked 2LZ15.
Overall, the BOM mixes established international suppliers for core control, bus interfaces, and LED drivers with domestic parts like Good-Ark on discrete power components, sitting at the opposite extreme of the Aito M7 hardware setup I saw before.
I’m a graduating senior in ECE and secured an offer with Lockheed Martin for a full time position (heard it’s involved troubleshooting in RF team) and an internship (validation/testing) in a major semiconductor company i’ve interned with before. I enjoy both hardware power electronic and silicon level design. If i want to do chip design, i have to get a master at a reputable school like GT or Texas A&M at least, which would rack up my student debt (i currently don’t have any as my goal is graduate debt free). Then hope to get a full time position out of master degree. If I want to do power electronic design, I probably should do a master as well but the degree and school program aren’t strictly required to be had and reputable. I accepted the internship offer as it also pays similar to my full time position when annualized and it will get me closer to chip design. But i’m getting mixed feeling that i’ve made the wrong decision. I’ve been blessed to have easy interview for all the internship/fulltime interview i had so that’s why i did well. I’m also family oriented and the internship requires 24 hour relocation and full time is 6 hours (both drive). My family likes the fulltime better since it’s closer even though the pay (in MCOL) is even lower than power company pay in my LCOL area.
What would you do? Am I making the right call by betting on the future and master program? Should I just settled for a master at my current school (can complete in 1 year) and work for power, which might involves optical network stuff that i thought is interesting
I have a technical interview with the CPU design verification team (UK). The recruiter said it's CV-focused plus critical thinking. Has anyone done this recently? Was there live coding, SystemVerilog/UVM questions, or mainly CPU concepts? Any tips appreciated!
So I am choosing my major and I am really interested in math and machine learning however I am also interested in hardware and chips. Hence I want to keep both doors open, I imagine that if I did a math/cs major I wouldn't be able to do much in terms of hardware, but was wondering if EE or CE is still viable for a machine learning career. I am also wondering if there are specific niches/fields that combine both sides (machine learning and hardware stuff)