I’ve sort of already discussed this in previous posts, but this will hopefully be a bit more focused. I’m gonna list specific experiences/activities that I’ve enjoyed previously. Tooling and lab automation: It feels good to enable others/myself to work faster - Built a Python script to speed up the process of calculating the volume of liquid inside a test tube from an image - Built level editors to create content for my Steam game - Creating a Docker image for installing and working with Geant4, a particle simulation software Pinpointing bottleneck and the root causes of errors: I enjoy breaking down a larger system/problem to reveal potential issues - Profiling my game code to find sources of potential optimization - Writing a custom language interpreter in C++, for my data structures class, and fixing issues with memory using a debugger Breaking down large systems into individual components/tasks to work on - Creating the state machines that manages the behavior of the enemies - Designing and developing an alert system for the enemies in my game to believably react to events in the environment like explosions and player footsteps Implementing theory and algorithms in practice: Thinking something might work to seeing it actually work is really exciting - Researching collision detection algorithms and struggling to implement them, until I finally get it work - Creating a square wave generator: Researching oscillators, drawing out circuits to understand the oscillators, doing the math to get the period of the oscillator, and breadboarding components together to create and test the oscillator Given this, I think I’d enjoy working on some sort of hardware-software system where I need to either iteratively develop code to be used on constrained hardware or build and put multiple pieces of a system together, in both hardware and software. On the way, I’d also enjoy automating manual tasks with scripts. I’m afraid this post might be a little vague. Frankly, I enjoy most technical problem solving especially when I go from not knowing where to start, to understanding a problem and effectively building a solution for it. I don’t think I’d enjoy problems where I have to deal with a lot of black boxes within the problem itself, because it wouldn’t feel like I actually understand what I’m solving. Thanks for reading!

Given that I have a pretty good understanding of my skills, experience, and where I want to go, I thought I'd combine these milestones into one post to save some time (plus its exam season!) What TECHNICAL work do you look forward to doing? I've always been better at and enjoyed my hardware/electronics/devices classes more than my software classes. This has been reflected in my grades, and where I choose to spend my time on. I know that if/when I enter the quantum engineering industry, I will somewhat prefer to be physically tinkering with, debugging, and building things in the lab rather than sitting in front of a monitor. As a result, I choose to focus my efforts in improving those skills. This is reflected in my experience with materials fabrication and characterization, and in my RF lab work. What's one thing you will do to deepen your technical skills? The technical skill that I have in mind is RF engineering. So far, I have done coursework on it, and I have done a undergraduate research project that exposed me to MATLAB, HFSS, and VNA testing. I intend to complete an internship next summer on this topic as well, where I will be exposed to Python scripting, circuit design, and fabrication. I hope that after these experiences, I will be able to apply to quantum positions beyond my senior year. I will also be taking some electives in quantum physics and computing. What is your unique starting point? As approach the end of my undergraduate degree (3 semesters left), I will have had a lot of research experience (with results hopefully soon), internship experience, and a good GPA. My most competitive asset in industry is my RF engineering experience, while my research experiences prepares me for graduate school. My biggest qualm is that I was not able to directly get any quantum experience to apply my RF skills to before graduating. I goal is to hopefully do a capstone related to quantum computing, and then apply to graduate programs where I can apply my RF skills to a quantum computing lab. I already volunteer a lot in different leadership positions in both technical and non-technical clubs, so I'd say I have a good grasp on the soft skills.

I’m an undergraduate engineering student deciding between Electrical Engineering (EE) and Computer Engineering (CE) with long‑term interest in quantum technologies. What I enjoy most lab experiments, tuning parameters, and writing my own analysis/visualization code. My dilemma is that EE seems essential for quantum hardware (analog/RF, devices, control). However, CE seems to offer more “ready‑for‑market” skills (systems, security, networking, robotics) in case I don’t land a quantum role immediately. Access to internships is limited where I live, so I’m weighing foundation vs employability. I’ve listed the course plans below (sanitized):– EE core: circuits, signals/systems, electromagnetics, analog/mixed‑signal, control, devices/semiconductors, RF/microwave, lab.– CE core: computer architecture, OS, networks, embedded systems, digital design/HDL, security, algorithms, lab. My question is give all these factors and for someone who loves hands‑on lab work and coding for experiments, which path would you prioritize? What electives/minors would best keep both doors open (quantum hardware and broader industry)?

So far in my journey, the technical work I most look forward to is designing and building the high-frequency or mixed-signal hardware that directly interfaces with quantum systems. This comes from the trial and error system that I have conducted where I have dabbled in hardware, software, and theory. When I realized hardware is what I truly enjoyed, I switched out of Computer Engineering and into Electrical Engineering. Because I know hardware is what I'm passionate about, I tried to get involved in as many hardware projects as possible that are applicable to quantum computing. I was essentially filling out my roadmap without even realizing. Thanks to this community, I am now bridging the gaps for areas that I have neglected or missed. This is why my senior design project is heavily involved with RF engineering, and I started a new research project involving RF engineering to build a system that interfaces with the atomic experiments. I have found through this process that getting in the lab and getting things done is what I truly enjoy doing. Building the actual hardware that solves the tough experimental challenges, like control, readout, and noise suppression even when they are a headache.

My calling towards quantum computing came in bits(qubits? haha) and pieces before I was able to string them together into one cohesive mission. In one such story, I was 12 years old when I first started learning about computers. As I read that they are just manipulating “1s and 0s,” my first thought jumped immediately towards, “Why are we stuck with base 2? There has got to be something better.” This was before I knew what quantum was. As a kid with hyperphantasia, my mind has always been filled with vivid scenes. I often daydream about highly advanced infrastructure that would help all humans prosper. Whereas other kids may have appreciated the fights and character development in sci-fi franchises like Star Wars, I was captivated by the control all the sentient species had over their dominion. I was so passionate about moving up on the Kardashev scale and wanting to contribute my efforts to such an enterprise. That belief still resides in me today. It was those types of thoughts stuck with me as I was deciding what to do with my life after my sophomore year in university. I had chosen electrical engineering for its versatility and practicality, and there were too many desires pulling at me in so many directions. I thought about what drove me as a child, and what choices my innate self would make. Quantum computing actually came to the table after I reflected over those things with a trusted supervisor. We both went over the things that excited me in the classroom, such as analog circuitry, electromagnetics, and signals and systems, as well as the impact I wanted to make after starting my career. With experience in microwave engineering, and nanofabrication, along with my deep seated desires, quantum computing just felt so correct, like a relief across my body. That was the moment I knew that a career in quantum would be something I would love to put much of my energy towards. I have read some of the other answers here and they are really methodical and analytical (in a good way!). I fear that my story may be too emotionally/whimsical to be taken seriously if I tell an interviewer or even others in general. However, this is more or less the story of how I decided I wanted to be a quantum engineer, so… thanks for reading!