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.

Looks like the stuff he’s working on, I think😅

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.