Mentoring Early-Career Engineers in Technical Disciplines

As a Principal Engineer, one of my main goals is to enable and empower other engineers. Being a Principal Engineer involves not only technical expertise but also leadership and mentorship. Here are some of the things I do to enable and empower other engineers effectively: Clear Communication and Context Sharing: - Provide thorough context when assigning tasks or explaining projects. This helps engineers understand the bigger picture and make informed decisions. - Explain the "why" behind technical decisions and architectural choices to help engineers connect the dots. Encourage Autonomy: - Give engineers the freedom to experiment and explore different solutions. This fosters creativity and innovation. - Set guidelines and expectations while allowing room for individual problem-solving approaches. Safe Environment for Failure: - Emphasize that failures are learning opportunities, not setbacks. Encourage risk-taking and experimentation. - Foster an open culture where engineers feel comfortable sharing their failures and lessons learned without fear of judgment. Mentorship and Coaching: - Offer guidance and mentorship to help engineers navigate challenges and make informed decisions. - Provide constructive feedback on their work and help them identify areas for growth. Provide Growth Opportunities: - Identify projects or tasks that align with their career goals and give them a chance to learn and stretch their skills. - Support their professional development by suggesting relevant workshops, courses, or conferences. Advocate and Support: - Stand up for "your" engineers in meetings and discussions, especially during challenging situations. - Acknowledge and highlight their accomplishments to leadership and stakeholders. Open Door Policy: - Be approachable and available for discussions, questions, and concerns. - Create an atmosphere where team members feel comfortable seeking help when needed. Lead by Example: - Demonstrate a strong work ethic, technical proficiency, and collaboration skills. - Display a positive attitude and a willingness to learn from others. Promote Knowledge Sharing: - Organize regular knowledge-sharing sessions, where engineers can present their work, share insights, and learn from each other. Celebrate Successes: - Recognize and celebrate achievements, both big and small, to boost morale and motivation. Inclusive and Diverse Environment: - Foster inclusivity and diversity within the team. Respect different perspectives and encourage open discussions. Continuous Improvement: - Regularly seek feedback from engineers on your leadership style and ways to improve the work environment. Enabling and empowering engineers is an ongoing process that requires adaptability and empathy. These strategies help me create an environment where engineers feel valued, motivated, and empowered to excel in their roles.

✈️ Sending Juniors to a Conference is Not Training. It’s a Vacation. Let's be blunt: Real engineering learning is not a passive activity. It’s active, often uncomfortable, and forged in failure. A quick talk on "Modern C++ Best Practices" is forgotten by lunch. You can't buy competence with a corporate credit card. The most effective training program I've ever seen had a zero budget for external courses. It was built on a culture of "Guided Struggle." The Setup: A junior engineer is paired with a senior mentor and given a real, but bounded, problem. E.g., "Get this tricky I2C sensor driver working," or "Figure out why this high-frequency ISR is corrupting the buffer." The Mentorship: The senior doesn't hand out the answer. They act as a guide, forcing the junior to navigate the complexity: “What does the logic analyzer say about the timing?” “Have you cross-referenced the datasheet with the SoC errata?” “Walk me through your choice of synchronization primitive.” Code reviews weren't for approval; they were live tutoring sessions. The goal wasn't to find a typo; it was to force the junior to deeply understand and defend their design decisions and trade-offs. This is how you build resilience, critical thinking, and real competence—the ability to choose the right solution, not just the coolest one. Stop paying for keynote speeches and hotel rooms. Start investing in deep mentorship and controlled failure. 🔥 What is the single most valuable, non-classroom lesson a senior engineer ever taught you? Was it in a lecture hall or on the battlefield of a failing prototype? #Firmware #EmbeddedSystems #EngineeringManagement #Mentorship #JuniorEngineer #DeveloperTraining #EngineeringCulture

