As winter rolls in, I'm starting to apply to internships and research for the summer. I just applied to an internship at Figma (they develop a popular UI design tool), and I've attached the resume I used for that application here. At the moment, I'm trying to just get any internship or research that where I can gain "real" experience in either quantum engineering, computer engineering, software engineering, or game development, so I can understand more of what I want to do. I don't know how to best move forward with applying for internships and research, as well as, just finding the opportunities in the first place. Unfortunately, my community college does haven't many career fairs (like Ari mentioned in the classroom) nor any research labs, so at the moment I'm stuck to applying directly to positions I find online. I'm currently using a combination of LinkedIn, HandShake, and VentureLoop to search for internships, but I don't where to look for research. I also found that IBM is hosting a career webinar this Wednesday so I'll be attending that. I'd like feedback on how to improve my resume, as well as, any tips for finding opportunities and preparing for the interviews once I land one. Thanks so much!

Hi everyone! I’ve received some questions about my project, so I figured I would share my major milestones about the project with you guys. I have attached my proposal for the project below.

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!

HI guys, I'll be gone from 11/19/2025 - 11/30/2025 and I won't be able to be online at all. Watch the video to find out what I'm doing for those days.

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!