Abstract
As individual contributors we sharpen our technical chops striving to improve our code and craft. But you may become aware you can do more, and could help others and the team. The path to make that shift isn’t always clear.
In order to support our product roadmap and team I’ve had to learn several skills beyond writing code. I’ve had to practice patience and learn to check my own ego. It’s taken years, and I’m still learning, but the rewards have made it worthwhile.
In this presentation I’ll share some lessons that helped me expand my scope, including recognizing and supporting other’s work and communication styles, working across and between teams, and driving change that lasts. I’ll share real examples and practical takeaways for anyone looking to move forward.
Interview:
What is your session about, and why is it important for senior software developers?
I'm presenting my lessons learned on expanding from individual contributor to tech lead. Skills used to lead a technical team are broader than that required for technical product, and I want to help provide a path to those interested in expanding their influence.
Why is it critical for software leaders to focus on this topic right now, as we head into 2026?
There's always been a need for people with both technical expertise and cross-organizational skills. As we head into 2026, this is becoming even more critical. With AI tools automating many coding tasks, success increasingly depends on the ability to communicate clearly, provide context, and explain the 'why'—the exact skillset that technical leaders use to work effectively across engineering teams and the broader organization.
What are the common challenges developers and architects face in this area?
If one is determined to be a strong developer or architect, those skills initially focus on technical problem-solving rather than collaboration. Growing as a technical leader requires turning one's attention outward. That means understanding people's work and communication styles, reaching out to other teams to understand their requirements, and better supporting business needs. Building these skills can mean growing pains and feeling like a beginner again.
What's one thing you hope attendees will implement immediately after your talk?
I hope that attendees will start to turn their day-to-day activities from individual accomplishment to solving problems across their team and organization.
Speaker
Brad Grantham
Software Architect and Team Lead @LunarG - Responsible for Cross-Platform, GPU-Independent Graphics API Capture and Replay Technologies
Brad Grantham is an engineering leader with over two decades of experience in cross-platform GPU tooling. He’s grown from writing graphics code at Silicon Graphics, AMD, and ARM to leading a 14-engineer team at LunarG and helping guide company strategy. Along the way, he’s learned the value of service and sharing knowledge beyond just building software.
Find Brad Grantham at:
Date
Tuesday Nov 18 / 03:55PM PST ( 50 minutes )
Location
Seacliff ABC
