job-application

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Job Application Skill

职位申请技能

Use this skill for Zaid's software job search and application work. The skill turns a job description into a careful application packet, not a generic resume dump.

本技能用于Zaid的软件职位搜索与申请工作。该技能会根据职位描述生成精心准备的申请包，而非通用简历的堆砌。

Operating Goal

操作目标

Every run should end in one of these concrete outcomes:

```
Submitted
```
: application accepted by the direct company/ATS site.
```
Prepared, not submitted
```
: resume/packet ready and final submit intentionally paused.
```
Blocked
```
: exact blocker recorded with the next required user action or source fact. This does not count toward a requested application count.
```
Skipped
```
: role/company rejected by a clear rule before resume work begins. This does not count toward a requested application count.

Do not drift into broad job browsing after an

apply

candidate is found. Work the pipeline until the role is submitted, blocked, prepared, or skipped. If the user requested multiple applications, continue sourcing until the requested number of countable outcomes is reached.

每次运行都应达成以下具体结果之一：

```
已提交
```
：申请被目标公司/ATS系统接收。
```
已准备，未提交
```
：简历/申请包已就绪，且有意暂停最终提交。
```
受阻
```
：记录具体阻碍因素及下一步所需用户操作或关键信息。此状态不计入请求的申请数量。
```
跳过
```
：在开始简历工作前，因明确规则拒绝该职位/公司。此状态不计入请求的申请数量。

找到目标申请职位后，不要转向宽泛的职位浏览。推进流程直至该职位状态变为已提交、受阻、已准备或已跳过。若用户要求提交多个申请，持续寻找合适职位直至达到要求的有效结果数量。

Requested Count Rules

请求数量规则

When the user asks to apply for a number of jobs, such as "apply for 3 jobs":

The number means successful application targets, not inspected links.
Count only
```
Submitted
```
roles toward the requested application number.
Do not count
```
Prepared, not submitted
```
,
```
Blocked
```
,
```
Skipped
```
, stale, duplicate, paywalled, archived, LinkedIn-only, or no-direct-route roles.
Keep sourcing replacement roles until the requested submitted count is reached. Do not stop just because the first candidates failed gates.
If the user did not provide job links, source new roles from eligible first-party company pages and direct ATS postings. Do not use old tracker entries as the candidate pool unless the user explicitly asks to resume old applications.
Use the tracker/history only to detect duplicates, resume known prepared applications when explicitly requested, and avoid repeating blocked work. Do not use previous tracker entries as today's job list unless the user asks to resume them.
If a LinkedIn page does not expose a direct company route, use Chrome to inspect the live page when available. If the direct route still cannot be verified, skip that lead and continue sourcing.

Report progress as counts, for example:

1 submitted, 1 prepared, 4 skipped/blocked, still sourcing 1 more

当用户要求申请一定数量的职位（例如“申请3个职位”）：

该数量指成功提交的目标数量，而非查看的链接数量。
仅将
```
已提交
```
的职位计入请求的申请数量。
```
已准备，未提交
```
、
```
受阻
```
、
```
已跳过
```
、过期、重复、付费墙限制、已归档、仅LinkedIn渠道、无直接申请路径的职位不计入数量。
持续寻找替代职位直至达到要求的提交数量。不要因首批候选职位不符合要求就停止。
若用户未提供职位链接，从符合条件的官方公司页面和直接ATS发布信息中寻找新职位。除非用户明确要求恢复旧申请，否则不要将旧跟踪记录作为候选池。
跟踪记录/历史仅用于检测重复项、在明确要求时恢复已准备的申请，以及避免重复处理受阻的工作。除非用户要求恢复旧申请，否则不要将之前的跟踪记录作为当前的职位列表。
若LinkedIn页面未显示直接的公司申请路径，在可用时使用Chrome查看实时页面。若仍无法确认直接路径，跳过该线索并继续寻找其他职位。

以计数形式报告进度，例如：

已提交1个，已准备1个，已跳过/受阻4个，仍在寻找1个

。

Candidate Failure Recovery

候选职位失败处理

Failed gates are candidate-level failures, not run-level completion.

If a role fails company/source, direct route, live posting, duplicate, fit, form, or eligibility gates, mark that role skipped/blocked in the trackers and immediately source a replacement.
Do not return to the user with only failed candidates when the user requested an application count.
Treat user-provided links as seed candidates unless the user says "only apply to these exact jobs." If all seed candidates fail and the user asked to apply for a count, continue with fresh first-party company/ATS roles.
Before saying no credible eligible roles remain, search beyond the failed candidates using first-party company career pages and common ATS boards. For each remaining requested submission, inspect multiple fresh leads, not just one replacement.
A run may end below the requested submitted count only when a real hard blocker remains after replacement sourcing, such as unavailable browser tools, login/captcha/verification, required legal/compensation answers, or no eligible live direct routes after a documented search.
If the run ends below the requested submitted count, say
```
not complete
```
, report the exact submitted count, list blockers, and state what must happen next. Do not present skipped/blocked work as done.

