Home | About | Blog | Projects | Contact
I'm excited to announce that I've accepted a Hardware Application Engineer Intern position at Arm!
This role is literally everything that I've been thinking about doing since I built my first PC back in high school. I told myself, "I am going to design computer parts." Now here I am, getting ready to work on a hardware application team in CPU and SoC architecture. I am over the moon.
The interview process consisted of two rounds: a HireVue round followed by an hour-long technical interview.
The technical interview focused heavily on MIPS/RISC-V architecture that I had listed on my resume. They asked about:
My coursework in ECE 463 (Microprocessor Architecture) and ECE 406 (Parallel Computing Architecture) gave me the foundation I needed to answer these questions. I also got to talk extensively about my previous project on serial communication with bare metal C on an Arm-based microprocessor during my internship at Persistent Systems.
What caught their attention wasn't just the technical knowledge — they specifically mentioned my dual undergraduate degree in Electrical and Computer Engineering. They also valued my experience as a department ambassador: speaking on panels at open houses, giving tours to prospective students, and leading soldering workshops. They said these communication and customer-facing skills would translate well to Applications Engineering work.
I'm looking forward to working for an industry-standard computer architecture company and diving deep into CPU/SoC architecture. This internship is an opportunity to learn not just the technical details, but also how the industry is evolving — seeing firsthand how these systems are designed, optimized, and brought to market.
It's one thing to study architecture in textbooks and courses; it's another to work on it at a company that literally sets the standard for modern computing.
One piece of advice I'd give: really study and learn from your textbooks. Don't just try to pass the homeworks.
Seriously understanding each and every assignment, chapter, and lecture really does pay off for these technical interviews. When they asked about pipeline stages or cache coherence, I wasn't scrambling to remember formulas — I actually understood the concepts because I had taken the time to deeply learn them the first time around.
The depth matters. Cramming might get you through the exam, but true understanding gets you through the interview.
Looking forward to this new chapter and continuing to learn in public.