<?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>Forem: Cloud Strife</title>
    <description>The latest articles on Forem by Cloud Strife (@cloudhighfive).</description>
    <link>https://forem.com/cloudhighfive</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3258828%2F8a8e3dcc-43d9-4ff1-a3e0-099265bce5f4.png</url>
      <title>Forem: Cloud Strife</title>
      <link>https://forem.com/cloudhighfive</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/cloudhighfive"/>
    <language>en</language>
    <item>
      <title>Building an AI-Powered Resume Tailoring Pipeline: Lessons Learned</title>
      <dc:creator>Cloud Strife</dc:creator>
      <pubDate>Fri, 07 Nov 2025 15:57:57 +0000</pubDate>
      <link>https://forem.com/cloudhighfive/building-an-ai-powered-resume-tailoring-pipeline-lessons-learned-2f42</link>
      <guid>https://forem.com/cloudhighfive/building-an-ai-powered-resume-tailoring-pipeline-lessons-learned-2f42</guid>
      <description>&lt;p&gt;Hey devs! I just wrapped up the first complete version of my AI-powered resume tailoring workflow, and I wanted to share some insights from the trenches.&lt;/p&gt;

&lt;p&gt;The project combines Python, Flask, and state-of-the-art LLMs to automate the entire resume customization process. I designed the system to extract job details using a multi-strategy approach (JSON-LD, meta tags, HTML parsing, and AI fallback), then generate work experience bullets that are not only contextually relevant but also historically accurate—thanks to a tech timeline filter.&lt;/p&gt;

&lt;p&gt;One of the biggest challenges was ensuring output quality. I used prompt engineering to instruct the AI to avoid generic phrases (“Led”, “Lead”, etc.), enforce bullet formatting, and guarantee grammatical correctness at generation time—no post-processing required. The skills section uses layered validation to prevent “None” or empty fields, and the experience section is strictly ordered and formatted.&lt;/p&gt;

&lt;p&gt;From a software design standpoint, I leaned heavily on modularity and testability. Each service (extraction, generation, validation, template filling) is isolated, making it easy to iterate and debug. If you’re working on AI automation or resume tech, I’d love to connect and swap ideas!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/cloudhighfive/alphajob" rel="noopener noreferrer"&gt;https://github.com/cloudhighfive/alphajob&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>career</category>
      <category>python</category>
      <category>automation</category>
    </item>
    <item>
      <title>Day 1 Automating the Job Hunt: Battling Spam Detection and the Gender Field Nightmare</title>
      <dc:creator>Cloud Strife</dc:creator>
      <pubDate>Tue, 04 Nov 2025 16:03:53 +0000</pubDate>
      <link>https://forem.com/cloudhighfive/day-1-automating-the-job-hunt-battling-spam-detection-and-the-gender-field-nightmare-1e6i</link>
      <guid>https://forem.com/cloudhighfive/day-1-automating-the-job-hunt-battling-spam-detection-and-the-gender-field-nightmare-1e6i</guid>
      <description>&lt;p&gt;&lt;a href="https://github.com/cloudhighfive/alphajob" rel="noopener noreferrer"&gt;https://github.com/cloudhighfive/alphajob&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I began working on a new project which targets the developer problem of handling endless job application tasks. The process of completing forms on &lt;strong&gt;Lever, SmartRecruiters, and Greenhouse&lt;/strong&gt; requires full-time dedication because it takes up that amount of time. I began developing this solution during the previous day.&lt;/p&gt;

