<?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: Krisha Shah</title>
    <description>The latest articles on DEV Community by Krisha Shah (@krishashah03).</description>
    <link>https://dev.to/krishashah03</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%2F4161200%2F78500bb4-9b49-439e-869c-60939d5186b4.png</url>
      <title>DEV Community: Krisha Shah</title>
      <link>https://dev.to/krishashah03</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/krishashah03"/>
    <language>en</language>
    <item>
      <title>FillMate: An AI Add-in for My HR Friend</title>
      <dc:creator>Krisha Shah</dc:creator>
      <pubDate>Sun, 04 Oct 2026 18:30:30 +0000</pubDate>
      <link>https://dev.to/krishashah03/fillmate-an-ai-add-in-for-my-hr-friend-4gej</link>
      <guid>https://dev.to/krishashah03/fillmate-an-ai-add-in-for-my-hr-friend-4gej</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.tolink-to-challenge"&gt;Hacktoberfest Weekend Challenge: Build for a Friend&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;A close friend of mine handles HR at a small company. Every new hire means opening the same Word salary template and copying details from emails by hand: name, designation, joining date, CTC, notice period. It's slow, and one wrong digit in a salary letter is a real problem.&lt;/p&gt;

&lt;p&gt;So I built &lt;strong&gt;AI Word Template Filler&lt;/strong&gt;: a Word add-in where she pastes an email or a few lines of text, and it fills the template for her. Nothing is written silently. Every field shows up for review first, and anything missing is flagged instead of guessed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/VrrP5rSS1sM" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;br&gt;
[Short video: paste text → review panel → Apply to Word]&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;[&lt;a href="https://github.com/krishashah-03/superdocs-builds/tree/main/extensions/krishashah-03/word-fill-template" rel="noopener noreferrer"&gt;https://github.com/krishashah-03/superdocs-builds/tree/main/extensions/krishashah-03/word-fill-template&lt;/a&gt;]&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;[Open-weight model, e.g. Llama 3.3 70B] via OpenRouter&lt;/strong&gt; extracts fields from free text like emails and bullet points&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FastAPI&lt;/strong&gt; backend normalizes dates, salary ("8 LPA" → 800000), and yes/no values, then detects gaps&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;React + Office.js&lt;/strong&gt; task pane shows a review screen; only approved fields are written into Word&lt;/li&gt;
&lt;li&gt;JSON/CSV input skips the AI entirely, so structured data stays deterministic&lt;/li&gt;
&lt;li&gt;63 pytest tests cover parsing, normalization, gap detection, and AI error handling&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why Open Models Matter Here
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No lock-in:&lt;/strong&gt; OpenRouter's OpenAI-compatible API let me test several open-weight models and pick the one best at structured extraction by changing one config line.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A path to fully local:&lt;/strong&gt; because the model is open-weight, the same setup can run on her own machine through Ollama later, so salary data never has to leave the office.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Low cost:&lt;/strong&gt; a small company can't justify an expensive API bill for filling forms; open models keep it nearly free.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What She Said
&lt;/h2&gt;

&lt;p&gt;[I've sent her a demo, and she'll try it on the next new joiner's salary letter. I'll update this section with her honest verdict, good or bad]&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next
&lt;/h2&gt;

&lt;p&gt;Offer letters and NDAs. The engine is schema-driven, so a new template only needs a new schema.json.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>weekendchallenge</category>
      <category>hf26challenge</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
