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.

Hey everyone, I'm at the point in my career at IBM where I am now the interviewer and resume reviewer rather than the interviewee. That's given me some enlightening perspectives I didn't have as a student. For context, I'm interviewing and looking at resumes for a few internship positions we have here. Often, students cram as much experience on their resume as possible. That practice is certainly valid because: 1. Most students have a wide breadth of experience rather than depth 2. Most students don't have an extensive amount of resume line-items, so they want to include all experience they have However, I've noticed that the students who have more general resumes get rejected faster. For example, let's say you're interested in hardware, but you have two software engineering internships on your resume. Someone might say "he's a software person, reject!". However, what if that person realized they don't like software anymore, and wants to transition to hardware? What if they only had software opportunities available to them? This example specifically pertains to internships. If we were hiring a full time person, we'd expect them to have clear experience in the role they're applying for. However, it is your responsibility to make sure you articulate your experience in a manner that connects it to the job description. In summary, here's the advice I'd give my younger self: 1. Job descriptions are often not what the hiring manager actually wants. Try to read between the lines, and figure out what they truly want from a candidate. Do some investigation work, and if possible, try to cold contact the people on the team/hiring for the job with some genuine questions about the type of candidate they're looking for. 2. Once you have some understanding of the job, you absolutely have to tailor your resume/experience to the job. 3. Iterate: once you have the interview scheduled, you most important task during the interview is to figure out what their ideal candidate is. Managers always have this unconscious profile for their ideal candidate, and you almost have to be a therapist and get them to articulate it out loud. Then, convince them how you fit that ideal candidate.

I am studying electrical engineering at McMaster University in Hamilton, ON. I am also a Fulbright Canada Killam Fellow studying for a few months at Georgia Tech. I am definitely more interested in the microwave engineering aspect of quantum computing hardware, and I hope to make a substantial impact on this nascent, but very exciting, industry! My main challenge right now is that although I have "quantum adjacent" skills, I do not have any direct experience applying those skills in a quantum context (Will go into detail in future posts). Cheers to an amazing online learning community!

In case you missed it: https://ibmglobal.avature.net/en_US/careers/JobDetail?jobId=69136&source=SN_LinkedIn I just started at my new job so I won’t be throwing my hat in the ring for this one, but I’d be really interested in @Ari Noori’s input if he has any.

Hey everybody! I am hoping to get some guidance on which path I should take to break into quantum computing. My primary plan is to pursue an online master’s in ECE with Purdue university. They have a few different specialization tracks. These tracks are: 1. Automatic Control 2. Communications, Networking, Signal and Image Processing 3. Computer Engineering 4. Fields and Optics 5. Microelectronics and Nanotechnology 6. Schweitzer Power and Energy Systems 7. VLSI and Circuit Design Here is also the link to their website: https://engineering.purdue.edu/ECE/Academics/Graduates/MASTERS/POS Which path do you guys recommend I take to help maximize the chances of breaking into quantum computing? The other plan I have in mind is to pursue the OMSCS from Georgia tech which is a lot cheaper than Purdue’s path. But then that would reserve me to software only. Whereas the online master’s in EE gives me more flexibility for both a software path and hardware path into quantum computing. Please, I would love to hear any insights you guys can offer! Thank you