How to Tailor a Tech Application by Hand
Job Search · Tailoring
Everyone tells you to tailor your resume to each job. Almost nobody tells you what that actually takes.
So here is the honest version. This is the full manual process, the same logic a good tailoring system runs under the hood, done by hand with two spreadsheets and a lot of patience. Follow it for one job and you will understand why most people quit after three.
Open a fresh spreadsheet. Let's go.
Step 1: List every skill you have
Not the skills on your current resume. Every skill you have ever used on the job, in a side project, or in the parts of a role that never made it onto the page.
One row per skill. Languages, frameworks, tools, cloud services, databases, testing setups, the CI pipeline you babysat, the dashboard you built that nobody asked for. Be thorough and be honest. If you only touched Kubernetes for a week, write it down and note that it was a week.
This is the tedious part people skip, and skipping it is why their tailoring stays shallow. A real inventory runs long. Most engineers who do this properly land somewhere between sixty and a hundred and twenty rows. Give it an afternoon.
Why this comes first: You cannot tailor from memory. Memory forgets the exact thing this job is asking for. A written inventory is the source of truth you will compare everything against.
Step 2: List every skill the job wants
New sheet. Now read the job description line by line, slowly, and pull out every skill it names or implies.
The named ones are easy. "Five years of Python." "Experience with Terraform." Write those down. The implied ones are where it gets slow. "Comfortable owning a service end to end" is asking for on-call experience, deployment ownership, and monitoring. "Work closely with product" is asking for stakeholder communication. One sentence can hide three skills.
Go through the entire posting this way. Responsibilities, requirements, the nice-to-haves, even the culture paragraph. When you finish you should have a second column, usually twenty to forty rows, of everything this specific role is actually screening for.
Step 3: Line the two sheets up and compare
Put the job's skills next to yours. Go down the job list one row at a time and mark each one.
Green if it is clearly on your inventory and already on your resume. Yellow if you have the skill but it is buried or missing from the resume you are about to send. Red if it is not on your inventory at all.
The green ones are fine. The yellow and red rows are the whole job. Those are the gaps, and the gaps are where the interview is won or lost.
The gap between the posting and your resume is the real work of tailoring.
Step 4: Interrogate every gap
Now the part that actually takes judgment. Go to each yellow and red row and ask yourself one honest question.
Have I really done this, in some form I just never wrote down?
Sit with it. The posting wants "experience with event-driven architecture" and it is not on your resume. But two years ago you wired up a queue so orders stopped getting lost during traffic spikes. That is event-driven architecture. You did it. It just never made the page because nobody told you it counted.
This question has exactly two answers, and you have to be strict about both.
If yes: you have done it, and it matters to this description. That row is now a job. Go to step 5.
If no: you have not done it. Leave it. Do not stretch, do not borrow a teammate's work, do not invent. A tailored line you cannot defend in the interview is worse than a missing one.
Step 5: Turn each real gap into a bullet AND a skill
For every gap you can honestly claim, you do two things, not one.
First, write it as a resume bullet. Real work, real numbers where you have them. The queue example becomes something like: "Designed an event-driven order pipeline with a message queue, cutting dropped orders during peak traffic to near zero." Specific, true, and aimed straight at what the posting asked for.
Second, add it to your skills section as a named skill, so the term the job used and the term on your resume finally match. "Event-driven architecture." "Message queues." The reviewer, and the software that reads your resume before the reviewer does, is scanning for those exact words.
Bullet for the human. Skill keyword for the scan. You need both, because your resume gets read by both.
Step 6: Now do that for every gap. Then every job.
Back to the top of your compare sheet and down through every remaining yellow and red row. Same honest question, same two answers, same bullet-and-skill for every real one.
When you finish, you have one genuinely tailored application. Trim it to two pages, check that nothing important fell off, and send it.
Then remember: you wanted to apply to twelve of these. That afternoon of inventory carries over, which helps. But steps 2 through 6, the read, the compare, the gap check, the writing, start again from scratch for every single posting. A different job wants different things, hides different implied skills, and opens different gaps.
2
spreadsheets you rebuild the second sheet of for every job
20-40
skills to extract and gap-check per posting
45+ min
per honest, tailored application once your inventory exists
The process is right. Doing it by hand is the problem.
None of the steps above are wrong. That is genuinely how tailoring works, and doing it by hand will teach you more about your own experience than any template. The trouble is the math. Real tailoring costs most of an hour per job, and the roles you want fill up in days. Speed and quality pull against each other, and quality usually loses.
So I built the same six steps into my Apply Kit, and handed the grind to a machine.
You build your master resume once, and that becomes the inventory from step 1, kept in one place instead of a spreadsheet you have to maintain. Then you paste in a job posting. My system reads it for the skills it names and the ones it only implies, compares them against your master, and finds the gaps, which is steps 2 and 3, in seconds.
For step 4 it does the one thing software should never do alone: it asks you. When it spots a gap, it hands you a short list of clarifying questions. Have you actually done this? Your honest answer, in your words, is the only thing that fills the gap. Say yes and it weaves that experience into a bullet and adds the matching skill, which is step 5, for every gap at once. Say nothing, and nothing gets invented. It only ever works with what is true, because you are the one who has to defend it in the interview.
Same logic, different clock: The manual version is an afternoon per handful of jobs. The Kit preps a tailored, honest application in a few minutes, so you can send it while the posting is still fresh.
The spreadsheets taught you why tailoring matters. Now you never have to open them again.
See how the Apply Kit turns a job posting into a tailored application.