候选职位不符合要求属于单个职位的失败，而非整个运行流程的完成。

若某职位不符合公司/来源、直接路径、有效发布、重复匹配、岗位适配、表单填写或资格要求，在跟踪记录中标记为已跳过/受阻，并立即寻找替代职位。
当用户要求申请一定数量的职位时，不要仅向用户返回不符合要求的候选职位。
除非用户明确表示“仅申请这些特定职位”，否则将用户提供的链接视为初始候选职位。若所有初始候选职位都不符合要求，且用户要求申请一定数量的职位，继续从官方公司/ATS职位中寻找新的候选职位。
在声称没有可信的符合条件的职位之前，要在不符合要求的候选职位之外，通过官方公司职业页面和常见ATS平台进行搜索。对于每个仍需提交的申请，查看多个新线索，而非仅一个替代职位。
只有在寻找替代职位后仍存在实际硬阻碍（例如浏览器工具不可用、登录/验证码/验证要求、必填的法律/薪酬问题，或经记录搜索后无符合条件的实时直接申请路径）时，运行流程才可在未达到请求提交数量的情况下结束。
若运行流程未达到请求提交数量，需说明
```
未完成
```
，报告实际提交数量，列出阻碍因素，并说明下一步必须采取的行动。不要将已跳过/受阻的工作视为已完成。

Apply Means Live Submission Attempt

“申请”意味着尝试实时提交

If the user says

apply

, do not stop at resume creation, packet preparation, or tracker updates.

Try to open and operate the live application route using the browser tool priority below.
Use Chrome first for LinkedIn, authenticated pages, company careers pages, ATS forms, and final submission.
If Chrome is unavailable or cannot operate the page and the user allowed fallback, try the built-in Browser.
Use Computer Use when a native file picker, desktop auth prompt, upload control, Microsoft Word/PDF export, or visual form interaction blocks browser-only progress.
Do not tell the user to manually open links unless all allowed tools are unavailable or the site requires a human-only step such as login, captcha, verification, compensation/legal answer, or final confirmation that the user has not pre-approved.
```
Prepared, not submitted
```
is allowed only after a real live route attempt, a generated resume/packet, and a specific blocker or intentional user pause.
If the model cannot access Chrome, Browser, or Computer Use in the current session, it must say that clearly before preparing applications and must not imply it applied.

若用户说“申请”，不要在简历创建、申请包准备或跟踪记录更新阶段停止。

尝试按照以下工具优先级打开并操作实时申请路径。
对于LinkedIn、需认证的页面、公司职业页面、ATS表单及最终提交，优先使用Chrome。
若Chrome不可用或无法操作页面，且用户允许 fallback，尝试使用内置Browser。
当原生文件选择器、桌面认证提示、上传控件、Microsoft Word/PDF导出或可视化表单交互阻碍仅靠浏览器推进流程时，使用Computer Use。
除非所有允许的工具都不可用，或网站需要人工步骤（例如登录、验证码、验证、薪酬/法律问题回答，或用户未预先批准的最终确认），否则不要让用户手动打开链接。
```
已准备，未提交
```
状态仅允许在尝试过实时申请路径、生成简历/申请包，且存在具体阻碍因素或用户有意暂停的情况下使用。
若当前会话中模型无法访问Chrome、Browser或Computer Use，必须在准备申请前明确说明，且不得暗示已完成申请。

Mandatory Stage Gates

强制阶段检查

Follow these gates in order. Do not tailor a resume or fill a form until the earlier gates pass.

Request scope: identify target country, role type, seniority, remote/on-site preference, whether the user asked to apply or only search, and the requested count.
Company/source gate: reject third-party posters, hidden clients, vague marketplaces, broad EMEA posts, and unclear country eligibility before scoring the role.
Direct route gate: find the company-owned careers page or ATS posting. If the company website has its own application form for the role, use that over LinkedIn Easy Apply, aggregators, or recruiter mirrors.
Live posting gate: verify title, company, location, eligibility, and apply button on the direct page. If archived, removed, paywalled, region-blocked, login-blocked, or not present on the company site, mark this candidate blocked/skipped and source a replacement.

Duplicate gate: check

/Users/zaid/Documents/Job Applications/applications_history.md

and

/Users/zaid/Documents/Job Applications/applications_tracker.csv

for the same company/role before submitting again.