It took me 3 promotions to learn these 4 secrets of becoming a 10x SWE mentor. And another 2 years of testing them on mentees to know they get results – consistently. 1️⃣ 𝗟𝗲𝘁 𝗰𝘂𝗿𝗶𝗼𝘀𝗶𝘁𝘆 𝗯𝗲 𝘆𝗼𝘂𝗿 𝗰𝗼𝗺𝗽𝗮𝘀𝘀. Ravenously consume knowledge from engineers ahead of you, and understand that everyone is an expert in 𝘴𝘰𝘮𝘦𝘵𝘩𝘪𝘯𝘨. The only thing between you and their idle wisdom is the right question (this applies to LLMs too). 2️⃣ 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝘆𝗼𝘂𝗿 𝗷𝗼𝘂𝗿𝗻𝗲𝘆 𝗮𝘀 𝘆𝗼𝘂 𝗴𝗼. Clear writing = clear thinking. Cement key learnings by building a historical record of the challenges you face each week. 3️⃣ 𝗗𝗲𝘃𝗲𝗹𝗼𝗽 𝗳𝗿𝗮𝗺𝗲𝘄𝗼𝗿𝗸𝘀 𝗳𝗼𝗿 𝘀𝘂𝗰𝗰𝗲𝘀𝘀. Reflect on your wins and losses – what patterns emerge? Which processes could you pass down to other engineers? Distill complex topics into approachable stepping stones for your former self. Apply them to your own career and ensure they get results, then continuously improve them along the way. 4️⃣ 𝗦𝗮𝘆 “𝘄𝗮𝘁𝗰𝗵 𝘆𝗼𝘂𝗿 𝘀𝘁𝗲𝗽” 𝗮𝘀 𝗼𝗳𝘁𝗲𝗻 𝗮𝘀 𝘆𝗼𝘂 𝗰𝗮𝗻. Give away all your battle-tested frameworks, and know that you don’t need to be an “expert” to share your wisdom. You just need to be a couple steps ahead of the person behind you. –––––––––––––––––––– P.S. Mentorship is the path to your own career growth too. You’re going to learn just as much through teaching as they will being your student. 😉 #softwareengineering #mentorship #leadership

The Three Ls of Leadership A senior leader recently asked me why our junior engineers seemed to gravitate toward me and what advice I give them that earns their loyalty. I remembered a story from my own journey. After graduating in civil engineering and finishing postgraduate studies, I assumed I was ready for the workplace. Then I met my mentor, who gave me a simple but powerful prescription: complete the three Ls to become the kind of leader who earns respect. Since then, I’ve used that framework with every graduate and young engineer I mentor. The three Ls—Learn, Listen, Lead—are implemented weekly and practiced consistently for at least two years. Together they form a practical roadmap for anyone pursuing success, especially in technical fields where growth, trust, and influence are earned, not granted. Learn: Build technical competence and curiosity. Early-career engineers should focus on mastering fundamentals, staying current with tools and methods, and cultivating a habit of continuous learning. Technical credibility opens doors and creates the foundation for confident decision-making. Why it matters: Competence earns respect. When people see you can solve problems reliably, they’ll seek you out and trust your judgment. Listen: Cultivate empathy and attention. Listening means seeking diverse perspectives, asking thoughtful questions, and understanding teammates’ concerns. When leaders listen, they build trust and uncover insights that technical knowledge alone cannot provide. Why it matters: Listening builds relationships and contextual wisdom. It signals humility and allows you to integrate practical knowledge with technical ability. Lead: Translate knowledge and empathy into action. Leading at any level means taking responsibility, communicating clearly, and empowering others. Small acts of leadership—mentoring a colleague, owning a problem, or proposing a safer solution—compound into real influence. Why it matters: Real leadership multiplies impact. A competent leader creates better engineers, stronger teams, and more reliable results. A Cautionary Note: The Illusion of Instant Leadership Unfortunately, currently many leaders pursue influence by other means— through favoritism, rapid promotion, or political maneuvering. While luck or circumstance can place someone in a role briefly, lacking the three LLLs usually leads to poor outcomes. Those approaches may yield short-term gains, but they invite disrespect from staff and ultimately lead to failure. Learn, Listen, Lead—these three LLLs form a simple but powerful progression. Competence gained through continuous learning opens doors. Humility and curiosity through listening win trust and accelerate growth. Leadership—earned, not assumed—amplifies your impact and secures lasting loyalty. Follow these steps consistently, and you’ll build both capability and respect; skip them, and any short-term gains are likely to crumble under pressure.

