---
title: Hyre
description: AI recruiting platform (hyre.io) where Jan Wilmake joined as a founding/ZZP engineer in July 2026, working on MCP tooling for recruitment
category: Organizations
---

# Hyre

**Hyre** (`hyre.io`) is an AI-powered recruiting platform that provides AI-driven tools for recruitment — including conversation management, candidate pipelines, and integrations with existing hiring workflows. [[Jan_Wilmake]] discovered the company during a job-search session in June 2026 and met founder **Luc van Poll** shortly after.[^x-posts-2026-07-09]

## Company

Hyre positions itself as an AI layer for recruitment agencies, automating conversation management, candidate pipelines, and outreach. It competes with tools such as **Metaview** (AI note-taking for interviews) and **Carv**. As of mid-2026, Hyre was hiring for founding engineering roles.[^x-posts-2026-07-09]

## Jan Wilmake's Role

Jan signed a **ZZP (freelance) contract** with Hyre around **July 5–6, 2026** as a founding engineer, progressing from first contact to signed contract in under four weeks — the fastest cycle of his 2026 job search.[^x-posts-2026-07-09]

His stated ambition at Hyre is to build **"the best MCP for recruitment agencies"**, drawing on his prior Model Context Protocol experience from [[Parallel_AI]], [[ContextArea]], [[installthismcp]], and the open-source `janwilmake/hyre-mcp` repository he built during the interview process.[^x-posts-2026-07-09]

## Public Discussion: Vibecoded Codebases

Shortly after joining, Jan publicly discussed the realities of working with a large AI-generated ("vibecoded") codebase. The thread began with a viral reflection — *"so before ai coding it would take much longer to build a codebase up to like 100k loc... but now its like peanuts but the problem is nobody understands crap"* — which spawned a major debate with 30+ replies from developers including @mattpocockuk, @waincarver, @iwhaleocean, @antirez, and @badlogicgames.[^x-posts-2026-07-10]

He followed up by articulating a three-part stewardship strategy for large AI-generated codebases: (1) prompting habits that increase understanding as a side-effect, (2) a CI/CD process with AI review that keeps complexity in check, and (3) disciplined use of type interfaces as the locus of design decisions.[^x-posts-2026-07-11] This debate is documented in [[Vibecoding_Comprehension_Debate]].

During this period Jan also adopted **Claude Max** (replacing per-token API usage) and highlighted the value of **Claude's sandbox mode** for unblocking a multi-agent workflow.[^x-posts-2026-07-09] [^activity-2026-07-13]

## See Also

- [[Career_Plan_2026]]
- [[Jan_Wilmake]]
- [[Parallel_AI]]
- [[ContextArea]]
- [[Vibecoding_Comprehension_Debate]]
- [[uithub]]

[^x-posts-2026-07-09]: X posts: `x-archive/raw/x-posts/2026-07-09.md`
[^x-posts-2026-07-10]: X posts: `x-archive/raw/x-posts/2026-07-10.md`
[^x-posts-2026-07-11]: X posts: `x-archive/raw/x-posts/2026-07-11.md`
[^activity-2026-07-13]: Activity summary: `x-archive/raw/activity-summary/2026-07-13.md`