Lead Developer Career Guide (Shelley Benhoff) (Z-Library)

📄 File Format: PDF

💾 File Size: 29.1 MB

📖 Read Online ⬇️ Download

Registered users can read the full content for free

Register as a Gaohf Library member to read the complete e-book online for free and enjoy a better reading experience.

📄 Page 1

M A N N I N G Shelley Benhoff Foreword by Steve Buchanan

📄 Page 2

MANN I NG Shelter ISland Lead Developer Career Guide Shelley Benhoff FOREWORD BY STEVE BUCHANAN

📄 Page 3

For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. 20 Baldwin Road PO Box 761 Shelter Island, NY 11964 Email: orders@manning.com © 2025 Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid- free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without the use of elemental chlorine. ∞ Manning Publications Co. 20 Baldwin Road PO Box 761 Shelter Island, NY 11964 ISBN 9781633438071 Printed in the United States of America The author and publisher have made every effort to ensure that the information in this book was correct at press time. The author and publisher do not assume and hereby disclaim any liability to any party for any loss, damage, or disruption caused by errors or omissions, whether such errors or omissions result from negligence, accident, or any other cause, or from any usage of the information herein. Development editor: Rebecca Johnson Technical editor: Stephen Mizell Review editor: Dunja NikitoviÊ Production editor: Kathy Rossland Copy editor: Julie McNamee Proofreader: Melody Dolab Typesetter: Tamara ŠveliÊ SabljiÊ Cover designer: Marija Tudor

📄 Page 4

This book is dedicated to my parents who bought me my first computer, the Tandy 1000, and recognized my aptitude for technology. I also dedicate this book to my husband, Jason, and my sisters, Jennifer and Tricia, who have supported me through all the ups and downs I’ve experienced over the years.

📄 Page 5

iv brief contents 1 ■ What is a lead developer? 1 2 ■ Lead developer career trajectory 25 3 ■ Learning lead developer skills 50 4 ■ Learning any developer skill 72 5 ■ Writing technical documentation 92 6 ■ Optimizing the development process 115 7 ■ Working with project teams 139 8 ■ Speaking with clients 165 9 ■ Being a mentor 188 10 ■ Taking the lead 210 11 ■ Leading with emotional intelligence 237 12 ■ Being a successful lead developer 268

📄 Page 6

v contents foreword xii preface xiv acknowledgments xv about this book xvii about the author xix about the cover illustration xx 1 What is a lead developer? 1 1.1 Who can be a lead developer 2 Who this book is for 4 ■ Reviewing top industries for lead developers 5 ■ Being a successful lead developer 6 1.2 Lead developer tasks 7 Leading the development team 9 ■ Working with project teams 11 ■ Communicating with clients and stakeholders 12 Setting development standards 13 ■ Building technical architecture 15 1.3 Lead developer expectations 16 Providing team support 17 ■ Forming working relationships 18 ■ Being a leader 20 1.4 Case study 22 What was your first experience as a lead developer? 22 What did you enjoy the most as a lead developer? 23 How did your experience as a lead developer set you up for success in your current job? 23

📄 Page 7

vi contents 2 Lead developer career trajectory 25 2.1 Reviewing software developer roles 26 Starting as a junior developer 26 ■ Becoming a senior developer 27 ■ Moving to lead developer or lead architect 29 Considering management and beyond 31 ■ Considering your career options 33 2.2 Moving through a software development career 35 Writing a résumé 36 ■ Creating a cover letter 38 Achieving success in technical interviews 39 Interviewing for development leadership positions 40 2.3 The job market for lead developers 42 Assessing the competition 42 ■ Standing above the crowd 43 Reviewing in-demand technical skills 44 2.4 Case study 46 What advice do you have for developers who are setting a career plan? 46 ■ How can developers stay on top of the competition in today’s job market? 47 ■ How can developers stand out during the interview process? 48 3 Learning lead developer skills 50 3.1 Prioritizing learning new skills 51 Learning current technical skills 52 ■ Reviewing necessary soft skills 53 ■ Practicing soft skills on the job 55 ■ Setting aside time for learning 56 3.2 Finding your leadership style 58 Reviewing popular leadership styles 58 ■ Assessing your personality type 61 ■ Observing personalities on your team 62 3.3 Improving your presentation skills 64 Calming your nerves 65 ■ Creating effective slides 66 Giving a great performance 68 3.4 Case study 69 What soft skills have you learned that helped you most in your career? 69 ■ How do you prepare for giving a presentation? 69 Why is it important to observe personalities on your team? 70 What advice do you have for lead developers with a busy schedule to help them prioritize learning new skills? 70

