About the role
Recruitcha.ai is sales intelligence for recruitment agencies. We watch the market for hiring signals so agency recruiters know which companies to call, who to talk to, and why now. Our products include Jobs Listener, Social Listener, ATS Graveyard and Market Mapping. We're three people. We're bootstrapped and profitable, with 100+ agencies using our platform. The founders spent 10+ years running and selling into recruiting agencies, so we already know what our customers need. Our job is to build it well. We built the first version fast, using AI heavily. It works, and customers pay for it. Some of it is held together with duct tape. We're hiring our first engineer to turn it into a platform that scales without losing the speed that got us here. At a glanceLocation: Remote, with 2+ hours of daily overlap with US PST time Team: 3 people today; you'd be the first engineer Reports to: The founders What you'll ownYou'll decide what to refactor, what to rebuild, and what to leave alone. Here are the problems on the table today:
• Signal ingestion. We pull hiring signals from job boards, ATS pages, social activity and third-party data providers. Much of it runs on scheduled jobs that fail silently. It needs to become a reliable pipeline with monitoring, retries and deduplication.
• Data model at scale. Companies, contacts, jobs and signals have grown faster than our Supabase schema was designed for. Queries are slowing down and the data has duplicates.
• Agentic workflows. Our AI agents research accounts, find decision-makers and draft outreach. They work well in demos.



Before we can trust them across every customer, they need evals, guardrails, cost controls and observability.
• Engineering foundations. We need CI, tests where they matter, staging environments, and a deploy process that doesn't depend on luck.
• New product. Customers ask for features every week. You'll work with the founders to decide what to build and then ship it across the full stack. Your first 90 days
• By day 30: You've shipped to production, sat in on customer calls, and mapped the codebase. You've told us what's fragile and what's fine.
• By day 60: You've fixed the worst reliability problem, likely signal ingestion. Failures now alert someone instead of disappearing.
• By day 90: You own deploys, monitoring and the technical roadmap. You're shipping customer features every week, and we make architecture decisions based on your judgment. Our stack
• Frontend: Next.js, TypeScript
• Backend: Node.js, Python, Supabase (Postgres)
• AI: model providers, e.g. Anthropic, OpenAI, Google You don't need experience with all of these. We want a strong engineer first, and the stack can change if you make the case. You'll probably be a great fit if you've




• Taken a prototype or MVP to production and kept it running under real customer load
• Owned features end to end, from the database to the UI
• Inherited a messy codebase and improved it without stopping to rewrite everything
• Built data pipelines, scrapers or integrations that had to be reliable
• Shipped something with LLMs that ran in production, beyond a demo
• Worked as a founding engineer, an early startup engineer, or a senior full-stack engineer This probably isn't the role for you if you want
• Detailed specs before you start building
• A large engineering team to learn from
• A frontend-only or backend-only role
• Someone else to make the technical decisions How we workWe're remote and open to excellent people anywhere. You'll need at least 3 hours of overlap each workday with the founders, who work on US PST time. During that overlap we talk directly with you, not through tickets. The rest of your day is yours to plan. We care about clear communication, ownership, and what you ship. Priorities shift as customers teach us things, and you'll help decide what comes next. Hiring processWe aim to go from first call to offer in about [2 to 3] weeks.
• Intro call (30 min) with a founder

about the role
, the business, and what you want next.
• Technical conversation (60 min): we walk through our architecture together and ask how you'd approach one of the problems above.
• Paid trial project: a small, real piece of work in our codebase.
• Founder conversations, then an offer.

📌 Founding Software Engineer (Bengaluru)
🏢 Recruitcha GTM
📍 Bengaluru