KadaKareer x JPSSITE LCUP: Pace Level Up V. 7.1 - Q&A
During my talk at the Pace Level Up V. 7.1 event hosted by the KadaKareer and JPSSITE LCUP, I introduced mentorship as a critical career catalyst by examining my own professional journey, defining the four essential pillars of mentoring (psychosocial support, career guidance, skill development, and sponsorship), walking students through the 5/20 formula as a practical diagnostic tool to evaluate their direction, workplace preferences, technical skills, self-management, and barriers. I then wrapped up the session by opening the floor for a live Q&A.
Read the full talk at Kada Kommunity Forum.
Part 1: Live Session Q&A
Q1: What is one hard piece of advice and feedback a mentor gave you about your skills or work ethic that stood out the most for you?
A: One thing that comes to mind — though I’m sure there are more — was from a couple of companies ago. I had a mentor who was also my manager, and our team hit a roadblock with a colleague. That colleague was disappointed because they wanted to learn a specific topic, but our team wasn’t advanced in it yet. Since I was more senior, they expected me to teach them.
Looking back, I didn’t handle it well because I didn’t know what to do. They ended up giving me the silent treatment, which completely derailed our project communication. It weighed heavily on me and caused a lot of anxiety.
When my manager and I finally talked about it, she gave me some tough advice: face the situation. She pointed out that as the senior team member, I had a responsibility to at least talk to the person and look for solutions. That might sound obvious to some, but given my maturity level back then, even an obvious solution felt like a big challenge. I kept thinking, “How do I talk to this person? I’m not confrontational.”
That conversation made me realize that breaking through takes courage. My manager shifted my perspective: as a lead, you have a responsibility to address and clear the roadblocks that get in the way of working together smoothly.
Q2: What advice do you have for college students with no programming knowledge who end up in a programming course?
A: If you’re already in that course, let’s assume you made it through the entrance requirements. Think of it like getting hired at a company. Organizations have rigorous interview processes precisely to ensure that whoever gets in possesses the foundational potential to survive and grow.
If you don’t have prior coding experience but chose the course anyway, it means you have what it takes to start. On the other hand, you’re in school to learn. Make friends with like-minded peers or those who already have more programming experience. Lean on your community, be curious, and let them help you bridge the gap.
Q3: What advice could you give to people who are struggling with internal doubt and low self-esteem?
A: This is something everyone deals with — internal doubt and low self-esteem don’t discriminate based on age or whether you’re in school or at work. It’s not as simple as someone telling you, “Don’t feel that way.”
When you don’t have anyone else to talk to, start by talking to yourself. But you need the courage to answer the hard question: What is actually causing this? Sometimes, we avoid the answer even when we’re the ones who have to face it.
Once you are honest about the root cause, you can start looking for solutions. If the doubt stems from lacking a specific skill, find someone who is good at it and ask how they started. Everyone begins at zero. Ask what books they read or what steps they took, and copy those initial milestones. Identifying the exact roadblock is the best first step to self-doubt.
Q4: If a student has a lot of potential but not much confidence, what should they work on first: skills, mindset, or network, and why?
A: Wow, thank you for that wonderful question — that sounds like a classic pageant question!
When we talk about potential, I see it in two ways. First, someone might have the actual capability — like being a great singer who only performs in the bathroom because of shyness. The skill is already there; the barrier is just a lack of confidence. Second, someone might have raw potential (like a strong math background that makes them great for logic and programming), but they lack the confidence to take practical steps.
So, between skills, mindset, and network, which comes first? Skills and mindset are internal — they sit right inside us. The network is external. Naturally, the things closest to us are what we have the most immediate control over.
I’d say mindset comes first. If your lack of confidence keeps you from joining a club or putting yourself out there, you have to tackle that internal barrier first. Of course, telling someone to “just be brave” is easier said than done, which is why working through this with a mentor is so valuable. Once your mindset shifts, it unlocks your ability to build skills, and your skills naturally help you expand your network.
Part 2: Offline Q&A
Q5: Koach, with AI changing so many industries, what skills do you think students should develop that will remain valuable?
A: Even in scenarios where AI can handle tasks from end to end — imagine a self-driving car — people still need to be in the passenger seat telling it where to go, or behind the wheel to take control. Humans must ultimately accept and shoulder the responsibility.
Because of this, foundational skills remain critical. If you want to build an application using AI, you might get an initial output, but you still need logic, analytical skills, and coding knowledge to debug, connect databases, and make it functional.
If you are inclined toward tech, mastering the fundamentals of your field is invaluable. Alongside that, systems thinking — the ability to see the big picture and understand how different disciplines and components interconnect — is a superpower.
Q6: What would you tell someone who feels like they’re falling behind in their career journey?
A: The first quote that comes to mind is: “Comparison is the thief of happiness”.
Feeling like you’re falling behind — whether comparing yourself to batchmates or struggling with a tough topic — is completely valid. But first, ask yourself: Where are you comparing yourself, and relative to what?
In reality, everyone moves at a different pace. Not everyone from the same graduation batch will end up at the same career level. Instead of measuring your journey against a crowd, measure yourself against your own ideal scenario and what brings you fulfillment. Identify any skill gaps constructively, and focus entirely on your personal growth.
Q7: If you were starting your career again today, what would you focus on during your first year?
A: In high school, we didn’t have a STEM track yet, and I didn’t have a clear idea of what to take in college. My parents chose engineering for me, and I spent a miserable first year flunking math before switching to advertising. Every challenge shaped who I am today.
If I were starting my career today, I’d definitely focus on learning how to leverage AI tools. More importantly, I’d shake off the misconception that professional experience only starts after graduation.
The better mindset is to apply your skills immediately through side projects that solve real-world problems for businesses, big or small. Getting that hands-on execution experience right from your first year is what makes all the difference.
Q8: What should I aim for more: certificates or projects?
A: Between the two, definitely projects.
Certificates are essentially informational promises — they state that because someone attended a workshop, they supposedly acquired knowledge. At the end of the day, a certificate is just a piece of paper.
A project, however, is something you actually built and brought into reality, even if it didn’t succeed. A failed project — when you can articulate why it failed and what you learned — is immensely valuable. Certificates can help check institutional boxes, but projects prove actual execution. Focus on building things; certificates are just a nice bonus on the side.
Q9: What is a beginner-friendly language for new programmers?
A: While not a traditional programming language, I always recommend starting with HTML and CSS, followed closely by JavaScript. When I started designing websites years ago, my curiosity led me to inspect and modify existing pages, which got me hooked.
Think of learning to code like two siblings crossing a mountain (I’ve read this somewhere): one takes a rugged trail on foot, while the other takes a cable car. The second sibling arrives faster, but the first experiences breathtaking views and learns invaluable lessons along the way. Studying HTML, CSS, and JavaScript by hand is taking that trail — you build foundational intuition that you miss if you let AI automate everything from the start.
Q10: When you were deciding on your career, did you reach a point where you felt stuck between options?
A: Definitely. Career dilemmas never really go away; it’s just about how you navigate them.
I faced a major fork in the road when choosing between UI design and corporate communications design. Corporate comms leaned toward marketing and branding, while UI design leaned toward tech and digital products. I was genuinely interested in both.
I ultimately chose UI design because I loved building interactive digital things. Would I have failed if I chose the other path? Not necessarily. Success depends on your character and how you solve challenges when things get tough. Lean toward what genuinely brings you personal fulfillment and makes your day worthwhile.
Q11: How do we balance learning different IT skills without becoming a jack-of-all-trades, master of none?
A: The phrase “jack of all trades, master of none” often carries a negative tone, as if specializing in just one thing is the ultimate goal. But in today’s landscape of product design and AI automation, being knowledgeable across multiple disciplines and knowing how to connect them is one of the greatest strengths you can have.
Think of being a T-shaped professional: the horizontal bar represents broad knowledge across various domains, while the vertical bar represents deep expertise in your core specialty. Hone your core strengths, but keep yourself open to learning adjacent fields. You might not see how they are related, but the dots will eventually connect.
Q12: Can you tell me about your first job interview? How prepared and pressured were you?
A: After graduating, I spent six months applying for web design jobs with zero callbacks. That was six months of being a true couch potato — which is where I finally learned why the term exists!
When my web design applications fell through, I pivoted and applied for a BPO tech support role. Because I was still living that sluggish routine, the recruiter called at 10:00 AM while I was half-asleep. Let’s just say the interview did not go well, and my English was a bit wonky. I didn’t get the job. But luckily, a web design company called me a week later.
The takeaway? Practice and prepare ahead of time. Review your resume, know your projects inside and out, and run mock interviews. That way, whenever a recruiter calls out of the blue, you’re sharp and just be sure that you’re fully awake.
Q13: Were there people who had a different educational background from their work?
A: Definitely. In product and UI/UX design, I’ve worked with team members who have computer programming and IT degrees, alongside folks from mass communication, fine arts, and multimedia design.
During the pandemic especially, I saw many teachers and engineers planning to transition into UI/UX design and user research. Cross-disciplinary movement is completely normal. Down the road, you might decide to pivot into a totally different path, and that is entirely valid. As the saying goes, it’s never too late to learn something new.
Q14: What are the common mistakes students make when seeking mentorship, and how can we avoid them?
A: It usually boils down to two main things:
- Going in with overly open-ended questions: Showing up and asking, “What advice can you give me?” leaves the session directionless. Even if you don’t have a crisis, surface specific questions to serve as your agenda.
- Lacking follow-through and breaking the feedback loop: After a session, you’ll have action items or new approaches to try. A common mistake is dropping the ball because maybe mentorships aren’t graded. Be accountable, test the advice, see what happens, and schedule a follow-up session to share your progress. That closes the feedback loop and turns a one-off chat into a potentially genuine, continuing mentorship.
Q15: Is it okay to behave like a student if someone has a programming course in college, with working activities and quizzes for my students?
A: The question isn’t very clear for me. However, I firmly believe that as you teach, you are also learning. Once you are able to articulate a complex topic simply, you reinforce your own understanding while helping others grasp it. At the same time, you will constantly learn new perspectives from your students.
Maintaining a beginner’s mind is essential in any aspect of life, even long after you leave college. Staying curious and eager to learn is one of the best traits you can carry into the workplace.
Q16: What separates a genuinely good mentor from someone who just has more experience?
A: Not everyone with experience makes a good mentor, but all mentors should have relevant experience in the area they’re guiding you through. They don’t need to know everything about life — they just need to be a few steps ahead of you on that particular path, having weathered the highs and lows.
Beyond experience, what makes a great mentor is trust, communication skills, and genuine sincerity. Remember that mentorship is a two-way street: their job as mentor is to guide you and your job as a mentee is to commit to the action items, report back on your progress, and stay accountable.
Q17: What if someone has lost confidence in a project, and everyone keeps telling them “Kaya mo” (You can do it), but they still have doubts?
A: First, you need to understand why you lost confidence. When you answer that honestly, you can pinpoint the root cause. From there, you can choose to tackle the problem head-on, or make the conscious choice to step away if the project genuinely isn’t the right fit.
Sometimes, hearing everyone say “kaya mo 'yan” isn’t actually helpful, because you are the only one facing the challenge. Once you identify what’s blocking you — or admit to yourself that a project isn’t for you — you break out of that mental rut. Talk it out with a trusted friend or mentor, but always start by knowing the exact source of your doubt.