Fit gate: score fit only after the source and direct route are credible. Apply only at
```
70%+
```
unless the user explicitly approves a lower score.
Resume gate: tailor the resume and packet only for roles that passed the prior gates.
Form gate: fill truthfully, validate dropdowns/uploads, and pause only that candidate for compensation, work authorization, legal, relocation, or residency questions that need user input. Continue sourcing replacements for the requested submitted count unless every viable candidate is blocked by required user input.
Submit gate: show a review packet immediately before final submit unless the user has explicitly pre-approved final submission. If the user asked to apply and pre-approved submission, proceed to submit unless a truthful answer or site blocker prevents it.
Tracker gate: update the Markdown history and tracker CSV for every submitted, prepared, skipped, or blocked role. If more applications were requested, continue sourcing replacements for blocked/skipped roles.

按顺序遵循以下检查步骤。在通过前期检查之前，不要定制简历或填写表单。

请求范围：确定目标国家、职位类型、职级、远程/现场偏好、用户要求是申请还是仅搜索，以及请求的数量。
公司/来源检查：在评估职位适配度之前，拒绝第三方发布者、隐藏客户、模糊的人才市场、宽泛的EMEA职位发布，以及资格要求不明确的职位。
直接路径检查：找到公司官方职业页面或ATS发布信息。若公司官网有该职位的专属申请表单，优先使用该表单，而非LinkedIn Easy Apply、职位聚合平台或招聘者转发的链接。
有效发布检查：在直接页面上验证职位名称、公司、地点、资格要求及申请按钮。若职位已归档、移除、需付费、区域限制、登录限制，或未在公司网站上显示，标记该候选职位为受阻/已跳过，并寻找替代职位。

重复项检查：在提交前，检查

/Users/zaid/Documents/Job Applications/applications_history.md

和

/Users/zaid/Documents/Job Applications/applications_tracker.csv

中是否存在相同公司/职位的记录。

适配度检查：仅在来源和直接路径可信后评估适配度。仅适配度达到
```
70%+
```
的职位才可申请，除非用户明确批准适配度更低的职位。
简历检查：仅为通过前期检查的职位定制简历和申请包。
表单检查：如实填写表单，验证下拉菜单/上传内容，若遇到薪酬、工作授权、法律、 relocation或居住权等需要用户输入的问题，仅暂停该候选职位的处理。除非所有可行候选职位都因需用户输入而受阻，否则继续寻找替代职位以达到请求的提交数量。
提交检查：除非用户明确预先批准最终提交，否则在最终提交前立即展示审核包。若用户要求申请并预先批准提交，除非如实回答问题或网站阻碍导致无法提交，否则继续完成提交。
跟踪记录检查：为每个已提交、已准备、已跳过或受阻的职位更新Markdown历史记录和跟踪CSV文件。若仍需提交更多申请，继续为受阻/已跳过的职位寻找替代职位。

Core Rules

核心规则

Target backend and backend-heavy full-stack roles.
Prioritize Pakistan, Turkiye, and Saudi Arabia; use UK, USA, and Europe only for remote roles unless the user says otherwise.
Do not apply to broad
```
EMEA remote
```
roles by default. Only consider them if the direct company posting explicitly includes Pakistan, Turkiye, Saudi Arabia, MENA, or worldwide remote eligibility.
Avoid third-party LinkedIn posters, staffing agencies, repost farms, and vague recruiter listings. Prefer first-party company posts or the company's own ATS/careers page.
Prefer companies that look directly eligible for Zaid: real product/SaaS/e-commerce/healthtech/fintech/backend teams hiring for their own engineering team, with clear remote/location rules.
Avoid talent marketplaces, outsourcing/interview platforms, employer-of-record/payroll platforms, and mass third-party hiring brands when they are posting on LinkedIn for another client or unclear end employer. Examples to treat cautiously or skip by default: Turing, Deel-style marketplace/EOR postings, STC-style third-party/recruiter postings, and similar intermediaries.
Apply only to roles with a
```
70%+
```
fit score unless the user explicitly approves a lower-fit role.
Treat live availability as part of fit. Do not keep an
```
apply
```
verdict if the direct posting is archived, expired, region-blocked, or no longer visible on the company/ATS site.
Prefer direct company or ATS application URLs over aggregators. Use aggregators only to discover leads or recover job details.
Tailor from the job description. Do not paste every skill or project into every resume.
Use conservative claims. Do not invent metrics, leadership, work authorization, language fluency, or production status.
Before final job submission, produce a review packet and pause for confirmation unless the user has explicitly pre-approved that exact submission behavior.