📄 Page 8

viicontents 4 Learning any developer skill 72 4.1 Improving your learning methods 73 Understanding how you learn 74 ■ Boosting your memory 75 ■ Taking care of your physical and mental health 76 ■ Teaching while you learn 77 4.2 Applying your skills 79 Developing personal projects 80 ■ Working on community projects 81 ■ Creating prototypes 82 4.3 Overcoming learning blockers 84 Taking breaks 84 ■ Setting attainable goals 85 Seeking help 86 4.4 Case study 88 How can a developer find community projects, and how can they get involved? 88 ■ How can a developer find the help they need to overcome learning blockers? 89 ■ What would you tell a developer who feels inadequate because they aren’t working on as many community projects as other developers in their network? 89 How do you like to learn new skills? 90 5 Writing technical documentation 92 5.1 Setting the team up for success 93 Documenting everything 94 ■ Managing technical debt 96 Onboarding new developers 97 5.2 Structuring documentation 99 Chunking the content 99 ■ Using visual aids 101 Including an introduction and summary 101 5.3 Creating the content 103 Starting with an outline 103 ■ Writing specific instructions 105 ■ Getting right to the point 106 Using a style guide 107 5.4 Implementing a documentation maintenance cycle 108 Testing the documentation 108 ■ Getting feedback 109 Setting a documentation maintenance window 110 5.5 Case study 111 How has writing proper documentation helped you set your team up for success? 111 ■ Have you received feedback from other developers about your documentation? Did they suggest any

📄 Page 9

viii contents improvements, and what were the suggestions? 112 What if someone has never written technical documentation before? What is your advice to help them get started? 112 Have you used any AI tools for writing technical documentation, and what was the result? 113 6 Optimizing the development process 115 6.1 Identifying opportunities for process improvement 117 Recognizing pain points 118 ■ Providing ideas for improvement 119 ■ Using AI coding tools 120 Managing the development process 122 6.2 Receiving feedback 123 Interviewing stakeholders 124 ■ Being open to constructive criticism 124 ■ Keeping an open mind 125 6.3 Reviewing the software development lifecycle 126 Identifying opportunities for automation 127 Removing bottlenecks 128 ■ Using a preventative versus reactionary approach 130 6.4 Maintaining the development process 131 Documenting the development process 131 Documenting the quality assurance process 133 Setting a development process maintenance schedule 135 6.5 Case study 135 What pain points have you encountered in the development process, and how did you address them? 136 ■ What are some ways that you’ve reduced technical debt? 136 ■ What advice do you have for lead developers to ensure that their development process is optimized? 137 7 Working with project teams 139 7.1 Cross-training project management skills 140 Reviewing the waterfall method 140 ■ Defining agile 142 Comparing agile to waterfall 144 7.2 Providing accurate estimates 145 Measuring hourly estimates 146 ■ Estimating in story points 147 ■ Including the team 149 7.3 Facilitating communication 152 Connecting team members 153 ■ Asking for help 154 Avoiding miscommunication 155

📄 Page 10

