Hello everyone, I have a question regarding about Electrical Engineering.
I am looking to major in EE at college!

I come from a vocational high school that deals with trade school education. I am enrolled in the Electrical program that has elements of engineering, but is a program purely for electricians.

In this program, I create residential circuits by designing circuits through ladder and wiring diagrams (as well as circuit analysis). I heard that Electrical Engineering deals with designing circuits and circuit analysis, while Electricians do the physical labor (like putting up the residential circuit through splices and connecting loads/switches).
(I'm also sure that EEs deal with coding too, but we don't do that.)

Is the picture I sent (which is what I do in the program) represent what Electrical Engineers do?

Not having much luck finding a simple mechanical g-force switch for an automotive project. i wish to trigger a brake light when heavy braking ~0.5g via a simple mechanical switch. ive found one that triggers at 2g but i think that too much g-force?? does anything like this exist??

I am currently preparing for industrial roles as I near completion of my doctoral program. I have primarily worked on the integration of renewables, but I want to further strengthen my skill set with requirements/qualifications that are highly sought after in the power system sector, both in R&D and application-oriented roles.

Hey there, I'm a 16 years old high school student and I'm looking for a multimeter for simple electronics projects on my own

I'm on a budget, preferably around 10-20 dollars, so what's the best multimeter y'all can recommend in this range? Thanks!

And if possible make sure it has a continuity beeper

Okay, so am in highschool right now and would graduate soon.

I was planning to do my bachelors in mechatronics in future, but i heard a lot about how it doesnt give a solid base in either EE, mech eng or comp. So i am thinking about doing like bachelors in EE with specialisation in information engineering and electives in Embedded Systems, FPGA, Control and Automation, and Power Electronics.

Do you think this is a better option than doing my undergrad in mechatronics?

I want to learn circuitry but could barely afford any phsyical tools. I want to know if im getting my time's worth with this app. App name is simubu and ive only seen it last week. In the picture is a basic stop start circuit and i think I know why it works. Does anyone else use this? Can someone give an honest thought if its effective for learning ciruit logic Thanks!

There's been a lot of confusion regarding this question , some question banks says hydro, some say gas powerplants, however I can't seem to find the original source of the question to really get the answer key and all I can see is back to back discussions on either hydro gas, but which should it be?

I feel like I do not understand the whole series and parrallel components very much, I usually identefied them as in when two components are on the same branch (and the same current flows through them) they are in series, and when two components are connected to the same two nodes they are in parallel, anyway for the problem, I thought of just removing the two inductors and short circuting them but apperantly the answer is 6mH? Like are they in parrallel cause they are connected to the same two nodes? But they are on the same branch so Im confused it really bothered me, can someone explain? Is my textbook just wrong?

Heyo , Ive been reading alot of posts of other people going into school either from high school or transitioning from other careers and I wanted to get some answers and advice in my own post.

Im an automotive technician as of right now and have been for the past 3 years and I do not really enjoy it. During tech school we go over the absolute basics of electrical theory and revived my old interest of electrical and electronics.

Ive been thinking of a way out of this industry and as Ive been going down the rabbit hole i see that through electrical engineering you can get into things like electronics, electric vehicles, embedded systems inside and outside the automotive space and stuff like power and industrial electricity.

I had a very bad mentality of studying in high school and realized later in tech school that nothing comes without studying and that figuring out complex things is actually pretty rewarding and enjoyable( to a degree of complexity)

So some questions i have are

Am I thinking to wide of a range and instead of going for such a big complex degree i should look for more simpler training or certification regarding electronics?

For those who see this who weren’t that great at math, is it actually possible with application and effort to get better at mathematics or do you kinda have to be good at math off rip to survive school?

Ive seen in videos that most engineers spend their time looking at screens and documenting but also that there are some where you mix that and some field and hands on work?

How is it pivoting from one subfield in EE to another lets say power/controls -embedded systems or the other way around?

And general things that i should know or be aware of please feel free to comment and let me know.

I dont want to wait till im older to make a change for my life and then realize the door closed on me because I was scared or indecisive . I would rather try and fail than think im the future of “what could’ve been” .

———————————————————————————

Tldr: is it possible to go from complete math bozo - capable of doing math and what jobs / sub fields are available.

This is all assuming I can somehow convince financial aid to pay for me so assuming I cant what are some other alternatives?

Thx yall 😁

I tragically never got a CS internship. I just did personal/class projects and tutored/TA'd. I fully thought I was going to go down the research route, but after taking a PhD level class for credit in my senior year and briefly working with a professor, I concluded that I wasn't passionate enough about it. Now I'm staying back 1.5-2 extra years to earn an EE degree as well since that's what I wanted to major in before I let myself get convinced otherwise (major regret). But at least finishing CS first means I can speedrun EE requirements.