&lt;p&gt;The solution requires advanced techniques for web scraping and browser automation to solve this complex technical problem.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Code Strategy &amp;amp; What's Done So Far:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The system uses &lt;strong&gt;Playwright&lt;/strong&gt; for browser control to enable smooth navigation between different &lt;strong&gt;ATS platforms&lt;/strong&gt; through a Python-based framework.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The system uses separate modules for each major platform including &lt;strong&gt;Ashby and Workable&lt;/strong&gt; to handle URL and form field extraction tasks.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The system successfully detects and fills all typical application fields which include name, email, and basic work history information.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The Current Grind (Technical Issues Requiring Refinement):&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;The system faces two main challenges because it triggers aggressive &lt;strong&gt;spam filters&lt;/strong&gt; which Playwright's built-in stealth features fail to prevent. The system needs to learn how to hide &lt;strong&gt;headers&lt;/strong&gt; and create fake human-like submission delays to defeat complex bot detection systems.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The selection process for &lt;strong&gt;gender or demographic options&lt;/strong&gt; proves to be a major stability issue because it seems like a basic operation. The different application forms use inconsistent &lt;strong&gt;HTML tags and hidden containers and unreliable CSS selectors&lt;/strong&gt; which makes my element identification system unstable.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>showdev</category>
      <category>python</category>
      <category>career</category>
      <category>automation</category>
    </item>
    <item>
      <title>My First Post: I Built a Payment Template—Now Reality Check Me on KYC</title>
      <dc:creator>Cloud Strife</dc:creator>
      <pubDate>Thu, 12 Jun 2025 02:47:06 +0000</pubDate>
      <link>https://forem.com/cloudhighfive/my-first-post-i-built-a-payment-template-now-reality-check-me-on-kyc-3l0d</link>
      <guid>https://forem.com/cloudhighfive/my-first-post-i-built-a-payment-template-now-reality-check-me-on-kyc-3l0d</guid>
      <description>&lt;p&gt;&lt;strong&gt;Okay, real talk:&lt;/strong&gt; I built a payment platform template that &lt;em&gt;pretends&lt;/em&gt; KYC doesn’t exist.  &lt;/p&gt;

&lt;p&gt;It’s called &lt;strong&gt;NoVerif&lt;/strong&gt; (because naming things is hard), and it’s for &lt;strong&gt;devs who want to prototype fast&lt;/strong&gt;—not break financial laws.  &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;What’s Inside?&lt;/strong&gt;
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Email/password auth (Firebase)
&lt;/li&gt;
&lt;li&gt;Virtual bank account &lt;em&gt;cosplay&lt;/em&gt; (ACH approval flow)
&lt;/li&gt;
&lt;li&gt;Crypto wallet connections (for that ~degen~ vibe)
&lt;/li&gt;
&lt;li&gt;Invoice generation + admin dashboard
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Tech stack: &lt;strong&gt;Next.js, Firebase, Tailwind&lt;/strong&gt;—zero surprises.  &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Why This Exists&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;I wanted to &lt;strong&gt;mock a payment system in hours&lt;/strong&gt;, not months. But let’s be clear:  &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;🚨 Real payments need KYC, compliance, lawyers, etc.&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;🚨 This is a TEMPLATE for demos/hackathons&lt;/strong&gt; (or your startup’s &lt;em&gt;first&lt;/em&gt; PowerPoint).
&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Who’s This For?&lt;/strong&gt;
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;You, &lt;strong&gt;iterating on a fintech idea&lt;/strong&gt; before bringing in the compliance squad
&lt;/li&gt;
&lt;li&gt;You, &lt;strong&gt;teaching web dev&lt;/strong&gt; and need a realistic (but legal) payments demo
&lt;/li&gt;
&lt;li&gt;You, &lt;strong&gt;ignoring my warnings&lt;/strong&gt; (please don’t)
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Try it here:&lt;/strong&gt; &lt;a href="https://github.com/cloudhighfive/noverif" rel="noopener noreferrer"&gt;https://github.com/cloudhighfive/noverif&lt;/a&gt;  &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hot take:&lt;/strong&gt; Prototyping ≠ production. What’s the &lt;em&gt;fastest&lt;/em&gt; way you’ve hacked around compliance? (Or am I the only one cutting corners? 😬)&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>fintech</category>
      <category>javascript</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
