There’s a document published on the first of every month that contains more useful signal about where the tech labor market is really heading than anything Goldman Sachs or Gartner will publish this quarter.
I’m talking about Ask HN: Who is hiring? The April 2026 thread dropped this week, and it’s worth reading carefully — not to look for a job, but to understand what people are willing to pay to build things. That’s the best proxy we have for where the market is going.
Three things caught my attention.
Agentic fluency: no longer a plus, it’s the minimum requirement
The most revealing signal this month came from Spade — a startup building AI tools for the dairy industry. In their posting they wrote: “Never heard of a Ralph loop? NGMI.”
Read it again. A livestock data company. In their job posting. On Hacker News. Citing a Claude Code plugin by name as a filter to know if you’re the kind of engineer they want to hire.
We covered Ralph Loop here at yoDEV a couple of months ago. At that time it was a niche tool popular in the Claude Code community. By April 2026, it’s what a dairy data company uses to filter engineering candidates.
That’s what a cultural inflection point looks like. It doesn’t announce itself — it appears sideways, in postings from industries you weren’t looking at.
Spade isn’t an isolated case. Throughout the April thread, the language appearing in role after role is no longer “familiarity with AI tools, desirable.” It’s direct and specific: agentic scaffolding, multi-agent orchestration, LangGraph, RAG pipelines, context management, evaluation frameworks. BIT Capital, an asset management fund in Berlin, explicitly lists “Agentic AI” in their core stack and asks for engineers who can build “infrastructure for AI/LLM workflows (agentic scaffolding, RAG, LLMOps).” Subsalt directly lists “agent interfaces (MCP, mem0, ???)” as a required skill — they don’t even know yet which will be the third standard, but they know they’re going to need it.
The message from companies that are really hiring now is clear: experience with agentic workflows is no longer what separates senior candidates from junior candidates. It’s what separates candidates from non-candidates.
Security + AI has its own hiring wave
One of the least discussed dynamics in the April thread is the concentration of security companies hiring aggressively. Oneleet (cybersecurity, Series A), Trustle (cloud access management), ThreatMark (behavioral security ML), WireScreen (corporate intelligence and risk). Their presence this month is no coincidence.
Security was always going to follow the AI wave — the attack surface expands as tooling does. But the interesting shift is what these companies are building. They’re not hiring for traditional infosec roles. Trustle’s posting explicitly notes as a bonus: “experience with agentic AI/LLM workflows.” Burnin — which literally describes their product as “harsh environments that break AI agents” — hires engineers to design evaluation arenas for multi-agent coordination.
The attack surface of an agentic environment is categorically different from what security teams were protecting two years ago. Every AI agent is an identity. It needs credentials, accumulates privileges, operates autonomously across systems. The security industry is hiring people who understand this — and that requires a new hybrid profile: deep infosec experience combined with genuine fluency in how modern AI systems operate.
This isn’t a future trend. It’s the current hiring reality of the companies in the thread.
The role of “founding engineer for an agentic system from scratch” has its own gravity
There’s a third pattern in the April thread I’ve been watching emerge over the last few months: the founding engineer role where the explicit mandate is to design and build a complete agentic system with no existing codebase, no legacy constraints, and with a founding team of two or three people.
These postings have a distinctive signature. They describe what’s being built in terms of domain (quantitative investment analysis, molecular discovery, logistics autonomy), then specify that the candidate must design the architecture, agent orchestration, evaluation framework, and production infrastructure — all from scratch. One posting is direct about the profile sought: “You probably tried multiple orchestration frameworks and found them all inadequate in different ways. You think about failure modes, evaluation, and context management all the time.”
That’s not a job description. It’s a characterization of a specific type of engineering mind that emerged from the last 18 months of building with LLMs in production.
These roles are high-risk, high-responsibility, and — from a market signal perspective — they tell you where the next layer of AI infrastructure is being built. Not in big tech. In small teams, with serious funding, solving specific domain problems that require deep agentic expertise.
What this means if you’re a developer right now
Three things.
First: the gap between developers who’ve built with agentic tools in production and those who haven’t is becoming legible in the labor market. It’s showing up in how companies write their job descriptions. That gap is going to grow.
Second: security is the sector where AI and traditional software infrastructure converge most urgently. If you have any interest in that intersection — MCP security, agent identity management, evaluation frameworks for autonomous systems — the hiring signal from this thread is unequivocal.
Third: the window of opportunity for “founding engineer for an agentic system” is real, but it requires a specific type of preparation. These companies aren’t looking for people who read about multi-agent frameworks. They’re looking for people who built with them, ran into the failure modes, and developed opinions on how to do it better.
The HN thread drops on the first of every month. Most people look at it to find a job. The most useful way to read it is as a real-time map of what the market is actually paying for.
April 2026 is saying something clearly. It’s worth listening.