3,67,38,973 lines of code. One day. Written by people who came in with curiosity and left with something they actually built.

That number isn’t a flex. It’s a question worth sitting with. What changes when you give people the right tools, a real problem, and the freedom to figure it out?

Sarjan was Amnex’s attempt to find out.

सर्जन — Sanskrit for creation. Our first in-house AI-powered hackathon. One day, one real-world challenge, and an open door for every person in the company to walk through. No filters. No prerequisites. Just: show up and build.

The Day AI Stopped Being a Buzzword

292 people registered. 62 teams formed. And on the day itself, something interesting happened.

People stopped waiting.

A team that had never worked together before skipped the awkward warm-up and went straight to building. Someone from operations, no coding background, no prior AI experience, opened a prompt window and started. A group that had never touched the technology they were about to use decided that was a problem they’d solve on the way.

AI made that possible, not by doing the work for them, but by removing the walls that usually slow people down. It wrote the boilerplate. It suggested architecture. It answered the questions that would have cost an hour of Googling in thirty seconds. It turned “I don’t know how to do this” into “let me try this and see.”

By the time the day closed, 2,197 commits. 3,67,38,973 lines of code.

Not written by a team of engineers running at full capacity. Written by accountants, testers, designers, analysts, and developers, many of whom were using AI as a serious building tool for the very first time.

What the Leaderboard Actually Measured

When the submissions came in, the leaderboard didn’t rank by who looked most impressive in a room.

It measured code quality, AI usage, usability, and FRS quality. In other words, did it work, was it built well, and did the team actually use AI as a meaningful part of how they got there?

That last part mattered. Because Sarjan wasn’t just asking people to build fast. It was asking them to build differently. To treat AI not as a novelty but as a collaborator. The teams that understood that early moved in ways the others couldn’t keep up with.

The Jury Round

The shortlisted teams then walked into something harder than a leaderboard.

A jury drawn from Amnex’s leadership sat through every presentation. They used the products. They questioned the decisions. They pushed on the thinking behind the build, not just the build itself. Some teams were validated. Some were challenged in ways they didn’t expect. Every single one of them left with something they didn’t have walking in.

That’s the part that doesn’t show up in the commit count.

The Leadership’s Vision for What Comes Next

On the day of the winner announcement, the full company came together.

And before the results, leadership said something worth repeating.

AI is not coming. It’s here. And the question is no longer whether it will change how work gets done. At Amnex, the answer is clear. We are building a workforce that doesn’t wait for AI to be handed to them in a polished tool. We want people who can think with it, build with it, and use it to do things that would have been impossible the day before.

Sarjan made the case in a way no meeting, no presentation, and no strategy document ever could.

The Moment Everyone Waited For

Five teams were called to the stage. And what followed wasn’t just a prize ceremony. It was a full circle moment. Every person sitting in that auditorium had shown up, figured it out, and shipped something that didn’t exist the night before. The recognition went to five teams. But the proof belonged to all participants.

A Shift That Doesn’t Stop Here

Sarjan answered a question Amnex had been quietly asking. Not whether our people could work with AI, but how far they could go when they actually did.

Amnex heard the answer loud and clear. AI fluency is the direction. The speed, the quality, and the ambition shown at Sarjan are now the benchmark for what’s possible in our actual projects. And the creative freedom that made it happen? There’s more of that coming.

One day proved it. The rest is execution.

That’s not a celebration. That’s a culture of creation.