← Back to context

Comment by 7thaccount

4 days ago

I'm a EE and had no problem finding a job and neither did any of my classmates in my EE program (early 2010s). I also didn't exactly go to anything approaching MIT, but it was an engineering school and I had a decent GPA. Particularly, there are a lot of well paying jobs in power systems with good work life balance. We have an energy transition going on, so that helps. Having an internship probably helped me too. I acknowledge that things might have broadly changed.

> there are a lot of well paying jobs in power systems with good work life balance

How much electrical engineering is there in these jobs? I knew a few electrical engineer at university (weirdly they outnumbered the software engineers 3 to 1) and some of them told me they could get work for a local power company, but it was mostly looking at spreadsheets and not really using anything that they'd learned.

  • It depends on what exactly you do as the industry is so vast.

    It is true (I'd wager this is true in most engineering fields) that very few actually use a lot of what you learned in school as it has all been put into fancy software packages. For example, my wife uses some kind of drafting software to design things like roads that she learned all the math to understand in college. It is the same in my industry where yeah, you use a lot of spreadsheets and Python scripts and SQL to help automate software and analyze the results. In a lot of cases you don't really need an engineering degree, but it helps a lot in understanding what is going on when the results don't make sense. Getting the engineering degree is also just really good training for the kind of rigorous thought processes needed for solving open problems.

    There are also plenty of jobs in power that are closer to what you would consider engineering. For example, you might have to go to the substation switch yard, help supervise a crew installing new transformers, help design a microgrid...etc.

    I'll add that it is pretty common for engineers to have some kind of existential crisis once you graduate and you realize what you thought you'd be doing once you graduated (in my case crawling around Jefferies tubes and fixing the warp reactor) is totally different in the real world. It's kind of similar in computer science where most graduates are basically just gluing library code together instead of writing their own software from scratch in C. I recall reading somewhere that the famous SICP course moved from Scheme to Python precisely because of the change in how people coded now.

    • > I'll add that it is pretty common for engineers to have some kind of existential crisis once you graduate and you realize what you thought you'd be doing once you graduated (in my case crawling around Jefferies tubes and fixing the warp reactor) is totally different in the real world.

      Thank you for saying this out loud. It took me years to recover from this, and I "recovered" mostly by giving up and accepting that, unlike fiction, real world doesn't have to make sense or offer interesting, fulfilling work.

      Now I just dream that one of these days, I'll build a house, and I'll design it with a Jefferies tube, just to scratch my itch.

      1 reply →

Similar qualifications here, but no internships. Couldn't find anything after grad school in the early 2010s (and still nothing in the mid 2010s after trying again). Went into telcom and I'm a happy little coder now. Nice to actually feel appreciated in this field compared to EE where it felt like I was always working my butt off for scraps.

  • Just curious, were you still looking for entry level jobs after grad school or something more in the R&D realm?

    • I was focused on finding something entry-level. Did a non-thesis masters focused on mixed signal / RF design and R&D didn't really appeal to me at the time