Industry Expert Interview – Post-Interview Reflection
Interviewee: Sothy Lean
Title: Information Technology Specialist
Organization: Fresno Unified School District
Introduction
For this assignment, I talked to Mr. Sothy Lean, who works as an Information Technology Specialist for Fresno Unified School District. I reached out to him mainly because he’s in the same district I work in, and I’ve always noticed how dependable the IT department is—especially in high-pressure moments. Honestly, I’ve seen them work during device outages and internet issues, and it’s made me respect how much they do behind the scenes.
When schools shifted to remote learning during the pandemic, the tech team kept things afloat. That left an impression on me, and I’ve wanted to better understand what goes into their day-to-day ever since. Mr. Lean seemed like the right person to talk to because he’s done this for over 30 years, starting in a basic support role and gradually growing into more advanced responsibilities. I figured his perspective would be a good reality check—something deeper than what you find in textbooks or job ads.
Since I’m thinking about moving into cybersecurity or an entry-level IT support position myself, I thought this would give me a chance to see the path more clearly and ask the kind of questions I couldn’t find on Google.
Summary of Key Takeaways
One of the biggest takeaways from our conversation was how unpredictable and sometimes chaotic IT support can be, especially in a school district setting. Mr. Lean said that even now, he often finds himself jumping in to repair devices or troubleshoot network issues because there simply isn’t enough staff to go around. It surprised me how much improvisation the job still requires.
He explained how priorities shift minute by minute—you might be working on a device update when someone suddenly needs help connecting to the Wi-Fi, and then another person shows up with a broken screen. There’s no “normal day” in this role. That kind of flexibility and calm under pressure is something he’s learned over time.
Something else that stood out was how tools and platforms have changed drastically since he started. He mentioned how cloud services like Microsoft 365 and Google Workspace are now baked into almost every part of school operations. Also, he talked about newer tools like JAMF and Intune for managing devices remotely. I didn’t even know schools were using that level of software for endpoint security.
When we moved into the topic of cybersecurity, he brought up phishing scams and ransomware attacks, especially how schools are increasingly being targeted. What really made me stop and think was when he said that IT support staff—especially in schools—are often the first people to detect when something’s off. That kind of frontline responsibility wasn’t something I had considered.
But honestly, what hit me most was when he started talking about soft skills. He said knowing how to communicate with non-technical people is just as important as knowing how to fix the problem. A lot of his time is spent helping teachers and staff understand what went wrong without overwhelming them with tech jargon. He also stressed patience—something he admitted he had to learn the hard way.
Before wrapping up, he gave me a few pieces of advice. First, just start wherever you can, even if that means helping someone with a minor issue. Second, don’t be afraid of mistakes—he said they’re part of learning. Third, he said certifications like CompTIA A+ and Network+ are helpful, but they’re not enough on their own. What matters most, he said, is experience—figuring things out, tinkering, breaking stuff, and fixing it.
Reflection
Before this interview, I had a general idea of what working in IT looked like, but it was pretty vague. I thought it would mostly be responding to help desk tickets and installing software. After talking with Mr. Lean, I realized that there’s way more to it. The job requires flexibility, people skills, a good memory, and honestly—some thick skin too.
What really made an impact on me was learning how he built his entire career through hands-on learning. No fancy degrees, no bootcamp. Just decades of showing up, being helpful, and not being afraid to say, “I’ll figure it out.” That reminded me a lot of my own approach. I’ve always been a “learn by doing” type, and hearing that someone succeeded by following that same style gave me more confidence in myself.
I also appreciated how honest he was. He didn’t try to make the job sound easy or glamorous. Instead, he told stories of long days, of having to repair 15 Chromebooks before lunch, of being called into classrooms mid-lesson. That kind of transparency made it feel real. It made me want to prepare myself not just technically, but mentally too.
What I took away from his experience is that it’s okay not to have all the answers at the beginning. The key is to be curious, keep learning little by little, and take chances to help when I can.And when mistakes happen (because they will), to treat them as part of the path rather than proof that I’m not cut out for it.
Future Steps
I’m taking several steps after this interview, and they’re all based on what we talked about:
I’m going to finish my CompTIA Network+, which I’ve been studying for, and then go straight into Security+ to round out my understanding.
Lately I’ve been messing with an old laptop I had lying around — not great hardware, but I’ve been using it to try out virtual machines and test stuff I’ve been learning. I wouldn’t say I have a perfect setup or anything, but it’s kind of nice to have a space where I can just try things and not worry if I break something.
Also, I’ve realized I need to get better at talking about tech without making it confusing. Sometimes I go too fast or use words people don’t follow, especially if I’m nervous. I’m trying to slow it down and explain things in a way that actually helps — maybe just by practicing with people I already know.
I’ll stay connected to mentors—especially Mr. Lean if he’s open to it. Even just sending updates or asking small questions can help me stay engaged.
I’ve been trying to stay more in the loop with tech stuff — sometimes that just means watching a random YouTube video or skimming through a forum when I get a chance. Things change so quickly that if I don’t check in every now and then, I feel like I’m already behind.
Finally, I’ll volunteer whenever I can, whether at work or through side projects, to keep gaining experience. I realize now that even small tasks add up to something bigger over time.
Closing Thoughts
After we talked, I kept thinking about everything he said. It honestly shifted how I’ve been seeing the whole IT field. I used to think you had to be some kind of genius to make it, but now I get that it’s more about being consistent, learning on the fly, and being the kind of person people can count on. I left that conversation feeling more motivated — not just because I’m into tech, but because I actually want to help people and fix real problems when they happen.
And for the first time in a while, I’m not overwhelmed by where to begin. I’m actually excited to take the next step.
No comments:
Post a Comment