<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wield Blog EN</title>
    <link>https://www.wield.ch/blog-en</link>
    <description>Recruitment intelligence, Swiss compliance, and product deep dives.</description>
    <language>en</language>
    <atom:link href="https://www.wield.ch/rss-en.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Fri, 24 Apr 2026 15:19:28 GMT</lastBuildDate>
    <item>
      <title>Welcome to the Wield Blog</title>
      <link>https://www.wield.ch/blog-en/welcome-to-the-wield-blog</link>
      <guid isPermaLink="true">https://www.wield.ch/blog-en/welcome-to-the-wield-blog</guid>
      <pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate>
      <description>Perspectives on recruitment intelligence, Swiss compliance, and how modern hiring teams use AI without the black box.</description>
      <content:encoded><![CDATA[<p>Recruiting is changing faster than most HR teams can keep up with. AI handles screening, candidates expect answers within hours, and the regulatory frame in Switzerland and the EU keeps tightening. This blog is our attempt to add substance to the conversation — with concrete numbers, reproducible workflows, and an honest view of what actually works.</p>
<h2 id="what-this-blog-is-about">What this blog is about</h2>
<p>We publish regularly on three topics:</p>
<ul>
<li><strong>Recruitment intelligence</strong> — how hiring teams use data to make better decisions, faster.</li>
<li><strong>Swiss compliance &amp; data protection</strong> — what nDSG, GDPR, and UWG mean for AI-assisted HR in practice.</li>
<li><strong>Product deep dives</strong> — how we build Wield and the trade-offs we make.</li>
</ul>
<h2 id="why-another-hr-blog">Why another HR blog?</h2>
<p>There are many already. Too many repeating the same textbook. We try to do three things differently:</p>
<div class="blog-table-wrap"><table>
<thead>
<tr>
<th>Claim</th>
<th>Typical HR blog</th>
<th>Wield blog</th>
</tr>
</thead>
<tbody><tr>
<td>Data sources</td>
<td>Vendor surveys</td>
<td>Our own product data + external benchmarks</td>
</tr>
<tr>
<td>Audience</td>
<td>Generalists</td>
<td>Hiring leads, HR-tech ops, CTOs</td>
</tr>
<tr>
<td>Depth</td>
<td>800-word SEO standard</td>
<td>2,000–3,000 words with a reproduction path</td>
</tr>
</tbody></table></div>
<h2 id="what-to-expect">What to expect</h2>
<p>Every post ships with at least one of the following:</p>
<ol>
<li><strong>A measurable claim.</strong> For example: &quot;Structured interviews cut 90-day attrition by 18%&quot; — with source and methodology.</li>
<li><strong>A concrete workflow.</strong> No &quot;think about a strategy&quot; — here are the five steps, here is the output.</li>
<li><strong>A counter-argument.</strong> Where AI hurts hiring, where Swiss hosting doesn&#39;t matter, where our own product hits limits.</li>
</ol>
<pre><code class="hljs language-text">Post = 1 claim × 1 workflow × 1 counter-argument
</code></pre><p>That&#39;s not accidental — it&#39;s the structure that scores best in our own readability tests.</p>
<h2 id="subscribe--follow-along">Subscribe &amp; follow along</h2>
<p>New posts go out bilingually, German and English, roughly once a week. If you don&#39;t want to miss one, sign up for our <a href="/newsletter-en">newsletter</a>. Feedback and topic suggestions go straight to <a href="mailto:info@tecminds.ch">info@tecminds.ch</a>.</p>
<p>See you in the next one.</p>
]]></content:encoded>
      <category>Wield</category>
      <category>Recruitment</category>
      <category>Switzerland</category>
    </item>
  </channel>
</rss>
