Every is hiring a Head of Social. I cloned the application repo this morning to read the job description and ended up POSTing the application thirty minutes later. The whole process was a curl command.
This is the first time I have applied for a job without a resume, a cover letter, or a portal. I don't know what to call it.
What the application looks like
The repo at github.com/EveryInc/apply-head-of-social has two files: JOB.md (the job description) and README.md (the apply instructions). The instructions are a curl command pointing at https://every-apply.vercel.app/api/submit.
Required fields:
role(Head of Social)nameemailsubmission(one skill, workflow, or example of something you built)
That is the entire application. No resume upload. No "tell us about a time you" essay. No form. No recruiter on the other end of an email thread. You link to your work and POST a paragraph.
What I sent
I run a stack of Claude Code skills that drives my personal brand and my agency's content work. The brief asked for one skill or workflow as the example. I picked analyze-reel: an agent that downloads any short-form video from Instagram, TikTok, or YouTube; transcribes the audio with Whisper; extracts the spoken hook, framework, structure, topic, and CTA with Claude; runs the first 5 seconds of the video through Gemini for visual hook analysis; generates a topic embedding with OpenAI; and writes everything to Supabase as one row.
I cleaned up a public version of the repo and pushed it to github.com/cartwrightdigitalmedia/analyze-reel. MIT licensed. Plug-and-play into any Claude Code install.
The submission paragraph that went in the JSON:
I built analyze-reel, a Claude Code skill that watches my videos and my competitors' videos, extracts every relevant data point, and stores them in a Supabase database I query constantly. It is one piece of the content automation system I run in Claude Code, the same system that took me from 0 to 6K followers in 5 weeks with industry-leading conversion rates to my website (2% view-to-click) and email list (6.1% website-to-signup). Full details + MIT-licensed source: https://github.com/cartwrightdigitalmedia/analyze-reel
The repo is the resume. The skill is the proof.
The response
{
"success": true,
"message": "Thanks for applying, Matty Cartwright! Your application for Head of Social has been received."
}
HTTP 200. That was the application.
Why this format makes sense
Every is an AI-native company. The team works with agents every day. The application format is the work itself. They are not asking what you would do with AI. They are watching what you do with it, in the form you would do it. Pointing your agent at their repo to read the job and prepare your submission is the demo.
For an AI-native role, this filters better than a resume could. Anyone can list "experience with LLMs" on a resume. Few people can ship a working agent skill on a public repo with a clean README and a proof artifact tied to real outcomes.
I don't know what this is called
A resume is a resume. A cover letter is a cover letter. A LinkedIn application is a LinkedIn application. What is this? Application-as-API. Curl-resume. The whole format is maybe a year old, maybe younger, and there is no name for it yet.
What I know is that I built the thing I sent in faster than I could have written a cover letter pretending to know how to do the job. The agent did the cloning and the reading. I made the decisions. The repo speaks for itself.