目标职位为后端及偏后端的全栈岗位。
优先考虑巴基斯坦、土耳其和沙特阿拉伯；仅在远程职位中考虑英国、美国和欧洲，除非用户另有说明。
默认不申请宽泛的
```
EMEA远程
```
职位。仅当公司直接发布的职位明确包含巴基斯坦、土耳其、沙特阿拉伯、中东及北非地区，或全球远程资格时，才考虑此类职位。
避免LinkedIn第三方发布者、人力资源中介、重复发布平台及模糊的招聘者列表。优先选择公司官方发布的职位或公司自有ATS/职业页面。
优先选择看起来直接符合Zaid条件的公司：拥有真实产品/SaaS/电商/健康科技/金融科技/后端团队，为自身工程团队招聘，且有明确的远程/地点规则。
避免人才市场、外包/面试平台、雇主代持/薪资平台，以及在LinkedIn上为其他客户或不明确最终雇主发布职位的大型第三方招聘品牌。默认需谨慎对待或跳过的例子包括：Turing、Deel类市场/EOR发布信息、STC类第三方/招聘者发布信息及类似中介机构。
仅适配度达到
```
70%+
```
的职位才可申请，除非用户明确批准适配度更低的职位。
将职位的有效状态视为适配度的一部分。若直接发布的职位已归档、过期、区域限制，或不再在公司/ATS网站上显示，不要维持“申请”的结论。
优先选择公司直接或ATS申请URL，而非聚合平台。仅使用聚合平台发现线索或恢复职位详情。
根据职位描述定制简历。不要将所有技能或项目都粘贴到每份简历中。
采用保守表述。不要编造指标、领导力经历、工作授权、语言流利度或项目投产状态。
在最终提交职位申请前，生成审核包并暂停等待确认，除非用户明确预先批准该提交行为。

Reference Loading

参考资料加载

Load only what the task needs:

For identity, title, contact, and positioning:
```
references/profile.md
```
.
For ElGrocer, Browse API, Haaameem, Standup Kid, MatTrack, and technical proof points:
```
references/project-bank.md
```
.
For deciding apply/maybe/skip and fit score:
```
references/role-matching.md
```
.
For resume edits, DOCX/PDF outputs, and role-specific tailoring:
```
references/resume-tailoring.md
```
.
For recruiter DMs, cover letters, form answers, and review packets:
```
references/templates.md
```
.
For claims to avoid, visa rules, weak jobs, and metric safety:
```
references/red-flags.md
```
.

Use

assets/resume-template.docx

as the stable base resume template.

仅加载任务所需的资料：

身份、职位名称、联系方式及定位：
```
references/profile.md
```
。
ElGrocer、Browse API、Haaameem、Standup Kid、MatTrack及技术证明点：
```
references/project-bank.md
```
。
决定申请/考虑/跳过及适配度评分：
```
references/role-matching.md
```
。
简历编辑、DOCX/PDF输出及职位定制：
```
references/resume-tailoring.md
```
。
招聘者私信、求职信、表单答案及审核包：
```
references/templates.md
```
。
需避免的表述、签证规则、低质量职位及指标安全：
```
references/red-flags.md
```
。

使用

assets/resume-template.docx

作为稳定的简历模板基础。

Application Workflow

申请工作流程

Inspect the job description and direct posting before deciding.
Extract role title, company, poster/source, location, work type, seniority, stack, responsibilities, requirements, application channel, and deal-breakers.
Run the mandatory stage gates above.
Score fit from
```
0-100
```
using
```
references/role-matching.md
```
.
Give verdict:
```
apply
```
,
```
maybe
```
, or
```
skip
```
, with the source reason included.
For
```
apply
```
, generate a full application packet:
- fit score
- verdict
- direct apply URL
- original source URL if different
- best angle
- matching skills
- risks or gaps
- tailored resume summary
- tailored resume bullets
- keywords to include
- recruiter DM only if useful
- cover letter only when requested or clearly useful
- LinkedIn or company form answer snippets
- interview talking points
- questions to ask recruiter
- final review checklist
If applying, create or update both tracker files under
```
/Users/zaid/Documents/Job Applications
```
, but do not mark the requested application count complete unless the status is
```
Submitted
```
.

在做出决定前，查看职位描述和直接发布信息。
提取职位名称、公司、发布者/来源、地点、工作类型、职级、技术栈、职责、要求、申请渠道及否决因素。
执行上述强制阶段检查。
使用
```
references/role-matching.md
```
进行0-100分的适配度评分。
给出结论：
```
申请
```
、
```
考虑
```
或
```
跳过
```
，并说明原因。
对于
```
申请
```
的职位，生成完整申请包：
- 适配度评分
- 结论
- 直接申请URL
- 原始来源URL（若与直接申请URL不同）
- 最佳申请角度
- 匹配技能
- 风险或差距
- 定制化简历摘要
- 定制化简历要点
- 需包含的关键词
- 仅在有用时提供招聘者私信内容
- 仅在要求或明显有用时提供求职信
- LinkedIn或公司表单答案片段
- 面试话术要点
- 需向招聘者提出的问题
- 最终审核清单
若进行申请，创建或更新
```
/Users/zaid/Documents/Job Applications
```
下的两个跟踪文件，但仅当状态为
```
已提交
```
时，才标记请求的申请数量已完成。

Persistent Application History

持久化申请历史记录

Every run must keep a cross-session Markdown record at:

