<?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: HR Pulsar</title>
    <description>The latest articles on DEV Community by HR Pulsar (@hr_pulsar).</description>
    <link>https://dev.to/hr_pulsar</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%2F3899056%2Fe966de8e-b20a-420c-a1aa-6a8538510154.png</url>
      <title>DEV Community: HR Pulsar</title>
      <link>https://dev.to/hr_pulsar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hr_pulsar"/>
    <language>en</language>
    <item>
      <title>Four years ago we started building an HR platform</title>
      <dc:creator>HR Pulsar</dc:creator>
      <pubDate>Mon, 18 May 2026 10:56:41 +0000</pubDate>
      <link>https://dev.to/hr_pulsar/four-years-ago-we-started-building-an-hr-platform-29jo</link>
      <guid>https://dev.to/hr_pulsar/four-years-ago-we-started-building-an-hr-platform-29jo</guid>
      <description>&lt;p&gt;Not because HR-tech looked exciting. Mostly because every company we talked to had the same setup:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;grades in Excel&lt;/li&gt;
&lt;li&gt;360 reviews in Google Forms&lt;/li&gt;
&lt;li&gt;competency matrices buried in Confluence&lt;/li&gt;
&lt;li&gt;“performance systems” that nobody wanted to open twice&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And eventually: &lt;em&gt;“Let’s just build our own thing.”&lt;/em&gt;&lt;br&gt;
So we did.&lt;/p&gt;

&lt;p&gt;Then this year we made a bigger decision: we rewrote the platform from the ground up — and open sourced it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Meet HRPulsar
&lt;/h2&gt;

&lt;p&gt;An open source talent management platform for teams where every employee already works with AI tools.&lt;/p&gt;

&lt;p&gt;Most HR systems still model companies like it’s 2015: &lt;strong&gt;employee → position → annual review.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;But that model is breaking. Roles change every quarter. Skills decay faster than job titles. Half the team uses AI agents nobody tracks. And “career frameworks” are often PDFs with better branding.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;We built HRPulsar around a different assumption:&lt;br&gt;
Skills are the stable unit. Not positions.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;So the platform is competency-first at the core: competency graphs, grade systems tied to behavioural anchors, 360 assessments, internal talent marketplace, development plans, AI fluency tracking, AI workforce registry&lt;br&gt;
&lt;em&gt;Yes, AI workforce registry.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Because “Shadow AI” is becoming a real operational problem:&lt;/strong&gt; teams use 15 different AI tools, security doesn’t know about half of them, and HR systems pretend none of this exists.&lt;/p&gt;

&lt;p&gt;So we added:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;AI tool registry&lt;/li&gt;
&lt;li&gt;employee ↔ AI tool assignments&lt;/li&gt;
&lt;li&gt;oversight levels&lt;/li&gt;
&lt;li&gt;workflow ownership&lt;/li&gt;
&lt;li&gt;audit trails&lt;/li&gt;
&lt;li&gt;workforce maps for hybrid teams (human + AI)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Useful for compliance &amp;amp; security. But mostly because companies should probably know which AI systems are already part of their workforce.&lt;/p&gt;

&lt;h2&gt;
  
  
  Technically, HRPulsar is
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;FastAPI&lt;/li&gt;
&lt;li&gt;Next.js&lt;/li&gt;
&lt;li&gt;PostgreSQL&lt;/li&gt;
&lt;li&gt;Redis&lt;/li&gt;
&lt;li&gt;200+ API endpoints&lt;/li&gt;
&lt;li&gt;~1000 automated tests&lt;/li&gt;
&lt;li&gt;Docker-first deployment&lt;/li&gt;
&lt;li&gt;AGPLv3&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;No “book a demo”. No sales call before seeing the product.&lt;br&gt;
And one thing we decided early: &lt;strong&gt;HRPulsar will stay free for individuals and small teams.&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Every workspace gets a monthly pool of renewable credits. Enough to run the core platform without turning “try the product” into a budgeting discussion.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And yes — self-hosting is fully supported. Because HR data is sensitive.&lt;br&gt;
And “trust us with your entire workforce structure” is a pretty big ask from a black-box SaaS vendor.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/hrpulsar/hrpulsar" rel="noopener noreferrer"&gt;We’re preparing the public GitHub release right now.&lt;/a&gt;&lt;br&gt;
*The repository goes live at the end of May. If you want early access, release updates, or just want to watch the project evolve — join the waitlist.&lt;/p&gt;

&lt;h2&gt;
  
  
  LLMs are useful ONLY for competency matching and draft recommendations
&lt;/h2&gt;

