How Structured Learning Helped a Senior PayPal Engineer Make Better Architecture Decisions

Joseph spent nearly two decades in tech — across India, the Gulf, and the US — before becoming a Staff Cybersecurity Engineer at PayPal. He was already senior and still chose to upskill with our DevOps and DevSecOps bootcamp. This is how it changed the way he makes architectural decisions, justifies his tool choices, and leads his team.

Watch Joseph's Complete Journey

See the full story — from his first job in India to building security systems at PayPal — and the exact learning approach he used along the way.

[NOTE BY EDITOR: YT VIDEO RELEASED SOON ON TWN CHANNEL!]

Meet Joseph 👋

Hi, I'm Joseph, a Staff Cybersecurity Engineer at PayPal, based in Austin, Texas 🇺🇸.

I'm originally from India, and I've been in tech for close to 20 years.

Most of my work today lives at the intersection of platform engineering, security, and applied AI — designing zero-trust and service-to-service authorization patterns, building production AI systems, and finding where engineers lose time or where risk hides, then fixing the root cause.

Outside my day job, I'm a Docker Captain and an AWS Community Builder, and I've published 100+ technical articles on cloud architecture, AI systems, and DevSecOps.

Writing and teaching keep me honest — explaining something clearly is how I know I actually understand it.

From a First Job in India… to Securing One of the World's Largest Payment Platforms

Joseph currently works as Staff Cybersecurity Engineer at Paypal in Austin (the new tech hub in US)

Joseph's story isn't the usual "career-switcher who found their first tech job through a bootcamp."

By the time he took his first TechWorld with Nana program, he had already been an engineer for more than a decade, lived and worked on three continents, survived a layoff, and rebuilt his career around Cloud and DevOps.

So why would someone that senior — a cybersecurity engineer at PayPal — sit down and work through bootcamp after bootcamp, starting from the fundamentals?

That's exactly what makes his story worth reading.

🧳 Joseph's Career Journey at a Glance

📍 Started his career in India — early roles in a consulting company, then business-intelligence development for a leading Indian bank. 📍 Moved to the Gulf (Oman) — SharePoint and collaboration work for banking, government, and oil-and-gas clients. 📍 Relocated to Austin, Texas (2013) — contractor work, then a Principal Applications Developer role at CA Technologies (later acquired by Broadcom). 📍 May 2018 — laid off after the acquisition. On an H1B visa with a 60-day window, he was forced to return to India for a time. 📍 The pivot — eight months at a startup as a delivery head, then a deliberate decision to move into Cloud and DevOps. 📍 Back to the US — Sr. Staff Software Engineer at Visa, then joined PayPal in November 2021 on the cybersecurity side, hired to do automation. 📍 2023–2026 — invested in structured TWN programs while already at PayPal: Kubernetes (CKA), GitLab CI/CD, the DevSecOps Bootcamp, and the DevOps Bootcamp. 📍 Recognition: earned the Docker Captain and AWS Community Builder titles (and was a Microsoft MVP for four years before that).

Joseph's journey in his own words 👇

You'd been in tech for almost 20 years. Where did the journey actually start?

I started my career in India in a consulting company. My first job was to hand over the CDs with the license printed on them — the MSDN CDs and others — to people who wanted to install software to test new hardware.

In my free time, I used to write some Java code to build small web apps.

One of my manager's friends came to my desk one day, saw what I was doing, and asked, "Why don't you come to my team and do something cool?"

That was my first change in my career — I became a business-intelligence developer working for a leading bank in India.

Then I moved to the Gulf. That gave me a lot of great opportunities — banking customers, the Ministry of Defense, the Ministry of Housing, finance, government sectors, oil and gas — which helped me improve my skills.

There's a mindset I've carried everywhere since school:

"In my school we used to have a motto, be first and be with the first. That motto I apply everywhere wherever I go. I try to be first, but otherwise I will try to be with the people who are first in the industry."

After the Gulf I came back to India for a while, then in 2013 I moved to Austin, Texas.

I worked as a contractor first, then spent four years as a Principal Applications Developer at CA Technologies — mostly Office 365, SharePoint, and enterprise collaboration tools.

Then in 2018, everything changed. What happened?

The company was acquired by Broadcom, and there was a large layoff in stages. I was part of the first phase.

"In May 2018, I went through a layoff. The previous year we bought a new home, new car and we settled. I thought life is settled and everything is going good."

That's when the real problem showed up. I had been working with low-code and no-code enterprise collaboration tools — important work, but a narrow stack.

"Until 2018 I was stuck with a specific stack. So when I try to search for jobs at that time it was very difficult because I'm on H1B visa here. So we had to find a job within 60 days."

"I got some offers but it was a bit delayed. So I was forced to go back to India for some time."

I got some offers, but not the ones I wanted, on that stack.

That's when I realized it was a narrow path — and I started to expand my skills into other technology stacks.

Editor's Note: This is the part a lot of experienced engineers underestimate. Deep expertise in one narrow stack feels safe right up until that stack stops being in demand. Joseph's response wasn't to find one more job on the old stack — it was to rebuild around skills that transfer.

