10 Unusual Ways to Apply for a Job That Beat the Standard CV

The form-and-CV application is a useful default, in the way that white rice is a useful default. It nourishes nobody and offends nobody. Once in a while, though, candidates apply in a way that is so specific, so unusually thoughtful, that the hiring manager forwards it to two people before opening the attachment. The reason these moves work — when they work — is not cleverness. It is that the candidate did something a real human, with a real opinion about a real company, would do.

What follows are ten patterns that fit that description. They are presented as worked examples rather than individual anecdotes, because the value is in the shape, not in any particular person’s story. Read them as templates — and then read the pattern analysis at the end, because that is where the practical lesson lives.

The ten

• The landing page. A candidate applying to an early-stage company ships a mock product landing page for a feature they think the company should build — complete with mock pricing and a waitlist form. A day or two of work, no permission asked. The application is the page.
• The 'we're not hiring' reply. A candidate receives the standard we're not hiring right now email and replies with a one-page memo on the team's single most visible problem — typically one the company has openly mentioned on its own blog or in press. The reply is the application.
• The 90-second Loom. Instead of a cover letter, a candidate sends a 90-second screen-recorded walkthrough of their thinking on the role. No editing, no music, no graphics. Just a person explaining, with their face on the corner of the video, why they're the right fit. The asymmetry — easy to record, easy to watch — is the whole point.
• The job description that doesn't exist. A candidate notices a gap in the org chart of a company they follow and writes the JD they think should exist — outcomes, scope, what a great year would look like — and applies to that. Sometimes the company has been drafting something similar internally; sometimes the candidate has handed them an idea.
• The rejection reply. After being rejected at final stage, a candidate sends a short, gracious note with one specific thing they'd have done differently in their first month, based on what they learned in the interviews. The reply costs nothing and survives the calendar — when a new opening surfaces, the candidate is already top of mind.
• The pricing teardown. A candidate sends a cold email containing a one-page teardown of the company's pricing page — three things that are working, two that aren't, one hypothesis to test. No CV in the first email. The teardown is the audition.
• The first-month plan, on paper. A candidate brings a printed one-page plan for their first month in the role to what was supposed to be an informal coffee chat. Bullet points, prioritised. The conversation tends to stop being a coffee chat and start being an interview.
• The working clone. An engineer applying to a B2B SaaS rebuilds part of the company's onboarding flow as their portfolio — same problem, slightly different opinions about the UX. The framing is not "mine is better" but "this is how I think about your problem."
• The mock memo. A candidate applying to a startup writes a memo from the perspective of the person doing the role — three months in, what has changed, what hasn't, what they would recommend the team stop doing. Two pages. The memo demonstrates the work in advance of being asked.
• The proof-of-work thread. A candidate publishes a public post or thread doing the thing the role would ask them to do — a marketing analyst doing a teardown of three competitor funnels, in public, before applying. By the time the application lands, the hiring manager has already seen the work.

What every one of these has in common

Reading them back-to-back, it is tempting to read them as cleverness. They aren’t. Cleverness is the candidate who sends a CV embedded in a haiku. Nobody hires the haiku person. What works in this list is plainer, and once you see it, you can’t unsee it.

Every one of these patterns is one-line specific. You could describe each one in a sentence to a friend at dinner without losing the point. They built a mock landing page for a product the company hadn’t shipped. They replied to a rejection with one specific first-month idea. That specificity is the whole game. The reason the standard cover letter fails is that you could not describe it in a sentence at dinner without sounding bored. (We dig into this in more detail in the four-sentence cover letter piece.)

Every one of them is low-effort to consume on the recipient’s end. None of them ask the hiring manager to read four pages of dense reasoning. A 90-second video. A one-page memo. A two-page mock memo. A working prototype someone can poke around in for five minutes. The candidate did the work; the hiring manager gets the payoff inside the time it takes to drink half a coffee.

And every one of them is tied to a real bet on a real company problem. Not a generic statement about being passionate. A specific thing the candidate noticed that the company is actually dealing with — a pricing-page issue, a missing role, a clunky onboarding flow, a competitor gaining ground. The bet might be wrong. That doesn’t matter. The fact that the candidate made a bet at all is the signal.

Where this fails

You will notice the list is heavy on startups, agencies, scale-ups, and creative functions. That is not coincidence. The weird-application playbook works in inverse proportion to the seniority of the role and the conservatism of the industry.

The boring playbook can absolutely win in the conservative industries. It is just a different game — a tight CV, a precise cover letter that mirrors the JD, and a referral if you can manage one. The weird applications win in environments where the hiring manager is allowed, structurally, to be surprised. If the company has a thirty-step competency framework, that window is closed before you reach for the Loom button.

What to take from it

If you are applying to a place where this playbook might land, the smallest version of it is this: pick one specific thing about the company you’d want to work on, and put one paragraph about it at the top of your application. Not in the CV. In the email. “I noticed your onboarding has a hand-off step between two products that seems to be where users churn. If hired, the first thing I’d want to test is X.” That’s it. That’s the whole trick, in twenty-eight words.

The patterns above just take that paragraph one step further. The nerve is not optional. The specificity is.

For the companion pieces, the four-sentence cover letter covers the minimum-viable version of the same move, and the no-cover-letter-field piece explains where to put the paragraph when the form doesn’t ask for one. If you’re applying via the recruiter pipeline, the Monday-morning inbox piece is the companion to this one — it explains why specificity wins so reliably in the first cut.