r/ComputerEngineering • u/AlexanderrFox111 • Oct 13 '23
What do computer engineers do
I always look up things like "day in the life of a computer engineer" and only see videos of software engineers coding. I know i can find online descriptions of various jobs a computer engineer can do but i have no idea what it actually looks like. Are you in front of your desk connecting pieces of hardware to see what happens, are you in a lab looking at graphs or simulations, are you working with new cutting edge technology? I have no idea and would appreciate if someone could help me get a better idea of what i should expect in a computer engineering workplace.
57
27
u/Zander9909 Oct 13 '23
As another commenter said, CE is a very broad domain where as a job you can have people who are doing web design, full stack dev, back end dev, FPGA design, hardware verification, IT/networking, and so many other things. There isn't one set path, which is exciting but also makes it difficult to describe our roles and career prospects
26
Oct 13 '23
i have a ce degree. work as a fullstack web dev
5
u/CarlosChampion Oct 18 '23
Same, my CE academic advisor told me if I don’t get a masters I would be stuck doing web development. Jokes on him this is one of the best jobs I’ve had
4
Oct 18 '23
Lol, definitely. I really love what I am doing and I can't say my CE degree doesn't help. I t gives me a lot of insight as to how the computer system works, especially in terms of cloud engineering.
Also, I cannot underestimate the beauty of remote work.
19
u/claytonkb Oct 13 '23
Mainly updating JIRA, lol.
In my career, I've mostly worked for household-name chip makers (CPU/SoC projects). Different CE's will have different answers, but I imagine that my answer will reflect any "mainstream" CE's experience.
Chip design flows are extremely long and complex. In software, you write the code, compile it, check/test it, then iterate. Ideally, the compile is the longest part of this loop and that might be only seconds if you're working on a small-to-mid-size app. By contrast, in chip design, the "design, 'compile', test"-loop is measured in months. For this reason, chip design is done more like a rocket-launch, in terms of timelines, project management (such PM, much wow).
The big-budget CPU/SoC pipeline is something like this: perf analysis, architecture, high-level (block) design, physical design / logic-cell design, RTL design/coding, unit testing, pre-silicon testing, tapeout, fabrication, post-silicon testing. [Note: I'm skipping approximately a million details.]
The perf analysis team is going to run real-world workloads on the previous chip and try to locate kinks in the pipeline. They will identify aspects of the design that have low-utilization or over-utilization. Power-analysis is another aspect that will happen during this stage.
Nobody knows what the architects actually do, but they give super good presentations. I'm just kidding, the architects are something like the "branch-predictors" of the chip design pipeline. Their job is to ratio-match between the goals that management wants to achieve for the product, versus what design is telling them is realistically achievable. Sometimes, this involves pushing design harder, sometimes it involves playing defense for the designers against management. In the end, the primary goal of the architects is to guide the design decisions to best-achievable metrics, on a realistic timeline. They work with perf-analysis teams a lot, and do a lot of their own simulations.
The high-level designs are done by the various unit leads. A unit or block in a chip design is just some functional component of the design that has a relatively well-defined interface. I say "relatively" because, compared to something like OOP, chips don't really have interfaces. It's a real nightmare: there is rarely, if ever, an authoritative single copy of important system state. It is often cached in multiple places, often stale, and who has the authoritative copy at any given time is frequently dependent upon the state of the machine. Everything in that previous sentence should give software folks a migraine. CE's live that migraine over their whole body, all day, every day. Anyway, what frequently happens is that the unit/blocks break down on floorplanning lines, meaning, "everything on this section of the die is yours, everything in this section is ours."
*Power-Management Unit has entered the chat*
PD/logic design is kind of a parallel track to the main pipeline, and has to do with setting up the main toolchain that will essentially be the "compiler" of the chip. In chip design, our "compiling" is called synthesis, and it is the job of the PD/logic team to ensure that the "standard library" of the synthesis toolchain is working properly and can actually meet the design-rule checks on-silicon. These are the folks who tell you how many nanometers your next technology node will be, so nobody messes with them.
The RTL design/coding team are the closest thing to "software developers" since they write the actual HDL (hardware description language) code that will be compiled by the synthesis tool into the final design. Even though they write HDL code, what they are doing is more like CAD design than like writing software. The HDL is really just instantiating hardware blocks, and then describing how the signals (interfaces) between those blocks will communicate, and what their internal logic/state will be.
Unit-testing and pre-silicon testing are closely related to RTL design since these teams actually simulate the chip during the design process. So, you can think of them as being the compile/test loop. The difference is that compile takes hours, and test can take hours, days or even weeks depending on the type of testing you're doing. I've never been in PM, but I assume that this is one of the most expensive aspects of chip design since it consumes enormous amounts of compute.
The final revision of the RTL will be frozen, subjected to a last battery of qualification tests and then will pass through what is called tapeout, which is a process by which the entire design is converted to a set of files that will be sent to the fab to be physically manufactured. The fab is what actually manufactures the initial parts.
Finally, there is post-silicon testing. This is a huge aspect of chip design and spans everything from powering up the chip, to fetching the first instruction from RAM, to recreating pre-silicon known-bugs, to pre-silicon simulation of new post-silicon bugs, to booting an OS on the fabricated chip, and so on. Typically, a top-to-bottom redesign of a chip will pass through this phase at least twice, meaning, the first time through, the chip is not going to be productized. We call this an "A-stepping" and is roughly analogous to an alpha version of software. The main goal of this stepping is to find all the product-killer bugs, meaning, the bugs that prevented the chip from actually going out the door to customers. It's bad enough to have to waste all the money on one failed stepping, you don't want to do it twice. So, the goal is to ensure that the B-stepping will at least be shippable, regardless of what other bugs it may turn out to have. In addition, the A-stepping is usually on a highly compressed time-frame, so we need to find all those bugs fast so RTL can fix the bugs and get the fixes checked in before the next freeze.
I know I didn't directly answer your question, but I hope that this overview of the chip-design pipeline helps you understand why there is no simple answer to your question. Personally, I've spent a lot of my career doing system-level verification (testing), so I have spent a lot of time getting help from other engineers who know more about the part of the design where the test is failing. So, it ends up being a lot of emails like, "Please explain to me how this thing in your unit works so I can figure out why it's breaking something else way over in some other unit that you don't care about." Then, once the threads are untangled and the cause of the failure becomes clear, then a fix is identified and checked in. A lot of this ends up being bad caching, wrong assumptions about interfacing, etc. "Oh, oops, we thought our copy of cached state was valid, but we missed the line in the spec where it says under XYZ condition, it's actually the other unit's copy that is valid and we are stale, so we have to query them first before moving to the next state." *sigh
11
u/ScheduleSame258 Oct 14 '23
Jesus . You are good at writing. Are you the designated Jira updater?
Lol.
10
Oct 13 '23
Jr engineer here (just over a year out of uni). I am one of those writing code all day.
But at my last job I was developing a prototype c-arm x-ray. So, I also spent a lot of time in a lab in front of a lead box, firing x-rays or random things to entertain myself as I worked out bugs in the system's code. Still mostly sitting at a desk writing code, but at a less comfortable desk with breaks of x-raying stuff and occasional assembly of electronics.
Current job, current project is writing a library to talk to a temperature controller (looks like a DC power supply). Very much at my desk all day writing code. But also there is something physical I'm communicating with which is loads more interesting to me than web stuff.
1
u/Comfortable-Fail-558 Oct 16 '23
That’s awesome!
Does the X-ray to data part already work and you are adding analysis? Or is it a driver for interpreting the X-ray signal?
I’m surprised you get to work on these things as a Jr, do you have a team interacting with the same X-ray?
1
Oct 16 '23
Pretty much already works. I worked on the image/data flow as well as developed the GUI for the system. There is a flat panel detector that captures the image that I would interface with, the x-ray generator that I sync to the detector, then do some image processing and put it up on the screen.
The GUI allowed for touch interface so you could pinch zoom, pan, and rotate the image.
9
u/BlackestFlame Oct 13 '23
I assumed using matlab and multi sim all day making complex circuits. One of my substitute teachers showed us something he was working on at the company he works at.
6
5
u/Quiquiro Oct 13 '23
Im a CE graduate, working as a Controls Engineer/Systems Engineer programming PLC for pharma companies.
2
u/shrubbyspex Oct 13 '23
This is what I just accepted a full time job doing, do you enjoy it?
4
u/Quiquiro Oct 13 '23
Ahhh...
I don't love it, but in the long run, it pays amazingly well. Im mostly in it because i started as a drafter and literally was handed a position later on, with amazing benefits and decent pay.
3
u/shrubbyspex Oct 13 '23
Intrestinggg. How decent of pay are we talking if you don’t mind me asking
2
u/Quiquiro Oct 13 '23 edited Oct 13 '23
ATM 55k in a low cost of living area. But I've gotten offers to up to 75k on several occasions.
I only have 1 year of experience, with 3 before that as a CAD Drafter.
Benefits are 3-6% match 401k (3% free + 3% for a 6% contribution)
Amazing health plan with super low deductibles.
Hybreed workweeks 3 days in office or with a client and 2 days remote.
Car and unlimited gas (I use it for personal usage).
15 days of vacation, 3 floating, every federal and local days, and 12 days of sicknesses. Goes to about 38 days a year free. Also super flexible hours.
The other offers I've gotten are usually on contract with no benefits at all.
1
u/buyo05 Oct 13 '23
Interesting. What type of machines are you working on?
1
u/Quiquiro Oct 13 '23
Mostly HVAC, Air handling units, chiller integration, system automation, etc.
Mostly systems from Allan Bradley, Johnson Controls, Siemens.
1
u/buyo05 Oct 13 '23
By any chance, have you worked on bioreactor machines?
1
u/Quiquiro Oct 14 '23
Nope, but you'll prob be making tons of money lol
2
u/buyo05 Oct 21 '23
I always wonder if CE's get to work on those type of machines
2
u/Quiquiro Oct 27 '23
Probably, remember CE is somewhat a Jack of all trades. I'm over simplifying it but I've seen university friends in way different areas.
Some are in development, banking, analysts, IT, management, Crypto, PLC, QA, Validations, finance, automation, AI, power grid, system signals, hardware programming, etc.
Technical and non technical jobs.
4
u/Peetersc93 Oct 13 '23
There’s lots of different options which is the best part of CE. You can do software, hardware, a specific subject in computing (e.g., ML or security), or something completely different. I’ve worked hardware positions in the past, I’ve done some work with machine learning and signal processing in software, and currently I do consulting for tech related patent law. There is a world of possibilities with computer engineering.
4
u/turkishjedi21 Oct 13 '23
You can be doing a lot of things. For me when I think of ECE I specifically think of rtl design or verification - to me its the most "ECE-y".
I'm an ASIC Design engineer for a telecom company, but they have me doing verification. My day to day is basically just writing systemverilog that adds on to our UVM infrastructure for an LDPC decoder accelerator we are working on. Sometimes I'll be writing sequences for a test, sometimes I'll be writing an entire test, sometimes I'll have to help make a testplan.
It's sick
4
3
u/socialist_mermaid34 Oct 13 '23 edited Oct 13 '23
CoEs can also go high-level and develop machine learning SCADA systems for the grid.
There's a special place in every organization for EE's who can code and understand software development.
Cheers!
Edit: It is baffling how many legacy desktop software applications are still being used to run the grid and perform electrical studies. There is a lot of money being dumped into Google start-ups to tackle the issues that come with these legacy systems.
3
u/RoyalBoot1388 Oct 13 '23
Everything....just everything. I work in data communications (networks), so I have done the following:
Site survey - Review sites and develop specifications for space, electrical, HVAC, fiber and copper plant and turn-over to subs for quoting then validate they meet requirements.
Network design (topology, protocols) of enterprise networks. Which includes planning, budgeting, list of materials, project plans, work scheduling, etc...
Network proposals - Take the design and create a formal bid or proposal (written with drawings and pricing) that could be 100+ pages, or a face-to-face interview to win the work.
Network installation - which includes acting on all the stuff above, leading installation teams, or going in the field and doing it myself. Then turning the keys over to the customer and never seeing the network again.
Network support - operations and maintenance of a network I manage for others. Maybe do system migrations, but maybe just boring upgrades and move/add/change (MAC) work.
It's like systems engineering because you have to know about electrical, electronics, mechanical, project management etc....; but you also have to be a subject matter expert for the network itself. I've presented to a major client in a suit and tie one day in silicon valley, and a week later I'm sweating my ass off 2000 miles away in a nasty rat infested closet, racking some equipment or ripping out some old stuff. Few months later, I'm climbing on a chopper to do a service call on a mountain.
I have friends & coworkers that never leave their office. Some only do design, some only do coding and some just manage others. I have an ex coworker that was a program manager....and I've seen that guy in a hole with a shovel helping set a cable vault and another (also a PM) that has his climbing certification so he can scale towers for inspection or repairs. Like lots of jobs, it's what you make it. Having an engineering degree just opens up the aperture a bit.
1
Oct 16 '23
Any advice for someone with a degree geared more towards programming and network and IT infrastructure, but also likes to go out and do stuff in the field like you described? Like which sorts of companies hire for those sorts of roles? Or is it something you really have to evolve into from a starting position?
1
u/RoyalBoot1388 Oct 16 '23
TL;DR You have to start doing grunt work before you start designing & planning; and never turn up your nose at field work, even after you're at the senior level (for senior level $$ of course). Defense contractors travel a lot.
I started my career (kinda) doing IT type support and installation for medium/large enterprises. This involved doing lots of local field work on the company network. Grunt work replacing switches, upgrading routers etc.... Eventually this morphed into more design, planning and overseeing others.
When I left commercial enterprise work, I went into the defense industry. Most of the the stuff I mentioned was when I was working for a systems integrator. There I did a mixture of desk work and field work, but over time, that changed into mostly desk work (design/bid/project management). The last 2 companies I worked for didn't want me doing any field work because it was too costly, and they wanted my skills to bid new work. That said, if the SHTF on a job, or a customer wanted a senior level guy on site, I could deploy as needed.
Being a router-monkey on the command-line or firewall GUI is still good experience, but the physical support and installation work gave me tons of actual hands on experience that allowed me to better understand requirements, how to perform site surveys, and make accurate bidding/estimating for proposals. That was very attractive to employers. I also never turned up my nose at field work, even as I got older, and I kept many of my certifications active. This is tough when you get older. It takes a ton of time, and you have to "find" opportunities to keep your skills somewhat sharp.
I still go into the field occasionally because I like it and it's infrequent enough that nobody complains about the budget getting killed.
3
3
u/Moby1029 Oct 17 '23
My mom maintained COBOL code bases for General Dynamics (various missle systems) and my dad literally built FoF systems for helicopters during Vietnam and designed communications satellites for the Navy, among other Top Secret projects. Both CEs. Mom focused mostly on software and my dad did it all from building a computer from various components to run flight Sims for crash analysis to actually writing the OS and the flight sim software and created the computer models and camera angels of the planes for the program. It's a very broad field.
2
2
u/fireflywithoutalight Oct 14 '23
CE grad in GPU verification. Attend many meetings. Debug and fix failing tests using combinations of waves, logs, code and debugger. Update/add to/improve/fix system verilog testbench. Update status and test plan spreadsheets, documentation and tickets. Read and try to understand specs. Answer questions from coworkers/management. Stare into the abyss sometimes? Also meetings.
1
u/manngeo Jul 12 '25
From the concepts to requirements and the architectures to design, , development = implementation like software coding, functional and unit testing to see if it is doing what it is supposed to do. Both in software and hardware. Then finally integrate into an overall product. Repeat the testing again before shipping or deployment.
1
u/patrick_wayne_herron Oct 13 '23
Depends on a multitude of complex issues related to a human doing a job or a robot. Ai is a CE because of analytical gathering. Then Nature(Birds, Bees, etc.) are also CE's because they can manipulate Some Police Dept Computers and US Military as well. Then ya got guys like myself who are bio hackers who were/are responsible for a multitude of different topics compared to say, a Bird spreading pollen, seeds, and poo. I' was trained to do what I know how though when I was stationed in Northern Canada.
1
u/filipinoferocity Oct 13 '23
I got a mechanical engineering job but i do a lot of data analysis and simulation development so that’s where i use most of the knowledge i got in college
1
Oct 14 '23
Mind if I ask specifically what you do? I’m about to transfer to a university and currently deciding between ME or CpE. I’ve had my eye on guidance, navigation, and controls engineering which I understand involves a lot of analysis and sim development.
2
u/filipinoferocity Oct 15 '23
My job title is Propulsion Analyst and I work at NASA. I love it a lot! I find my background with software has helped a lot as most of my team consists of mechanical engineers. I am able to understand a lot of the software we encounter at a much deeper level than they are and they help me understand all the ME elements that I don’t get.
1
u/Reddit_killed_RIF Oct 14 '23
Basically anything a computer science or electrical engineer can do. Sometimes even mechanical engineer but that's a lot more rare since they don't usually share the same courses in college.
IT is also another common route but it doesn't carry the engineering titles.
There is a lack of electrical engineers right now.
1
u/clingbat Oct 14 '23
Here's a less common one I've done for over a decade, regulate consumer electronics and IT/data center equipment for the government.
Undergrad was computer engineering, grad was electrical engineering.
1
u/strat61caster Oct 14 '23
You solve problems.
User found a bug - what’s causing that bug, get data, pinpoint problem and figure out solutions, often more then one available, start working on solutions, decide which ones to follow through on, communicate to the rest of the team to make sure it’s a good solution and won’t mess up someone else, or that there’s not a better one you just didn’t think of. Follow through on implementing the solution, sometimes it’s a bit of code, sometimes it’s ordering a different part, sometimes it’s a year long design update with paperwork and meetings for days and days.
Then there’s designing something from the ground up to solve a problem, sometimes you’re free, sometimes it’s copy X but add Y. Rinse, repeat until you retire or change careers.
1
95
u/Headshots_Only Oct 13 '23
There's lots of things a CE can do. They can code all day in languages like C or python, they can code for websites in those languages. They can design circuits using software by physically creating the layouts at the transistor level. They can design circuits using FPGAs by writing essentially C code.
Pretty much, they can do anything a computer science or electrical engineering major can do. Just depends on what classes you took at the end of your major and if you went for a masters/phd