JPMorganChase Code for Good 2024: Hackathon Experience

Reflections from 24 hours that shaped how I think about technology and impact

Receiving the JPMorgan Chase Code for Good 2024 selection email was one of those moments that immediately shifts your perspective on what’s possible. As a second-year Computer Engineering student at Thapar Institute of Engineering & Technology, I found myself selected for an experience that would fundamentally change how I approach problem-solving and collaboration.

The challenge? I had been working primarily in Python and machine learning, but the available team positions were focused on web development. Two weeks to bridge that gap.

Strategic Learning Under Pressure

When faced with a significant skill gap and limited time, I approached the challenge systematically. Rather than attempting to master everything, I focused on hands-on project building, starting with foundational concepts and progressively increasing complexity. This approach taught me something valuable about rapid skill acquisition — practical application accelerates learning far more effectively than theoretical study alone.

During this period, I discovered an affinity for backend development that I hadn’t expected. Sometimes our most valuable discoveries happen when we’re pushed beyond our initial comfort zones.

Learning tip: When acquiring new skills under time pressure, prioritize building over reading. Start with the simplest possible project and iterate upward — you’ll retain knowledge better and identify knowledge gaps faster than through tutorials alone.

The Challenge

The hackathon environment in Mumbai was exceptional — hundreds of motivated students, experienced industry mentors, and NGOs presenting genuine challenges that required thoughtful solutions. Our team partnered with Vowels of the People Association (VOPA), a Maharashtra-based organization that has already reached 3 million users through their digital learning platform.

Their challenge involved developing a speech analysis system for educational assessment in rural areas — a project that would help identify where educational resources could be most effectively deployed.

Interestingly, this pivot brought us back to NLP and speech recognition, areas where I had some existing expertise. That’s where the real thrill of hackathons lies — you don’t show up with a predetermined syllabus, which forces you to think on your feet and adapt your technical approach in real-time. The preparation I’d done in web development wasn’t wasted though — it provided valuable context for understanding how different technical components integrate within larger systems, and gave me the confidence to support other team members too.

The Execution

One of the most valuable aspects of the experience was learning to facilitate productive collaboration among team members with diverse backgrounds and perspectives. Those initial hours required careful navigation — everyone brought valid viewpoints about our approach, and aligning the team on priorities and deliverables was something we focused on getting right.

The key breakthrough came when we established clear task ownership based on individual strengths while maintaining regular check-ins to ensure alignment and address blockers proactively. I took responsibility for the Speech Recognition and NLP integration components, areas where I could contribute most effectively while supporting overall team objectives.

Pro tip: Establish component ownership early in any collaborative project. This creates clear accountability, reduces overlap, and allows team members to take initiative within their areas of expertise — a critical attribute in successful software development.

Our mentors provided exceptional guidance throughout the process. They consistently challenged us to evaluate whether our solutions addressed real user needs rather than just demonstrating technical capability. This perspective fundamentally shaped our development approach — we weren’t building for demonstration purposes, but creating tools that could genuinely impact educational outcomes for children in rural communities.

Key insight: Always validate that you’re solving the right problem, not just building impressive technology. The most elegant solution is worthless if it doesn’t address genuine user needs or stakeholder requirements.

Leading Through Challenges

The most intensive phase occurred during the late-night development cycles. This is where effective team management becomes critical — maintaining clear communication, managing energy levels, and keeping everyone focused on deliverable outcomes while working through complex technical challenges.

These sessions taught me significant lessons about persistence, collaborative problem-solving, and the importance of maintaining team morale during high-pressure situations. When technical obstacles arise at 3 AM, success depends more on team cohesion and shared commitment than individual technical prowess.

Recommendation: During intense development phases, schedule regular team check-ins even when everyone is heads-down coding. A quick 10-minute sync every few hours prevents integration nightmares and keeps everyone aligned on priorities.

Presenting with Impact

Phew, we finally reached the presentation prep stage where we focused on leveraging each team member’s expertise areas while maintaining a cohesive narrative about social impact. Despite considerable fatigue, we ensured our demonstration clearly articulated how our solution would integrate with VOPA’s existing programs and create measurable improvements in educational assessment processes.

The judges engaged meaningfully with our approach and asked thoughtful questions about scalability and implementation considerations. While we didn’t secure the overall hackathon victory, the experience provided valuable insights into presenting technical solutions to diverse stakeholder groups.

The Offer!

Several weeks after the hackathon, I received an offer for JPMorgan Chase’s Software Engineering Program internship. This outcome reflected the comprehensive evaluation approach they employ — assessing individual contributions, communication effectiveness, adaptability, and collaborative impact rather than solely team performance.

The experience reinforced several key insights about professional development: maintaining clear communication under pressure, contributing constructively to team discussions, demonstrating learning agility when circumstances change, and consistently focusing on outcomes that create genuine value for end users.

My Perspective on the Experience

The atmosphere throughout Code for Good was remarkable — an environment where learning, innovation, and social impact intersected naturally. Working directly with industry professionals and NGO leaders provided insights into real-world deployment challenges that academic environments rarely address.

The experience reinforced that professional growth happens most effectively when we embrace challenges that push us beyond our current capabilities. Sometimes the best preparation is simply showing up ready to learn, contribute, and build something meaningful alongside talented people who share your commitment to positive impact.

The connections formed, problems tackled, and lessons learned during those 24 hours continue to influence how I approach challenges and opportunities. That’s the real value of experiences like Code for Good — they don’t just develop technical skills, they shape how you think about technology’s role in creating positive change.

Always interested in connecting with fellow technologists focused on building impactful solutions. Feel free to reach out to discuss innovation, leadership, or social impact technology.