ixcontents 7.4 Improving project management processes 157 Supporting project managers 157 ■ Integrating deployments with project management systems 158 ■ Assessing your defect rate 159 7.5 Case study 161 How do you avoid miscommunication with your team members, and what are some important strategies you use? 161 Why is it important to ask for help? 161 ■ How do you support project managers? 162 ■ How do you connect team members with the people and resources they need to finish a task if they’re struggling? 162 8 Speaking with clients 165 8.1 Understanding your clients’ needs 166 Using active listening 166 ■ Asking insightful questions 167 Interviewing the end user 168 8.2 Suggesting technical approaches 170 Understanding wants vs. needs 171 ■ Considering the budget 172 ■ Presenting your case 174 8.3 Forming relationships with clients 176 Establishing trust with clients 176 ■ Getting to know your clients 177 ■ Remaining diplomatic 179 8.4 Dealing with difficult clients 180 Staying calm 181 ■ Letting them talk 182 Remaining engaged 184 8.5 Case study 185 How do you establish trust with your clients? 185 How do you handle clients who request features that are out of scope? 186 ■ What makes a successful presentation to outline your technical approach? 186 ■ How have you dealt with difficult clients? 186 9 Being a mentor 188 9.1 What is a mentor? 189 Comparing mentors and trainers 190 ■ Mentoring expectations 191 ■ Achieving success as a mentor 193 9.2 Forming relationships with mentees 194 Establishing trust with mentees 195 ■ Getting to know your mentees 197 ■ Finding common ground 198

📄 Page 11

x contents 9.3 Inspiring personal and career growth 199 Making a career plan 199 ■ Identifying skills to improve 201 Being a role model 202 9.4 Paying it forward 203 Empowering mentees to become mentors 204 Mentoring people outside of your organization 205 Participating in mentoring communities and events 206 9.5 Case study 207 Tell a story about one of your many achievements as a mentor. How did you help your mentees, and what success did they achieve? 208 ■ How do you help a mentee make their career plan? 208 ■ Do you have any examples of mentoring communities or events? What is your experience with these events? 208 ■ What advice do you have for lead developers who have never mentored anyone before? 208 10 Taking the lead 210 10.1 Providing instructions 213 Speaking with confidence 214 ■ Being clear and concise 215 Documenting frequently asked questions 217 10.2 Giving feedback 219 Providing positive feedback 219 ■ Giving negative feedback 221 ■ Planning feedback sessions 222 10.3 Handling emergencies 223 Remaining positive 225 ■ Bringing the team together 226 Outlining a plan 227 10.4 Improving your confidence 230 Assessing your strengths and weaknesses 230 ■ Avoiding comparing yourself to others 231 ■ Challenging negative thoughts 232 10.5 Case study 233 How did you know you were ready to be a leader? 234 How do you give negative feedback? 234 ■ What is your experience with leading a team through an emergency? 235 What advice do you have for lead developers who aren’t sure if they are ready to take the lead? 235

📄 Page 12

xicontents 11 Leading with emotional intelligence 237 11.1 What is emotional intelligence? 238 Understanding the four-branch model 239 ■ Teaching yourself to be emotionally intelligent 242 ■ Teaching your team to be emotionally intelligent 243 11.2 Using emotional intelligence 245 Becoming self-aware 247 ■ Managing working relationships 248 ■ Achieving personal growth 250 11.3 Learning radical empathy 250 Comparing empathy to radical empathy 251 ■ Understanding others 252 ■ Connecting on a deeper level 254 11.4 Having difficult conversations 254 Preparing before the conversation 256 ■ Listening more than you talk 257 ■ Following up on difficult conversations 258 11.5 Avoiding imposter syndrome 259 Practicing self-compassion 261 ■ Sharing your feelings 262 Discouraging perfectionism 263 11.6 Case study 264 How has practicing empathy affected your relationships at work? 265 ■ What lessons have you learned through self- awareness? 265 ■ How can emotional intelligence help balance a difficult conversation? 265 ■ What advice do you have for practicing emotional intelligence in the workplace? 266 12 Being a successful lead developer 268 12.1 Assessing your skill level 269 Shadowing other lead developers 270 ■ Building technical architecture from scratch 272 ■ Cultivating a positive working environment 274 12.2 Taking the leap 275 Gathering a group of mentors 276 ■ Starting your first project 278 ■ Setting yourself up for success 280 12.3 Working with management 281 Planning a budget 282 ■ Hiring developers 283 Firing developers 285 ■ Setting policies for AI tools 286 index 291

📄 Page 13