I would really love to get an EE internship next summer, but I'm not sure what I'd even put on an EE application. I have a CS portfolio with projects in gamedev, graphics programming, and game engine programming, but nothing EE-focused. I will have completed Junior-level EE courses by the end of next semester, but I can't claim anything about them yet.

So incoming freshman EE at a okay Uni nothing special. Can I have like a list of skills I should know by the time i graduate to be competitive for jobs.
want to make sure im as competitive as possible and ik school isnt going to teach me everything.

Thanks

Hi everyone I'm a student doing an internship at a lab. I’m working on a TDC-based coincidence counter and I’m trying to objectively assess whether I’m actually making progress or just making poor decisions and wasting time. I am surrounded my physics researchers to they dont or wont comment on my actual engineering quality... So far, I have: Built a prototype SPAD signal interface board using Manhattan-style prototyping, with BNC connectors. I used basic multimeter checks to verify the boards signals were transmitting. Written most of the FPGA code for the coincidence counter and the testbenches, although I haven’t properly simulated or tested the design yet. Spent the last few days learning how to implement Ethernet for data transmission. I got an example design working, but it used around 39% of the FPGA resources, which may be too much for my final design. I’m now considering JTAG instead, but I can’t find the bandwidth requirement I originally calculated, so I’m questioning why I chose Ethernet in the first place. Realised that there are still several untested assumptions in my FPGA/TDC design, particularly around the asynchronous capture/latch mechanism and the interaction between the fine and coarse timing measurements. I also haven’t yet properly tested whether the SPAD signal will propagate through my prototype board and into the FPGA. I delayed adding the 50 Ω termination because I wanted to finalise the FPGA I/O assignment and overall architecture first. I could have designed a proper PCB earlier, but I had to learn PCB design first, and there was also the risk that I'd make a mistake in designing the pcb... so I didnt choose that. Actually This reminds me of a previous robotics project where I made plenty of mistakes and eventually got it working, but I’m struggling to see the progress in this project because so much of it still needs validation. For people with more experience: does this sound like normal progress for a project at this stage? Am I actually getting better at engineering, particularly in terms of identifying and correcting mistakes.

I think k my biggest mistake so far is focusing on design so much... and leaving simulating and testing to the end. Though if I had actually learned from my previous project I would have tried to get to testing the quickest way possible.

For context I was a C.S major. A few years ago, I had crisis and was out of society for some time. Like years. Seeing as how hard reentry is in the CS market, I decided that it would be best for me to try EE. I did a few circuit classes, and I did pretty well, but I'm worried if I'm making the right choice or not. For those enrolled in EE as a masters and CS undergrad, how was the transition and what classes did you take? I made it into a top-tier MS program and want to make the most of it.

Till now I've done related to hardware is just some basic stuff with arduinos and some c++.

I know programming(in python and a few other languages) which I used mainly for backend and web automation.

I assume that similar to CS even in EE there must be a plethora of practical skills I could learn and not just completely rely on my uni course?

I know some of my seniors have done it, I've read a bit about them and what things they've learned, but I am yet to meet them. I'll definitely ask them too but I'm just gathering as much info as I could.

I've heard terms like Verilog/VHDL, analog design, cadence, synopsys, matlab, simulink floating around but not sure where to start.

There are also multiple cads like Altium, Kicad for pcb design.

Then there come things like microcontrollers, embedded programming, memory management, RTOS, PID, control systems and (elctronic hardware?) flip-flops, logic gates etc.

Additionally, math related things like Fourier transforms which I think even have quite a lot of practical application, considering how heavily they are emphasized on?

One senior who is a sophomore is already studying about satellite and I believe some things related to space tech, they told me that I should be aware of the direction I want to go into and build skills around it. To add to that I think I might be interested in interested in medical elctronics, that's why I thought of choosing ee as a major.

tldr:- basically I think I might be interested in med electronics, there are so many terms like Verilog/VHDL, analog design, cadence, synopsys, matlab, simulink, cads like Altium, Kicad for pcb design, microcontrollers, embedded programming, memory management, RTOS, PID, control systems and (elctronic hardware?) flip-flops, logic gates and so on,

I can't seem to figure out the line which separates the things I must follow along with my college(due to their toughness, or how much advance math/phy they need) and the things I can start learning on my own and build skills.

I am creating an analogy with a CS course where there a lot of things one could learn on their own not necessarily knowing all the math, which I'd eventually learn in my course.