/Users/zaid/Documents/Job Applications/applications_history.md

Create this file if it is missing before starting new applications.
Read this file at the start of every job-application run, before selecting roles, only to avoid duplicates, understand prior blockers, and continue explicitly requested unfinished applications.
Do not use this file as the candidate pool for a new
```
apply for N jobs
```
request unless the user explicitly says to resume previous applications.
Append one Markdown table row for every role inspected enough to receive a final outcome: submitted, prepared, blocked, or skipped.
Keep
```
applications_tracker.csv
```
updated too when it exists, but do not rely on CSV alone. The Markdown file is the human-readable source future sessions should inspect first.
Include these columns: date, company, role, location/work type, fit score, source URL, direct apply URL, resume file, channel, status, next action, notes.
Record blocked and skipped roles too, because they prevent future sessions from wasting time on the same dead lead.
If a requested application count is not reached, add a short session note at the bottom with the count state, for example:
```
Session note: 1 submitted, 1 prepared, 4 skipped/blocked, still sourcing 1 more.
```
Never erase previous rows. If a status changes later, append a new row or add a short update note with the new date.

每次运行都必须在以下路径保存跨会话的Markdown记录：

/Users/zaid/Documents/Job Applications/applications_history.md

若该文件不存在，在开始新申请前创建。
在每次职位申请运行开始时，选择职位前读取该文件，仅用于避免重复项、了解之前的阻碍因素，以及继续明确要求的未完成申请。
除非用户明确要求恢复之前的申请，否则不要将该文件作为新的“申请N个职位”请求的候选池。
为每个经过充分评估并得出最终结果（已提交、已准备、受阻、已跳过）的职位追加一行Markdown表格记录。
若
```
applications_tracker.csv
```
存在，也要更新该文件，但不要仅依赖CSV。Markdown文件是未来会话应优先查看的人类可读来源。
表格需包含以下列：日期、公司、职位、地点/工作类型、适配度评分、来源URL、直接申请URL、简历文件、渠道、状态、下一步行动、备注。
也要记录受阻和已跳过的职位，以避免未来会话在同一无效线索上浪费时间。
若未达到请求的申请数量，在文件底部添加简短会话备注，说明数量状态，例如：
```
会话备注：已提交1个，已准备1个，已跳过/受阻4个，仍在寻找1个。
```
永远不要删除之前的行。若状态后续发生变化，追加新行或添加带新日期的简短更新备注。

Live Job Discovery And Triage

实时职位发现与筛选

When searching for jobs or converting a shortlist into applications:

Evaluate company eligibility before role fit. A technically matching backend role is still a bad lead if the company/poster is an intermediary, unclear client, or region-vague listing.
Capture both the source URL and the direct apply URL. If they differ, track both.
Direct company application wins. If the company careers page or ATS has an application form for the same role, apply there instead of LinkedIn Easy Apply, DailyRemote, recruiter pages, or other mirrors.
Reject broad region labels like
```
EMEA
```
,
```
Europe
```
, or
```
remote anywhere in Europe
```
unless the direct posting explicitly includes Zaid's eligible countries.
Reject LinkedIn listings where the poster is a recruiter, staffing/intermediary company, job-board mirror, or unnamed third party unless the company confirms the same role on its own careers/ATS page.
For LinkedIn leads, check who posted the job. Prefer listings posted by the hiring company itself. Skip or downgrade listings posted by marketplaces, agencies, consultancies, or generic recruiting brands unless the direct company career page confirms the same role.
Do not treat famous remote-hiring brands as automatically good leads. If the business model is placing engineers into client companies, score the company/source risk before scoring the stack match.
If a job board hides the company or sends
```
Apply
```
to a paid page, inspect page source or structured data for the real company and ATS link.
Search the company careers page and common ATS boards before declaring a lead blocked.
Do not let static LinkedIn HTML scraping decide an application route by itself. Use Chrome for live LinkedIn/application pages when available; if no first-party route can be confirmed, skip and continue sourcing.
Common ATS targets to check: Greenhouse, Lever, Ashby, Workable, SmartRecruiters, LinkedIn Easy Apply, company-owned forms.
If an aggregator says the company is hidden but structured data names the company, use the named company to find the direct posting.
If the direct posting is archived, closed, or absent from the company careers page, mark it
```
Blocked, closed
```
or
```
Skip, no live posting
```
instead of trying to apply.
If a role exists on an aggregator but not on the company careers page, treat it as stale unless a direct ATS form still accepts applications.
If the company site has only a generic contact form or talent community and no matching role, do not submit a job application there unless the user approves outreach.
Do not spend time applying to paywalled job-board links when a free direct company route can be found.

在搜索职位或将候选列表转换为申请时：

