Gnani.ai
Website:
gnani.ai
Job details:
About Gnani.ai
Gnani.ai builds proprietary voice and conversational AI — ASR, TTS, small language models, and agentic voice platforms — across 22+ Indian languages. Our platforms Inya (a voice agent builder) and Vachana (multilingual voice AI) are deployed across BFSI, insurance, healthcare, and telecom, including some of India's largest enterprises.
We're a deep-tech voice AI company building for a market where every customer interaction happens in a mix of languages, dialects, and contexts that off-the-shelf global platforms don't handle well. That's our edge, and our platforms are how we deliver it at scale.
The Role
This is a founding hire for a new function inside our Product organization. You will be the first person on the ground building what we are calling Solutions Architecture for our GenAI platforms — a team whose mandate is to make Inya and Vachana usable, learnable, and deployable by the broader ecosystem of implementation partners and enterprise customers, without Gnani's engineering team in the loop.
You will come in, get deeply hands-on with both platforms, sit with our customers and partners, and figure out the right shape of this function as you go. Our working hypothesis is that the highest-leverage activity is technical enablement of implementation partners — system integrators and consulting firms who deliver Inya and Vachana to end customers — with direct enterprise workshops as a strong secondary mandate. We want you to pressure-test that hypothesis before we commit to scaling the team.
If you have been an early Solutions Architect, Developer Advocate, or Partner Enablement Lead at a platform company and want to do it again from zero with real ownership, this is that role.
What You'll Do
Partner enablement and certification
- Onboard, train, and certify Gnani's implementation partners — system integrators and consulting firms — so they can independently deliver production-grade Inya and Vachana deployments for their customers.
- Design and run a structured partner certification program (Foundational → Practitioner → Expert) that earns credibility through demonstrated build capability, not slide attendance.
- Deliver multi-day partner bootcamps where partner engineers leave able to architect, build, and deploy production-grade voice agents for the use cases they will encounter in the field.
- Maintain partner-facing assets: implementation playbooks, reference architectures, cookbooks for recurring patterns in BFSI, insurance, healthcare, and telecom.
- Partner closely with our Partnerships function — they own commercials and relationships; you own technical capability.
Platform mastery
- Develop architecture-level expertise across Inya and Vachana — agent builder, prompt configuration, tool calling, RAG, eval, telephony integration, voice configuration, language coverage, deployment, and observability.
- Be able to whiteboard how RAG is implemented in Inya for a customer architect — chunking, embeddings, retrieval, reranking, context injection — and answer the follow-up questions credibly.
- Be the source of truth for what the platforms can and cannot do today, and what is shipping on the roadmap.
- Stay current on the GenAI and voice AI landscape and how Gnani's platforms compare.
Enterprise workshops
- Run enablement workshops (half-day to one-day) for enterprises evaluating or starting on the platform — capability walkthroughs, live demos, Q&A.
- Run production-build workshops (multi-day, hands-on) for customer engineering teams who will build agents themselves and leave with a working, production-grade agent under your guidance.
- Build a library of workshop templates so delivery scales — Tier 1 sessions become near-turnkey; Tier 2 sessions are templated by use case.
Training and curriculum
- Build and maintain the structured learning surface — courses, video tutorials, hands-on labs, reference agents, and certification tracks — that scales platform expertise beyond one-to-one sessions.
- Run open-enrollment training cohorts on a regular cadence for individual builders outside partner and customer channels.
External evangelism and content
- Be one of Gnani's credible public technical voices through webinars, podcasts, conference talks, and technical content.
- Build the broader awareness pool from which future partners and customers emerge.
Internal enablement and product feedback
- Train Sales, Customer Success, and Partnerships on platform capabilities; maintain internal reference assets so internal teams never misrepresent what the platforms do.
- Channel structured monthly signal from partners and customers back to Product on adoption blockers, capability gaps, and roadmap pull.
What This Role Is Not
We're being explicit about scope because these boundaries matter:
- Not pre-sales deal ownership. Sales owns deals. You'll join calls when deep platform questions need answering, then exit.
- Not building customer agents. You teach, train, and enable. You do not deliver customer projects — that is our Delivery function.
- Not customer-embedded implementation. A multi-day workshop is in scope. Spending weeks inside one customer's team is not.
- Not L1 or L2 support. You are not in the ticket queue.
- Not partner relationship management or commercials. Our Partnerships function owns who is in the program and on what terms; you own whether they are technically capable.
The First Six Months
We want you to figure out the shape of this function. Roughly:
- Days 1–30 — Get deep on the platforms. Build agents on Inya and Vachana yourself across multiple use cases. Read every doc. Sit with engineering. Get cold on the technical surface.
- Days 30–60 — External listening. Sit on customer calls, partner calls, sales calls, and support escalations. Talk to current and prospective platform users — direct customers and SI partners. Document what you hear and what is broken.
- Days 60–90 — Run experiments. Deliver at least one enterprise workshop. Run at least one partner enablement session. Ship at least one piece of public technical content. Measure what worked.
- End of 90 days — Propose the shape. Come back with a recommendation: what should this function be at three people and at six people, what is the certification strategy, what cadence makes sense for workshops and content, and what is the next hire. We decide together and move.
You will report directly to the Head of Product for the first six months. You will have standing access to customer calls, partner conversations, sales calls, and engineering — no permission gates. When Sales or others ask you to do something outside the charter, you can say no and route it up. You will have full air cover.
Click on Apply to know more.