<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: RecruitKar</title>
    <description>The latest articles on DEV Community by RecruitKar (@recruitkar).</description>
    <link>https://dev.to/recruitkar</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4065430%2Fe53c315d-3925-4ecb-b9f3-e3aff086bbbb.png</url>
      <title>DEV Community: RecruitKar</title>
      <link>https://dev.to/recruitkar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/recruitkar"/>
    <language>en</language>
    <item>
      <title>What we learned building AI video interviews in 12 Indian languages</title>
      <dc:creator>RecruitKar</dc:creator>
      <pubDate>Thu, 06 Aug 2026 08:03:19 +0000</pubDate>
      <link>https://dev.to/recruitkar/what-we-learned-building-ai-video-interviews-in-12-indian-languages-5had</link>
      <guid>https://dev.to/recruitkar/what-we-learned-building-ai-video-interviews-in-12-indian-languages-5had</guid>
      <description>&lt;p&gt;When we set out to add AI interviews to &lt;a href="https://recruitkar.com" rel="noopener noreferrer"&gt;RecruitKar&lt;/a&gt;, the "easy" version was obvious: transcribe English audio, score it, done. The hard, and far more useful, version was doing it in the languages Indian candidates actually speak. Here is what surprised us.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Code-switching is the norm, not the exception.&lt;/strong&gt; Real Indian interview answers are rarely pure Hindi or pure English. They are Hinglish, Tanglish, a sentence that starts in Marathi and lands on an English technical term. A model that expects one language per utterance falls apart, so handling mixed-language input turned out to be the single biggest quality lever.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Accent and dialect variance is huge within one language.&lt;/strong&gt; Tamil in Chennai versus Madurai, Hindi across states: the acoustic spread inside a single language is wider than the gap between some entirely different ones. Broad, real-world speech coverage mattered far more than clean studio data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Scoring has to be language-fair.&lt;/strong&gt; A candidate answering brilliantly in Telugu should not score lower than a mediocre English answer just because the pipeline understands English better. Separating what was said from how well the model heard it was essential to keep the evaluation fair.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Proctoring plus video changes the trust equation.&lt;/strong&gt; Voice alone is convenient, but recorded, proctored video is what makes a hiring team actually trust a first round enough to skip it themselves.&lt;/p&gt;

&lt;p&gt;The payoff: a recruiter can screen 50 candidates across five languages overnight and wake up to scored transcripts, without a single scheduling call. For small Indian teams hiring without a recruiter, that is the difference between a two-week and a six-week hire.&lt;/p&gt;

&lt;p&gt;If you are working on multilingual speech or hiring tech, I would love to compare notes. And if you are hiring in India, that is exactly who we built &lt;a href="https://recruitkar.com" rel="noopener noreferrer"&gt;RecruitKar&lt;/a&gt; for.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>machinelearning</category>
      <category>startup</category>
      <category>india</category>
    </item>
  </channel>
</rss>
