If someone had told me a few years ago that I’d be working in cybersecurity at Microsoft, I probably wouldn’t have believed them. My path wasn’t straightforward or glamorous—it was messy, full of late nights small wins, rejections, and unexpected turns. But every step, from writing code at TCS to triaging bugs at HackerOne, added up and eventually brought me here.

This blog is my attempt to share the story behind that journey—what it’s really like, the things people don’t see, and the lessons that helped me along the way.

You might be on a journey similar to mine—dreaming of breaking into the world of cybersecurity and landing a role at your dream company. Through this blog, I want to share my experiences, lessons, and the challenges I faced so that freshers and aspiring professionals in infosec can find guidance, avoid common mistakes, and feel a little less alone in the process. If you’re just starting out, I hope my story helps you shape your own path and gives you the confidence to keep moving forward.

When people hear I landed at Microsoft, they usually think of the shiny part. What they don’t see are the hours I spent after work brushing up on fundamentals, or the number of interviews I didn’t crack.

There were moments of imposter syndrome and doubts about whether I was good enough. But those quiet struggles were just as important as the visible milestones. They taught me resilience and discipline, which, honestly, mattered as much as technical skills.

How It Feels to Work in Security at Microsoft

From the outside, working at Microsoft feels like a dream: cutting-edge technology, a massive impact, and some of the brightest minds in the field. And yes, it’s all of that. But what I’ve realized is that it’s not just about “hacking cool stuff.”

A lot of my day is about collaboration, design discussions, reviewing processes, and enabling developers to ship products securely. Security here isn’t just about breaking—it’s about building trust. That responsibility feels big, but it’s also incredibly motivating.

How my career progression helped me

If I had to pick one word that defined my journey, it would be exposure.

At TCS, I got exposed to development. I learned how products are built, why deadlines matter, and how developers think.I had done multiple dev projects in my college but a corporate experience with dev did add a real value. It gave me empathy for engineers. I started to understand why certain security fixes feel “hard” from their side, and why balancing functionality and safety is tricky. That mindset has been invaluable in my security career. It gives you a lot of perspective that now help me connect better with engineers when discussing security issues.

At HackerOne, the exposure was different—it was raw, fast, and very real. Triage meant I was looking at hundreds of vulnerability reports, reproducing them, figuring out impact, severity and communicating with both researchers and clients. Imagine dealing with bugs on criical customer’s platforms—it was high pressure, intense, and at times overwhelming, but it taught me speed, precision, and perspective, different techniques to approach a bug.

That combination—building systems and breaking them—became the foundation for my next leap.

The Microsoft Interview Experience

I can’t dive into every tiny detail, but here’s a look at my overall experience going through the Microsoft interview process.

Interviewing at Microsoft was nerve-wracking. I had my share of “what if I mess this up?” moments. The process tested me on fundamentals, problem-solving, and how I’d approach real-world scenarios.

Some rounds felt smooth, others left me replaying answers in my head for days. But what stood out was that it wasn’t just about “can you exploit this vulnerability?” It was about how I think—how I’d secure a system, how I’d balance risks, how I’d work with others.

Walking out of those interviews, I realized something: preparing only for technical questions isn’t enough. You need to prepare to think like a security engineer at scale.

The Team

When I joined my team, the first thing I noticed was how diverse everyone’s strengths were. Some were experts in cloud, others in offensive techniques, some in automation or product security. No one pretended to know everything.

The best part? The openness. People share, teach, and learn from each other. Coming from environments where knowledge was sometimes siloed, this was refreshing. It makes you feel less like “the new person” and more like part of a collective brain.

The Culture

Coming from a company like HackerOne, I realized early on that culture was something I couldn’t compromise on. The way a company treats its employees, encourages growth, and fosters collaboration matters just as much as the work itself. When I joined Microsoft, I was pleasantly surprised—its culture has truly been at par with, and in many ways even exceeded, my expectations.

From day one, I felt welcomed and supported. There’s a genuine emphasis on work-life balance, learning, and open communication. People are approachable, mentorship is encouraged, and knowledge-sharing isn’t just a buzzword—it’s practiced every day. I’ve loved being part of an environment where your contributions are valued, your growth is prioritized, and the culture genuinely feels employee-friendly. It makes showing up to work exciting, not just because of the projects, but because of the people and environment around you.

The Perks

One of the things I absolutely love about working at Microsoft are the perks that make everyday life so much better. The campus itself is designed to keep you inspired, with collaborative spaces, wellness programs, and flexibility that really helps with work-life balance. But if I had to pick a favorite, it would definitely be the food. The cafeterias offer an incredible variety—everything from healthy options to comfort food—and it feels like you’re spoiled for choice every single day. It may sound small, but great food and thoughtful perks really do make a difference in creating an environment where you look forward to coming to work.
Here are few pics from my gallery.

On a lighter note, I also picked up a new hobby at Microsoft—Table Tennis—which has quickly become one of my favorite ways to unwind and recharge between work sessions!

What I’ve Learned So Far

Some lessons stand out from this journey:

• Communication matters. Finding a bug is only step one. Explaining it clearly and helping fix it is where you create real value.
• You’ll never be “done.” The learning curve never flattens. And that’s a good thing.
• Security is about enabling. The best security folks don’t just block—they help teams ship safely.

For Anyone Wanting to Land a Security Role at Microsoft

I often hear from college students and freshers asking me how I made the jump from being a developer to working in security. I thought this section would be the perfect place to share my story.

When I was a developer, I never really let go of security. I worked on side projects that kept my security knowledge sharp, and whenever I developed a feature, I’d naturally look at it from a security perspective—even though nobody at my job ever asked me to. I also submitted papers to security conferences and built connections with people who had 10–15 years of experience in the field. Most of this happened because I made it a point to attend security meetups and conferences, meeting people face-to-face.

I know a lot of students think breaking into security as a fresher is almost impossible—and honestly, I get it. The job market is tough. Freshers openings are limited, and companies often look for a certain level of corporate experience or certifications.

But here’s one pathway that worked for me, and I think it can help anyone feeling stuck.

If you enjoy building things or have a development background, start by getting into a company via a development role. Work there for some time, but keep one eye on security. Try to find opportunities for an internal switch into a security team. Alongside, keep your “side hustle” alive—do bug bounties, CTFs, or labs on platforms like HTB. This way, you build experience in both worlds: development and security. Eventually, that combination can open doors to core security roles and help you land at your dream companies.

If you’re on this journey too, here’s what I’d say:

• Build strong fundamentals in OS, networking, cloud, and web security.
• Get practical exposure—bug bounties, labs, side projects, whatever works for you.
• Learn to think like a developer, not just a hacker.
• Practice communicating clearly. You’ll need it every day.
• Prepare for interviews with scenarios, not just technical trivia.
• Put yourself out there—blog, contribute, connect.
• And most importantly: be patient. It might take multiple tries, but every attempt builds you up.

Wrapping Up

For me, this journey wasn’t about one “big break.” It was about all the small steps: coding at TCS, triaging at HackerOne, late-night study sessions, failed interviews, and countless learnings along the way.

Landing at Microsoft is a milestone I’m proud of, but what I value more is the process it took to get here. If you’re chasing the same dream, my only advice is—keep at it. Focus on learning, building, and enjoying the journey. The rest will follow!!

That’s all for this post. See you in the next one. Until then, keep striving!!