New tech. New team. New expectations. The early-career phase is full of uncertainty but also packed with possibility. Most advice focuses on frameworks, interviews, and side projects. But thriving early in tech goes far beyond that. Last week, I spoke on “Navigating the Early Career” at the Faculty of Computing, NSBM Green University, as part of their IPT (Industry Preparation Training) series. Here’s what I shared: a practical system to help new engineers find their feet and grow with intention. 🔹 𝗦𝗽𝗲𝗮𝗸 𝗨𝗽 𝗘𝗮𝗿𝗹𝘆 Don’t wait to feel 100% ready. Ask questions. Share ideas. Ask for help when stuck. You grow faster when you engage earlier. 🔹 𝗕𝗲 𝗖𝘂𝗿𝗶𝗼𝘂𝘀 𝗮𝗻𝗱 𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹 Don’t just do the task. Question why. Why this stack? Why this architecture?  Curiosity + critical thinking = deep learning. 🔹 𝗟𝗲𝗮𝗿𝗻 𝗛𝗼𝘄 𝘁𝗼 𝗟𝗲𝗮𝗿𝗻 Frameworks change. Your learning ability stays. Start small:  Learn fundamentals → Practice → Document → Reflect → Improve. 🔹 𝗚𝗿𝗼𝘄𝘁𝗵 𝗧𝗿𝗮𝗰𝗸𝗶𝗻𝗴 𝗦𝘆𝘀𝘁𝗲𝗺 Keep track of your weekly wins: - What did I learn? - What did I deliver? - Who did I connect with? Review it weekly. It will surprise you how much you’re growing. 🔹 𝗔𝘃𝗼𝗶𝗱 𝗖𝗼𝗺𝗽𝗮𝗿𝗶𝘀𝗼𝗻 Everyone has their own path. What matters: your pace, your strengths, your goals.  Focus on learning, not performing. Compare yourself to who you were last week, not anyone else. 🔹 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 Go beyond code. Understand users, goals, and impact. That’s how engineers become valuable partners. 🔹 𝗧-𝗦𝗵𝗮𝗽𝗲 & 𝗖𝗼𝗺𝗯-𝗦𝗵𝗮𝗽𝗲 𝗚𝗿𝗼𝘄𝘁𝗵 Go deep in one area.  Build breadth in others. Depth makes you strong. Breadth makes you flexible. 🔹 𝗔𝗜 + 𝗖𝗼𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝗿𝘆 𝗦𝗸𝗶𝗹𝗹𝘀 Use AI tools. Learn how to prompt, debug, and enhance your work. Learn what AI can’t do and become good at that. 🔹 𝗙𝗶𝗻𝗱 𝗠𝗲𝗻𝘁𝗼𝗿𝘀 & 𝗕𝘂𝗱𝗱𝗶𝗲𝘀 A mentor gives guidance. A buddy shares the journey. You need both. 🔹 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗪𝗶𝘁𝗵 𝗣𝗲𝗲𝗿𝘀 Your peers are future collaborators, cofounders, and teammates. Grow together. 🔹 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆 𝗣𝗮𝗿𝘁𝗶𝗰𝗶𝗽𝗮𝘁𝗶𝗼𝗻 Join hackathons. Attend meetups. Engage online. Learning is social. 🔹 𝗜𝗻𝗱𝘂𝘀𝘁𝗿𝘆 𝗔𝘄𝗮𝗿𝗲𝗻𝗲𝘀𝘀 Follow people, not just tutorials. Observe trends. Learn from practitioners. 🔹 𝗖𝗿𝗲𝗮𝘁𝗲, 𝗗𝗼𝗻’𝘁 𝗝𝘂𝘀𝘁 𝗖𝗼𝗻𝘀𝘂𝗺𝗲 Teach what you learn. Share code. Write posts. Make resources. It compounds. 🔹 𝗕𝘂𝗶𝗹𝗱 𝗔 𝗥𝗲𝗮𝗹 𝗣𝗼𝗿𝘁𝗳𝗼𝗹𝗶𝗼 Move beyond tutorial projects. Build things that solve real problems, even small ones. 🔹 𝗖𝗵𝗲𝗰𝗸 𝗬𝗼𝘂𝗿 𝗖𝗼𝗺𝗽𝗮𝘀𝘀 𝗢𝗳𝘁𝗲𝗻 Ask every 6-12 months: Am I growing? Am I happy? Am I building toward something I care about? Your early years in tech won’t be linear. But they can be intentional. Start with small habits. Engage early. Learn deeply. Reflect often. You don’t need permission to start building a career that feels right for you.

