Anjali Rambhad

From My First Hackathon to an Internship at Mastercard: My Journey Through the Code for Change Hackathon

When I signed up for the Code for Change Hackathon last year, I had no idea it would lead to an internship at Mastercard. What made it even more special? It was my very first hackathon. I was extremely excited—and yes, a little nervous. But I didn’t want to go in unprepared, so I began my preparations a week in advance. Looking back, that decision made all the difference.

The First Hurdle: DSA Round

Before the actual hackathon began, we had a DSA (Data Structures & Algorithms) round with two medium-level questions—one based on trees and the other on graphs. Thankfully, I was able to solve both. Although the second problem had a couple of tricky test cases I couldn’t pass, I managed to crack most of them.

Here’s what I learned: Consistency in DSA is non-negotiable. I’m not a DSA expert, and I still struggle with many LeetCode problems. But I try to solve 1–2 questions every day. You can't master DSA in a week or even a month—it’s a long-term game. Keep at it, and you'll see the benefits.

Preparing for the Hackathon

One of the most common mistakes participants make is going into hackathons unprepared. No matter how proficient you are in development, AI/ML, or any other domain, take some time to revise your core concepts. Whether it's Java, React, Node.js, or machine learning—make sure you understand the foundations.

Our hackathon started early—at 6 AM—and we made sure to reach before time. Since all my teammates were from different colleges, we were meeting for the first time. Most of them were shy and introverted. That’s when it hit me: a hackathon is a team effort. It doesn't matter how skilled you are—unless you work with your team, you won’t be able to perform your best.

Breaking the Ice: Teamwork First

One of the first things I focused on was breaking the ice. I encouraged everyone to talk openly and share their ideas. Creating a comfortable and collaborative environment is crucial because planning is the most important phase of any hackathon. Clear communication ensures everyone is on the same page.

Don’t jump into coding right away. Instead, spend time deciding the tech stack, system architecture, and most importantly, clarifying each member's role. Equal involvement and early planning can save hours of confusion later on.

Building + Presenting = Winning

Here’s a reality check: What you make and what you present can be completely different. In our case, the backend wasn’t functioning perfectly, but we didn’t let that pull us down. We focused on building a clean and well-structured frontend, ensuring the UI/UX was polished and intuitive.

Adding small, out-of-the-box features can really impress the judges. Focus on the problem statement, but don’t hesitate to go a step further.

And remember—if there’s a mentor or leader assigned to your group, listen to their suggestions and try to implement them. They often have a broader perspective and can guide you in the right direction.

Lastly, take initiatives wherever you can. Whether it’s leading discussions, designing mockups, or presenting the final pitch—show ownership. It not only helps the team but also leaves a strong impression on mentors and judges alike.

Key Takeaways:

1. Participate in as many hackathons as possible. They help you think on your feet and improve logical and critical thinking.
2. Consistency is key in DSA. Even one question a day makes a difference.
3. Hackathons are team events. You can’t win alone—collaboration is the real superpower.
4. What you present matters as much as what you build. Make your demo count.
5. Early and clear communication is essential to avoid confusion later.
6. Take initiative and be proactive. It reflects both leadership and enthusiasm.