# Application form fields Free text typed into a portal, often under a character or word limit, with no formatting. It applies when a posting or portal asks for: - a self-introduction or "tell us about yourself" paragraph - structured project entries (name, role, start and end date, description) - a short pitch under a hard character limit ("why you, in 140 characters") - motivation questions ("why this company") - competency questions with a word cap ("describe a time you...", 200 words) Offer to draft them when the posting shows such fields; draft only on yes. ## The governing rule Every claim is already defensible from the career master and consistent with the CV and letter sent for the same role. A form field selects from what is true and arranges it for the question. It never introduces new claims, inflates scope or fills space. All rules in `writing-style.md` and `cv-rules.md` apply. ## Counting **Count characters and words with code in the sandbox. Never estimate.** Portals truncate silently, often mid-word. State the count next to every answer, with and without spaces where the portal is unclear. ## Self-introduction (usually 100-200 words) 1. Current status: what the candidate is doing now. 2. The strongest piece of evidence, with its number and scale. 3. One line of trajectory, if a pivot or specialisation is genuinely interesting. 4. What they want next, tied to this employer's actual work in the last sentence. Lead with evidence, not chronology. One version per role type, labelled. Supply a trimmed variant and name the sentence to cut first. ## Project entries - **Name**: a descriptive project name ("Warehouse demand forecasting platform"), not the employer. Name a client only where the career master states the relationship and the pitfalls allow the name. - **Role**: the candidate's role on that project, which may be narrower than the job title. Never upgraded. - **Dates**: the project's dates, not automatically the employment dates. Narrow them only when the career master gives the project's start; never invent a boundary. - **Description**: 100-150 words: what the system did and who used it, the hardest problem and how it was solved, the outcome with its number. Supply a ~60-word short version too. - **Ownership**: a project entry with the candidate's name on it reads as owning all of it. Where they contributed, say so inside the description. ## Hard character limits These reward a specific situation over an adjective. Most applicants submit adjectives, so a concrete situation stands out. 1. Pick the most distinctive true thing: a number, an unusual combination of backgrounds, or a problem that maps onto the employer's own problem. 2. Draft **4-6 variants** at different angles. 3. Count each with code. 4. Present all variants with their counts, recommend one, and say why. Prefer the one that maps the candidate's problem onto the employer's. ## Output - A header naming the employer and the role. - Each field labelled, with its limit and measured count. - Short variants where the limit may be tighter than stated. - **NOTE TO SELF** blocks, clearly marked as not for pasting: scope reminders and answers to questions the text invites. - A dates quick reference so date fields stay consistent. ## Checklist - [ ] Every claim traces to the career master; no pitfalls entry violated - [ ] No contradiction with the CV or letter for the same role - [ ] Ownership scoped on contributory work - [ ] Counts measured with code, within the limit - [ ] In-progress qualifications described as in progress - [ ] NOTE TO SELF blocks marked as internal