📍 Mulund, Mumbai · Hybrid · 6 months · Converts to full-time
About Us
We're building an AI-native platform for real estate developers and contractors in India. Our goal is to automate connected workflows, from tendering and procurement to site execution, billing and handover, reducing manual follow-ups, coordination effort, and time and money leakages. AI prepares, checks and moves work forward. People make the decisions.
About the role
This is a 6-month internship that converts to a full-time role based on performance. Working directly with the Founders, you'll build the AI core of the product and connect it to the outside world: the pipelines and agents that read documents and check work, and the integrations that bring documents, photos and messages in from WhatsApp, email and other systems. You'll own real pieces of the system, not side projects.
What you'll build
- Document pipelines: Extracting structured data from tenders, BOQs, purchase orders, delivery challans, bills and site photos.
- Agents & orchestration: Tool use, task routing and multi-step workflows that take a task from intake to a finished output.
- Integrations: WhatsApp intake for photos, PDFs and voice notes, email intake, and connections to ERPs and other third-party tools.
- Verification logic: Checking claims against evidence so every number is linked to its source.
- Evaluations: Test sets, quality checks and failure analysis across accuracy, latency and cost.
What you'll bring
- Hands-on projects in Python or JavaScript/TypeScript that you built yourself and can walk us through.
- Experience with LLM APIs, prompting and structured outputs. Coursework, personal projects and previous internships count.
- Experience with webhooks, third-party APIs or messaging platforms.
- An evidence-first mindset: you test assumptions, measure output quality and learn from failures.
- Availability for the full 6 months, with the intent to continue full-time.
Apply below
Answer a few short technical questions about what you've built and how you solve problems. We read every application, so specific answers about your own work matter more than polished ones.
Include a repository or demo link. Tell us what it did, what you personally built, and how you measured whether its output was correct, with numbers if you have them.
Explain how you'd prevent duplicate processing and keep messages in the right sequence.
How did you catch it, what did you change, and how did you check whether the fix worked?
