It's less about "AI said this guy" and more about proof, identity, and hopefully making getting seen as a candidate easier. Right now the signal/noise problem is progressively making that more difficult.

We have seven other companies involved that are listed on the website and have provided feedback for general use-cases -- given adoption curves are super hard, early traction we have around OJCP is encouraging to me. A lot more to do, but any help or ideas are greatly appreciated.

I'm chatting with other OSS organizations to help make sure this lands in no specific organizational control.

Agents are applying to jobs for people right now, with progressively more volume, and there's nothing built for it. So they scrape career pages and fight ATS forms with Playwright/Browser Use, which breaks constantly (or they get bot blocked). Employers get buried in applications that don't fit, candidates hear nothing back, and the resume is now an AI-written thing that another AI scores (which breaks the existing model entirely, btw).

OJCP is MCP tools for search and apply, a manifest at /.well-known/ojcp.json so agents can find providers, and schemas that extend schema.org instead of replacing it. The playground on the site is a live MCP endpoint, so you can throw calls at it right now.

Why a spec at all when models keep getting better at figuring things out? Inference can't produce authorization. An agent can work out what a form wants. It can't establish that someone consented to this specific submission, and then employer has no way to verify who's calling. So TL;DR a more capable agent is also a more capable impersonator.

In this model, trust runs both direction. Agents sign requests using the same method that CloudFlare and OpenAI are already using, providers sign their manifests, agents can check against a JWKS, and trust tiers cap how much candidate PII can go to a given provider. Validation happens at consent, so browsing costs nothing and you only pay the verify when the interaction occurs.

I'm the CTO of Recruitics (job advertising) and spent time at LinkedIn before that, so I've been at the intersection of hiring and job search for a while and have felt the pain of both sides.

Happy to answer any questions!

Comments URL: https://news.ycombinator.com/item?id=49273922

Points: 39

# Comments: 10

Comments URL: https://news.ycombinator.com/item?id=49259583

Points: 11

# Comments: 2

I think "the context" the author defines also includes harder to unlock peripheral components that makes software products in 2026 defensible.

For example, security is getting harder not easier. Enterprise trust rides on needing to have up-to-date knowledge on data regulation as well.

Relationships, brand maturity, discovery; all of that becomes rarified as we continue to reduce the actual product launch curve -- but also the "harder to do" hygiene stuff that takes you from a "I vibe coded this in two days, good luck" to a "your successful company can count on us" type of hardening has become progressively more of a baseline requirement.

Almost felt a bit *uncanny valley* for what "natural" conversation is supposed to be like. If the "uh huh" isn't timed correctly, it'll feel like a zoom call with lag.

I fear a world where critical software is stood up with increasingly non-human governed abstraction because it [seems like it] works.

Software engineers as the review terminal in a conveyor of business-led code mass production... coming to a company near you?

Been playing with GLM 5.2 in different contexts. It's less good if you don't max out thinking, but as xhigh it's been able to solve most problems I was throwing at Opus in the about the same amount of time (via OpenRouter).

Wild time to be alive.

Having my engineers swap over to it from Claude has garnered very little complaint. The lack of multi-modality is a limitation, but using minimax m3 for that isn't super inconvenient.

I remember making games ten years ago, and it was such a tedious and painful process. This is effectively lightning in a bottle even at a fraction of it's capability.

The next 12 months will be wild (assuming we don't have Chinese models banned by then in the US).

Not exactly saying this is the reason for their sell, but I'd imagine a lot of professional musicians are feeling the desire to exit the industry.

[1] https://www.npr.org/2026/05/02/nx-s1-5804489/music-listeners...

Praying to the security gods.

It seems like we've have non-stop supply chain attacks for months now?

The Sora sunsetting marked a big shift towards enterprise focus and meeting Anthropic on the enterprise battlefield, but almost all engineers I work with or know are using Claude at this point exclusively.

Anyone seeing differently?

Looked at the "how it works" -- is there a way to manually specify leaf element sizing? Thinking about dynamically sized elements that don't have markup-level specified sizes yet via bounding boxes.