TL;DR: When an Upwork job post says something like "start your proposal with the word banana" or "mention your favourite colour so I know you read this", the client is filtering out freelancers who did not read the post. Put the requested word or answer in the very first line of your proposal, exactly as asked, then move straight into the client's problem. Missing it usually gets your proposal skipped without being opened, no matter how good the rest is. Treat the instruction as a good sign about the client, because it means they read proposals carefully, but read the whole post before you comply, since a small number of posts use the same trick to pull you off the platform or into a scam.
You have probably seen a line like "Put the word PINEAPPLE at the top so I know you are human" halfway down an otherwise normal post. This guide covers why clients do it, the forms it takes, exactly where to put the answer, and the cases where an instruction in a job post is a warning rather than a test.
Why clients hide a code word in the job post
Popular Upwork posts can collect a long list of proposals quickly, and a large share of them are generic. Some are copied templates, some are mass-produced by tools, and some are from freelancers who skimmed the title and applied. The client has to get through all of them, and the proposal list only shows the first few lines of each one before they click in.
A code word is a cheap filter for that problem. If the proposal does not start with the word, the client knows without opening it that the sender did not read the post. That lets them discard a big part of the list in seconds and spend their attention on the proposals that followed the one simple instruction they gave. A client who writes a detailed brief also wants someone who reads detailed briefs, and this is the cheapest way to check.
Common forms the instruction takes
The wording varies, but most of these instructions fall into a few patterns:
- A literal word or phrase. "Start your proposal with 'blue whale'." The simplest version, and the easiest to get right.
- A short question. "What is the first thing you would check on our checkout page? Answer that in your first sentence." This is a code word and a skill test at the same time.
- A personal detail. "Tell me your favourite movie at the start." Mostly a reading check, sometimes a way for the client to get a feel for the person.
- A formatting rule. "Write your proposal in under 100 words" or "Do not include links." Easy to miss because it does not look like a test.
- A reference to the post itself. "Tell me which of the three tasks above you would do first." This one checks whether you understood the brief, not just whether you saw it.
Some posts include more than one. Read to the very end of the description before you write anything, because the instruction is often placed near the bottom on purpose.
Where to put the answer
At the very start of the proposal. Not in the second paragraph, not after a greeting, and not in a postscript.
The reason is mechanical. Clients scanning the proposal list see a short preview of each cover letter, and that preview is where most of them look for the word. If it is in the opening line, you pass the filter before the client has clicked anything. If it is buried lower down, a client working quickly may never see it, which is the same outcome as leaving it out. How long should an Upwork proposal be covers why the preview carries so much weight in general.
A clean way to do it:
Blue whale. You mentioned the checkout drops users on mobile after the shipping step, and that usually comes down to one of two things...
The word, then straight into the client's problem. No apology, no joke about it. The client asked for it, you gave it, and now the proposal reads like any strong proposal.
If the instruction is a question, answer it properly in the first sentence or two. A thoughtful one-line answer to "what would you check first?" can do more work than the rest of the proposal combined, because it is the first evidence the client sees that you know the job.
Spell it exactly as written
Use the word or phrase the way the client wrote it. If they asked for "PINEAPPLE", write PINEAPPLE. Some clients search the proposal list for the exact string, and a creative variation can fail that search. Once, at the top, is enough; repeating it reads as trying too hard.
What happens if you miss it
Usually nothing visible. The proposal simply does not get opened, sits there until the job closes and ends up in your archived proposals with no feedback. Declined vs archived proposals explains why that silent outcome is the most common one, and missing an instruction is one of the quieter causes of it.
The Connects are spent either way. If you notice the miss right after submitting, your only real option is withdrawing and resubmitting, which costs Connects again. How to follow up on an Upwork proposal covers when that trade is worth making. For a fresh post with a client who clearly reads carefully, it sometimes is. For an older, crowded post, it usually is not.
Code words and AI-written proposals
A lot of the recent growth in these instructions is a response to proposals written by tools. Clients have noticed that many cover letters now read the same way, and a simple reading check is one of the few filters they control.
Some posts go further and include instructions aimed at the tool rather than the person, for example a line asking AI tools to include an unrelated word or mention a specific topic. A freelancer who pastes the whole post into a generator and sends the output without reading it ends up with that word in their proposal, and the client knows exactly how it was written.
The practical lesson is the same whether you use AI or not. Read the post yourself, decide which instructions are meant for you, and check your final proposal against the post before sending. Should you use AI for Upwork proposals covers where tools help and where they quietly cost you jobs, and this is one of the clearest examples of the second.
When an instruction in a job post is a red flag
Most code-word instructions are harmless. A few instructions that look similar are not, and the difference matters.
Be cautious when the post tells you to:
- Contact the client outside Upwork. "Message me on Telegram with the word X" or "email your proposal to this address" is not a reading test. Moving the conversation off the platform before a contract exists is a common setup for scams, and it can also put your account at risk.
- Include personal or payment details. No genuine reading test needs your phone number, ID or bank information.
- Visit a link and do something there. Installing software, signing up somewhere or "verifying" yourself on an outside site is not part of applying for a job.
- Send a large piece of free work as the "test". Answering a question in one sentence is a reading check. Producing a finished deliverable is unpaid work, which Upwork free test projects covers in detail.
If an instruction asks you to leave Upwork or hand over something sensitive, skip the job. How to spot Upwork job scams walks through the patterns, and working with an Upwork client outside Upwork explains the rules around off-platform contact.
What a code word tells you about the client
A genuine reading check is generally a good sign. It suggests the client:
- Wrote the brief themselves and cares whether people read it.
- Has probably been burned by generic applicants before and knows what they want.
That does not replace the usual checks. A careful client can still have no payment method, no hiring history or a budget far below the work. Look at the client panel before you spend anything, as covered in how to spot good Upwork clients and Upwork payment verified meaning. But between two otherwise similar posts, the one with a reading check is often the one where a well-written, specific proposal has the better chance of actually being read.
It also shrinks the real competition: if many applicants skip the instruction, you face fewer serious proposals than the count in Upwork "Activity on This Job" suggests.
Code words, screening questions and templates
Code words are separate from Upwork screening questions, which the client sets up as a form you fill in alongside the cover letter. Both can appear on the same job. Answer the screening questions in their own fields, and still put the code word at the top of the cover letter, because that is where the client told you to put it.
If you work from a template, write the first line fresh for every job, which is exactly where a code word lives. The Upwork proposal template guide covers how.
Reach the careful clients early
Clients who add reading checks tend to read the first good proposals closely, which makes being early and being accurate a strong combination. The hard part is seeing those posts while they are fresh, without refreshing Upwork all day.
Upwork Scout watches Upwork continuously, filters jobs on your floors for payment verification, client spend, hire history and proposal count, and sends you the ones that pass while they are still new. You get time to read the full post, catch the instruction, and write a proposal that opens with exactly what the client asked for. The free tier lets you set up your filters and start receiving matched jobs today.
The bottom line
A code word in an Upwork job post is the client telling you how to get past their first filter. Put it in the first line, exactly as written, and then get straight to their problem. It costs you a few seconds and removes one of the most common silent reasons proposals are never opened. Just make sure the instruction is a reading check and not a request to leave the platform, and treat a client who adds one as someone likely to read your proposal properly, which is exactly the kind of client worth spending Connects on.