How to answer job application questions with a character limit

The box is a ranking test, not an essay

Pick one claim about yourself, back it with one piece of proof, tie it to something the listing asks for, and cut everything else. The limit forces the ranking: decide which one thing the reader should remember, and write that.

Treat the limit as hard. Forms can differ: some stop you typing at the cap, others may let you paste past it and reject the submission. Count with spaces, and check the form's own counter before you submit, because a pasted line break can count differently from what your word processor shows.

You do not need to fill the box. A reader going through a stack of answers gains nothing from padding, and padding is where filler gets in, so stop when the point is made. A decision rule for what to include at each size:

• Up to about 300 characters: the claim and one proof. Add the tie to the role only if it fits in a clause.
• About 300 to 700 characters: claim, proof, tie. This covers most short-answer boxes.
• 700 characters and up: the same three parts, plus one sentence on how you did it, such as what you tried first or what you decided against.

One claim, one proof, one tie to the role

Each part has a job, and each takes about a sentence.

• Claim: what you did, in one clause. "I led the mobile checkout redesign." Not a trait. Skip "I am a collaborative problem solver"; a reader cannot check it.
• Proof: the cause you found or the number that moved. Every number must be true, and any figure that also appears on your resume must match it exactly, because the next person to read both will compare them.
• Tie: one requirement from the listing, in the listing's own words. This is the sentence that makes the answer yours for this company instead of reusable anywhere.

Which project to use matters as much as how you write it. Take the listing's first requirement and choose the project that speaks to it. If two projects do, take the one with the clearer result. Here is the shape to fill in:

[Claim: what you did, in one clause.] [Proof: the cause you found, or the number that moved.] [Tie: one requirement from the listing, in its own words.]

A worked cut from 733 characters to 500, then to 250

The question is "Tell us about a project you're proud of" and the form allows 500 characters. Suppose the listing says "You find the root cause before you design." Here is an invented first draft of 733 characters. The project and every figure in it are made up for illustration:

I'm proud of the checkout redesign I led last year. I've always cared about making products simple for people, and I'm passionate about solving hard problems with a team. When I joined, mobile users were abandoning the cart, so I started by interviewing nine customers and watching session recordings. We found that the shipping step asked for the same address twice, and that the promo code field sent people off to search for codes. I worked closely with engineering and the PM to ship a one-page flow, removed the duplicate address step, and moved the promo field behind a link. After launch, completed mobile purchases rose 11%. I learned a great deal about collaboration, and I would love to bring that same energy to your team.

Nothing in it is false, so nothing is obviously wrong to cut. Rank the sentences instead, and cut in this order until you fit:

1. Self-description. "I've always cared about making products simple" and "passionate about solving hard problems" are claims with no proof. They go first.
2. The reflection and the closing. "I learned a great deal" and "bring that same energy" say nothing a reader can use. Replace them with the tie.
3. Process narration. "Worked closely with engineering and the PM" is true of almost every shipped project. Keep it only if the role is about that.
4. Setup. Keep the cause, not the backstory of how you came to the project.

What survives is 468 characters:

I led the mobile checkout redesign. Interviews with nine customers and session recordings showed two causes of abandonment: the shipping step asked for the address twice, and the promo field sent people off to hunt for codes. We shipped a one-page flow, dropped the duplicate step and moved promo behind a link. Completed mobile purchases rose 11%. The listing says 'You find the root cause before you design'; here, interviews and recordings came before any redesign.

The final sentence is the tie. It quotes the listing and points back at the evidence, and it replaces both the reflection and the closing.

For a 250 character box, keep the proof and let it imply the claim. The cause and the result are what carry the answer, so the second cause goes, and the tie shrinks to the listing's phrase. This version is 240 characters:

I redesigned mobile checkout after interviews showed a duplicate address step drove abandonment. Removing it and moving promo behind a link raised completed mobile purchases 11%. The listing says 'You find the root cause before you design.'

"Why do you want to work here" without the filler

This is the question where people write the most generic text, because it feels like it needs enthusiasm. It needs one specific fact instead. Spend ten minutes on the company and write down one thing you can point to: a product you have used, a post or changelog you read, or the problem the listing says the team is working on. Then connect it to one piece of your own work.

I use [the specific thing: a product you have used, a post or changelog you read, or the problem the listing names] and [what you noticed about it]. The listing says '[its own phrase]', and in my last role I [one piece of matching work, with its result].

Test the result by swapping in a competitor's name. If the answer still works, it is generic, and it will read the same as every other answer in the stack. If you honestly cannot find anything specific after ten minutes, say less rather than invent admiration. A short, plain answer about the work itself beats praise you do not mean.

Write each project once at three sizes

The same question comes back on form after form, usually at 250, 500 or 1000 characters. Write each of your three best projects once at those three sizes and keep them in a note. The facts in the proof stay the same at every size, and at the smallest size the claim can become implied. Only the tie is new each time, and it is one sentence.

At 1000 characters, the extra room goes to one true detail from your notes on how you did it, placed right after the proof. In the invented checkout example it could be:

I first tried adding a progress bar, then dropped it when the recordings showed people still left at the address step.

Keep the long version as the master and cut from it, in the order above. Cutting down is faster and safer than expanding a short answer, because the long version already holds every detail you have checked, and expanding means pulling new ones from your notes. Before you reuse an answer, re-read the listing and rewrite the tie. If the tie does not fit, pick a different project rather than stretching this one.

Where Lamr can do the first draft

If you want a first draft instead of a blank box, Lamr has one for pasted forms. Paste the block of custom questions from an employer's form into an application, and Lamr drafts answers from your master resume, profile and, if you imported one, your portfolio, respecting each question's character limit. It costs 3 credits for the block, and 1 credit to redraft a single answer. From Claude or ChatGPT over MCP, the tools are answer_application_questions and regenerate_application_answer; see Lamr over MCP and the tailoring page.

Lamr does not invent experience or numbers that are not in your master resume, but you are still the one signing the answer. Read each draft against your resume, check that the tie uses the listing's words, and edit anything that reads like it could fit any company. Lamr does not submit the form or send anything for you.

Before you paste: a checklist

1. The answer makes one claim, with one proof.
2. Every number is true, and any figure also on your resume matches it exactly.
3. One sentence quotes a phrase from this listing.
4. For a "why here" answer, swap in a competitor's name: it should stop working.
5. The form's own counter says it fits, with line breaks included.
6. You saved the answer at its size, so the next form starts from it.