-
Developing teams at different levels
Engineering leaders at different levels of seniority reflect on what they’ve learned.
-
Growing teams and culture with actionable feedback
We'll consider why developing a strategy around delivering feedback is important, how feedback can be optimized for reception and action, and why the consistent delivery of positive, reinforcing feedback makes feedback of all types more impactful.
-
On engineering impact
Tough technical problems are exciting to tackle and often engineers can think this is where they’re driving the most value.
-
Harnessing the power of storytelling to become a better leader
When we’re talking to engineers about change, we often just talk about what the change will be and not the context, why it’s necessary, and why we think it will be successful.
-
Crafting a mission and vision for your team
As you progress in seniority as a leader, the time horizon of your work progressively gets longer.
-
Sponsored by: you
We’ll also explore how to sponsor individuals by raising their visibility in an organisation and providing them with opportunities.
-
Why we must strive for belonging in our engineering orgs
Spotify’s focus on diversity has been the foundation of an enriched environment of culture, ideas, and innovative business solutions. However, diversity alone does not ensure open communication or retention in the workplace.
-
Preparing your software engineering teams for times of financial uncertainty
Financial crashes are cyclical in nature and although we can’t predict the timing of the next crash, we know that they are an inevitability.
-
Supporting employees through redundancies and business closures
Reality sometimes makes decisions for us. Teams and businesses come to an end or need to focus elsewhere. But lives go on...
-
Living without pre-production environments
Historically when we developed large monolithic applications we had several ‘lower’ environments such as dev, test, staging, pre-prod for verifying different stages of our development life cycle. These were particularly used for manual testing – integration testing, gatekeeping, acceptance testing.