Tips for Learning Through Practical Experience

Reflecting on my journey preparing for software engineering interviews, I'm reminded of the profound impact of truly getting my hands dirty with the fundamentals. It wasn't enough to just read about data structures; the real learning happened when I decided to build them myself. Take Red-Black Trees, for instance. Diving into the intricacies of rotations and balancing by actually implementing it ( https://lnkd.in/dXQXHE9u ) solidified my understanding in a way that theoretical study never could. Even exploring simpler structures like Linked Lists, Stacks, and Queues in Python ( https://lnkd.in/dfs-MAfp ) provided invaluable practical experience. This hands-on approach extended to more advanced concepts like Heaps ( https://lnkd.in/dKj8SH76 ) and Graphs ( https://lnkd.in/dMA8SeNW ). For graphs, I even ventured into performance testing ( https://lnkd.in/dZJvDv95 ) and wrote unit tests ( https://lnkd.in/d_p5Sq8y ) to ensure correctness and get a feel for efficiency. Beyond core data structures, personal projects like the Node.js filesystem analyzer ( https://lnkd.in/dHgRdd_g ) were equally crucial. They provided a context to apply these fundamental concepts to real-world problems. Looking back, this proactive, "go the extra mile" mentality in my interview preparation wasn't just about acing the technical rounds. It fostered a deeper intuition and a more robust problem-solving skillset that continues to serve me well. For those navigating the interview process now, I highly encourage you to move beyond passive learning. Build, test, and experiment with the concepts you're studying. That extra effort can be a game-changer in truly understanding the material and showcasing your passion to potential employers.

A Note for Sales & Marketing Interns this Summer, based on my own experience at Pidilite Industries Limited last year. Every project begins with a problem statement. Read your brief carefully, then read it again. Take ownership. Know the objectives before stepping into the field. Prepare a questionnaire to structure your information gathering, but let conversations flow naturally. Be present, be curious. Observe customers. Speak to retailers and distributors. Ask “why?” again and again, just don’t be annoying. Dig deep, but always with politeness and respect for their time. Observations are what you see and insights are what you understand beyond the obvious. It’s what makes a real difference. It’s the “aha!” that comes from digging a little deeper. You’ll probably visit hundreds of stores in two months and talk to dozens of people. Try to spot patterns in what you hear and see. At the end of each day, ask yourself: Can I summarise today in 3-5 key insights? Crunch the data. Connect the dots. Visualise the bigger picture. And don’t keep your findings to yourself. Share them. Discuss them. Sometimes, someone else’s take can change how you see everything. Be open to feedback and alternate perspectives. While working on your recommendation, ask yourself: How does this add value? Does it make life easier for the customer or the stakeholder? Aim for solutions that are both practical and meaningful. Think impact. Summer can be harsh. Carry enough water. For yourself, maybe even for a teammate. Over the next two months, there’ll be plenty to learn. But the most meaningful part will be meeting people from different walks of life who change your perspective. Focus on the process. Embrace the change. Results will follow. Hope this helps.

As part of my first software engineering job, which was at a manufacturing firm, my manager granted me freedom to choose what I wanted to work on. Little I knew that that meant independently identifying business needs and then crafting solutions. As a novice in the software engineering realm, I lacked the guidance and mentorship typically offered to newcomers. Instead, I was thrust into a role where I was expected to create my own work. In general, those skills are characteristic of mid to senior level engineers. I spent the following months observing mechanical engineers and technicians. I meticulously observed their routines, pinpointed their pain points, and identified the repetitive tasks that were consuming their time. Six months into the role and I prototyped a computer vision solution that automated visual inspection of freshly assembled medical devices. I wrote it fully in C++ using the OpenCV library, with unit tests and proper documentation. My prototype quickly garnered attention and piqued interest, evolving into a full-scale solution that significantly reduced the manual labor required, saving us tens of hours each week. This experience taught me valuable lessons about embarking on new projects and joining teams: 1️⃣ Observe and Inquire: Start by closely observing and asking questions. Take diligent notes as you go along. 2️⃣ Identify Pain Points: Understand where the team is struggling the most, and recognize the areas in need of improvement. 3️⃣ Propose Well-Considered Solutions: Suggest solutions with well-thought alternatives. Be prepared to present your ideas effectively. 4️⃣ Execute and Deliver: Put your plans into action, and ensure your implementation aligns with the team's needs. Following these steps will allow you to become an organizational asset and propel your growth. This journey not only honed my technical skills but also imparted crucial insights into the dynamics of software engineering and problem-solving in a real-world context.

A few years ago, I found myself in a new role that required skills I didn’t yet have. With no formal training or mentor to guide me, I had to figure it out on my own. By observing colleagues, asking questions, and exploring resources like blogs and tutorials, I gradually gained the skills I needed. This experience taught me that some of the most valuable lessons come not from structured teaching but from staying curious, adaptable, and proactive. I’m sharing some of my learnings to embrace continuous learning at work—even when there’s no clear teacher. 1. Learn Through Experience Imagine a situation when a project that initially failed due to unforeseen client demands. This is a clear sign of not involving stakeholders right from the word go and clear communication through documentation along with expectation setting. If you have ever faced a situation like this, leverage the past experience and build on.  2. Learn From Your Colleagues In the workplace, anyone can be a teacher. Observing and collaborating with peers, managers, or even subordinates can reveal new techniques, perspectives, or skills you might not discover alone. The key is to stay open and receptive. 3. Learn From Situations Not all lessons come from people. Challenges like tight deadlines, organisational changes, or crises can teach resilience, adaptability, and resourcefulness. Observing how you navigate these situations helps you identify areas for growth and improvement. 4. Embrace Self-Learning When there’s no formal teacher, take charge of your learning journey. Seek out books, online courses, blogs, or podcasts. Experiment with tools and approaches. By taking ownership, you turn uncertainty into an opportunity for growth. 5. Cultivate a Learning Mindset A learning mindset transforms ordinary moments into opportunities for improvement. Stay curious, ask questions, and embrace the process of unlearning and relearning as needed. Being adaptable and reflective ensures continuous growth. Continuous learning doesn’t always follow a clear path or involve formal lessons. The most meaningful growth often happens through self-discovery, collaboration, and adaptability. By staying open-minded and proactive, you can uncover opportunities to learn and grow in every experience. So, even when it feels like no one is explicitly teaching you, remember this: every challenge, interaction, and situation has a lesson to offer. The key is to stay curious, take action, and keep moving forward. Start where you are, learn from what’s around you, and let our journey of growth unfold.

They say experience is a great teacher. How do you leverage it? I rely heavily on experiential learning as a customer service trainer. Customer service reps have valuable experience from... * Serving customers * Being customers * Interacting with other humans The trick is optimizing what you learn from experiences. David Kolb created a four-step experiential process that anyone can use. 1. Experiencing: doing something. 2. Reflecting: evaluate how it went. 3. Thinking: decide how to adjust. 4. Acting: trying something new. My Customer Service Tip of the Week emails are built around this model. 1. Experience Each tip starts with a relatable story or example. For instance, I went to REI to buy hiking poles for my wife and a knowledgeable sales person used her expertise to help me make the right decision. 2. Reflecting The tip asks you to think about how the tip applies to you. The expertise tip suggested making a list of the top ten product questions customers ask. 3. Thinking Think about how you can use the tip when serving your customers. The expertise tip suggested coming up with extra helpful answers to each of the top ten questions. 4. Acting Apply the tip right away with the customers you serve. This process is self-reinforcing. Trying a new approach leads to a new experience. You can then repeat the steps and continue learning. I bet you already do this! What is one customer service skill you learned from experience?

‼️ATTENTION CYBERSECURITY FRESHERS HANDS-ON EXPERIENCE > CERTIFICATIONS I’ve noticed a trend where many freshers in cybersecurity focus heavily on earning certifications, hoping these will land them a job. While certifications have their place and can certainly boost your knowledge and credibility, relying on them alone can be a mistake. Why? Because cybersecurity is a field that thrives on practical skills. Employers value candidates who can demonstrate real-world problem-solving abilities, not just theoretical knowledge. Gaining hands-on experience through labs, simulations, internships or even personal projects can make a huge difference in your job prospects. I’m not against certifications, they are important and can give you a solid foundation in cybersecurity principles. But it’s crucial to understand that certifications should complement hands-on experience, not replace it. I want to help you secure the job you’re aiming for and the best way to do that is by showing employers that you can apply what you’ve learnt. Here’s what I suggest: 1. Get Your Hands Dirty: Set up your own lab environment, practise penetration testing, explore vulnerability assessments and work on real-world scenarios. The more you practise, the better you’ll become. 2. Contribute to Open Source: Participate in community projects, bug bounty programmes or volunteer with cybersecurity initiatives. This builds your portfolio and shows employers that you can apply your knowledge. 3. Internships & Projects: Prioritise internships, apprenticeships or any practical projects over stacking up certifications. These experiences are invaluable and often what hiring managers look for. 4. Network and Learn from Others: Connect with professionals in the industry, join cybersecurity forums and attend events. Learning from others experiences can provide insights that no certification can. Certifications are great, but they should be part of a broader strategy that includes gaining practical experience. Focus on building your skills through real-world application and you’ll stand out in the job market. I’m sharing this because I want to see you succeed in the cybersecurity field. By balancing certifications with hands-on experience, you’ll be well on your way to securing the job you’ve been working towards.

Just because someone has more degrees doesn't mean they're more equipped to lead.👩🏿🎓 In a recent leadership conversation, we unpacked something that doesn’t get said enough: Practical application is what builds real influence, not paper credentials. Yes, learning is essential. But here’s what I’ve observed: The leaders who advance aren’t chasing the next certification to feel qualified to speak. They’re building confidence by doing the work, developing skills through experience, and showing up ready to try, reflect, adapt, and grow. 💡The reality? I’ve seen brilliant women hold themselves back, convinced they need another degree to be heard or have their opinions valued. In reality, it's the act of staying quiet in strategic meetings, deferring to less qualified colleagues, hesitating to share innovative ideas, and missing key moments to contribute that keeps their insights from being recognized. Your Action Plan This Week: 🗣️ Ask for feedback on something you’re working on, and apply it right away 👩🏾💻Volunteer for the cross-functional project that stretches you 📚 Join that committee you've been considering Growth isn't about accumulating information. It’s about making meaning from experience and turning that into impact. The confidence you’re seeking won’t come from another certificate. It comes from proving to yourself, again and again, that you can learn, adapt, and deliver when it counts. What’s one skill you’re building through hands-on experience this week? Share your story below. I’d love to celebrate your practical learning journey. 👇🏿👇🏾 📬 Tired of vague leadership advice? I send a biweekly newsletter for women leaders who want practical, actionable solutions, not just insights. If you’re making bold moves and ready to lead with intention, subscribe here https://lnkd.in/eQPvEVxb #Leadership #ProfessionalDevelopment #ContinuousLearning #WomenInLeadership #CareerGrowth #LeadershipDevelopment