<?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: piyushmishra06</title>
    <description>The latest articles on DEV Community by piyushmishra06 (@piyushmishra0620).</description>
    <link>https://dev.to/piyushmishra0620</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%2F4176298%2Fddf76bac-c83c-4b99-bc1c-92c54f6a5330.png</url>
      <title>DEV Community: piyushmishra06</title>
      <link>https://dev.to/piyushmishra0620</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/piyushmishra0620"/>
    <language>en</language>
    <item>
      <title>Document Summarizer</title>
      <dc:creator>piyushmishra06</dc:creator>
      <pubDate>Mon, 26 Oct 2026 06:32:23 +0000</pubDate>
      <link>https://dev.to/piyushmishra0620/document-summarizer-2gj8</link>
      <guid>https://dev.to/piyushmishra0620/document-summarizer-2gj8</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week3-2026-10-19"&gt;Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

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

&lt;p&gt;Documents are always hectic to read , often they have their details tucked. A document Summarizer helps ease the tedious task of reading documents and understanding the key parts of it. I built docAnalyzer for that.&lt;/p&gt;

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

&lt;p&gt;&lt;a href="https://github.com/piyushmishra0620/HacktoberFest-Week-3" rel="noopener noreferrer"&gt;https://github.com/piyushmishra0620/HacktoberFest-Week-3&lt;/a&gt;&lt;/p&gt;

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

&lt;p&gt;Used fastApi backend to gathers the form data from the frontend through /api/Summarizer , extractor worker gets into work , picks the document to be read the document , scans them thoroughly and extracts the text . It uses the chunking method where the text longer than 12k characters are broken down into segments . It then sends the request to locally running gemma , which Summarizes the entire thing and gives out the response . &lt;br&gt;
The response is served to the frontend.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Lazy Payoff
&lt;/h2&gt;

&lt;p&gt;It saves a lot of time as a reward , where people with less effor can be able to know all about the document , rather than reading it from top to bottom in a detailed manner.&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>MatchForge - Resume Analysis And Job Search Tool</title>
      <dc:creator>piyushmishra06</dc:creator>
      <pubDate>Mon, 19 Oct 2026 06:54:28 +0000</pubDate>
      <link>https://dev.to/piyushmishra0620/matchforge-resume-analysis-and-job-search-tool-af3</link>
      <guid>https://dev.to/piyushmishra0620/matchforge-resume-analysis-and-job-search-tool-af3</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week2-2026-10-12"&gt;Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

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

&lt;p&gt;A Resume analysis and Job Search tool where users can upload their resume , get their ATS score for the job which they are applying and finally get some recommendations about areas of improvement in the resume along with the matching jobs from across various sources. People often don't know the exact things they should write inorder to get a higher chance of selection besides they apply at places they can't hope much to get selected . They need the right companies where they will gain edge at,   not the ones where they may get rejected . So, this task is a tedious one : to find the things missing in their resume or rectify some , and then to get the idea of the correct places to apply at . MatchForge makes it simpler . Just upload the resume , give the title of the job for which you are applying , then it will give the ATS score along with areas of improvements and then the list of places at which they can apply at . This will atleast give people an idea of the type of companies they should be aiming for.  &lt;/p&gt;

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

&lt;p&gt;-&amp;gt; Here's the drive link showing the demo to use it : &lt;a href="https://drive.google.com/file/d/1BTS_ShTyeeo8oAPvmWOSovR80NwNXzcy/view?usp=sharing" rel="noopener noreferrer"&gt;https://drive.google.com/file/d/1BTS_ShTyeeo8oAPvmWOSovR80NwNXzcy/view?usp=sharing&lt;/a&gt; .&lt;/p&gt;

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

&lt;p&gt;-&amp;gt; The link to source code : &lt;a href="https://github.com/piyushmishra0620/Hacktoberfest-Week-2" rel="noopener noreferrer"&gt;https://github.com/piyushmishra0620/Hacktoberfest-Week-2&lt;/a&gt; .&lt;/p&gt;

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

&lt;p&gt;I made a react application with an expressjs server , where users upload their resume and the role for which they are applying . Afterwards, the resume text is extracted and sent along with the job description to the locally running model - gemma3 in ollama . It analyzes all the things in resume , matches with the jobs thereby returning with the resume score , the scope of improvements and matching jobs . It takes upto 2 minutes to display the entire thing in the frontend . With more power and GPUs , time can be greatly reduced for the model to perform better . &lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;p&gt;-&amp;gt; I made use of gemma3 . Hope this is worthwhile to pay to use it!&lt;/p&gt;

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