Your Degree Doesn't Define You. Tech Is For Everyone.
On this episode, we have Michael Escobilla, Charvin Peñaverde, Juan Carlo Claudio, and Luigi Espiritu joining us to discuss "When Non-Tech Goes Tech - A Transformation Journey" and why your degree doesn't define you.
This episode is for anyone who thinks a career in tech is out of reach without a computer science degree. We'll share our own stories of moving from non-tech roles, like Human Resources, into the digital world. Join us as we talk about the changes we made and the lessons we learned on our journey. It's an inspiring conversation that proves you don't have to be a traditional tech professional to innovate and make a real impact in today's world.
What was the moment you realized you wanted to shift into tech? (Generalization)
The realization often comes from a moment of dissatisfaction with the status quo of the previous career and an attraction to the problem-solving nature of technology. It might be realizing that tech skills were needed to solve a key issue in the non-tech field, or simply discovering that the fast pace and continuous learning inherent in the IT world were more engaging. For many, the shift is driven by seeing the massive impact that technology has on every industry and wanting to be part of that innovation.
For someone coming from a non-tech background, what's the one skill they can leverage the most? (Generalization)
The most valuable skill non-tech professionals can leverage is domain expertise and business context. A background in fields like HR, finance, or marketing gives them an intimate understanding of specific user needs, regulatory constraints, and business goals that pure technologists often lack. This knowledge is crucial for bridging the gap between technical teams and business stakeholders, allowing them to build products and solutions that are truly relevant and impactful to the organization.
What was the biggest learning curve for you? Was it a technical skill or something else entirely? (Generalization)
For many, the biggest learning curve is less about a specific technical language and more about adopting the "tech mindset". This involves shifting from a static, procedure-driven approach to an iterative, agile, and constantly evolving one. It means becoming comfortable with continuous failure, debugging, and rapid change. While technical skills can be learned, internalizing the culture of perpetual learning, documentation, and systematic problem-solving is often the hardest, yet most critical, transition.
How did you deal with the feeling of imposter syndrome when you first started working in a tech role? (Generalization)
Dealing with imposter syndrome requires consciously separating feelings from facts. The strategy involves acknowledging the feeling but focusing on small, verifiable wins and contributions to build confidence incrementally. Finding a mentor or supportive colleague to talk to is also crucial, as they can provide objective validation of skills and progress. Recognizing that everyone in tech is constantly learning and that having a non-traditional path provides a unique, valuable perspective helps to quiet the internal critic.