Xavier F. Gouchet

This roundtable explores the unique challenge of joining a new team or company as a Staff or Principal Engineer—where you're expected to lead, but the structure, ownership, and legacy might already be deeply entrenched. Unlike earlier roles, Staff+ success often means defining your own lane, identifying unclaimed problems, and building influence without authority. We’ll share experiences and strategies for navigating ambiguity, earning trust, and making impact when you’re not handed a clear backlog. Whether you’re in a Staff+ role now, managing Staff engineers, or aspiring to grow into one, this conversation will offer real-world insight into leading without a script. What helped you (or someone you mentored) find traction when joining a new org as a Staff+ engineer? How do you balance observing vs. acting when you’re new and expected to lead? What are red flags or common traps for Staff+ engineers onboarding into legacy-heavy systems? How do you identify “high-leverage” problems or unclaimed ownership areas in a complex codebase or org? How can engineering managers or directors better support Staff engineers during their first 90–180 days?

Compiler plugins provide a gateway to extend the capabilities of the Kotlin compiler, allowing developers to inject custom logic into the compilation pipeline. Without compiler plugins, Android Jetpack Compose would have never been possible. Compiler plugins enable the use of Aspect Oriented Programming to apply cross-cutting logic for use cases when Kotlin's language is not modular enough, or create your own implementation of Kotlin’s Coroutine. In this session, we will explain the fundamentals of Kotlin's Internal Representation (IR) and explore the details of compiler phases. We will then showcase some meta-programming samples, illustrating how to inspect and modify the output of the compiler.