From troubleshooting computers in the residence halls to managing the very program that shaped his college experience, Clark Bilorusky reflects on growth, mentorship, and finding community at UC Berkeley.
What led you to apply for your first student position at UC Berkeley? What was the title of the position, and what was the application process like?
I had a very close friend from high school who was also going to UC Berkeley, and they got an email encouraging students to apply for Residential Computing (ResComp), a residential internet and tech support service for students living in the residence halls. I decided to apply, and it was a pretty rigorous process. There was a one-hour written exam with 100 questions, a 30-minute group interview with three other candidates, followed by a 30-minute one-on-one interview with an in-person technical assessment, where I had to troubleshoot a broken computer. I was selected as a backup candidate, but that opportunity ultimately started my journey at Berkeley.
Did you stay in that position for a while, or did you move to other positions on campus during your time as a student?
I was at UC Berkeley for seven years as an undergraduate. It was challenging for me, and I also switched majors from Mechanical Engineering to Asian American Studies along the way. During that time, I stayed within ResComp for six years. I spent three years as a Residential Computing Consultant, then moved into a student leadership role as a Unit Supervisor for another three years.
Do you have any tips for how students can balance the time and energy demands of balancing school and a job?
Even though it’s been almost twenty years since I was a student, I think the advice still holds true. The biggest thing is staying organized: using tools like Google Calendar, carving out dedicated study time, and setting realistic goals for yourself. Sometimes that means dialing things back, spreading out your workload, and learning your limits.
One thing that’s really difficult for Berkeley students is that we’re all so motivated. People don’t want to turn down exciting opportunities or let others down, and many students end up burning themselves out. I always encourage students to set boundaries and remember that it’s okay to say no sometimes. UC Berkeley can be a very high-achieving environment, and learning balance is important.
Did you transition from a student worker to a full-time campus employee? What was that like? Was it a big adjustment?
I didn’t transition directly from student employment into a full-time role at UC Berkeley. After graduating, I went to grad school, which helped me further develop my organizational, communication, negotiation, and critical thinking skills. During that time, I realized I wanted to pursue academic advising because I genuinely enjoyed mentoring students, supporting their growth, and sharing my own experiences.
After grad school, I worked for two years as a technician at a high school, which turned out to be a valuable stepping stone. I enjoyed the impact of the work, and the technical skills I developed there helped prepare me for my return to Berkeley. Seeing a former student employee return to the department as a full-time staff member inspired me to consider doing the same. When an opening was posted through the Residential Computing alumni listserv, I applied right away. I got the job, and honestly, the transition felt very smooth.
Do you feel your time as a student worker prepared you for full-time employment? If so, how?
Absolutely. One of the reasons I love my job so much now is because I once participated in the very program that I oversee today. When I first started college, I was much more introverted. During my first year working at ResComp, I actually received a poor formal evaluation. That experience pushed me to make adjustments and grow in areas like accountability, responsibility, interpersonal communication, and de-escalation.
I gained a strong foundation from my time at Berkeley, and I appreciate being in a position where I can give back and help other students grow and gain as much from the experience as I did.
Since then, what positions have you held at UC Berkeley?
I originally started as a residential computing consultant and then moved into the student lead role as a unit supervisor. I spent three years as a technician and another three years as a supervisor.
What do you enjoy the most about working at UC Berkeley?
There’s a lot that I enjoy. I feel fortunate to work on the Student Technology Services team alongside so many phenomenal people. We have a really supportive work culture, strong work-life balance, and great opportunities for professional development. It’s just a wonderful place to work.
On top of that, Berkeley has always been deeply personal to me. I have a lot of school spirit: my dad, younger brother, and sister are all Berkeley alumni, and I grew up going to Cal games. As a student, I was part of the Rally Committee, and I’ve had some incredible experiences, including carrying the Axe. Being able to work here now, continue being part of the Berkeley community, and give back to it means a lot to me.
What advice do you have for students who are considering a career with UC Berkeley?
The first step is getting involved in student staff opportunities on campus. Working at Berkeley in any capacity gives you a huge advantage because you begin to understand how the university operates, how different departments interact, and how the overall system works. You start developing a broader organizational perspective beyond your own individual role.
That experience becomes really valuable when applying for career staff positions because you can speak to that awareness and knowledge in your applications and interviews. Relationships also matter a lot. The more you work on campus, the more people you meet and the more connections you build. Those relationships, combined with hands-on experience, help you better understand how even a small role contributes to the larger Berkeley community. Overall, it’s about getting your hands dirty, building relationships, and beginning to understand how we, tiny cogs in the machine, connect to everything else.
