application-form-filler
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseApplication Form Filler
申请表填写技能
When to Use This Skill
何时使用此技能
Use this skill when the user wants to:
- Answer specific questions on a job application form
- Fill out text fields on Greenhouse, Lever, Ashby, Workday, or any ATS
- Write responses to "tell us about yourself" or "why do you want to work here" prompts
- Get clean, copy-pasteable answers to application questions
- Mentions: "fill this out", "what do I write here", "answer this question", "application form", "form field"
当用户有以下需求时使用此技能：
- 回答求职申请表上的特定问题
- 填写Greenhouse、Lever、Ashby、Workday或任何ATS系统上的文本字段
- 撰写“介绍一下你自己”或“你为什么想来这里工作”这类提示的回复
- 获取可直接复制粘贴的申请表问题答案
- 用户提及：“填写这个”、“这里我该写什么”、“回答这个问题”、“申请表”、“表单字段”
Core Principle
核心原则
Application form answers should be direct and specific — not a cover letter crammed into a text box. Each field has a purpose. Answer that purpose clearly, then stop.
The answer should feel like: A real person typed it, not a template was filled in.
申请表的回答应直接且具体——不要把求职信硬塞进文本框里。每个字段都有其用途。清晰地回答该用途即可，点到为止。
回答应给人的感觉： 是真实的人输入的内容，而非套用模板生成。
Before Answering
作答前须知
Always read:
- The job description — mirror its language and priorities
- The candidate's CV/profile — pull real projects, roles, and metrics
- The specific question — answer exactly what was asked, not what you wish was asked
If the user hasn't provided a CV or JD, ask for them before writing.
务必阅读以下内容：
- 职位描述 —— 呼应其措辞和优先级
- 候选人的简历/个人资料 —— 提取真实的项目、职位和数据指标
- 具体问题 —— 严格回答所问的内容，而非你希望被问到的内容
如果用户未提供简历或职位描述，请先索要这些材料再撰写答案。
Question Types and How to Handle Each
问题类型及处理方法
Type 1: Experience/Background Questions
类型1：经验/背景类问题
Examples:
- "How many years of experience do you have with [technology]?"
- "Describe your experience with [domain]"
- "What backend frameworks have you used?"
Format:
[Technology/skill] — [X years]. [One sentence on what you used it for, with a
specific project or context]. [Optional: secondary tools in the same category].Rules:
- Lead with the most used/relevant technology
- Give years honestly — don't inflate
- Anchor every claim to a real project or role
- For "describe experience" questions: 2-4 sentences max, one project per sentence
- If experience is indirect (adjacent domain), say so and pivot to what is relevant
示例：
- “你拥有[技术]相关的经验有多少年？”
- “描述你在[领域]的经验”
- “你使用过哪些后端框架？”
格式：
[Technology/skill] — [X years]. [One sentence on what you used it for, with a
specific project or context]. [Optional: secondary tools in the same category].规则：
- 优先列出使用最多/最相关的技术
- 如实填写年限——不要夸大
- 每项陈述都要结合真实项目或职位
- 对于“描述经验”类问题：最多2-4句话，每句对应一个项目
- 如果经验是间接相关（相邻领域），请说明并转向相关内容
Type 2: Why This Company / What Interests You
类型2：为什么选择这家公司/你对什么感兴趣
Examples:
- "Why do you want to work at [Company]?"
- "What interests you about this role?"
- "Why are you a good fit?"
Format:
[Specific thing about the company/role that's genuinely interesting — not generic].
[How that connects to something the candidate has actually worked on].
[Optional: one line on why this domain, not just this company].Rules:
- Must be specific to this company — no boilerplate
- Research the company before answering if needed
- Connect to real work, not aspirations
- Keep it under 150 words for a form field
- Don't repeat the JD back to them
示例：
- “你为什么想来[公司]工作？”
- “你对这个职位的哪些方面感兴趣？”
- “为什么你是合适人选？”
格式：
[关于公司/职位的具体亮点——而非泛泛之谈].
[该亮点如何与候选人实际参与过的工作关联].
[可选：一句话说明为何选择该领域，而非仅这家公司].规则：
- 内容必须针对该公司——不能使用通用模板
- 必要时先调研公司信息再作答
- 关联实际工作经历，而非空泛的志向
- 表单字段回答控制在150字以内
- 不要重复职位描述内容
Type 3: Portfolio / Work Samples
类型3：作品集/工作样本
Examples:
- "Include any other samples of work you're proud of"
- "Link to relevant projects or repositories"
- "Describe a project you've built end-to-end"
Format:
List projects with one-line descriptions and links. Lead with the most relevant.
[Project Name] ([live URL] | [github URL]) — [one line: what it is and one
proof point]. [Stack if relevant].Rules:
- Only include projects relevant to the role
- Always include links (live demo > GitHub > nothing)
- If the project has paying users or measurable usage, say so — once
- Don't pad with irrelevant projects to look prolific
示例：
- “附上任何你引以为傲的其他工作样本”
- “链接到相关项目或代码仓库”
- “描述一个你从头到尾搭建的项目”
格式：
列出项目，包含一句话描述和链接。优先展示最相关的项目。
[Project Name] ([live URL] | [github URL]) — [one line: what it is and one
proof point]. [Stack if relevant].规则：
- 仅包含与职位相关的项目
- 务必附上链接（演示地址 > GitHub仓库 > 无链接）
- 如果项目有付费用户或可衡量的使用数据，请说明——仅提及一次
- 不要为了显得项目多而添加无关内容
Type 4: Technical Skill Questions
类型4：技术技能类问题
Examples:
- "Which frontend frameworks have you used most extensively?"
- "Rate your proficiency in Python"
- "Describe your experience with cloud infrastructure"
Format:
For open-text fields:
[Primary skill] — [X years]. [Specific use: what you built with it, in what context].
[Secondary skill] — [X years]. [Same].
[Note any relevant gaps honestly].For rating/dropdown fields: pick the honest level — don't optimize for the highest rating if it's not accurate.
Rules:
- Years + context beats years alone
- Acknowledge gaps rather than hiding them
- If asked to rate, rate honestly — inflated ratings create problems in technical interviews
- For stacks you've used but not recently, note it
示例：
- “你最常用的前端框架有哪些？”
- “给自己的Python熟练度打分”
- “描述你在云基础设施方面的经验”
格式：
对于开放文本字段：
[Primary skill] — [X years]. [Specific use: what you built with it, in what context].
[Secondary skill] — [X years]. [Same].
[Note any relevant gaps honestly].对于评分/下拉选择字段：选择真实水平——如果不符合，不要刻意选最高评分。
规则：
- 年限+场景描述优于仅标注年限
- 如实说明技能缺口，而非隐瞒
- 如果要求评分，如实填写——夸大评分会在技术面试中引发问题
- 对于曾使用但近期未接触的技术栈，请注明
Type 5: Open-Ended / "Tell Us About Yourself"
类型5：开放式/“介绍一下你自己”类问题
Examples:
- "Tell us about yourself"
- "Describe your professional background"
- "What are you looking for in your next role?"
Format:
Current role + what you do there (1 sentence).
Relevant prior experience, briefly (1 sentence).
What you're looking for / why this role (1-2 sentences — specific to the company).
Optional: one project or side work that's relevant (1 sentence).Rules:
- Start with current role, not education
- Keep to 100-200 words for most form fields
- End on the forward-looking note (what you want, not where you've been)
- No trait statements ("I'm passionate about...") — just facts and projects
示例：
- “介绍一下你自己”
- “描述你的职业背景”
- “你对下一份工作有什么期待？”
格式：
Current role + what you do there (1 sentence).
Relevant prior experience, briefly (1 sentence).
What you're looking for / why this role (1-2 sentences — specific to the company).
Optional: one project or side work that's relevant (1 sentence).规则：
- 从当前职位开始介绍，而非教育背景
- 多数表单字段回答控制在100-200字
- 结尾聚焦未来（你的需求，而非过往经历）
- 不要用特质描述（“我热衷于……”）——只需陈述事实和项目
Type 6: Situational / Behavioral Questions
类型6：情景/行为类问题
Examples:
- "Describe a time you solved a complex technical problem"
- "Tell us about a project you led end-to-end"
- "How do you handle working across multiple teams?"
Format: Condensed STAR (no labels, just flow)
[Context in one sentence]. [What you specifically did — 2 sentences]. [Outcome
with a metric if possible — 1 sentence].Rules:
- Be specific — name the project, the tech, the team size
- Don't generalize ("I always approach problems by...")
- Keep to 150-250 words
- First-person, active voice throughout
- End with the result, not the lesson learned (save that for interviews)
示例：
- “描述一次你解决复杂技术问题的经历”
- “谈谈你从头到尾主导的一个项目”
- “你如何处理跨多个团队的工作？”
格式： 简化版STAR法则（无需标注，自然叙述）
[Context in one sentence]. [What you specifically did — 2 sentences]. [Outcome
with a metric if possible — 1 sentence].规则：
- 内容要具体——说出项目名称、技术、团队规模
- 不要泛泛而谈（“我总是通过……解决问题”）
- 控制在150-250字
- 全程使用第一人称、主动语态
- 结尾强调结果，而非学到的经验（经验留到面试中分享）
Type 7: Opinion / Vision Questions
类型7：观点/愿景类问题
Examples:
- "Which technologies do you think are most important for the future?"
- "What would you learn if you had unlimited time?"
- "Where do you see AI/[domain] in 5 years?"
Format:
Answer with a genuine opinion. Pick one or two things and explain the reasoning briefly.
Rules:
- Have an actual point of view — vague answers are forgettable
- Ground opinions in domain knowledge or real experience
- Keep to 100-150 words
- Don't hedge everything — commit to a view, acknowledge it's one perspective
示例：
- “你认为未来最重要的技术有哪些？”
- “如果有无限时间，你会学习什么？”
- “你认为AI/[领域]在5年后会发展到什么程度？”
格式：
给出真实观点。选择1-2个方向并简要说明理由。
规则：
- 要有明确观点——模糊的回答容易被遗忘
- 观点要基于领域知识或实际经验
- 控制在100-150字
- 不要模棱两可——明确表达观点，同时承认这只是一种视角
Output Format
输出格式
Always wrap the answer in a plain code block so it's clean to copy-paste:
[Answer text here]If providing multiple answers (one per field), use separate code blocks with a label above each:
Years of React experience:
4 years. Used it across Screenr (agentic hiring SaaS), a Tauri-based POS
system, and several client projects. Also used Next.js where SSR was needed.Describe your backend experience:
...务必将答案包裹在纯代码块中，方便复制粘贴：
[Answer text here]如果提供多个答案（每个字段对应一个），请为每个答案单独使用代码块，并在上方添加标签：
Years of React experience:
4 years. Used it across Screenr (agentic hiring SaaS), a Tauri-based POS
system, and several client projects. Also used Next.js where SSR was needed.Describe your backend experience:
...Length Calibration
长度校准
| Field type | Target length |
|---|---|
| Single-line text | 1 sentence |
| Short answer | 2-4 sentences |
| Long answer / textarea | 100-250 words |
| "Describe your experience" | 150-300 words |
| "Tell us about yourself" | 100-200 words |
| Portfolio / links section | List format, no prose |
When in doubt, shorter is better. Recruiters skim form answers. The goal is to be clear and memorable, not comprehensive.
| Field type | Target length |
|---|---|
| Single-line text | 1 sentence |
| Short answer | 2-4 sentences |
| Long answer / textarea | 100-250 words |
| "Describe your experience" | 150-300 words |
| "Tell us about yourself" | 100-200 words |
| Portfolio / links section | List format, no prose |
拿不准时，越短越好。招聘人员只会快速浏览表单答案。目标是清晰、令人印象深刻，而非面面俱到。
Common Mistakes to Avoid
需避免的常见错误
Repeating the JD:
❌ "I am interested in this role because you are looking for someone to build scalable backend systems..."
✅ "What caught my attention was the real-time constraint — healthcare data at milliseconds latency is a different class of problem than most backend work."
Generic trait claims:
❌ "I am a fast learner who thrives in collaborative environments"
✅ [Just describe the actual work — the traits come through]
Over-qualifying:
❌ "While I may not have exactly 5 years, I believe my experience..."
✅ "The role mentions 5 years — I'm at 3, but the systems I've shipped are production-facing."
Listing without context:
❌ "React, Vue, Angular, Next.js, TypeScript, Node.js..."
✅ "React is my primary frontend framework — 4 years across Screenr and several client projects. Vue and Angular for about 3 years each, mostly dashboards and admin tooling."
Padding to fill space:
❌ Adding projects or experience that aren't relevant just to look prolific
✅ Include only what's relevant to this specific role
重复职位描述：
❌ "我对这个职位感兴趣是因为你们需要有人构建可扩展的后端系统……"
✅ "吸引我的是实时性要求——毫秒级延迟的医疗数据处理是与大多数后端工作不同的问题类型。"
泛泛的特质声明：
❌ "我学习能力强，在协作环境中能充分发挥实力"
✅ [直接描述实际工作——特质会自然体现]
过度解释资历：
❌ "虽然我没有正好5年经验，但我相信我的经历……"
✅ "职位要求5年经验——我有3年，但我交付的系统都是面向生产环境的。"
无上下文的罗列：
❌ "React, Vue, Angular, Next.js, TypeScript, Node.js..."
✅ "React是我主要使用的前端框架——在Screenr和多个客户项目中使用了4年。Vue和Angular各使用了约3年，主要用于仪表盘和管理工具开发。"
凑字数：
❌ 添加无关项目或经历来显得经验丰富
✅ 仅包含与该职位相关的内容