We don’t lose young engineers to burnout. We lose them to irrelevance. Why the churn keeps churning → Lecture halls teach Laplace transforms. → Job sites demand client questions no one trained them to ask. Between those two worlds we built a void. And we call it “𝘦𝘹𝘱𝘦𝘳𝘪𝘦𝘯𝘤𝘦.”   The early‑career reality 1️⃣ Day 1: “Shadow the CAD line.” 2️⃣ Month 3: “Hit 90% billable.” 3️⃣ Year 2: “Why aren’t you strategic yet?” That’s not a development path. It’s a conveyor belt and the belt it speeding up. We say we want future‑ready engineers, yet we: → Grade them on theory, then hand them dimension checking. → Overload instead of challenge. → Delegate instead of mentor. Someone just spent 4 + years (and $$$) learning systems thinking. We answer with redlines and radio silence. Uncomfortable truth? Workload rarely breaks rookies. Working without a 𝘸𝘩𝘺 does. 𝗨𝗻𝗶𝘃𝗲𝗿𝘀𝗶𝘁𝗶𝗲𝘀: 𝗥𝗲𝘄𝗶𝗿𝗲 𝘁𝗵𝗲 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲 1️⃣ Client communication, not just capstones Pair every design class with real stakeholders. Yes, live feedback, awkward questions and all. 2️⃣ Systems > Silos Replace single discipline labs with cross‑discipline “mini‑project studios” where civil meets data, meets finance, meets community impact. 3️⃣Leadership 101 Make reflection, persuasion, and conflict navigation core credits, not electives buried in the humanities wing. 4️⃣ K!ll the curve, keep the mastery Shift grading from who survives to who demonstrates competence and can teach it to peers. If academia won’t reboot, industry will keep paying the price in retraining and turnover. 𝗧𝗵𝗿𝗲𝗲 𝗳𝗶𝘅𝗲𝘀 𝘄𝗲 𝗰𝗮𝗻 𝗱𝗲𝗽𝗹𝗼𝘆 𝗯𝘆 𝗠𝗼𝗻𝗱𝗮𝘆 ➡ Context Every drawing package starts with the story of the problem it solves; spoken, not just emailed. ➡ Coaching Weekly 30 min “ask me anything” huddles with a senior who 𝘳𝘦𝘮𝘦𝘮𝘣𝘦𝘳𝘴 the struggle. ➡ Challenge Tie 10% of tasks to cross‑discipline exploration (permits, public meetings, AI tools). Systems thinking grows with the project.   𝗟𝗲𝗮𝗱𝗲𝗿𝘀, 𝗱𝗼 𝘁𝗵𝗲 𝗺𝗶𝗿𝗿𝗼𝗿 𝘁𝗲𝘀𝘁 If your future‑ready initiative is a lunch & learn playlist, it’s lipstick on a staffing plan. Future‑ready means relevance‑ready. Stop treating engineers like expensive drafters. Start treating them like the problem‑solvers they trained to be. 𝗡𝗲𝘄 𝗴𝗿𝗮𝗱𝘀, 𝗱𝗼𝗻'𝘁 𝘄𝗮𝗶𝘁 𝗳𝗼𝗿 𝗽𝗲𝗿𝗺𝗶𝘀𝘀𝗶𝗼𝗻 Volunteer for messy, cross-functional work others avoid. Ask "what problem does this solve?" EVERY TIME. Curiosity is rocket fuel. Use it. Request to sit in on client calls. 𝗠𝘆 𝗮𝘀𝗸 ↳ Professors & Managers: Audit your onboarding this week. Where are meaning, mentorship, and mastery missing? ↳ Engineers & Students: Share one practice that kept you hungry instead of hollow. Let’s close the gap between theory and 𝘪𝘮𝘱𝘢𝘤𝘵 before another brilliant mind pivots to a profession that offers both.

