Monday, 8:00. You open Slack and a key architectural decision was made overnight — without you. You're a strong Senior Android engineer. So why aren't you in the room where it happens? And what's the path beyond Senior that isn't "become a manager"?

From 14 years building Android apps — business features, payments, app security — and now leading a team of Staff engineers across a 9-hour San Diego–Warsaw gap, I'll map the third path: Staff Engineer. The shift from "my ticket" to "our system," where your success is measured by the decisions others make because of you.

You'll leave with:

The 4 Staff archetypes — Tech Lead, Architect, Solver, Right Hand — and when to switch
4 anti-patterns that quietly derail strong seniors
"Influence without authority": how I got a security team to champion my Android work — without being their boss
Why, in the AI era, deciding whether to write code beats writing it