Transitioning from an individual contributor to a technical leader requires more than just technical expertise—it demands a new set of leadership skills, strategic thinking, and the ability to empower a team. This half day interactive workshop is designed to help new and aspiring technical leaders build a strong foundation in technical leadership.

1-1s are ubiquitous in the software engineering industry, and great leaders cherish these discussions. What makes 1-1s so valuable? 1-1s are just like any other meeting - they are used to exchange data - be it tactical project updates, personal updates, or perspectives on how a project is going. There is also implicit data exchanged, signals that are interwoven with each word that is spoken. These are our emotions. Emotions can be felt and observed but can be difficult to interpret and process. Our brains are in overdrive when communicating with other humans as we take in these implicit signals along with the literal words being spoken. During 1-1s, this can intensify as our focus is entirely on the other person; What signals are they sending? How will I respond? What isn’t being said here?

In the ever-evolving landscape of software engineering, the success of a team is not solely determined by the mastery of coding languages or the ability to develop cutting-edge solutions. It also hinges on the presence of an often underestimated yet essential element: psychological safety. Psychological safety, as coined by Harvard Business School professor Amy Edmondson, refers to an environment where team members feel comfortable taking risks, sharing ideas, and making mistakes without fear of ridicule or retribution. In the context of software engineering, fostering such an environment can significantly impact team dynamics, productivity, and innovation.

Imposter Syndrome, a pervasive phenomenon affecting individuals across various industries, holds a particularly potent grip within the realm of software engineering. It is characterized by persistent self-doubt and a belief that one's accomplishments are mere flukes, is alarmingly common in the technical engineering community.