An application a person will read

Why the button is not enough

This is not a study, and there are no hiring statistics here. It is an order of steps we believe works, and texts to start from.

A one-click application costs the candidate nothing, so a posting gets a lot of them. The company can’t read them all with care, and it defends itself: a questionnaire before you apply, a take-home test before the first conversation, a template rejection or plain silence.

The candidate sees silence and decides to apply more. There are more applications, they get read even less, and the circle closes. Any job board with a quick-apply button works this way: the problem is not the board but the price of an application.

The way out is fewer applications, not more. An hour on a posting that fits you instead of a minute on every posting in the list. That hour goes into three things.

• A resume for the posting — so the reader sees at once that you have done what they need.
• A message to a person — so the resume gets opened at all.
• A follow-up — because first messages get lost, and that is not a rejection yet.

Step 1. Build a resume for the posting

One resume for every job answers the question “who am I”. The company is asking something else: has this person done what we need? A resume built for the posting answers that second question.

Read the posting as a list of questions. What comes first, what is repeated, what is called required — that is what they want to see. Write down five to seven requirements.

Find your answer to each requirement: a bullet, a project, a skill. Move what answers a requirement higher. Take what has nothing to do with this job out of this version; it stays in your base resume.

Use the posting’s words where they are true. If your resume says “set up deployments”, the posting says “CI/CD”, and it is the same thing, call it what they call it.

Fit it into two pages, or one early in your career. In a long resume the reader never gets to the part that matters.

Add nothing that didn’t happen. Positioning is choosing and ordering, not inventing. Invented experience comes out at the interview at the latest, and after that the real experience isn’t believed either. If the posting asks for something you haven’t done, it is not in the resume.

This is the part Tuned does: it builds a version for the posting from your base resume, uses only what you wrote, and asks about what the base doesn’t mention. You can check your resume’s format for free, with no account.

Step 2. Apply, then write to a person

First, the regular application. Wherever the job is posted: on the job board or in the form on the company’s site. Many companies track candidates in their own system, and the recruiter will ask you to apply there anyway. But don’t stop at that.

Then find a person. Any of these three will do.

• The company’s recruiter. On LinkedIn, search for the company name plus “recruiter” or “talent”. Sometimes the recruiter is named in the posting itself.
• The hiring manager. The person who needs someone on the team: a head of department, a team lead. Your application matters to them more than to anyone.
• The careers mailbox. An address like jobs@ or careers@ on the company’s site, in the careers section.

Write three or four sentences. Which role you applied for, why you fit — one fact with a number — and what you are asking for. Attach the resume as a file.

To a recruiter. Hi [name], I’m writing about the [role] position — my application is already in your system. For the past [N] years I’ve worked on [what], most recently [one result with a number from your resume]. I’m attaching the resume I prepared for this role. Could you tell me who is handling this opening and what the best next step is?

What not to do. Don’t retell the resume — it is attached. Don’t write “take a look, maybe I’m a fit” without naming the role: the reader would have to work out where to put you. And don’t send the same text to ten people at one company — they talk to each other.

Step 3. A referral: ask for a conversation, not a favor

An employee referral is a short way to a conversation: your resume is brought in by someone the company trusts. You don’t need to know anyone at the company for that. But asking a stranger for a referral in the first message is not worth it: they can’t vouch for someone they don’t know.

Who to write to. Someone you would work with: an engineer or a designer on the same team, a team lead. One person, not everyone on the list.

What to ask for. Fifteen minutes, or an answer to a couple of questions about the team. Say why you are writing to them in particular: their talk, a post, an open-source project, a shared stack. If the conversation goes well, they will offer the referral themselves — some companies pay employees for one.

To a future teammate. Hi [name], I read your [talk, post, project] — [what exactly was useful]. I’m a [role] with [N] years in [what], and I’m applying for the [role] position on your team. Could I ask you a couple of questions about how the team works? Fifteen minutes or a written reply would be plenty. My resume is attached so you know who is writing.

No reply? Let it go. This person owes you nothing, and hiring is not their job. One message, no follow-ups.

Step 4. Follow up

Silence is not always a rejection: the message was read between two meetings and forgotten. With a recruiter or a hiring manager, following up is fine and worth doing.

• The first follow-up comes a week later. In the same thread, as a reply to your own message, so nobody has to work out who you are.
• The second, one or two weeks after that. With something new: you finished a project, your post came out, you now have a date by which you need an answer.
• There is no third. Two follow-ups with no answer are an answer. Note it down and move on.

Follow-up. Hi [name], I’m following up on my note about the [role] position — I’m still very interested. Happy to resend my resume or answer questions in writing. Any reply helps, including “not a fit right now”.

What should make you think twice

Some signs are visible before you apply. They don’t say the company is bad. They say how its hiring works, and whether it is worth your hour.

• A questionnaire with dozens of questions before any contact. You are asked to spend time before anyone has spent any on you.
• A take-home test before you have talked to a person. A test makes sense once both sides know they agree on the main things: the role, the pay, the way of working.
• A rejection minutes after you applied. That is hardly enough time to read a resume.
• A posting with no company name. Nobody to write to and nothing to check.

If the role is still yours, start with a message to a person, as in step 2, not with the questionnaire.

Keep a list

With ten applications of three parts each, you can’t hold them in your head. A spreadsheet with six things per application is enough.

• The company and the role, with a link to the posting.
• When you applied.
• Who you wrote to, and when.
• When to follow up.
• Which version of the resume you sent.
• How it ended.

The resume version is not a formality: at the interview you will be asked about the resume they have, not the one you remember.

What Tuned does here

The first part of the application, and the texts for the second.

• A resume for the posting. Built from your base resume: only what you wrote, every change shown, fitted to the page count you pick.
• A letter and a message to the recruiter. Written from the same resume: an email with a subject line, the fields for LinkedIn Easy Apply, a message of three or four sentences.

The rest is yours. Tuned doesn’t look for the person to write to and doesn’t keep a list of applications. It doesn’t write the message to a future teammate or the follow-up — the templates for those are above. And it doesn’t apply for you: there is no auto-apply.

The free plan gives up to 4 tailoring runs every month, with no card; a letter costs a fraction of a run. The first run is written by the larger model, as on Pro, and later ones by a lighter model.

Questions