A story about a hackathon, a misunderstanding, and the day I confused product thinking with ego.
I thought I'd missed the Top 10. In the span of five minutes, panic turned into ego, and I confused product thinking with tearing down someone else's work. This is the story of how that happened.
There is a specific kind of arrogance that sets in when you are a 3rd-year computer science student who has just spent a summer building software for real businesses. You start to think you have it all figured out.
When I walked into a hackathon hosted by a prominent tech startup, I felt terrified, but also dangerously confident. The room was packed with around 50 of the strongest technical 4th-year students, and only four 3rd-years had made the cut. But having just spent three months building enterprise pipelines and presenting technical architectures to corporate leadership, I felt like I knew how to build, and I knew how to pitch.
Over the next 48 hours, I learned a brutal truth: technical brilliance isn't enough if you lack the maturity, self-awareness, and professional empathy to work with other people.
We had eight hours to produce a working, full-stack prototype tackling one of three specific user problem statements.
I spent the first 90 minutes just staring at the prompts. I realized two of the problems required deep internal context about the startup's actual product to solve correctly. But the remaining prompt was a pure UX and workflow challenge: designing a solution for a high-volume power user drowning in hundreds of files under extreme time pressure, someone who would abandon a tool the moment it slowed them down.
I immediately knew how I wanted to approach it. During my internship, I'd watched professionals navigate massive enterprise tools with incredible speed, their hands rarely leaving the keyboard. In high-volume data work, every second spent reaching for a mouse is a bottleneck. With that in mind, I decided to build a keyboard-first frontend, entirely navigable via rapid keystrokes.
More importantly, the startup's product ran strictly locally to ensure data privacy. To match that, I paired a Next.js frontend with a Python sidecar, a backend pattern I had never deployed before. To ensure it ran offline like native software, I used Electron to bundle the stack into a standalone .exe application. The gamble on an unfamiliar sidecar architecture paid off. By 6:00 PM, my submission was locked in.
But the night was far from over. With college assignments to catch up on and hackathon rules allowing code refinements until morning, I stayed up polishing the application until 3:00 AM. I finally collapsed into bed completely exhausted and dangerously sleep-deprived.
The next morning, we were told only the Top 10 finalists would get to present their projects to the crowd.
Right before presentations began, I slipped into the hallway to ask Revanth anna, a trusted senior who had helped recommend me, if I had made the cut. Between the noise and the rush, a simple miscommunication happened, and I completely misunderstood his answer. Blinded by the panic of the moment, I walked back into the hall utterly convinced my project had been rejected.
My confidence flatlined. But instead of accepting it gracefully, my exhausted, sleep-deprived brain went into a desperate, self-destructive survival mode. I felt hopeless, but my ego couldn't bear the thought of the judges never knowing what I had built. I made a terrible decision: If they won't let me present on stage, I am going to force them to hear about my project from the audience.
A brilliant 4th-year student took the stage, tackling the exact same problem statement I had. I saw my opportunity to use her pitch as my own backdoor presentation. I opened a notepad on my laptop and aggressively started hunting for flaws: weird keybindings, missing anonymization constraints, anything I could use as leverage to announce my own features.
When the floor opened for questions, I took the mic.
I didn't ask a question. I stood up in front of the entire room, peers, industry professionals, and the faculty who had vouched for me, and ruthlessly criticized her product.
I looked at a peer who had worked incredibly hard and said, "My product has those features, and yours doesn't." I ended my tirade with a condescending "These things might be improved."
Even while I was speaking, part of me believed I was demonstrating product thinking. In reality, everyone else simply saw someone trying to score points at another student's expense.
I handed the mic back. The presenter stood on stage, completely blindsided.
The second the mic left my hand, the adrenaline crashed. I hadn't sounded smart or superior. I had just ruined the vibe of the entire event.
After the next presentation, the founder took the mic. She looked directly into my eyes, smiled politely, and gently reminded the room to keep things strictly to questions. Her intention was crystal clear. She was talking directly to me.
I was mortified. And then, the absolute worst-case scenario happened. The founder called the 9th presenter to the stage and announced who was on deck for the final spot:
"Lohit, you're our 10th presenter. Be ready to go next."
I froze. I had made the Top 10. And I had just made a complete fool of myself right before my turn.
I walked up to the stage shivering. I connected my laptop, took a breath, and started my presentation by publicly apologizing for my behavior. I admitted I had crossed a line. An uncomfortable, heavy silence hung over the room; the startup's team simply nodded, their expressions seemed to say, Just do your pitch and get off the stage. Whether or not they felt that way, that's how it felt to me.
It ended up being a decent presentation, but knowing what I am capable of, I knew I could have delivered it twice as well if I hadn't been so rattled. The moment I finished, I bolted out of the hall.
I walked to the corner of the building and stood motionless for thirty seconds. I couldn't decide whether I wanted to disappear or rewind the last five minutes. I splashed freezing cold water on my face, letting the immense weight of my regret wash over me. In my desperate attempt to force my hard work into the spotlight from the audience, I ruined my actual moment on the stage. If I had just kept my mouth shut, I could have enjoyed the moment instead of spending it ashamed.
When I finally walked back in, the results were being announced. The student I had criticized rightfully took third place.
I spent the next week in a depressed, sleep-deprived haze. I was convinced I had permanently destroyed my reputation and humiliated the professors who stuck their necks out to recommend me.
When I finally spoke to Professor Vedaj, my primary college mentor and the faculty member who had officially recommended me for the event, he didn't just scold me; he analyzed me. He pointed out that my issue wasn't just ego; it was emotional regulation. When I get stressed or emotional, I lose my filter. It was a harsh truth, but it made complete sense.
A few days later, I texted Revanth anna to apologize for embarrassing him. I expected him to be furious.
Instead, he laughed it off and gave me the best advice of my early career. At the end of the day, he was a well-wisher looking out for me. He knew the air was already cleared, but he wanted to make sure I took the right lesson away from the crash. More importantly, he told me this:
"When will you learn if you don't mess up? I would say mess up more and faster, you'll evolve sooner."
This hackathon taught me a brutal but necessary lesson about engineering that has nothing to do with code. You can write the cleanest architecture in the world, but building great software isn't just about out-coding the person next to you. It's about empathy, collaboration, emotional regulation, and knowing when to keep your ego in check.
Two pieces of advice from that week will stay with me for the rest of my career: master your emotional regulation and have the humility to mess up faster. Not because mistakes are desirable, but because if you're willing to own them completely, they stop being permanent parts of your identity and start becoming part of your education.
(If you're curious about the technical side of the story, you can explore the complete source code and architecture on GitHub: https://github.com/zappvik/sprintfour-hack)