When Writing Code Is No Longer the Bottleneck: Rethinking Engineering Seniority

As AI takes on implementation, debugging, refactoring, testing, and increasingly complex engineering tasks, how does our role evolve? What does seniority mean when more of the work we once used to demonstrate it can be delegated?

I went from bootcamp graduate to Staff Engineer in four years. The biggest shifts were in how I understood my responsibilities: looking beyond the frontend, connecting technical decisions to product outcomes, and learning how to move work forward within an organisation.

As the role expands from frontend developer to full-stack and product engineer, what should we take ownership of? How do we balance user experience, architecture, reliability, commercial priorities, and the constraints of the teams around us? And how do we improve the stack while keeping the product moving?

This talk explores the judgment behind those decisions. We’ll look at thinking across layers and disciplines, choosing where to invest engineering effort, and creating room for change without requiring every team to share our priorities.

You’ll leave with a broader understanding of engineering seniority and practical ways to develop it: asking better questions, making trade-offs explicit, taking ownership of outcomes, and helping your organisation adapt as the tools and expectations of software engineering evolve.