在评估职位适配度之前，先评估公司资格。即使技术上匹配的后端职位，若公司/发布者是中介、不明确客户或区域模糊的列表，仍属于不良线索。
同时记录来源URL和直接申请URL。若两者不同，都要跟踪。
公司直接申请优先。若公司职业页面或ATS有同一职位的申请表单，优先在该处申请，而非LinkedIn Easy Apply、DailyRemote、招聘者页面或其他转发链接。
拒绝宽泛的区域标签，如
```
EMEA
```
、
```
Europe
```
或
```
欧洲任意地点远程
```
，除非直接发布的职位明确包含Zaid的符合条件的国家。
拒绝LinkedIn上由招聘者、人力资源中介/机构、职位平台转发或匿名第三方发布的列表，除非公司在自身职业/ATS页面确认该职位存在。
对于LinkedIn线索，查看职位发布者。优先选择招聘公司自身发布的列表。若列表由市场平台、中介、咨询公司或通用招聘品牌发布，除非公司官方职业页面确认该职位存在，否则跳过或降低优先级。
不要将知名远程招聘品牌视为自动可靠的线索。若其商业模式是将工程师安排到客户公司，在评估技术栈匹配度之前，先评估公司/来源风险。
若职位平台隐藏公司信息或引导至付费页面，查看页面源代码或结构化数据以获取真实公司和ATS链接。
在宣布线索受阻之前，搜索公司职业页面和常见ATS平台。
不要仅通过静态LinkedIn HTML爬取来决定申请路径。在可用时使用Chrome查看LinkedIn/申请实时页面；若无法确认官方路径，跳过并继续寻找其他职位。
需检查的常见ATS平台：Greenhouse、Lever、Ashby、Workable、SmartRecruiters、LinkedIn Easy Apply、公司自有表单。
若聚合平台显示公司信息隐藏，但结构化数据显示了公司名称，使用该公司名称寻找直接发布信息。
若直接发布的职位已归档、关闭或未在公司职业页面显示，标记为
```
受阻，已关闭
```
或
```
跳过，无有效发布
```
，而非尝试申请。
若职位在聚合平台存在，但未在公司职业页面显示，视为过期，除非直接ATS表单仍接受申请。
若公司网站仅有通用联系表单或人才社区，且无匹配职位，除非用户批准主动联系，否则不要在该处提交职位申请。
当存在免费的公司直接申请路径时，不要花费时间申请付费职位平台的链接。

Direct Application Route Priority

直接申请路径优先级

Use the first available route in this order:

Company careers page for the exact role.
Company-linked ATS page for the exact role, including Greenhouse, Lever, Ashby, Workable, SmartRecruiters, or a company-owned form.
First-party LinkedIn Easy Apply only when the hiring company posted it, no company/ATS form exists, and eligibility is clear.
Company-domain recruiter email or referral link only when the job post explicitly says to apply that way.
Outreach/talent community only when the user explicitly approves it. Treat this as outreach, not a submitted job application.

If the company website redirects to an ATS, treat the ATS as the direct route. If the company website has an application form and LinkedIn also has Easy Apply, use the company form. Do not apply through DailyRemote, generic job boards, staffing agencies, talent marketplaces, or paywalled mirrors when a first-party route exists.

按以下顺序使用第一个可用的路径：

对应职位的公司官方职业页面。
对应职位的公司关联ATS页面，包括Greenhouse、Lever、Ashby、Workable、SmartRecruiters或公司自有表单。
仅当招聘公司自身发布、无公司/ATS表单且资格明确时，使用官方LinkedIn Easy Apply。
仅当职位发布明确说明需通过该方式申请时，使用公司域名的招聘者邮箱或推荐链接。
仅当用户明确批准时，使用主动联系/人才社区。将此视为主动 outreach，而非已提交的职位申请。

若公司网站重定向至ATS，将该ATS视为直接路径。若公司网站有申请表单且LinkedIn也有Easy Apply，使用公司表单。当存在官方路径时，不要通过DailyRemote、通用职位平台、人力资源中介、人才市场或付费转发链接申请。

Browser And Submission Workflow

浏览器与提交工作流程

Use these tools as needed, with this priority:

Chrome plugin: first choice for job discovery, LinkedIn, company career pages, ATS forms, authenticated/profile-dependent pages, existing Chrome tabs, cookies, extensions, remote URLs, and final application submission.
Built-in Browser plugin: use when Chrome plugin is not available or not needed, especially for simple web inspection, direct company pages, public ATS pages, and quick form/navigation checks.
Computer Use plugin: use for resume polishing through desktop apps, DOCX/PDF visual checks, Microsoft Word/Preview exports, native file picker uploads, drag/drop upload controls, desktop authentication prompts, or web forms that Chrome/Browser cannot operate reliably.

Do not silently switch tools when the user explicitly names a tool. If Chrome is requested but unavailable, say that briefly and then use Browser or Computer Use only when the user has allowed that fallback.

