16 years. One Company

People ask me how I stayed at my firm that long.

Honest answer: I didn’t stay. I kept moving — just inside the same brand. (My firm doesn’t really let you settle in one place anyway 😄)

From writing code as an analyst to architecting enterprise platforms for some of the largest digital programs across the US and the Middle East. From India, to the US, to the Middle East. From early implementations to designing end-to-end architectures spanning multiple vendors and complex client use cases.

Here’s what 16 years actually teaches:

𝗬𝗼𝘂𝗿 𝘁𝗶𝘁𝗹𝗲 𝗰𝗵𝗮𝗻𝗴𝗲𝘀. 𝗬𝗼𝘂𝗿 𝗿𝗲𝗽𝘂𝘁𝗮𝘁𝗶𝗼𝗻 𝗱𝗼𝗲𝘀𝗻’𝘁 𝗿𝗲𝘀𝗲𝘁.
Every room I walk into, my track record walks in with me. That only compounds if you stay long enough to build it. Job-hopping optimises for salary. Staying optimises for depth.

𝗧𝗵𝗲 𝗵𝗮𝗿𝗱𝗲𝘀𝘁 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀 𝗮𝗿𝗲 𝗻𝗲𝘃𝗲𝗿 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹.
I’ve solved complex architecture challenges at scale. But the real difficulty is always people — aligning internal stakeholders, wrangling multiple vendors, getting teams with competing priorities to agree on a shared standard. No certification teaches you that. You just have to live through it enough times.

𝗙𝗶𝗻𝗱 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗺𝗲𝗻𝘁𝗼𝗿.
No one figures this out alone. The right mentor isn’t just someone who guides you — they give you honest feedback even when it’s uncomfortable, they believe in you in your hardest moments when you don’t quite believe in yourself, and they genuinely invest in your growth without expecting anything back. That kind of person is rare. If you find one, don’t take it for granted.

𝗚𝗼 𝗱𝗲𝗲𝗽 𝗲𝗮𝗿𝗹𝘆. 𝗚𝗼 𝘄𝗶𝗱𝗲 𝗹𝗮𝘁𝗲𝗿. 𝗡𝗲𝘃𝗲𝗿 𝗹𝗼𝘀𝗲 𝘁𝗵𝗲 𝗵𝗮𝗻𝗱𝘀-𝗼𝗻.
There’s a trap at the senior level — you drift into decks and decisions and stop understanding what’s actually being built. The architects I respect most can still roll up their sleeves. Breadth without hands-on experience is just expensive opinions.

One thing I’d tell my 2010 self: the work compounds. Show up, do good work, stay curious. The rest follows.