The Engineer Guide, Part 2: My First Hackathon Adventure Revealed

If you didn't read Part 1 of the Engineer Guide, go read it! this is Part 2, for God's sake.

How a Random Conversation Changed Everything

Back during my university years, I used to participate in various activities at the Faculty of Letters and Humanities in Marrakech, especially those related to cultural dialogue, languages, and Japanese culture (which I'm an absolute fan of). I built quite a circle there, connecting with people from different ethnicities and study fields.

One day, I was talking with a stranger, a girl from the English department, and she asked me about Jupiter. Was it really the biggest planet in our solar system? And did Flat Earthers have any common sense in their reptile brains?

I felt like I'd been waiting my whole life for these questions. She poked the nerd in me, and I spent hours explaining the entire solar system, how gravity works, and how Jupiter, the gas giant, is essentially defending our beloved Earth from gigantic comets hurtling through space.

A few weeks later, I was surprised when that same girl called me. "Remember our talk about the planets? I got an amazing opportunity for you, don't miss it." She shared a subscription form link for the Space Apps Challenge, the world's biggest hackathon organized by NASA.

I was impressed, but also confused. At that time, I didn't even know what the word "Hackathon" meant. So naturally, I Googled it. Don't worry, I've been there.

What's a Hackathon, Anyway?

A Hackathon (the word comes from "hack" + "marathon") is an event, usually lasting 24 to 48 hours, where people come together to collaborate intensely on creative projects, typically related to technology, software development, or problem-solving. Think of it as a creative sprint where teams brainstorm, build prototypes, and pitch solutions to real world challenges within a tight deadline. It's not just for coders; designers, engineers, business minds, and creatives all participate. The goal? Innovation under pressure, networking, and sometimes, winning prizes.

The Terrible Timing

That time, God, I was drowning in midterm exams. But I told myself: I can catch up on exams, but not on a once in a lifetime opportunity. So I jumped on it.

A few days later, I received my official invitation to the hackathon along with my hotel reservation. Hooray, I got accepted! I can't lie, I was anxious. Especially since I chose to work on a complicated subject by myself. I had no teammates to back me up.

But let me assure you: in hackathons, you don't need to be Einstein, and you don't need the best team to participate. The purpose isn't even to win. What's truly valuable is the interesting people you'll meet, the friendships you'll build, the future opportunities you'll incubate, and most importantly, dedicating all your grey matter for a continuous 48 hours to make an impact in this world.

That said, I can't deny that participating with a team you get along with could balance the game in your favor.

Day Zero: Ice Breakers and Social Anxiety

Once there, all the participants gathered for an icebreaker session. The organizing team paired me with people who chose to work on the same problem, then told us to get enough sleep because the next day would be draining.

Spoiler: nobody got enough sleep.

Day One: Meeting NASA's Elite (and Astronaut Ice Cream)

We started the next morning with an opening speech from Dr. Deborah Barnhart, the U.S. Space and Rocket Center CEO and Executive Director herself. I still remember the social anxiety that hit me when her eye contact matched mine, and she asked me to come to the stage to introduce myself and explain what I do in life.

That was an awkwardly embarrassing moment that somehow turned amazing when she rewarded me with astronaut ice cream, a token for my courage. (Yes, astronaut ice cream is real, and yes, it tastes exactly like you'd expect freeze dried nostalgia to taste.)

Then we were introduced to our mentors: experts and professors from various fields, including (wait for it) video game developers. Yes, you heard me right. NASA isn't just looking for ways to build rovers and send people to the International Space Station. They're also very interested in promoting their brand and vision, and what's better for that than video games?

These mentors stayed with us throughout the hackathon, offering counsel and workshops. We also got access to NASA databases, software licenses, and fablabs to develop our ideas accurately.

A Critical Tip: Network Like Your Future Depends on It (Because It Does)

Here's something important I want to highlight: don't work on the problem nonstop without breaks. Take time to network with the mentors. You might not get this opportunity twice, and these people are gold mines who could teach you something life-changing or inspire you in ways you can't predict.

If you're the extroverted type and can ask for their social media or find a way to stay in touch, go ahead, that's even better.

And don't forget the other participants. They come from different disciplines: students, artists, engineers, designers. There are millions of ways you can learn from them and turn them into allies. Remember, the hackathon isn't just about solving the challenge you're assigned. Take it as an opportunity to network and expand your knowledge.

The Challenge: Building a Lunar Robot in 48 Hours

My team members were all skilled, but we were completely disorganized. It's not easy to work with new people from day one, but somehow we managed to split the tasks based on each person's field of expertise.

Our challenge? Develop a prototype of a lunar robot using machine learning concepts for collecting samples, dividing them, and making the necessary in-situ characterizations, all in less than 48 hours before sharing data with astronauts on the nearest space station.

We made a virtual prototype and a physical model of our robot. We pulled all-nighters. We debated. We problem-solved. We thought we had something solid.

But guess what? We failed. Badly.

Why We Failed, And What I Learned From It

Here's why we crashed and burned: we didn't give enough time or importance to the presentation and pitch. English was our third language, which added another layer of difficulty. And when we finally got on stage, everything fell apart.

The person we trusted with the presentation forgot literally everything. Another teammate, stressed out of his mind, started being hilarious to hide his public speaking fear. As for me? Just speaking into a microphone in a room full of people was a massive challenge.

We had a solid solution, but we couldn't communicate it effectively. And in the real world, that's often what matters most.

A "Successful Failure"

I'd call it a "successful failure," just like NASA's Apollo 13 mission. Apollo 13 never completed its lunar landing, an oxygen tank exploded mid-flight, turning the mission into a survival challenge. But it became one of NASA's most celebrated missions because the team demonstrated incredible problem-solving, resilience, and creativity under pressure. They brought the astronauts home safely against all odds, turning disaster into triumph.

Similarly, my hackathon experience didn't result in a win, but it gave me something far more valuable: lessons, confidence, and the foundation for my second hackathon, which went much better and deserves its own dedicated post.

The winners, by the way, got tickets to participate in a wider hackathon in the USA, including a two person visit to NASA Headquarters. Worth the trouble, right?

The Aftermath: Exhaustion and Exams

At the end, I made sure to congratulate the winners and collected contacts from participants and the organizing committee. Those connections proved beneficial later on.

After two nights without sleep, I returned home dog-tired and woke up with two exams looming over me. Somehow, I managed to pass both.

Key Takeaways

1. Meaningful Conversations Lead to Unexpected Opportunities

That random discussion about Jupiter opened a door I didn't even know existed. Never underestimate casual conversations, they might lead to life-changing opportunities.

2. Some Opportunities Are Worth the Risk

Failing an exam or two isn't the end of the world. Some experiences could fundamentally change your life and the way you think. That's why we should dare to try new things, even when the timing seems terrible.

3. Networking Pays Off in Unexpected Ways

Keeping in touch with some participants and organizers later got me the amazing experience of meeting an astronaut in person. Your network is your net worth, as they say.

4. Video Games Aren't Just Entertainment

I got inspired by the importance of the video game industry. I stopped seeing games only as entertainment and started viewing them as legitimate business and communication tools. My recent participation in another hackathon involved developing a mock-up game that got me to the finals. Would I have known how to do that without the Space Apps Challenge? Absolutely not.

5. Public Speaking and Presentation Skills Are as Important as Technical Skills

I gained more confidence in speaking publicly and improved my spoken English. I understood the importance of storytelling when interacting with the jury. Preparing neat, compelling slides is just as important as solving the problem itself.

6. Adaptability Is a Superpower

I developed the skill of adapting quickly and working effectively in a new team under pressure. This skill has been invaluable in every professional setting since.

7. Failure Teaches More Than Success

Losing taught me what not to do next time. It forced me to confront my weaknesses (public speaking, presentation skills, team coordination) and work on them deliberately.

8. Sleep Deprivation Builds Character (Sort Of)

Okay, maybe don't make this a habit, but learning to function and problem-solve under extreme exhaustion is something engineers face regularly in the real world. Consider it training.

Final Thoughts

That first hackathon didn't give me a trophy or a trip to NASA Headquarters, but it gave me something better: clarity about my weaknesses, proof of my strengths, and a burning desire to do better next time.

If you're an engineer (or aspiring to be one), this is obvious advice. But honestly? This applies to anyone, artists, writers, business minds, whoever you are. Find a hackathon and participate. Even if you fail spectacularly. Especially if you fail spectacularly. The lessons you'll learn and the people you'll meet are worth infinitely more than any prize.

And who knows? A random conversation about planets might just change your life too.

Part 3 is coming… eventually. Stay tuned, and don't forget to subscribe to my newsletters if you haven't already. Seriously, what are you waiting for?