Meghal Shah

The best advice I got on my promotions as a software engineer was from a Principal Architect at Amazon after he told me his story of getting promoted to Principal, and this has stayed with me my whole career. He said, very simply: > Your architecture can be a love letter to your technical brilliance, > but if it does not move customer and company goals, it will not move your level. That hurt a little. Because I recognised myself in it. A few years ago I wanted to design something with every shiny thing in the book: API Gateway, Lambda, DynamoDB, event bus, the works. On paper it was beautiful. In reality it was expensive, slow to ship, and did not match the skills of the team that would maintain it. So we shipped a hybrid architecture instead. Fewer moving parts, more reuse of existing services, cheaper to run, easier to hand over. Over time, here is how my thinking about promotions changed. 1. Start from the business goal, not the tech stack Before talking about Kafka vs SQS or MySQL vs DynamoDB, answer this first: What money, risk, or customer pain will this remove? Promotions track that, not the number of services in your diagram. 2. Ship finished products, not clever demos Leaders remember the feature that went live, stayed stable, and earned or saved real money. Drive the entire lifecycle yourself: design, build, launch, oncall, cleanup, docs. 3. Make the team faster, not just yourself Tools, scripts, templates, better CI, better dashboards. If people quietly say “things move faster when you are on this” your manager already has half a promotion case. 4. Do your share of the unsexy work Oncall, migrations, bugs, incident reviews. Senior folks who avoid this slow the entire org. Senior folks who lean into it become trusted very quickly. 5. Grow people, not just systems Mentor juniors, run design reviews, write clear docs, set standards. When your manager sees that you are already acting like the next level, formal promotion becomes a catch up, not a favour. 6. Be proactive about your promotion, not obsessed with it Have periodic one to ones. Talk about where you want to go and ask what evidence your manager would need to support that. Remember your manager has ten other people to manage. It is your responsibility to make your impact visible. Do not be desperate. Understand the timelines and work within them. As you get close to the boundary, collect the missing data points: impact metrics, incident write ups, design docs, peer feedback. Make the story easy to tell. Most importantly, work for the business, not for promotion-driven development. If your roadmap only exists to tick boxes on a promotion rubric, people can feel it. If your roadmap clearly creates value, saves cost, or reduces risk, promotion becomes the natural side effect. So instead of asking “What new tech can I use this year?” Ask, “Where can I create obvious business impact and leave the system and the people around me better than I found them?”

182

15 Comments

18 Years of Vision: A Reflection on an Era at Adobe After 18 years at the helm, Shantanu Narayen has decided to step down as CEO of Adobe. 18 years is more than a tenure. It’s an era. When he became CEO in 2007, Adobe looked very different. Software came in boxes. Products were sold once. Updates arrived every few years. Then came a bold decision that many doubted. Adobe moved from boxed software to the cloud. Photoshop. Illustrator. Premiere Pro. All transitioned to Creative Cloud, turning a traditional software company into a subscription-driven platform. At the time, it looked risky. Today, it’s taught in business schools. During those years, Adobe didn’t just evolve its products. It reshaped its identity. Revenue grew from roughly $3B in 2007 to over $23B+ annually. Adobe expanded from creative tools into digital marketing and customer experience platforms. Its market value climbed from about $20B to hundreds of billions at its peak. But perhaps the bigger transformation was cultural. Adobe stopped thinking like a product company. It started thinking like a platform for creators and businesses worldwide. And now, as Narayen steps aside, Adobe stands at another turning point. Artificial Intelligence. Generative tools. Creative automation. New ways of building, designing, and telling stories. The next chapter will be written in AI. But the foundation of that chapter was built over the last 18 years. Leadership transitions are often described as endings. But the best ones feel more like passing the baton in the middle of a race. Because companies like Adobe don’t move in decades. They move in eras. And this was one of them. ​Shantanu Narayen's 18-year journey at Adobe is a testament to his exceptional leadership, vision, and dedication. He has transformed Adobe into a global powerhouse, and his impact on the creative and technology industries will be felt for years to come. As we pay tribute to his remarkable tenure, we can look forward to seeing what the future holds for Adobe under his continued guidance. The question now isn’t just who becomes the next CEO. It’s: What will the next 18 years of creativity look like? #Leadership #Adobe #Innovation #TechnologyLeadership #FutureOfWork

48