How did you decide DevOps was the right pivot — and not, say, more software development?

Going back to India was hard after years of building a career in the US.

I spent eight months at a startup, which taught me a lot about how fast products ship and where customers feel pain.

"But I kept coming back to one question: what should I actually learn next?"

I looked at how software was built and shipped to customers, and I realized DevOps was completely different from how I'd been working — and that it wasn't something you can pick up from a few random videos.

You need a definite plan: what tools, what concepts, in what order. The reason I chose DevOps over going deeper into development was simple:

"I just need to learn the generalized skills which I can apply anywhere where I go. The tools may be different. But the process and the methodology or the framework or the patterns what we use, it's kind of common everywhere."

So I started with the foundations — Linux basics, then networking, then Docker, Kubernetes, and the rest.

That's also around the time I found Nana's channel, about six years ago, and went through the free content first.

Editor's Note: Notice the order of operations. Joseph didn't pick a trendy tool and go deep. He looked for the transferable layer underneath the tools — the process and patterns that stay the same when the tooling changes.

That instinct is exactly what the bootcamps are built around.

You were already a senior engineer at PayPal when you invested in structured courses. Why bother?

It's very easy at a senior level to say, "I know my stuff, I'll just learn on the job."

I took the opposite approach, and a big part of that is where I come from.

"Coming from a teachers' family — all my aunties and my mom and my sister is a teacher. My wife is also a teacher now."

So learning from others, and learning every day, has always been part of who I am. And things change so fast that I can't rely on what I happen to know right now.

"Don't rely on my own skills. What I know at the moment, because things change rapidly."

There's also a multiplier most people miss. Learning by itself helps you. But it's not only about learning:

"It's not about learning only. It's about sharing what you learn... it's a compounding effect, I will say, when you share, because you will see people's different perspective and how they solve the same problem with a different idea."

You took the programs in an unusual order — Kubernetes first, DevOps last. Why?

I thought about budget and time, so I didn't start with the biggest course. I started with the most useful next step for where I was.

"What I did first, before even I took the DevOps course, I took GitLab and Kubernetes course. Kubernetes course was my first course actually, because end of the day, even if you dockerize it has to be deployed in a cluster."

Next I did GitLab, because I was heavily into Jenkins at the time and wanted to learn another CI/CD tool end to end. (I now use a lot of what I learned there with Harness.)

Then I went for the DevSecOps Bootcamp:

"I decided to buy a full course, DevSecOps course, because... I'm part of the cybersecurity team. In every phase of your software development process, I need to introduce security in the projects."

And the reason I eventually took the full DevOps Bootcamp too comes down to leadership. I can't lead a team in something I only half-understand.

"If I don't know, I cannot teach my fellow engineers. So that is the thought that led me to take a proper course so that I can build a team with the security mindset culture in the team."

"I decided, okay, we will take DevOps course completely so that it will be end to end for me to learn and grow in this and make other people also grow in that aspect."

Editor's Note: We recommend DevOps Bootcamp first, then DevSecOps.

Joseph reversed it on purpose — he was on a security team and needed the DevSecOps layer immediately, then completed the picture with the full DevOps Bootcamp.

Different starting point, same destination: end-to-end understanding.

How did the programs change the way you make technical and architectural decisions?

At a staff level, your job isn't just knowing tools. You have to evaluate architectures, justify choices, and convince both leadership and the engineers downstream who have to build what you decide.

That requires more than a diagram.

"You can design a very beautiful solution in terms of architecture diagrams and other things. But why I chose that, and what are all the trade-offs I made? That is very important for people to trust your decision."

The training gave me a way to reason about and explain those decisions:

"You need to tell a story first of all. Why this tool was introduced and how it is going to help, and what kind of return on investment if you implement this tool. Why this tool versus the other tool in the same space — for example, GitLab versus Harness."

And the result showed up directly in how my team responded to me:

"When I design some solution, the team members, they were able to trust my decisions with the data points, whatever I'm presenting."

"This course has definitely helped me to decide on this."

In his written feedback to us, Joseph put the same point even more directly:

"Your courses helped me gain the knowledge and confidence to speak boldly within my company and in public forums."

You also lead and mentor engineers. How did the training feed into that?

A big part of my role is bringing a security mindset into every stage of how we build — and getting interns and engineers to adopt it early in their careers, because that's not always something they were taught.

I got to put it into practice on a real project: a lot of Slack bots had been built and deployed across the company, with engineers provisioning their own servers wherever they wanted.

My task was to find those patterns, convert them into a proper microservices solution, and deploy them in the cluster.

"That's when I really used the skills, what I learned from these courses."

That migration was also a culture change, not just a technical one — working closely with teams, helping with proof-of-concepts, unblocking them where they got stuck. And I keep that going through mentorship every day:

"People will trust you when you show something, not when you say I know something. So try to prove by doing something."

Editor's Note: Highlight worth pausing on — Joseph used the programs not only to upskill himself, but to train his own engineers and instill a security-mindset culture across his teams. That's the difference between an individual learner and a force multiplier.

How did all of this apply to your actual work at PayPal?