xii foreword My name is Steve Buchanan, and I’m honored to write this foreword. With more than 20 years of experience in the tech industry, I’ve worked as a generalist, led internal and consulting teams, and gained extensive knowledge in various facets of technology, including development. Recently, I’ve been advising startups and leading a research team at Microsoft, collaborating cross-functionally with executives, engineers, design- ers, and customer teams to evaluate end-to-end experiences across multicloud environ- ments, with a focus on improving Azure. I’ve known Shelley Benhoff for several years, meeting her as a fellow author of Plu- ralsight courses in the tech space. She is an established expert with more than 20 years of experience in the tech industry, much of it spent in development and leading devel- opment teams. Her most recent role is as a Senior Developer Experience Manager at Docker. I’ve always respected Shelley and followed her remarkable accomplishments throughout her career. When I heard she was writing the Lead Developer Career Guide, I was ecstatic. I knew she would bring a wealth of real-world knowledge to the topic. When she asked me to write a use case for the book, I didn’t hesitate to contribute. And when she asked me to write the foreword, I was even more excited because it gave me the opportunity to read the book early and recognize how invaluable it is for developers. Shelley is a leader, whether she is leading teams in her day-to-day job, supporting the community, or creating content to help others develop their skills. Manning could not have chosen a better author to write this book. In the world of development, especially as a junior developer, there is often little guidance on how to advance your career and start leading teams. Navigating the tran- sition from a junior role to a leadership position can be daunting without a clear road map. Many developers who have successfully made this leap did so without direct guid- ance, relying on their own experiences and learning through trial and error. This lack of structured support means that valuable lessons are often learned the hard way, with mistakes serving as the primary teacher.

📄 Page 14

xiiiforeword Recognizing this gap, the Lead Developer Career Guide steps in as a crucial resource. This book is designed to be a comprehensive, step-by-step guide for developers who are ready to move from junior or individual contributor roles to positions of leadership. The guidance it offers is not just theory but grounded in real-world experience. The author, along with other carefully selected contributors, shares practical advice and insights gained from years of navigating the tech industry. The collective wisdom in this book provides readers with a solid foundation on which to build their leadership skills. What sets this book apart is its focus on actionable advice and real-world use cases. Each chapter is filled with practical examples that illustrate the challenges and rewards of moving into a leadership role. The author, as a seasoned professional, offers a unique perspective on various aspects of the transition, from developing essential soft skills to mastering the technical competencies required for effective leadership. This diverse array of insights ensures that readers can relate to and learn from multiple experiences, making the journey to becoming a lead developer more accessible and achievable. As a reader, this book takes you, the junior developer, on a journey to understanding what it means to be a lead developer. It covers the career trajectory for the role and the necessary skills, both soft and technical: how to write technical documents, work with project teams, and optimize development processes. You’ll also explore the world of consulting, working with clients, increasing your emotional intelligence, stepping into leadership roles, and even becoming a mentor. The book is enriched with real-world use cases from experts in the tech field, and it includes numerous charts, graphs, diagrams, and other graphics to provide a visual breakdown of complex concepts and processes. By the end, you’ll have a comprehen- sive understanding of what it truly takes to become a lead developer. For the foreseeable future, this book will be my go-to recommendation for junior developers who aspire to level up into a lead developer role. It stands out as an essential resource, providing the structured guidance that so many developers need but often lack. Whether you’re just starting to think about advancing your career or are already on the path to leadership, this book offers invaluable insights and practical advice to help you achieve your goals. I hope you enjoy this book as much as I have, from start to finish. It offers a wealth of knowledge that is not only valuable for a full read-through but also serves as a lasting reference. You can return to it anytime you need specific advice on the many aspects of a career as a lead developer. Whether you’re dealing with technical challenges, team dynamics, or personal growth, the guidance in this book will be a reliable companion throughout your career. This book is designed to grow with you, offering insights and guidance at every stage of your journey into leadership. Its practical examples and real-world use cases make it easy to apply the lessons learned to your own experiences. As you progress in your career, you’ll find that this book continues to provide relevant and actionable advice, helping you navigate the complexities of leadership in the tech industry. — Steve Buchanan Principal Program Manager, Microsoft

📄 Page 15