Before interacting with a browser form:

Confirm the page title, role title, company, and location match the intended job.
Confirm the role is not archived, expired, location-blocked, or paywalled.
Use the tailored resume file intended for that exact role. If no exact resume exists, use the closest backend or full-stack resume and note the fallback in the tracker.
Use Computer Use for resume upload when the browser exposes a native file picker or the upload control is not accessible through the browser plugin.
Do not click final submit if the form contains unanswered legal, compensation, work authorization, location, or identity questions that are ambiguous or risky.

After filling a form:

Run a validation pass by checking that required fields are genuinely accepted, not just visually typed.
For dropdowns and comboboxes, typed text is not enough. Open the menu and select the option when the site requires an actual option value.
If submit shows validation errors, correct those fields before trying again. If the site offers no valid option matching the truthful answer, stop and report the blocker.
If reCAPTCHA, login, paywall, or account verification blocks submission, stop and report exactly where it blocked.
After successful submission, record the confirmation state, timestamp, channel, resume file, and any notable answers in the tracker.

根据需要使用以下工具，优先级如下：

Chrome插件：职位发现、LinkedIn、公司职业页面、ATS表单、需认证/依赖个人资料的页面、现有Chrome标签页、Cookie、扩展程序、远程URL及最终申请提交的首选工具。
内置Browser插件：当Chrome插件不可用或不需要时使用，尤其适用于简单网页查看、公司直接页面、公开ATS页面及快速表单/导航检查。
Computer Use插件：用于通过桌面应用优化简历、DOCX/PDF可视化检查、Microsoft Word/Preview导出、原生文件选择器上传、拖放上传控件、桌面认证提示，或Chrome/Browser无法可靠操作的网页表单。

若用户明确指定工具，不要擅自切换。若用户要求使用Chrome但不可用，简要说明后，仅在用户允许fallback时使用Browser或Computer Use。

在与浏览器表单交互前：

确认页面标题、职位名称、公司及地点与目标职位匹配。
确认职位未归档、过期、区域限制或需付费。
使用为该职位定制的简历文件。若没有对应简历，使用最接近的后端或全栈简历，并在跟踪记录中注明使用了备选简历。
当浏览器显示原生文件选择器或上传控件无法通过浏览器插件访问时，使用Computer Use上传简历。
若表单包含未回答的法律、薪酬、工作授权、地点或身份问题，且这些问题模糊或存在风险，不要点击最终提交按钮。

填写表单后：

执行验证步骤，确认必填字段已被系统真正接受，而非仅视觉上填写完成。
对于下拉菜单和组合框，仅输入文本不够。当网站要求选择实际选项值时，打开菜单并选择对应选项。
若提交时显示验证错误，修正这些字段后再尝试提交。若网站没有与真实答案匹配的有效选项，停止并报告阻碍因素。
若reCAPTCHA、登录、付费墙或账户验证阻碍提交，停止并准确报告阻碍位置。
提交成功后，在跟踪记录中记录确认状态、时间戳、渠道、简历文件及任何重要答案。

Form Answer Rules

表单答案规则

Be truthful on location. If the user is not in a required city or country, answer truthfully and treat a hard requirement as a risk or blocker.
Be truthful on language level and technical depth. Prefer conservative answers such as
```
Beginner
```
,
```
Intermediate
```
, or
```
Advanced
```
only when supported by the profile.
For salary/current compensation fields:
- Use
```
Prefer to discuss
```
  ,
```
Negotiable
```
  , or a market-aligned value only if the form accepts text.
- Pause if the form requires a numeric current salary, exact expected salary, hourly rate, or currency and the user has not already provided a safe value.
For work authorization, relocation, visa sponsorship, contractor status, and tax residency questions, pause if the answer is not obvious from the profile.
For gender, demographic, disability, veteran, or EEO questions, prefer
```
Prefer not to say
```
when available unless the user has provided a standing preference.
Do not invent city residency, work authorization, citizenship, degree details, or years of experience to pass validation.

地点信息如实填写。若用户不在要求的城市或国家，如实回答，并将硬性要求视为风险或阻碍因素。
语言水平和技术深度如实填写。仅当个人资料支持时，选择保守答案，如
```
Beginner
```
（初级）、
```
Intermediate
```
（中级）或
```
Advanced
```
（高级）。
对于薪资/当前薪酬字段：
- 若表单接受文本输入，使用
```
Prefer to discuss
```
  （面议）、
```
Negotiable
```
  （可协商）或符合市场水平的数值。
- 若表单要求填写当前薪资数值、确切期望薪资、小时费率或货币类型，且用户未提供安全数值，暂停处理。
对于工作授权、relocation、签证担保、承包商身份及税务居住权问题，若答案无法从个人资料中明确得知，暂停处理。
对于性别、人口统计信息、残疾、退伍军人或EEO问题，若有
```
Prefer not to say
```
（不愿透露）选项，优先选择该选项，除非用户已提供固定偏好。
不要编造城市居住权、工作授权、公民身份、学位细节或工作年限以通过验证。

