Overview
Quick Commerce is moving too fast for "good enough" tech.
We’re hiring a Lead Engineer to help us rebuild for scale. 🚀
RevQ is an AI-led SaaS platform helping brands like Blinkit, Zepto, and Swiggy Instamart turn massive distribution data into instant action.
We have a growing dev team, paying customers, and a production pipeline that’s proven the concept. Now, we’re moving from "making it work" to "making it scale."
The Mission
Our dev team have built a solid foundation using Python/Flask and SQL Server. But as we grow, we’re hitting the limits of our current architecture. We need a Lead Software Engineer (3-6 years experience) to own the tech vision and lead the transition to a high-performance stack.
The Priorities:
Decouple & Build: Lead the shift from Flask to a high-concurrency Node.js API layer.
The Dashboard: Architect a brand-facing, multi-tenant React dashboard to replace our current Tooljet setup.
Data Integrity: Implement a proper raw → staging → computed pipeline to ensure we never push bad scrape data to production.
The AI Layer: Build the rule/trigger engine that transforms data into proposed actions with human-in-the-loop approval.
What we’re looking for:
3-6 years of experience shipping production-grade Node.js and React.
The ability to audit a "messy" legacy codebase and improve it incrementally without breaking the business.
Experience with multi-tenant data models and Postgres migrations.
A "Player-Coach" mentality—you can lead a team’s vision but you’re still the strongest coder in the room.
What this role isn't:
This isn't a role for someone who wants to manage from a spreadsheet. This is for a builder who wants to make real architectural decisions from Day 1 and see them impact some of the biggest brands in India.
The Stack:
Node.js | React | SQL Server (migrating to Postgres) | Python scrapers | Claude API
When you Apply, please write down:
A breakdown of a complex system you’ve built or scaled.
One specific thing in this JD that you’d push back on. We value people who challenge the "how" to get to a better "why."