The concept of hackathons is well-established and has proven to be very popular among tech enthusiasts across India. These intensive two or three-day events bring people together who are passionate about technology to work on software-related challenges, often provided by sponsor companies.

For companies, hackathons serve multiple purposes: they help identify promising talent, test new ideas, and sometimes even build prototypes that evolve into real products. For participants, they offer hands-on experience, networking opportunities, and direct exposure to how product companies think.

But as interest in technology careers grows among women across India's engineering colleges, the traditional hackathon format presents some challenges worth addressing.

ScriptedByHer was Meesho's answer to that. A women-only hackathon, but not the kind built around inspiration and participation certificates. Built around real engineering challenges, serious stakes, and the kind of mentorship that actually changes how someone thinks about building products.

Designing a Talent Funnel, Not Just a Hackathon

What made ScriptedByHer different was the clarity behind its design.

We were not looking to solve a surface-level problem built around visibility alone. We wanted to address something deeper: how do we identify strong engineering talent before traditional hiring systems narrow the pipeline too early?

The women-only format was a deliberate call, but it isn't the most important thing about ScriptedByHer. It was a condition that made everything else possible.

Competitive hackathons tend to attract participants who already have hackathon experience. That sounds circular because it is. Engineers who have competed before know what to expect, how to scope a problem, how to pitch under pressure, and how to pace a sprint. First-timers, regardless of ability, often don't make it past early rounds simply because the environment is unfamiliar.

What remained was a straightforward question: who can actually solve hard problems under real conditions?

That distinction mattered.

Because ScriptedByHer was never designed to identify students who were simply good at competitions. We were looking for engineers capable of thinking through ambiguity the way real product teams do every day.

Round One: Skip the Resume

Most hiring processes start with a filter that has nothing to do with ability. College name, internship history, extracurriculars, the usual signals. ScriptedByHer started differently.

The first stage was a coding assessment, full stop. Machine coding, data structures, and algorithmic problem-solving, all under timed conditions. No resume screening came before it. No institute filter. No pedigree shortcut.

This matters more than it might seem. A large chunk of strong engineering talent in India comes from colleges that rarely appear on a recruiter's radar. Those engineers don't always get early visibility, and that shapes how careers begin. Starting with a clean technical filter gives everyone the same shot and surfaces people who might otherwise have been quietly passed over.

Only participants who demonstrated real technical depth moved on.

Round Two: Build for Problems That Actually Exist

Shortlisted participants were given two themes to work within: Building for Bharat and Generative AI.

The choice of themes was deliberate.

Building for Bharat meant grappling with what it actually takes to build products for India at scale. Limited connectivity. First-generation internet users. Regional languages. Affordability as a hard requirement. These aren't hypothetical design constraints; they're the real conditions that hundreds of millions of Indian users live with every day.

A solution that works beautifully for someone in Bengaluru with a fast connection and a premium phone isn't a solution for the user this theme asked participants to think about. Recognising that gap and designing around it is a specific kind of maturity that not every engineer has developed yet. This theme was tested for it.

Generative AI asked a different kind of question. Not just "what can you build with AI?" — that bar is easy to clear with an impressive demo. The harder question was: what problem does this actually solve, and can you explain why clearly? Knowing the difference between a slick prototype and a genuinely useful product is a skill in itself. This theme tested whether participants could make that distinction.

The Part That Made It Different: Mentorship During the Build

After shortlisting, participants got access to Meesho's engineering leaders. Not just at the end as judges scoring a final pitch, but during the build itself.

This shifted the experience significantly.

In most academic settings, a good idea is one that's technically sound and well-presented. In a real product environment, a good idea is one that survives contact with actual constraints: scale, user behaviour, engineering trade-offs, timelines. Most engineers don't encounter that kind of pressure until they're already on the job, and adjusting to it takes time.

ScriptedByHer brought that pressure into the hackathon itself.

Meesho's mentors didn't observe passively. They asked hard questions and challenged assumptions. They pushed teams to explain why their approach would work for the user they were actually building for, not the idealised version they had in their heads.

Some teams found mid-sprint that their core idea didn't hold up. Others discovered that a simpler, more grounded version of their idea was far stronger. One participant put it plainly: "We stopped thinking in terms of perfect answers and started thinking in terms of real constraints."

That shift, from academic correctness to product-world practicality, is exactly what separates engineers who are ready to build at scale from those who aren't. ScriptedByHer built a structure that forced it to happen in four days.

What Participants Walked Away With

Some participants left with Pre-Placement Offers. Some had full-time hiring conversations open. Some found mentors they hadn't expected, and came away with a clearer picture of what engineering inside a large product company actually looks like day to day.

For many, it was their first serious competitive engineering experience. The first time they'd sat across the table from engineers building real systems. The first time an idea they had worked on got genuinely stress-tested by someone who would have to think about shipping it.

That kind of exposure doesn't appear on a transcript. But it changes how an engineer approaches the next challenge, and the one after that.

Why It Matters Beyond Meesho

ScriptedByHer wasn't trying to make a statement. It was testing a format, and that format worked.

The industry doesn't have a shortage of capable women engineers. What it has is hiring systems that, often unintentionally, are optimised for patterns that narrow the pipeline too early. Familiar college names. Hackathon track records. Networks that are hard to enter from the outside.

Meesho's goal was straightforward: create an evaluation environment where capability is the filter, not familiarity with the process.

Some participants will join Meesho. Others will take what they learned into other companies and other teams. Either way, the industry benefits when more engineers get the chance to show what they can actually do — not just what their resume signals.

That's the real outcome of ScriptedByHer. A format that makes hiring sharper by changing who gets in the room. ​