Tracker Statuses

跟踪记录状态

Use precise statuses so future runs do not repeat dead work:

```
Submitted
```
: final application was accepted by the target site.
```
Prepared, not submitted
```
: packet/resume is ready, but final submit was not clicked.
```
Blocked, needs user answer
```
: form requires compensation, legal, or other personal input.
```
Blocked, form validation
```
: site rejects dropdowns, upload, captcha, or required fields despite truthful data.
```
Blocked, closed
```
: posting is archived, expired, removed, or no longer live.
```
Blocked, paywalled
```
: application link requires paid job-board access and no direct route was found.
```
Blocked, duplicate
```
: tracker shows the same company/role was already submitted or is already in progress.
```
Skip, no direct route
```
: no company-owned careers page, ATS form, or verified first-party application route was found.
```
Skip, low fit
```
: role is below threshold or has major mismatch.
```
Skip, third-party poster
```
: role is posted by an agency, marketplace, recruiter, or unclear intermediary rather than the direct hiring company.
```
Skip, unclear eligibility
```
: company or posting does not clearly accept Zaid's eligible locations.

使用精确状态，避免未来重复处理无效工作：

```
已提交
```
：最终申请已被目标网站接收。
```
已准备，未提交
```
：申请包/简历已就绪，但未点击最终提交。
```
受阻，需用户回答
```
：表单要求填写薪酬、法律或其他个人信息。
```
受阻，表单验证
```
：尽管提供了真实数据，网站仍拒绝下拉菜单、上传内容、验证码或必填字段。
```
受阻，已关闭
```
：职位发布已归档、过期、移除或不再有效。
```
受阻，付费墙限制
```
：申请链接需要付费职位平台权限，且未找到直接申请路径。
```
受阻，重复项
```
：跟踪记录显示同一公司/职位已提交或正在处理中。
```
跳过，无直接路径
```
：未找到公司官方职业页面、ATS表单或已验证的官方申请路径。
```
跳过，适配度低
```
：职位适配度低于阈值或存在重大不匹配。
```
跳过，第三方发布
```
：职位由中介、市场平台、招聘者或不明确的中介发布，而非直接招聘公司。
```
跳过，资格不明确
```
：公司或职位发布未明确接受Zaid的符合条件的地点。

Resume Workflow

简历工作流程

Use the

documents:documents

skill for DOCX creation/editing and verification.

Start from
```
assets/resume-template.docx
```
.
Keep the ATS-friendly, single-column, compact Times New Roman style.
Use Pakistan phone only.
Use current title
```
Backend Engineer
```
.
Allow 2 pages.
Export both DOCX and PDF per job.
Save generated files in
```
/Users/zaid/Documents/Job Applications
```
.

Name files as

Zaid_<Role>_<Company>_<YYYY-MM-DD>.docx

and

.pdf

Run render and visual QA when
```
soffice
```
is available.
If
```
soffice
```
is unavailable, export PDF through Microsoft Word and visually check the result.

使用

documents:documents

技能创建/编辑DOCX文件并进行验证。

从
```
assets/resume-template.docx
```
开始。
保持ATS友好的单栏紧凑Times New Roman格式。
仅使用巴基斯坦电话号码。
使用当前职位名称
```
Backend Engineer
```
。
允许简历为2页。
每个职位导出DOCX和PDF两种格式。
将生成的文件保存至
```
/Users/zaid/Documents/Job Applications
```
。

文件命名格式为

Zaid_<职位名称>_<公司名称>_<YYYY-MM-DD>.docx

和

.pdf

。

当
```
soffice
```
可用时，执行渲染和可视化质量检查。
若
```
soffice
```
不可用，通过Microsoft Word导出PDF并进行可视化检查。

Submission Safety

提交安全

Job applications transmit personal/professional data to third parties. Prepare everything first, then show the review packet immediately before final submit. The packet must include company, role, location/work type, channel, fit score, resume file, legal/pay answers, and any uploaded file names.

职位申请会向第三方传输个人/专业数据。先准备好所有内容，然后在最终提交前立即展示审核包。审核包必须包含公司、职位、地点/工作类型、渠道、适配度评分、简历文件、法律/薪资答案及所有上传文件名。

Output Style

输出风格

Short, human, confident, and direct.
No fake enthusiasm.
No desperate tone.
No inflated corporate language.
No em dashes.
Use simple English.
Hook the recruiter in the first line of DMs or notes.

简洁、人性化、自信且直接。
不要虚假热情。
不要使用绝望语气。
不要使用夸大的企业用语。
不要使用破折号。
使用简单英语。
在私信或备注的第一句话就吸引招聘者注意。