xiv preface Throughout my 25-year journey as a developer, my focus wasn’t always on leadership. Starting out as a junior developer, I found immense satisfaction in the technical intri- cacies of the job, thriving in research and training. It wasn’t until my boss, recogniz- ing my potential, broached the subject of leadership that I began to contemplate its possibilities. Initially, I hesitated, uncertain of what leadership entailed or whether I possessed the necessary skills. However, driven by my aspirations, I embraced the challenge. With time, I progressed from senior developer to team lead, eventually attaining the role of lead developer. Reflecting on my journey, I recognize that perhaps a bit more preparation before- hand would have eased some of the early struggles. I encountered my fair share of chal- lenges, particularly in navigating conflicts within my team, which proved to be stressful. Yet, each obstacle was a learning opportunity, shaping me into a more resilient leader. The inspiration for this book struck me when I stumbled upon Alyssa Miller’s Cyber- security Career Guide. Realizing the lack of resources specifically tailored for lead devel- opers, I felt compelled to fill the gap. My own experiences as a novice lead developer fueled my determination to create a comprehensive guide for those embarking on a similar path. Being a successful lead developer demands a delicate balance of technical prowess and interpersonal finesse. Within these pages, I not only delve into enhancing techni- cal skills but also provide practical examples to cultivate crucial soft skills, such as effec- tive communication. Additionally, I’ve curated a selection of supplementary resources to facilitate a deeper exploration of the topics discussed. It’s my sincere hope that this book serves as a beacon for aspiring lead developers, guiding them away from the pitfalls I encountered and toward a smoother, more fulfill- ing journey in leadership.

📄 Page 16

xv acknowledgments I want to thank my husband, Jason Benhoff, for supporting me to reach my goals. Writ- ing a book is hard work, and it takes time away from quality time with my family. This was my first book, and I didn’t know what to expect. I often felt discouraged because everything took longer than I intended, but you were there for me, and you listened to my concerns, which helped me push through to the finish line. I also want to thank the contributors to the case studies throughout the book: Ryan Lewis, Deborah Kurata, Dan Wahlin, Chloe Condon, Maureen Josephine, Scott Hansel- man, Jamie Maguire, Edidiong Askipo, and Gabriela Martinez-Sanchez. Thank you for your time and for sharing your real-world experiences to create engaging case studies to tie into the topics presented. I appreciate every one of you, and I’m lucky to know you. Next, I’d like to acknowledge my editor at Manning, Rebecca Johnson. Thank you for your guidance and patience when life got in the way of my progress. Your dedication to the quality of this book has truly enhanced the experience for all who delve into its pages. Thank you to everyone at Manning who worked with me on the production and promotion of the book. It was truly a team effort, and I enjoyed working with the team at Manning throughout the development of this book. I also want to extend my heartfelt gratitude to the reviewers who generously dedi- cated their time to reading my manuscript at different points in its journey, offering invaluable feedback along the way: Alex Rios, Ari-Pekka Lappi, Avinash Kumar, Avishek Roy Chowdhury, Balraj Singh, Bill LeBorgne, Dinesh Kumar, Foster Haines, Giacomo Gamba, Greg MacLean, Greg White, Ian De La Cruz, Javid Asgarov, Johannes Loch- mann, John Kasiewicz, Leonardo José Gomes da Silva, Marc Taylor, Mario (Plamenov) Pavlov, Matt Deimel, Matthias Bartsch, Mike Baran, Neil Croll, Nolan To, Philippe Vialatte, Raul Murciano, Steve Goodman, Stuart A. Schmukler, Tam Nguyen, Tim O’Leary, and Zeynep Nur Aktaş.

📄 Page 17

xvi acknowledgments Special thanks to Stephen Mizell, technical editor, for your detailed reviews. Your knowledge regarding the lead developer role was crucial to crafting the storytelling aspects of this book and aided me in writing relatable scenarios in which lead develop- ers may find themselves. The quality of your reviews was always excellent, and I appre- ciate the time you spent making sure my book was of the highest quality. Stephen is a leader in the API industry and has helped companies such as Autodesk, SmartBear, Apiary, and Optic build great API products. He’s the author of API by Design and The Language-Oriented Approach to API Development and is a co-author of the API standard RESTful JSON. And finally, thank you to Steve Buchanan for your contributions, including a case study and the book’s foreword. Your enthusiasm for mentoring lead developers exem- plifies mentoring excellence that we should all strive to uphold. I learned a lot from you, and I appreciate the thought that went into your case study and foreword. I feel very honored that you spent so much time on this, and your efforts are much appreciated.

