From Work-in-Progress to Software Engineer: Shaping My Cisco Tech Career

It All Started With a Text

It was semester break, and everyone was upskilling for the upcoming campus placement drives. One night, I was just chilling at home when a WhatsApp group chat message popped up. “Look at this! Cisco is organizing something called Code with Cisco (an event for university students to solve real-world challenges through coding). We can participate in groups of three, shall we?” Another message followed, “Be quick, the application closes at midnight!” I wasn’t ready, my resume was a total work-in-progress, I had little to no time.

I almost decided to pass on the opportunity, but my friends convinced me to try my luck. I quickly added a few Cisco Networking Academy certifications and a networking project from high school, and hit submit. I had no idea at that time that this decision would shape my career.

Carefree but Curious

Hello everyone, I am Satyajit, and my journey into tech isn’t a typical one. I didn’t get into a top-tier university, but instead, made my way through a private institution, where I took computer science, not for the status or future pay, but for the love of technology.

I lived a carefree life, pursuing hobbies, going on spontaneous trips and to concerts with friends, and binge-watching shows.

College was a cycle of deadlines and theory. I wasn’t really thinking about a career or my future until a friend landed an internship at the end of sophomore year, and I realized I was a bit behind. That all changed when that WhatsApp message popped up. My team didn’t make it to the finale, but I got an internship interview invite from Cisco.

Before the interview, I was asked to submit a version of my resume stripping away all personally identifiable information, like my name, address, college, and GPA. I had never experienced anything like it before. With any assumptions out of the way, I was able to focus on just giving my best.

Two weeks later I got a call — I GOT THE INTERNSHIP.

The Shift Begins

Walking on to the Cisco Bangalore campus was even better than I expected based on the social media posts I had seen. Then, nerves set in. “Do I know the coding language? Is my knowledge enough? What if I mess something up?” But as time went by, I met my manager, mentor, team, and fellow interns, and everything fell into place. Yes, I faced challenges. Yes, I got stuck. Yes, I stared blank at lines of code not knowing what to do. But in every step someone was there to solve my issue and tell me that it’s okay.

Things felt familiar when I returned for my spring internship, where I was lucky to continue working on the same project. I wasn’t just shadowing anymore — I was a contributor. I was answering questions, collaborating across teams, and even presenting to senior leadership. It was scary, but it was where my confidence was truly built. Thinking back, I can hardly believe that I was actually working on important things for use in real world applications.

Outside of work, we built community, whether we were watching movies in the “Box Office,” jamming in the music room, or attending exciting Accelerate (intern and early talent) events. Beyond that, I actively looked for ways to give back and stay involved, volunteering at events, speaking at pre-placement talks, and hosting campus tours for incoming interns. I even participated in a promotional video for new talent hires, representing the early-in-career experience. 

Ownership Becomes Real

Now, I am a full time software engineer. At first, things felt similar — I am on the same team, with the same manager, and even sitting at the same desk, but the stakes have changed. I am not just responsible; I am accountable, working on time-critical deliverables that affect my whole team. That realization felt scary at first, but it’s pushed me to speak up when I am stuck or don’t understand something. My new mantra is: communicate clearly and ask questions.

I also learned that taking my career seriously doesn’t mean giving up my life outside of work. I still binge-watch shows, travel, and have plenty of hobbies. I’ve learned to make work a part of my life, not a thing I have to constantly balance.

What Changed vs. What Stayed the Same

What changed most was my sense of ownership. In college, my goals were short-term — finish the assignment, pass the exam. Now, I think in terms of impact. I am more confident in speaking up, making calls, and understanding how my technical choices tie back to real business outcomes.

What hasn’t changed is the core of who I am. I’m still curious, still learning. Growth added responsibility, but I didn’t lose myself.

Take the Leap

One thing I learnt at Cisco is that growing doesn’t mean that I have to be a different person. Programs like Code with Cisco gave me an opportunity to start my tech career. Now that I’m at Cisco, the culture — where everyone is heard, mentorship is standard, and you are trusted with important work, no matter your level — shaped me professionally.

If you are wondering if you should take the leap, do it. Cisco isn’t looking for the perfect resume; it’s looking for the person and their potential.

Are you ready to take the leap? Explore open roles on our career site.

Subscribe to the WeAreCisco Blog.