I picked "software" as that's my job. However, like most people I do a bit of everything. I've done everything on the scale of high level architecture down to embedded and the hardware it runs on.
One thing I particularly like about my current job is the overlap between what is officially my job and the things around it. It might not be in my job description, but I've worked with custom hardware, VR headsets, interfaced with industrial robots, drifted into interfacing with and developing for game engines - and then even modifying the source code of that game engine. I find it's the gaps between areas of expertise where the really interesting stuff happens.
I picked "software" as that's my job. However, like most people I do a bit of everything. I've done everything on the scale of high level architecture down to embedded and the hardware it runs on.
One thing I particularly like about my current job is the overlap between what is officially my job and the things around it. It might not be in my job description, but I've worked with custom hardware, VR headsets, interfaced with industrial robots, drifted into interfacing with and developing for game engines - and then even modifying the source code of that game engine. I find it's the gaps between areas of expertise where the really interesting stuff happens.
My job title is STAFF, which means I should be very flexible to fit into all unpredictable jobs from my day-to-day work. After many years practice in the electrical engineering path, I am pretty enjoy the role as a STAFF engineer. So I picked embedded design engineer. I do more hardware projects than software projects.
