Consequential Work. Dedicated People. About Onebrief Onebrief builds collaboration and AI-powered workflow software for military planning and operational coordination. Military planning is complex by nature, requiring teams to coordinate information, people, and decisions across systems and locations. Onebrief brings planning, collaboration, simulation, and AI into one connected environment, helping teams test strategies, adapt to changing conditions, and make decisions with greater clarity when the stakes are real. We are a distributed team of builders from military, operational, and technology backgrounds who care deeply about improving how important work gets done. Some team members work remotely, while others work directly alongside customers in operational environments around the world. Founded in 2019, Onebrief is backed by leading investors including General Catalyst, Battery Ventures, Insight Partners, Sapphire Ventures, and Human Capital. Valued at more than $2 billion, we continue to invest in product innovation, AI capabilities, and team growth. Why This Role Exists As a Solutions Engineer at Onebrief, you work where mission, engineering, and compliance meet. You'll own technical solution design and deployment readiness, translating customer requirements into secure, scalable deployment architectures. You'll partner with Platform Engineering, SRE, and our Cybersecurity team to validate infrastructure, configure environments, resolve technical blockers, and successfully transition solutions into production. Youâll work with our go-to-market and customer facing teams to meet with planners, operations officers, and network owners to understand how they work today. Youâll help show them what that work looks like in Onebrief, and then you'll make it real. You connect a staff's planning problem to a live, accredited Onebrief deployment. What You'll Do Core responsibilities: Run technical discovery. With Sales and Engineering, map a staff's current workflow and pain points, specifically focusing on their technical constraints: networks, hosting, identity, and integration requirements, especially in multi-network environments. Lead deployment engineering. Coordinate the technical delivery of new deployments, including infrastructure validation, network configuration checks, and system readiness verification. Write code to configure new deployments and support new environments. Support accreditation. Help create and review security documentation, including STIG checklists and ATO artifacts, alongside our cybersecurity team so deployments are accredited on the customer's timeline. Align stakeholders. Get technical stakeholders on both sides to agree on requirements, constraints, and tradeoffs, so customers see value sooner. Ensure those technical requirements are properly translated into contract deliverables. Scope integrations. Design how Onebrief Connect fits into a command's ecosystem: APIs, data pipelines, Foundry and Maven Smart System, CUOPS tools, and dashboards. Deliver tailored demos. Lead technical demonstrations and solution validation, partnering with Sales and customer-facing teams to demonstrate Onebrief's technical capabilities, deployment architecture, security posture, and integration options. Run pilot deployments. Configure Onebrief in new and untested environments to enable limited uses in support of new sales. Turn field experience into patterns . Convert what you learn in deployments into structured workflows and reusable implementation patterns, and feed clear requirements to Product and Engineering. Travel 30â50% of the time to customer sites and exercises. Minimum Qualifications Top Secret clearance with SCI eligibility. Bachelor's degree in computer science, engineering, or a related field, or equivalent practical experience 4+ years in solutions engineering, infrastructure or deployment engineering, or forward-deployed engineering, working closely with go-to-market and operational teams Experience in DoW environments and their security and compliance requirements (RMF, STIGs, ICD 503) Strong expertise with containers (Docker) and orchestration (Kubernetes) Experience with cloud platforms (AWS, Azure, Google Cloud) and on-premises virtualization (RHEL) Solid understanding of networking concepts and protocols, and of security best practices for highly sensitive environments Strong presence with customers, from action officers to senior leaders, and clear, concise writing Calm under pressure, and focused on forward motion Preferred Qualifications Proficiency in a scripting language (Python, Go, or Bash) Infrastructure as code (Terraform, CloudFormation, Ansible) Monitoring and logging tools (Prometheus, Grafana, ELK, Datadog) and service mesh (Istio, Linkerd) Experience as a military planner or staff officer, or with mission command systems, Foundry, or Maven Smart System Presales experience, including building and delivering demos Notice to Third Party Recruitment Agencies Please note that Onebrief does not accept unsolicited resumes from recruiters or employment agencies. In the absence of an executed Recruitment Services Agreement, there will be no obligation to any referral compensation or recruiter fee. In the event a recruiter or agency submits a resume or candidate without an agreement Onebrief explicitly reserves the right to pursue and hire those candidate(s) without any financial obligation to the recruiter or agency. Any unsolicited resumes, including those submitted to hiring managers, shall be deemed the property of Onebrief. Please mention the word **DESIRING** and tag RMTM0LjE5NS4xMDEuMTkz when applying to show you read the job post completely (#RMTM0LjE5NS4xMDEuMTkz). This is a beta feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.
有意义的工作。敬业的人。关于 Onebrief Onebrief 为军事规划与作战协调构建协作和 AI 驱动的工作流软件。军事规划本质上很复杂,需要团队跨系统和地点协调信息、人员和决策。Onebrief 将规划、协作、仿真和 AI 整合到一个互联环境中,帮助团队测试策略、适应变化的条件,并在事关重大的真实场景中更清晰地做出决策。我们是一支由来自军事、运营和技术背景的建设者组成的分布式团队,深切关注改进重要工作的完成方式。部分团队成员远程工作,另一些成员则直接在世界各地的作战环境中与客户并肩工作。Onebrief 成立于 2019 年,获得了包括 General Catalyst、Battery Ventures、Insight Partners、Sapphire Ventures 和 Human Capital 在内的领先投资者支持。公司估值超过 $2 billion,我们持续投资于产品创新、AI 能力和团队成长。为什么设立这个职位 作为 Onebrief 的解决方案工程师,你在使命、工程和合规的交汇处工作。你将负责技术解决方案设计和部署就绪度,将客户需求转化为安全、可扩展的部署架构。你将与平台工程、SRE 和我们的网络安全团队合作,验证基础设施、配置环境、解决技术阻碍,并成功将解决方案转入生产环境。你将与我们的市场进入和客户对接团队合作,会见规划人员、作战军官和网络负责人,了解他们当前的工作方式。你将帮助他们了解这些工作在 Onebrief 中是什么样子,然后将其落地实现。你将参谋团队的规划问题与一个实际运行且
---
> 分析对象:RemoteOK 平台发布的 Onebrief "Solutions Engineer" 岗位
> 服务对象:约 12 年安全经验、现任/曾任安全负责人(总监级)、带团队管预算、双体系认证背景的求职者
> 目标岗位:安全总监 / 安全经理 / 安全工程师 / 安全架构师
> 说明:本报告面向非安全领域读者,所有专业概念均做通俗解释,所有结论均回扣 JD 原文。
---
> 说明:下表覆盖 JD 中出现的每一个关键术语/缩写。按"术语—通俗解释—为什么这个岗位要它"三列呈现。
| 术语 / 缩写 | 一句话通俗解释 | 为什么这个岗位要它(回扣 JD) |
|---|---|---|
| **Solutions Engineer(解决方案工程师)** | 介于"销售"和"技术"之间的角色:客户要买软件,你负责把软件"装进"客户的环境里、证明它能用、能过审。 | 这就是岗位本身。JD 标题即此。 |
| **AI-powered workflow software** | 用人工智能辅助工作流程的软件(比如自动整理情报、生成方案草稿)。 | 公司主营产品形态,JD 开头 "builds collaboration and AI-powered workflow software"。 |
| **Military planning / operational coordination** | 军事计划与作战协同——军队里"怎么排兵布阵、怎么协调多部门行动"的工作。 | 公司服务的客户场景,决定岗位的敏感性。 |
| **Simulation** | 仿真:在电脑里模拟推演,比如模拟一场作战计划会怎样发展。 | JD 说产品把 "planning, collaboration, simulation, and AI" 融为一体。 |
| **Platform Engineering** | 平台工程团队:负责搭建公司内部"基础设施底座"(服务器、部署流水线等)的团队。 | JD 说你要 "partner with Platform Engineering"。 |
| **SRE(Site Reliability Engineering,站点可靠性工程)** | 保障系统"不宕机、跑得稳"的工程团队,类似"系统运维的升级版"。 | JD 明确要你和 SRE 合作验证基础设施。 |
| **Cybersecurity team** | 公司内部的安全团队。 | JD 要你和安全团队一起做认证文档。 |
| **Go-to-market(GTM)** | "走向市场"的统称,指销售、市场、客户成功等面向客户的团队。 | JD 说你要和 "go-to-market and customer facing teams" 合作。 |
| **Technical discovery(技术尽调/技术勘察)** | 售前阶段去摸清客户"现在怎么干活、有什么技术限制"的过程。 | JD 第一条职责 "Run technical discovery"。 |
| **Multi-network environments(多网络环境)** | 一个单位同时有多个互相隔离的网络(如涉密网、非涉密网、战术网),数据不能随便互通。 | JD 说 discovery 要聚焦 "networks, hosting, identity, and integration requirements, especially in multi-network environments"。 |
| **Deployment engineering(部署工程)** | 把软件真正安装、配置、跑通在客户环境里的工程工作。 | JD 职责 "Lead deployment engineering"。 |
| **Infrastructure validation(基础设施验证)** | 检查客户的服务器、网络、存储等"地基"是否满足软件运行要求。 | JD 原文 "infrastructure validation"。 |
| **Network configuration checks(网络配置检查)** | 检查防火墙、路由、端口等网络设置对不对。 | JD 原文 "network configuration checks"。 |
| **System readiness verification(系统就绪验证)** | 确认"一切准备就绪、可以上线"的检查。 | JD 原文 "system readiness verification"。 |
| **Accreditation(认证/授权,指系统过审)** | 政府/军队允许某套 IT 系统在特定环境里正式使用的官方审批流程。没过审 = 不能用。 | JD 职责 "Support accreditation",这是本岗位最核心的"合规"价值。 |
| **STIG(Security Technical Implementation Guide,安全技术实施指南)** | 美国国防部出的一套"系统安全配置检查清单",逐条规定系统该怎么配才安全(比如密码策略、日志留存)。 | JD 原文 "STIG checklists",是认证必交材料。 |
| **ATO(Authority to Operate,运行授权)** | 官方盖章"这套系统批准上线运行"的批文。没有 ATO,系统不能碰真实数据。 | JD 原文 "ATO artifacts"(ATO 相关材料)。 |
| **RMF(Risk Management Framework,风险管理框架)** | 美国政府对 IT 系统做安全风险评估与授权的一整套标准流程(NIST 出品),ATO 就是 RMF 流程的产物。 | JD 最低要求里明确 "RMF"。 |
| **ICD 503** | 美国情报界(Intelligence Community)关于"信息系统安全风险评估"的一份指令文件,和 RMF 配套使用。 | JD 最低要求里明确 "ICD 503"。 |
| **DoW(Department of War,战争部)** | 即美国国防部(DoD)在特定语境下的称呼/新提法,指美国军事体系。 | JD 要求 "Experience in DoW environments"。 |
| **Containers / Docker(容器)** | 把软件和它依赖的环境"打包成一个盒子",到哪都能一致运行的技术。Docker 是最流行的容器工具。 | JD 要求 "containers (Docker)"。 |
| **Kubernetes(K8s,容器编排)** | 管理成百上千个"容器盒子"的调度系统,负责自动部署、扩容、故障恢复。 | JD 要求 "orchestration (Kubernetes)"。 |
| **Cloud platforms(AWS / Azure / Google Cloud)** | 三大公有云:亚马逊云、微软云、谷歌云。 | JD 要求 "cloud platforms (AWS, Azure, Google Cloud)"。 |
| **On-premises virtualization(本地虚拟化)** | 客户自己机房里的虚拟化技术(把一台物理机切成多台虚拟机)。 | JD 要求 "on-premises virtualization"。 |
| **RHEL(Red Hat Enterprise Linux,红帽企业版 Linux)** | 企业级 Linux 操作系统,政府和军工环境常用。 | JD 原文括号里点名 "RHEL"。 |
| **Networking concepts and protocols(网络概念与协议)** | TCP/IP、DNS、VPN、防火墙规则等网络基础知识。 | JD 要求 "Solid understanding of networking concepts and protocols"。 |
| **APIs(应用程序接口)** | 软件之间"对话"的接口,让 A 系统能调 B 系统的数据/功能。 | JD 职责 "Scope integrations... APIs"。 |
| **Data pipelines(数据管道)** | 数据从 A 点自动流向 B 点、并经过清洗处理的通道。 | JD 原文 "data pipelines"。 |
| **Foundry(Palantir Foundry)** | Palantir 公司的大数据集成分析平台,美军大量使用。 | JD 原文点名 "Foundry"。 |
| **Maven Smart System(MSS)** | 美军"马文计划"下的 AI 作战辅助系统(用 AI 分析战场图像/情报)。 | JD 原文点名 "Maven Smart System"。 |
| **CUOPS tools(Current Operations tools,当前作战工具)** | 军队里用来实时掌握"当前战况/行动"的软件系统。 | JD 原文 "CUOPS tools"。 |
| **Dashboards(仪表盘)** | 把关键数据可视化展示的界面。 | JD 原文 "dashboards"。 |
| **Onebrief Connect** | Onebrief 自家的一款"连接器"产品,用来和客户已有系统对接。 | JD 原文 "how Onebrief Connect fits into a command's ecosystem"。 |
| **Command's ecosystem(指挥体系生态)** | 一个军事指挥单位里所有在用系统的总和。 | JD 原文。 |
| **Pilot deployments(试点部署)** | 先在小范围/新环境里试装,验证可行后再推广。 | JD 职责 "Run pilot deployments"。 |
| **Implementation patterns(实施模式/复用套路)** | 把每次部署的经验沉淀成"标准打法",下次直接套用。 | JD 原文 "reusable implementation patterns"。 |
| **Top Secret clearance(绝密级安全许可)** | 美国政府给个人做的背景审查等级,"Top Secret"是最高常用级,能接触绝密信息。 | JD 最低要求第一条。 |
| **SCI eligibility(敏感隔离信息资格)** | 比 Top Secret 更高一档的访问资格,能接触"敏感隔离信息"(如情报来源)。 | JD 原文 "Top Secret clearance with SCI eligibility"。 |
| **Forward-deployed engineering(前置部署工程)** | 工程师直接"驻扎"到客户现场,边用边改、快速响应。 | JD 最低要求里作为相关经验列出。 |
| **Infrastructure as code(IaC,基础设施即代码)** | 用写代码的方式(而非手工点鼠标)来创建和配置服务器/网络。 | JD 加分项 "Infrastructure as code (Terraform, CloudFormation, Ansible)"。 |
| **Terraform / CloudFormation / Ansible** | 三种主流 IaC 工具:Terraform(跨云)、CloudFormation(AWS 专用)、Ansible(配置管理)。 | JD 加分项点名。 |
| **Prometheus / Grafana / ELK / Datadog** | 监控与日志工具:Prometheus(指标采集)、Grafana(可视化)、ELK(日志搜索分析)、Datadog(商业监控平台)。 | JD 加分项 "Monitoring and logging tools"。 |
| **Service mesh(服务网格)** | 管理微服务之间通信(加密、限流、追踪)的基础设施层。 | JD 加分项。 |
| **Istio / Linkerd** | 两种主流服务网格产品。 | JD 加分项点名。 |
| **Mission command systems(任务指挥系统)** | 军队用来下达命令、共享态势的指挥信息系统。 | JD 加分项 "mission command systems"。 |
| **Presales(售前)** | 销售过程中提供技术方案、做演示、答疑的环节。 | JD 加分项 "Presales experience"。 |
| **Staff officer(参谋军官)** | 军队里做计划、协调、参谋工作的军官。 | JD 加分项 "military planner or staff officer"。 |
| **Action officer(行动官/项目经办军官)** | 军队里具体负责推进某项事务的军官。 | JD 要求 "from action officers to senior leaders"。 |
| **SBOM / Zero Trust** | (注:本 JD **未出现**这两个词,特此说明,避免误读。)SBOM=软件物料清单;Zero Trust=零信任架构。 | 本 JD 未涉及,故不展开。 |
| **RMTgwLjE2NS40LjIyMw==** | JD 末尾的一串 Base64 编码(解码后为 IP 地址 180.165.4.223),是平台防垃圾投递的"暗号"。 | 投递时需在申请中提及 **DESIRING** 并附上该串,证明你读完了全文。 |
> **特别提醒**:JD 末尾要求 "Please mention the word **DESIRING** and tag RMTgwLjE2NS40LjIyMw== when applying"。这是硬性投递动作,漏了可能被系统过滤。
---
**Onebrief 做什么生意?**
**赛道阶段:成长早期 → 快速成长期**
**主要玩家与 Onebrief 的位置**
---
一个"Solutions Engineer"岗位的出现,通常意味着三件事同时发生:
1. **产品从"能演示"进入"能交付"阶段**:客户不再满足于看 demo,而是要真正装进自己的环境跑起来。JD 说 "transition solutions into production"、"make it real"——这就是从"卖概念"到"卖落地"的信号。
2. **合规成为成交前提**:军工客户采购的硬门槛是 **ATO(运行授权)**。没过审,产品再好也进不去。所以需要专人写 STIG 清单、ATO 材料。JD 把 "Support accreditation" 单列为职责,说明**合规已是销售瓶颈**。
3. **客户环境高度异构**:每个指挥单位的网络、云、本地机房都不一样(multi-network、on-prem RHEL、多云),需要"懂技术又能和客户对话"的人去逐个适配。JD 说 "configure Onebrief in new and untested environments"。
> **结论**:这个岗位是"军工软件商业化走到'规模化交付'阶段"的产物——**产品能卖了,但每个客户都要定制化落地 + 过审,于是需要既懂技术又懂合规还能面对客户的工程师**。这与求职者"安全负责人 + 双体系认证"的背景有天然交集(认证/合规),但岗位本质是**售前+部署工程**,不是纯安全管理。
---
**一句话**:这是一个"军工软件售前 + 部署 + 合规认证"三合一的**解决方案工程师**岗位——你要陪销售去见军官,摸清他们的网络和流程,把 Onebrief 装进他们的环境,写出能过 ATO 的安全材料,做演示、跑试点,再把现场经验沉淀成可复用的打法。
**属于安全哪条线?**
> 对求职者的含义:这个岗位**用得上你的合规与架构能力,但会大量消耗在"客户现场部署 + 售前演示"上**,管理属性弱、工程与客户属性强。
---
**公司做什么**:军事计划与作战协同的 AI 协作软件(JD 开头原文)。
**规模与阶段**(从 JD 推断,标注"推断"):
**为什么现在招这个人**(从措辞推断,标注"推断"):
**市场发展(基于行业常识,标注)**:
---
> 占比为基于 JD 措辞与同类岗位经验的**推断**,非原文。
| # | JD 原文 | 中文翻译 | 点评(什么活 / 含金量 / 占比推断) |
|---|---|---|---|
| 1 | Run technical discovery. With Sales and Engineering, map a staff's current workflow and pain points, specifically focusing on their technical constraints: networks, hosting, identity, and integration requirements, especially in multi-network environments. | 做技术勘察:和销售、工程一起,摸清客户参谋团队现在的工作流和痛点,重点摸清网络、托管、身份、集成方面的技术限制,尤其是多网络环境。 | **售前调研活**。含金量中高(考验沟通+技术广度),但偏"陪聊+记录"。**占比推断 15%**。 |
| 2 | Lead deployment engineering. Coordinate the technical delivery of new deployments, including infrastructure validation, network configuration checks, and system readiness verification. Write code to configure new deployments and support new environments. | 主导部署工程:协调新部署的技术交付,包括基础设施验证、网络配置检查、系统就绪验证;写代码来配置新部署、支持新环境。 | **核心交付活**。含金量高(真刀真枪装系统),但体力活多、要写配置代码。**占比推断 25%**。 |
| 3 | Support accreditation. Help create and review security documentation, including STIG checklists and ATO artifacts, alongside our cybersecurity team so deployments are accredited on the customer's timeline. | 支持认证:和安全团队一起编写和审阅安全文档,包括 STIG 检查清单和 ATO 材料,确保部署按客户时间线过审。 | **合规活,求职者最强项**。含金量高(直接决定能否成交),但偏文档、琐碎。**占比推断 20%**。 |
| 4 | Align stakeholders. Get technical stakeholders on both sides to agree on requirements, constraints, and tradeoffs... Ensure those technical requirements are properly translated into contract deliverables. | 对齐干系人:让双方技术干系人对需求、约束、取舍达成一致;把技术需求准确翻译成合同交付物。 | **协调+商务翻译活**。含金量中(软技能为主),考验跨组织沟通。**占比推断 10%**。 |
| 5 | Scope integrations. Design how Onebrief Connect fits into a command's ecosystem: APIs, data pipelines, Foundry and Maven Smart System, CUOPS tools, and dashboards. | 界定集成范围:设计 Onebrief Connect 如何嵌入指挥体系生态——API、数据管道、Foundry、Maven、CUOPS 工具、仪表盘。 | **架构设计活**。含金量高(要懂生态、懂对接),但受限于自家产品边界。**占比推断 10%**。 |
| 6 | Deliver tailored demos. Lead technical demonstrations and solution validation... demonstrate Onebrief's technical capabilities, deployment architecture, security posture, and integration options. | 做定制演示:主导技术演示和方案验证,展示技术能力、部署架构、安全态势、集成选项。 | **售前演示活**。含金量中(表演+技术),高频但重复。**占比推断 10%**。 |
| 7 | Run pilot deployments. Configure Onebrief in new and untested environments to enable limited uses in support of new sales. | 跑试点部署:在全新、未测试的环境里配置 Onebrief,支撑新销售的有限使用。 | **前线试错活**。含金量高(真环境、真风险),但压力大、易背锅。**占比推断 5%**。 |
| 8 | Turn field experience into patterns. Convert what you learn in deployments into structured workflows and reusable implementation patterns, and feed clear requirements to Product and Engineering. | 把现场经验变成模式:把部署中学到的沉淀成结构化工作流和可复用实施模式,并把清晰需求反馈给产品和工程。 | **知识沉淀活**。含金量中高(体现系统性思维),但常被业务挤压。**占比推断 5%**。 |
| 9 | Travel 30–50% of the time to customer sites and exercises. | 30–50% 时间出差到客户现场和演习。 | **硬性成本**。不是"职责"但是"生活方式的定义"。**占比即时间成本**。 |
**总体判断**:这是一个**"售前 40% + 部署 35% + 合规 20% + 沉淀 5%"** 的混合岗。对求职者而言,**合规(20%)是舒适区,部署与售前(75%)是主战场且需补课**。
---
| 要求(JD 原文) | 解读 |
|---|---|
| **Top Secret clearance with SCI eligibility** | **最硬的门槛**。这是美国政府给个人的安全许可,**中国人几乎不可能持有**(需美国公民身份+长期背景审查)。详见第 6 节。 |
| Bachelor's degree in CS/engineering or equivalent practical experience | 学历可被"等效实践经验"替代,弹性较大。 |
| 4+ years in solutions engineering, infrastructure/deployment engineering, or forward-deployed engineering, working closely with GTM and operational teams | 4 年以上**售前/部署/前置工程**经验,且要"贴近销售和运营团队"。求职者 12 年安全经验,但**是否做过"售前+部署"是问号**。 |
| Experience in DoW environments and their security and compliance requirements (RMF, STIGs, ICD 503) | **必须有美军环境经验 + 懂 RMF/STIG/ICD 503**。求职者的"双体系认证"(推测为 ISO 27001 + 等保)**不等于** RMF/STIG,需补。 |
| Strong expertise with containers (Docker) and orchestration (Kubernetes) | Docker/K8s 硬要求。 |
| Experience with cloud platforms (AWS, Azure, Google Cloud) and on-premises virtualization (RHEL) | 多云 + 本地 RHEL 虚拟化。 |
| Solid understanding of networking concepts and protocols, and security best practices for highly sensitive environments | 网络基础 + 高敏感环境安全实践。 |
| Strong presence with customers, from action officers to senior leaders, and clear, concise writing | 面对从经办军官到高级将领都能镇得住场 + 写作清晰。 |
| Calm under pressure, focused on forward motion | 抗压、推进力。 |
| 要求(JD 原文) | 解读 |
|---|---|
| Proficiency in a scripting language (Python, Go, or Bash) | 脚本能力,部署自动化用。 |
| Infrastructure as code (Terraform, CloudFormation, Ansible) | IaC 工具。 |
| Monitoring and logging tools (Prometheus, Grafana, ELK, Datadog) and service mesh (Istio, Linkerd) | 可观测性 + 服务网格。 |
| Experience as a military planner or staff officer, or with mission command systems, Foundry, or Maven Smart System | **军事背景/军工系统经验**,这是"圈内人"加分项。 |
| Presales experience, including building and delivering demos | 售前演示经验。 |
---
**原文**:$180,000–220,000 / 年(美元)。
**换算人民币**(按 1 USD ≈ 7.2 CNY 粗算,标注"汇率假设"):
**与同类岗位市场水平对比**:
**当地税后粗估**(标注"粗估,实际因州/身份差异大"):
> **对求职者的现实提醒**:这个薪资数字**建立在"能拿到 TS clearance 并合法在美国工作"的前提上**。若身份不满足,薪资数字对你是"看得见摸不着"。
---
| 维度 | JD 原文/信号 | 分析 | 结论 |
|---|---|---|---|
| **Security clearance** | "Top Secret clearance with SCI eligibility" | 美国安全许可**只授予美国公民**(极少数绿卡持有者可获非 SCI 级)。SCI 基本要求公民身份 + 长期背景审查。**中国人几乎不可能满足**。 | 🔴 **红灯(决定性)** |
| **Sponsorship(工签担保)** | JD **未提及** sponsorship,也未说"must be US citizen",但 clearance 要求隐含公民身份。 | 军工项目通常要求公民身份,**不会为外国人办工签**。 | 🔴 红灯 |
| **Right to work(工作权)** | 未明说,但 "DoW environments" + clearance 隐含需在美国合法工作且为公民。 | 无工作权 + 无公民身份 = 无法入职。 | 🔴 红灯 |
| **远程限制** | "remoteok" 平台 + "Some team members work remotely" | 远程是"美国境内远程"或"盟友国境内远程",**不等于"全球任意地点远程"**。军工数据受 ITAR/EAR 出口管制,**中国境内远程接触军工系统几乎不可能合法**。 | 🔴 红灯 |
**综合结论:中国人可投性 = 🔴 红灯(硬性不可行)**。
> 理由链:TS/SCI clearance → 需美国公民 → 中国人不满足 → 岗位核心职责(接触军工系统、写 ATO、进指挥体系)无法履行 → 即使简历再匹配也无法录用。
>
> **唯一例外**:若求职者已入外籍(如美籍/盟友国籍)并已持有或可获 clearance,则转为 🟡 黄灯(需核实 clearance 状态)。**本报告按"中国籍、base 中国"假设,判红灯**。
---
**综合评分:约 35 / 100**(假设中国籍、无 clearance)
| 维度 | 求职者 | JD 要求 | 得分逻辑 |
|---|---|---|---|
| 安全合规经验 | 12 年,双体系认证,管过预算 | RMF/STIG/ICD 503 | **部分匹配**:合规思维通,但**具体框架不同**(等保/ISO ≠ RMF/STIG)。+15 |
| 架构能力 | 安全架构师目标岗 | 部署架构、集成设计 | **部分匹配**:安全架构 ≠ 部署工程架构。+8 |
| 售前/客户 | 总监级,带团队 | 强客户存在感、demo | **弱匹配**:管理沟通强,但**售前演示经验存疑**。+5 |
| 工程实操 | 安全负责人 | Docker/K8s/云/IaC/脚本 | **弱匹配**:管理岗可能远离一线实操。+5 |
| 军工/clearance | 无 | TS/SCI + DoW | **不匹配**:硬伤。-0(直接归零项) |
| 出差意愿 | 未知 | 30–50% | 中性。+2 |
**加分点**:
**失分点**:
---
> 前提:**即使补齐技能,clearance 仍是红灯**。以下缺口分析对"若未来身份问题解决"或"投递同类非军工岗位"仍有价值。
| 缺口 |
|---|