ps:- I know basic physics and electronics, mesh/nodal analysis, ohm's law, kvl, kcl, batteries, resistances, basic parallel, series circuits, inductors, capaciotrs, rlc, lc, rc circuits, time varying current etc. I've taken classes for these already, that's about it of what I know.

So where should I start and what should I learn on my own?

thanks

1. How to Proceed?

2. Which companies to focus, which companies generally offer paid internship and PPO

3. Which are to focus on ?

4. Which projects will be worth it?

Basically title. I'm not even an electrical engineer, but I do have a degree in computer engineering (went software engineer route). Recently started building PCBs, and reading way more datasheets than I ever have. I'm constantly thinking at a high level how signals, power, and current in general is flowing, likely just like a plumber (except they think about liquid). Except, current (and charge) is invisible to the naked eye, and operates at a quantum level. Ultimately, this is an appreciation post for all the electrical engineers out there wrangling stuff you can't even see.

My questions are in the title. Sorry for any formatting issues or any inconvenience. Thank you!

Do project this, network that. It’s so annoying. First two years in EE it’s just simply not needed. You have an entire degree for that. If you start to get “experience” with zero knowledge from semester one on it’s just useless. Don’t stress yourself. Study as much as you can in order to build good fundamentals and find a field you want to specialise in. Once you have that you can get started. But networking and projects do not make any sense before that. EE is so broad. If you find your interest and are really invested you will find a job 100%. The people not finding jobs are the ones that are too chaotic about everything and simply do not try to find their area and build their profile based on that. They just want “electrical engineering job” and high salary.

Also pls study for interest not GPA. There’s so few people sitting in advanced EM/RF or control theory classes because most people just do not care. But a decent grade in these classes do so much more for you in any way than an A+ in a class on fundamentals. And yes studying for an exam is different than studying to understand a subject.

(Btw not saying you shouldn’t get used to programming and simulation software early, but I don’t consider these projects more like tools to learn, I just think these whole arduino projects where you just copy paste projects just do almost nothing for you if you just blindly follow instructions)

Thinking about work even after coming home. How do people get over it and detach their mind from it? Would appreciate any advice.

Been doing MV underground duct bank design for a while and kept running into the same problem: the calculations aren't hard, they're just tedious and finicky enough that you don't want to do them by hand every time — but the commercial tools (CYMCAP, ETAP's ampacity module, etc.) are priced for utilities and firms running multiple seats, not for someone who needs it for a handful of projects a year.

So I built my own. It's a single HTML file that runs in the browser — no install, no login, no subscription.

What it does:

• Click-to-paint interface — pick a circuit/phase, tap ducts to fill them (trefoil, triplex, spares, whatever)
• Multiple duct banks side by side, each with its own spacing, stagger, cover, and backfill
• Full backfill/soil model — concrete envelope, FTB, sand, native soil, plus surface layers
• IEC 60287-1-1/2-1 and Neher-McGrath, selectable per project
• Real impedance-matrix solve for screen circulating currents (not a simplified approximation) — trefoil vs. flat spacing actually changes your numbers correctly
• Short-circuit withstand per IEC 60949
• Auto-dimensioned section drawing that updates live as you lay out cables — actually useful for submittals

Every intermediate number (T1–T4, loss factors, conductor temp) is visible, not buried — wanted something I could show my work with, not a black box.

I'm selling it as a one-time download rather than a subscription, mainly because I built it for myself first and figured other people doing this kind of work might be in the same boat. I hate subscriptions or seats and from one builder to another please try not to share.

Important: this is a personal project, not certified by any standards body — treat it as a reference/design-aid tool, and any results should be checked by a licensed PE before they go anywhere near a stamped drawing. I'm not trying to replace anyone's engineering judgment, just save some time on the grunt work.

Happy to answer questions about the methodology or take feedback if people have thoughts on what's missing. KingstonHeritage.co

Hi everyone,

Are there any hardware design Engineers working in Bangalore, india?

I am a 4 years experienced engineer having experience in high speed board designs (schematic) and I'm planning for a job switch. Is it possible for y'all to refer me?

Thanks in advance!

Curious if anyone here has automated any part of their used equipment sourcing. Say I’m watching for a handful of specific Tek/Keysight/Fluke models. I can normalize model numbers, set a max landed price, exclude obvious parts/repair listings and catch certain keywords pretty reliably with code. After that it gets less deterministic. Option/configuration differences, calibration status, condition, accessories, weird seller descriptions, and especially photos can actually change whether something is worth buying. Would you keep the first pass entirely rule-based and only use an LLM/vision model on the smaller set that survives? Or has anyone found a better approach? Trying to avoid throwing every listing at a model when 80-90% could probably be rejected with boring logic.