Your first break won't come from a resume.
It'll come from what you build.

A year ago, building a product required a full team — designers, frontend engineers, backend engineers, PMs writing specs. Today, one person with the right instincts and AI tools can do what a team of five used to do.

Maybe you code and want to build products people actually use — not just scripts that run. Maybe you think in products and user problems, and you've realised that AI tools like Cursor, Replit, or Claude let you build what you imagine without waiting for an engineering team.

Either way, you're someone who:

Does your solution directly address the challenge? Is it specific to fintech, financial services, or your assigned track?

Is the code real and working? Is the architecture sound? Did you deploy it? Code quality, system design, and commit history matter.

Is this a genuinely new angle? Non-obvious approaches and systems thinking are rewarded over incremental tweaks.

Can you explain what you built, why it matters, and how it works? A polished, clear demo is half the battle.

If funded, could it scale? Does it address a real problem with genuine market size in India?

Tip: A working deployed app with a tight narrative beats an impressive codebase that nobody can run. Ship first, polish second.

Everyone's been "experimenting" with AI. Playing with wrappers. Sharing ChatGPT screenshots. But almost nobody is shipping real products with it — especially not in India's financial ecosystem, where the problems are specific, messy, and urgent.

We built Blostem to make banking products accessible to every fintech in India. Now we want to find the next generation of builders who think the same way — people who see gaps in the system and have the instincts to close them.

This is a solo challenge. No teams. No hiding behind someone else’s code. Just you, your tools, and a real problem. Show us what one builder can do. This is a solo-only challenge.