<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:media="http://search.yahoo.com/mrss/">
<channel>

<title>Blogosm &#45; Boring project</title>

<!-- FIX -->
<link>https://blogosm.com/rss/author/boring-project</link>

<description>Blogosm &#45; Boring project</description>
<dc:language>en</dc:language>

<dc:rights>Copyright 2020 to 2026 Blogosm &#45; All Rights Reserved.</dc:rights>



<item>

<title>Job Application API: How It Works and What It&amp;apos;s Actually Good For</title>

<link>https://blogosm.com/apijobapply</link>

<guid>https://blogosm.com/apijobapply</guid>

<description><![CDATA[ There&#039;s a specific kind of frustration that comes from filling out the same job application ten different ways. Your resume already has the information. The company&#039;s form wants you to type it in anyway, field by field, then answer a handful of questions that have nothing to do with whether you can do the job. Multiply that by every role you apply to, and it&#039;s not hard to see why a job application API turned into something people actually build products around instead of just a nice idea. ]]></description>


<pubDate>Mon, 03 Aug 2026 23:09:02 +0530</pubDate>

<dc:creator>Boring project</dc:creator>

<media:keywords>ai job search, ai, api job search</media:keywords>


</item>


</channel>
</rss>