Ever noticed how certain embedded teams transform junior engineers from "LED blinkers" to production-ready developers in record time? 🚀 The secret isn't fancy tools or complex processes—it's intentional mentorship. The most effective embedded mentorship goes far beyond casual code reviews: • Structured one-on-ones focused on both technical and career growth • Carefully designed project experiences that stretch skills without breaking confidence • Deliberate sharing of "war stories" that contextualize technical decisions • Creating safe spaces for asking the uncomfortable "why" questions about system architecture When done right, the ripple effects are remarkable: - Junior engineers contribute meaningfully to production code 3-4x faster - Documentation quality improves as knowledge transfer becomes cultural - Teams build resilience against the "bus factor" problem - The entire organization develops a foundation of technical trust I've seen teams where this mentorship culture turns into their strongest recruiting advantage. Engineers actively seek out these environments over higher-paying alternatives. What specific mentorship practices have you found most effective in embedded teams? Have you been on either side of a mentorship relationship that fundamentally changed your career trajectory? #EmbeddedSystems #EngineeringLeadership #Mentorship #CareerGrowth #EmbeddedSoftware

They gave me a junior engineer to mentor. He was sharp. Eager. And completely terrified of being wrong. In his first month, he flagged a potential issue in a protection coordination study — but kept it to himself because he wasn't sure enough to speak up in front of senior engineers. Three weeks later, the same issue triggered a fault. When I found out he'd seen it early, I didn't reprimand him. I asked him: "What would it have taken for you to say something?" He said: "I needed to know it was okay to be wrong." That conversation changed how I mentor. Now on every project I tell the junior engineers on my team the same thing: In this field, your silence is more dangerous than your mistake. A wrong calculation can be corrected. A fault that wasn't reported cannot be undone. Saudi Electricity Company operates infrastructure that serves millions of people. At that scale, the culture we build in our teams matters as much as the technical knowledge we pass down. If you manage or mentor engineers — what's one thing you wish someone had told you about speaking up early in your career? #EngineeringLeadership #PowerSystems #SEC #SaudiElectricityCompany #Mentorship #ElectricalEngineering #GridReliability #PowerQuality

One thing my team is passionate about is developing talent and providing unique learning opportunities for our teams. Over the past six months, we have been investing in our Technical Community, one conversation at a time. What's top of mind for technologists, especially those early in profession? Career Development. Microsoft is a complex, highly-matrixed, global organization. Navigating its complexities can feel overwhelming, and building a plan takes time and thoughtful consideration. The SME&C Tech Community Career Development Series, led by Sukhdev Singh and Ali Valdez, M.A., brought together leaders from across the Microsoft Commercial Business to support our community through a Technical Career Development Series.   This program was designed like a career journey, and included resources to help our teams reflect, plan, and grow—and I couldn’t be impressed by the engagement and energy across every session.   The outline was simple. The Journey Dr. Novelle Maxwell-Sinclair, Sukhdev Singh, and Stephen Tanaka helped anchor our tech teams in something simple but powerful: Your career is your responsibility. It starts with self-awareness, clarity on what matters to you, and the willingness to course-correct along the way. They explored three different types of career paths and exercises to help people find the career roadmap that worked best for them. No career path is identical, and frankly, there is no wrong approach if aligned to one's aspirations, skillsets, and plan. Designing Your Career Plan With Fadi Barghouthy, Radhika Shukla, David Lochridge, and Ann-Marie Clayton Johnson, we moved from reflection to action. The message here was clear—intent matters, but execution matters more. The leaders outlined the importance of aligning to your strengths and defining your priorities. Mentorship & Executive Perspective Mark Souza, Blane Spiers, Steve Dispensa, and Stephen Seed helped bring it all together with real-world senior leadership perspective: You don’t scale your impact alone—you grow by investing in others. The team was encouraged to stay close to technology AND customers—that’s where credibility is built. True mentorship only works if you show up prepared and open to change. And above all—be deliberate. Careers don’t just “happen” at this level, they take all the steps of self-awareness, planning, skilling, and networking with intention. The people who continue to grow—regardless of role or level—are the ones who: take ownership, stay curious, and keep leaning in, even when it’s uncomfortable. Thank you to all of our speakers for showing up with honesty and perspective—and to the community for engaging the way you did. The feedback has been incredibly positive, and more importantly, actionable. This is just the beginning—we’re excited to continue building momentum into FY27 with more opportunities to connect, learn, and grow together.   #Leadership #CareerGrowth #Mentorship