I was hired to do automation on the security side, and automation is the fastest way to earn trust — operations teams love you when you save them time.

But you have to pick the right problems:

"Take something like 70% is high-impact problem and 30% is low-hanging fruit that we can solve — that will be something helping them a lot."

From there it's about proving value with small POCs before going deeper, connecting with the right people for context, and committing to the team decision even when it isn't the one you proposed.

The learning plugged straight into that — better architecture calls, clearer justifications, more credibility, and more visibility for the work.

You have a demanding job and a family. How do you find time to keep learning?

This is the hard part. Motivation is easy; consistency is not.

"Everyone will take the gym membership on the first day of January, but after one week they will not go there."

So I protect a fixed window:

"For me, I'm an early morning person, so my timing, 5:30 to 6:30, is my learning time every day. And Saturdays — at least I'll spend one hour or two hours, mostly when the kids and family take rest."

The other half is knowing what to learn. I read job descriptions from different companies to see what's actually in demand, follow the right people, and protect that time like an appointment.

Can engineers really get their employer to pay for this kind of learning?

Two things here.

First, before any employer funding, invest in yourself:

"Setting a budget for your own growth is very important, I will say, because we change our phones every year. So why not spend more money in building our own career."

Second, employer funding is a huge, under-used opportunity — but you usually can't walk in asking for a big budget on day one.

"Take the courses like Kubernetes or GitLab — kind of low-budget courses — first of all, and prove yourself in the place where you're working. That will help to build trust with your manager to get the budget for the bigger bootcamps."

PayPal is a great company which spends a lot of time and effort in building the people.

You became a Docker Captain and an AWS Community Builder. How did that happen?

When I first started learning about Docker, I was casually looking at Nana's profile and saw the Docker Captain and AWS badges.

My honest first reaction was that it wasn't for me.

"When I first saw that badge in your profile, I thought, they are not going to give it to me, because you're too good in DevOps and Kubernetes space."

But I kept learning and sharing consistently, and at some point it stopped feeling out of reach.

"It took nearly two years for me to learn all this and implement it and share my real experience."

"During my trip, I was in Florida in Disneyland, and I got an email from the Docker team that I was awarded with the Docker Captain." 🙂

And the plan that got me there wasn't a secret:

"Basically, the plan is nothing but your bootcamp curriculum."

Editor's Note: 

We love this arc — from "this is definitely not for me" to following a concrete, reverse-engineered plan and earning one of roughly 60 Docker Captain titles in the world. 💪

The badge wasn't the goal; it was recognition for work he was already doing.

Huge congrats to Joseph! 😊

---

A personal memory Joseph shared with us 💙

"A couple of years ago, my wife applied for a role at your company and was interviewed by Nana.

During the interview, she mentioned how many of your courses I take.

Nana actually asked me to join the call to say hello face-to-face. That was a truly joyous moment for me — meeting a 'tech crush' while on a call with my wife!" 😊

---

Is it still worth learning DevOps and DevSecOps in the age of AI?

Yes — and from where I sit, it's clearer than ever.

AI still has to run somewhere.

"Infrastructure provisioning or managing the infrastructure, that is definitely not going to change. It's going to be there for a long time."

And there's a gap AI doesn't close on its own — there's no shared-responsibility model for what these tools generate.

Someone still owns the security, the access, and the infrastructure it runs on.

"Infrastructure, access and security — these three things are not going away."

Security only becomes more important as teams ship faster and experiment with AI agents.

Learning AI-specific skills on top of DevOps and DevSecOps is, in his words, "definitely going to help."

Joseph's Key Takeaways for Engineers at Any Level

✅ Learn the transferable layer, not just the tool

Tools differ between companies; the process, patterns, and reasoning stay the same. Understand those and you can adapt to any stack.

✅ Seniority is not a reason to stop learning — it's a reason to lead by learning

A Staff Cybersecurity Engineer at PayPal still went through a paid structured program. The payoff was sharper decisions and a team that trusts them.

✅ Back your decisions with trade-offs and ROI, not just diagrams

"Why this tool versus that one" earns trust from both leadership and the engineers who build it.

✅ Protect a fixed learning window

Consistency beats motivation. For Joseph that's 5:30–6:30 every morning, plus weekend deep sessions.

✅ Use employer funding — earn it with small wins first

Start with a lower-cost course, prove the value at work, then ask for the bigger budget.

✅ Prove by doing

People trust what you show, not what you say. A small POC beats a big claim.

---

Ready to become confident in

DevOps and DevSecOps?

Joseph's story is proof that structured learning isn't only for beginners. Even a senior engineer at a company like PayPal used it to make better architectural decisions, justify his tool choices with data, and lead his team with confidence.

Whether you're moving into DevOps for the first time or you're an experienced engineer who wants to deepen your skills and lead more effectively, the DevOps Bootcamp and the DevSecOps Bootcamp are built to take you there — with the concepts and reasoning that stay valuable even as the tools keep changing.

You can download the full syllabus to see exactly how the programs are structured before you start.

If Joseph kept learning at the top of his field, there's a path here for you too 😊