&lt;p&gt;They are &lt;strong&gt;&lt;em&gt;not qualified&lt;/em&gt;&lt;/strong&gt; to decide someone’s promotion. We’re very explicit about that in the product.&lt;/p&gt;

&lt;p&gt;LLMs are useful for competency matching and draft recommendations.&lt;br&gt;
They are not qualified to decide someone’s promotion. We’re very explicit about that in the product.&lt;/p&gt;

&lt;p&gt;Current limitations?&lt;br&gt;
We don’t cover recruiting yet. ATS/recruiting is on the roadmap, but not today.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Would genuinely love feedback&lt;/strong&gt; from developers building internal tools, people running self-hosted infrastructure, HR engineers, teams experimenting with AI-heavy workflows... and especially from anyone who has ever tried to manage competencies in Excel. &lt;em&gt;We know you exist.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a href="https://hrpulsar.com/" rel="noopener noreferrer"&gt;try it on website&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>opensource</category>
      <category>hrtech</category>
      <category>news</category>
    </item>
    <item>
      <title>Why AI adoption fails inside companies</title>
      <dc:creator>HR Pulsar</dc:creator>
      <pubDate>Thu, 07 May 2026 12:15:48 +0000</pubDate>
      <link>https://dev.to/hr_pulsar/why-ai-adoption-fails-inside-companies-j8j</link>
      <guid>https://dev.to/hr_pulsar/why-ai-adoption-fails-inside-companies-j8j</guid>
      <description>&lt;p&gt;A company buys ChatGPT Enterprise. Then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;marketing uses it for copy&lt;/li&gt;
&lt;li&gt;one engineer automates half their workflow&lt;/li&gt;
&lt;li&gt;another refuses to touch it&lt;/li&gt;
&lt;li&gt;managers say “we should use AI more”&lt;/li&gt;
&lt;li&gt;nobody knows what “more” means&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Three months later, leadership asks the inevitable question: &lt;em&gt;“So… are we actually getting ROI from this?”.&lt;/em&gt; Silence. Not because AI failed.&lt;br&gt;
Because adoption inside companies is mostly random. And random systems don't scale.&lt;/p&gt;

&lt;p&gt;Most companies approach AI rollout like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Buy tools&lt;/li&gt;
&lt;li&gt;Announce initiative&lt;/li&gt;
&lt;li&gt;Hope employees figure it out&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That works for maybe two weeks. After that, you get what every company gets:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;inconsistent usage&lt;/li&gt;
&lt;li&gt;inconsistent output&lt;/li&gt;
&lt;li&gt;no shared standards&lt;/li&gt;
&lt;li&gt;no visibility into who’s actually effective with AI&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Useful? Sometimes.&lt;br&gt;
Measurable? Not really.&lt;/p&gt;

&lt;p&gt;The uncomfortable part: &lt;strong&gt;most companies still evaluate people like AI doesn’t exist.&lt;/strong&gt;&lt;br&gt;
Performance reviews ask communication, ownership &amp;amp; collaboration.&lt;br&gt;
Fine. But now we also need to ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;can this person delegate effectively to AI?&lt;/li&gt;
&lt;li&gt;can they verify AI output?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;do they know when not to use it?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;are they faster because of AI — or just noisier?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because there’s a difference between “uses AI” and “works effectively with AI” is enormous.&lt;br&gt;
And this is where most AI adoption projects quietly break. Not on infrastructure. Not on tooling. On management.&lt;br&gt;
No competency model. No measurement system. No shared definition of “good AI usage” - just licenses and optimism.&lt;/p&gt;

&lt;p&gt;The weird part is that companies already solved this problem once.&lt;br&gt;
We don’t say: “&lt;em&gt;Everyone has Excel now, good luck”.&lt;/em&gt; We train people, define expectations, measure proficiency.&lt;br&gt;
AI will end up the same way. Except the impact is bigger.&lt;/p&gt;

&lt;p&gt;At &lt;a href="https://hrpulsar.com/" rel="noopener noreferrer"&gt;HRPulsar&lt;/a&gt;, we’ve been thinking about this a lot. Not as “AI replacing employees”. But as: how do you systematically measure and develop AI fluency inside teams?&lt;br&gt;
And honestly, we don’t think the industry has good answers yet.&lt;/p&gt;

&lt;p&gt;Especially for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;role-specific AI competencies&lt;/li&gt;
&lt;li&gt;measuring real usage quality&lt;/li&gt;
&lt;li&gt;separating employee contribution from AI contribution
One thing already seems obvious: buying AI tools is easy, building an organization that actually knows how to use them is the hard part.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Curious how other teams are handling this right now. &lt;strong&gt;Do you actually measure AI adoption in any meaningful way — or is it still mostly vibes?&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>hrtech</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