📄 Page 18

xvii about this book Being a lead developer was one of the hardest roles I’ve taken on in my career. Moving from a senior developer into leadership has a very steep learning curve. Most lead developers lack the soft skills or training to achieve true leadership, and they need guidance to set themselves up for success. In this book, you’ll learn how to lead teams, work with project managers, present solutions to clients, and use critical thinking during emergencies. You’ll also learn how to mentor teams and provide accurate esti- mates to help project managers keep projects on track and within the budget. When you’re finished reading this book, you’ll understand how to combine your technical skills with the leadership skills necessary to become a successful lead developer. Who should read this book If you’re a junior developer, this guide will help you plan your career path to becoming a technical lead. If you’re a senior developer, you’ll master the leadership abilities that will turn your technical knowledge into an asset for your whole team. If you’re a team leader, hand this book to your best developer to help them mature into the role of lead. How this book is organized: A road map The book has 12 chapters: ¡ Chapter 1 defines the role of lead developer, including the daily tasks and what team members expect in a successful lead developer. ¡ Chapter 2 discusses the lead developer career trajectory starting with junior developer and moving through different career paths into technical leadership. ¡ Chapter 3 lists lead developer skills you should learn, including different leader- ship styles and how to choose the right one for your personality. ¡ Chapter 4 provides tactics and tools you can use to learn any developer skill, apply these skills on the job, and overcome learning blockers.

📄 Page 19

xviii about this book ¡ Chapter 5 details the importance of technical documentation and how to write documentation that is easily accessible to your team. ¡ Chapter 6 discusses the optimization of development processes and how to main- tain a streamlined development process to follow best practices in the Software Development Lifecycle (SDLC). ¡ Chapter 7 reviews how to work with project teams and communicate effectively to avoid miscommunication and improve project management processes. ¡ Chapter 8 describes how to form relationships with your clients and stakeholders while catering to their needs and resolving conflicts with difficult clients. ¡ Chapter 9 defines what it means to be a mentor and how you can help your team members achieve career and personal growth. ¡ Chapter 10 provides examples of hurdles that lead developers face when taking the lead for the first time and how to overcome them to improve confidence and lead a successful team. ¡ Chapter 11 defines emotional intelligence and its importance to the role of lead developer. ¡ Chapter 12 discusses how to decide when you’re ready to take the leap into a lead developer role and set yourself up for success. liveBook discussion forum Purchase of Lead Developer Career Guide includes free access to liveBook, Manning’s online reading platform. Using liveBook’s exclusive discussion features, you can attach comments to the book globally or to specific sections or paragraphs. It’s a snap to make notes for yourself, ask and answer technical questions, and receive help from the author and other users. To access the forum, go to https://livebook.manning.com/ book/lead-developer-career-guide/discussion. You can also learn more about Man- ning’s forums and the rules of conduct at https://livebook.manning.com/discussion. Manning’s commitment to our readers is to provide a venue where a meaningful dia- logue between individual readers and between readers and the author can take place. It’s not a commitment to any specific amount of participation on the part of the author, whose contribution to the forum remains voluntary (and unpaid). We suggest you try asking the author some challenging questions lest her interest stray! The forum and the archives of previous discussions will be accessible from the publisher’s website as long as the book is in print. Other online resources If you want to deep dive into the soft skills presented in this book, you can watch Shel- ley’s online courses on Pluralsight: https://pluralsight.com/authors/shelley-benhoff. She also has courses on LinkedIn Learning: www.linkedin.com/learning/instructors/ shelley-benhoff.

📄 Page 20

xix about the author Shelley Benhoff has 25+ years of experience in IT as a lead developer, trainer, Docker Community Leader, and Sitecore MVP. She has a passion for tiaras, technol- ogy, gaming, and general nerdery. She loves to learn new things as well as mentor and teach others. She teaches leadership, communication, Docker, and Sitecore devel- opment on Pluralsight and LinkedIn Learning. Shelley aims to provide her students with an immersive learn- ing experience based on real-world scenarios. She has studied soft skills and technical skills to become a well- rounded leader. Many of her online courses include entertaining animated scenarios using real experiences from her career to walk students through common workplace events to help visualize learning objectives.