{
  "schemaVersion": 1,
  "id": "openai-swe-2026-11-10",
  "company": "OpenAI",
  "roleFamily": "Software Engineer / SDE",
  "researchedAt": "2026-11-10",
  "mode": "reviewed_snapshot",
  "method": "公开职位界定范围 → 阅读面经及官方指南 → 提取面试观察 → 反推可展示能力 → 设计练习产物与自测标准",
  "limits": [
    "本版是 2026-11-10 已阅读来源的研究快照；打开报告不会重新联网搜索。当前支持 OpenAI 的三个已核查职位。",
    "未找到能确认属于这三个具体团队的面经。所有候选人叙述只作同公司 SWE 的参考，不能当作该职位的固定流程或必考题。",
    "匿名作者的身份、题目及结果均未独立核实；转载不计作新的独立面试，样本不支持题频、通过率或录用概率估计。",
    "下面的能力映射、练习、时间盒和自测标准由 OFABU 推导和设计，均不是 OpenAI 官方评分规则。",
    "没有读取候选人简历或做个人差距诊断；完成训练记录不等于达到录用标准。"
  ],
  "sources": [
    {
      "id": "O1", "kind": "official", "title": "OpenAI Interview Guide", "url": "https://openai.com/interview-guide/", "publisher": "OpenAI", "publishedAt": null, "interviewAt": null, "checkedAt": "2026-11-10", "access": "full", "group": "openai-official-guide", "role": "全公司；工程面试另有说明",
      "observation": "官方说明工程面试看方案质量、代码、性能、测试，以及沟通协作；考核形式和 AI 工具政策随团队及轮次变化。",
      "locator": "Interview process → Skills-based assessment / Final interviews",
      "caveat": "官方通用说明，不提供本岗位题库或精确评分线。"
    },
    {
      "id": "J1", "kind": "official", "title": "Software Engineer, Core Services", "url": "https://openai.com/careers/software-engineer-core-services-san-francisco/", "publisher": "OpenAI Careers", "publishedAt": null, "interviewAt": null, "checkedAt": "2026-11-10", "access": "full", "group": "openai-core-services-jd", "role": "Core Services / Applied AI Infrastructure",
      "observation": "岗位涉及共享缓存、工作流、元数据及文件服务，强调分布式一致性、复制、跨区域性能与生产运维。",
      "locator": "About the Role / In this role, you will / You might thrive",
      "caveat": "JD 说明工作内容与能力相关性，不证明某道题会出现。"
    },
    {
      "id": "J2", "kind": "official", "title": "Backend Software Engineer, Applied Foundations", "url": "https://openai.com/careers/backend-software-engineer-applied-foundations-san-francisco/", "publisher": "OpenAI Careers", "publishedAt": null, "interviewAt": null, "checkedAt": "2026-11-10", "access": "full", "group": "openai-applied-foundations-jd", "role": "Backend / Applied Foundations",
      "observation": "岗位覆盖大规模后端 API、存取与数据流水线，要求可靠性、安全性、跨团队合作及端到端负责。",
      "locator": "About the Team / What You'll Do / You Might Thrive Here If",
      "caveat": "语言例子不是完整面试语言白名单，具体工具与语言应向招聘方确认。"
    },
    {
      "id": "J3", "kind": "official", "title": "Software Engineer, Database Systems", "url": "https://openai.com/careers/software-engineer-database-systems-san-francisco/", "publisher": "OpenAI Careers", "publishedAt": null, "interviewAt": null, "checkedAt": "2026-11-10", "access": "full", "group": "openai-database-systems-jd", "role": "Database Systems / Applied AI Infrastructure",
      "observation": "岗位强调数据库引擎、查询与存储性能、生产故障处理；核心引擎使用 C++，系统语言能力受偏好。",
      "locator": "About the Role / Qualifications",
      "caveat": "JD 将数据库领域知识列为加分项；不能把全部数据库内部知识都改写成硬门槛。"
    },
    {
      "id": "E1", "kind": "self_report", "title": "Software Engineer — October 8, 2026", "url": "https://static.glassdoor.com/Interview/OpenAI-Software-Engineer-Interview-Questions-EI_IE2210885.0,6_KO7,24.htm", "publisher": "Glassdoor / 匿名自述", "publishedAt": "2026-10-08", "interviewAt": "2026-10", "checkedAt": "2026-11-10", "access": "full_entry", "group": "glassdoor-2026-10-08", "role": "Software Engineer；团队与级别未注明",
      "observation": "该条自述描述逐步增加需求的编码、测试、既有代码修复，以及系统设计和项目追问。",
      "locator": "Oct 8, 2026 → Interview（非页面总体统计）",
      "caveat": "匿名且含商业服务推荐，无法独立核实；同文在其他站点的镜像不另计一次面试。"
    },
    {
      "id": "E2", "kind": "self_report", "title": "OAI SDE BE 店面新鲜出炉", "url": "https://www.1point3acres.com/bbs/thread-1152021-1-1.html", "publisher": "一亩三分地 / ben_viv", "publishedAt": "2025-10-29", "interviewAt": "2025-10", "checkedAt": "2026-11-10", "access": "partial", "group": "1p3a-thread-1152021", "role": "SDE Backend；具体团队与级别未注明",
      "observation": "公开段落提到聊天系统设计、大频道扇出与通知，并自述编码速度不足、需要补充编码考核。",
      "locator": "主帖公开可见段落",
      "caveat": "超过一年，仅作历史参照。题目细节有积分限制，未读取隐藏段落，也不据标题补全。"
    },
    {
      "id": "E3", "kind": "self_report", "title": "OpenAI SWE Interview Experience — full loop breakdown", "url": "https://www.reddit.com/r/InterviewCoderHQ/comments/1rhfjpw/openai_swe_interview_experience_full_loop/", "publisher": "Reddit / u/juneska", "publishedAt": "2026-02-28", "interviewAt": null, "checkedAt": "2026-11-10", "access": "public_post", "group": "reddit-juneska-platform-loop", "role": "Platform SWE；级别未确认",
      "observation": "作者描述可靠 webhook 作业、现场扩展、worker 崩溃恢复讨论、数据库设计及项目和行为追问。",
      "locator": "Take Home / Technical Deep Dive / System Design / Behavioral",
      "caveat": "匿名第一人称，发在面试工具社群，身份和叙述未核实；评论中也有人报告未做 take-home。发布日期不是面试日期。"
    },
    {
      "id": "E4", "kind": "edited_report", "title": "Phone, Virtual Onsite, and a Silent Extra Round", "url": "https://prachub.com/interview-experiences/openai-software-engineer-interview-experience-phone-virtual-onsite-and-a-silent-extra-round", "publisher": "PracHub / 编辑整理", "publishedAt": "2026-08-25", "interviewAt": "2026-07", "checkedAt": "2026-11-10", "access": "public_article", "group": "prachub-jul-2026-extra-round", "role": "Software Engineer；团队与级别未注明",
      "observation": "编辑稿描述多阶段编码未调通、设计中的队列和故障追问，以及加面陌生任务时澄清不足。",
      "locator": "Phone Screen / Virtual Onsite / extra round",
      "caveat": "平台编辑稿，原作者与原始帖子未确认，可能与其他站点同源；仅作辅助线索。"
    },
    {
      "id": "E5", "kind": "edited_report", "title": "Senior SWE — It Felt More Like Real Engineering", "url": "https://www.reddit.com/r/OfferEngineering/comments/1wzedra/openai_senior_software_engineer_interview_it_felt/", "publisher": "Reddit / Chill Interview 转载推广", "publishedAt": "2026-10-06", "interviewAt": null, "checkedAt": "2026-11-10", "access": "public_excerpt", "group": "chill-interview-openai-oct-2026", "role": "Senior SWE；与所选团队未确认匹配",
      "observation": "公开摘要提到聊天产品设计、自定义数据结构和调试 Python 调度器；正文可见流式协议与需求澄清讨论。",
      "locator": "Interview Summary / Round 1 / Round 2",
      "caveat": "明确转载并推广外站，不当作第一手经历；全文链接后的内容未读取。"
    }
  ],
  "jobs": [
    {
      "id": "core-services", "title": "Software Engineer, Core Services", "sourceId": "J1", "location": "San Francisco", "scope": "SDE / 后端基础设施", "summary": "从缓存、工作流和元数据服务的实际职责，倒推你要能证明的可靠性与工程判断。",
      "priority": ["reliability", "coding", "debugging", "project", "collaboration"],
      "focus": {"title": "岗位专项：缓存与工作流的故障边界", "result": "一份共享缓存 + 异步工作流设计说明，标出一致性和故障恢复边界。", "reason": "J1 明确列出缓存、工作流和跨区域一致性；这是岗位相关性推导，没有该团队必考证据。", "topics": ["缓存失效与热点", "重试、租约与幂等", "元数据一致性与跨区域复制", "生产监控与 CI/CD"], "exercise": "给一个文件处理服务加入缓存和异步工作流。分别模拟缓存全失效、worker 重启和区域不可用，写出用户可见结果及恢复步骤。", "checks": ["说明源数据和缓存谁是权威，陈旧数据可接受多久", "明确重复执行时业务效果如何处理", "在性能、可用性和一致性间做出有条件的取舍"]}
    },
    {
      "id": "applied-foundations", "title": "Backend Software Engineer, Applied Foundations", "sourceId": "J2", "location": "San Francisco / Mountain View", "scope": "SDE / 产品后端", "summary": "从 API、数据服务与安全的实际职责，倒推端到端后端实现与运维能力。",
      "priority": ["coding", "reliability", "project", "debugging", "collaboration"],
      "focus": {"title": "岗位专项：可安全重试的业务 API", "result": "一份创建资源 API 的实现与运维说明，覆盖认证、数据保存和可观察性。", "reason": "J2 同时要求后端 API、可靠性、安全和跨团队交付；不能因此断言一定考支付题。", "topics": ["API 契约与数据建模", "认证、授权与滥用控制", "幂等及事务边界", "性能与故障定位"], "exercise": "设计并实现一个创建任务的 API：重复请求、超时重试、权限不足和下游失败都有明确行为；解释如何平滑上线。", "checks": ["重复请求不会生成多个业务资源", "授权检查覆盖读取与写入，错误不泄露敏感信息", "写出可用于发现失败和延迟的指标及回滚条件"]}
    },
    {
      "id": "database-systems", "title": "Software Engineer, Database Systems", "sourceId": "J3", "location": "San Francisco / Mountain View", "scope": "SDE / 数据库系统", "summary": "从数据库引擎和生产性能的职责，倒推正确性、性能诊断与系统深度；这与产品后端的重点不同。",
      "priority": ["debugging", "reliability", "coding", "project", "collaboration"],
      "focus": {"title": "岗位专项：用测量证明一次性能改进", "result": "一个小型键值存储原型及基准记录，清楚区分实现范围与未实现保证。", "reason": "J3 关注引擎性能和生产问题，并偏好 C++ 等系统语言；领域知识为加分项，不是全部硬要求。", "topics": ["查询、索引和存储的代价", "内存布局、剖析与基准测试", "并发正确性与恢复", "生产故障与可观察性"], "exercise": "实现可插入、查询和删除的小型存储，构造一种明确负载，定位瓶颈后比较改进前后结果。持久化和事务可作为扩展，先说明范围。", "checks": ["基准写明数据量、负载、环境与重复次数", "用剖析或可复现实验支持瓶颈判断", "优化后正确性测试通过，明确尚未提供的事务和持久化保证"]}
    }
  ],
  "outcomes": [
    {
      "id": "coding", "title": "能交付会变化的正确代码", "artifact": "一份可运行、可扩展、有边界测试的小程序。", "sourceIds": ["O1", "E1", "E4"],
      "observation": "官方看重代码和测试；两条未经独立核实的经历提到多阶段需求、调试或未完成。",
      "inference": "要展示的不是记住一道答案，而是在需求变化后仍守住状态约束、解释复杂度并验证行为。",
      "topics": ["需求澄清与接口契约", "状态建模、不变量、时间边界", "合适的数据结构与复杂度", "可执行测试与回归"],
      "exercise": "原创练习：有有效期的权益账本。先支持发放和使用，再加入过期、重复事件和乱序到达。自己明确区间端点、额度不足及回溯查询语义，再实现。",
      "timebox": "建议自测：45 分钟实现，再用 15 分钟加入一项新需求。",
      "checks": ["写明 API 与时间语义，不依赖面试者猜测", "测试空输入、过期端点、重复、乱序和额度不足", "增加新需求后原测试仍通过，能解释数据结构代价"],
      "confidence": "代码与测试方向有官方依据；具体形式来自匿名面经，适用团队未确认。"
    },
    {
      "id": "reliability", "title": "能解释系统在故障下怎样工作", "artifact": "一份有失败路径的设计，加一个能演示恢复的最小服务。", "sourceIds": ["O1", "E2", "E3", "E4"],
      "observation": "可见面经涉及扇出、队列选择和 worker 崩溃恢复；这些观察与所选后端 JD 的可靠性职责相符。",
      "inference": "准备内容应落到业务语义和失败时序：何时重试、谁去重、任务何时可重领，以及系统怎样知道自己坏了。",
      "topics": ["队列、租约与重试退避", "幂等键、事务及去重边界", "扇出、背压与故障隔离", "指标、告警与容量假设"],
      "exercise": "原创练习：可靠通知投递器。实现入队、worker、失败重试、查询状态和失败终态；注入超时，以及副作用已发生但确认未保存时的崩溃。",
      "timebox": "建议自测：一次设计讨论，加一个可重复运行的故障演示。",
      "checks": ["能画出任务状态变化和崩溃时序", "重复投递不会产生重复业务效果，或明确说明无法保证及补偿方案", "任务能在租约到期后恢复，耗尽重试有终态和可观察信号"],
      "confidence": "岗位相关性由 JD 支持；具体考题与失败归因只来自未核实自述。"
    },
    {
      "id": "debugging", "title": "能读懂并修复陌生代码", "artifact": "一个最小复现、最小修复和回归测试。", "sourceIds": ["O1", "E1", "E5"],
      "observation": "一条匿名经历和一条转载摘要提到修复已有代码；官方对代码质量与测试的要求提供更稳固依据。",
      "inference": "只从空文件练题会漏掉读代码、提出假设、缩小故障和验证修复的能力。",
      "topics": ["快速建立调用与状态模型", "最小复现与诊断假设", "异步、重试和边界条件", "最小变更与回归测试"],
      "exercise": "原创练习：让同伴给一个已有任务调度器注入未公开的状态或重试 bug。先写失败测试，再修改实现；不要先重写整个系统。",
      "timebox": "建议自测：30 分钟定位与修复，再用 5 分钟说明根因。",
      "checks": ["修复前测试稳定失败，修复后通过", "指出触发条件、根因和受影响范围", "正常路径测试仍通过，说明剩余风险"],
      "confidence": "值得准备，但现有证据不能证明所选团队一定设置独立调试轮。"
    },
    {
      "id": "project", "title": "能为自己做过的工程决策辩护", "artifact": "两份真实项目档案：一份交付，一份故障或失败。", "sourceIds": ["O1", "E1", "E3"],
      "observation": "官方会了解经验和推理；自述中的项目深挖会延伸到架构选择、生产问题和现场扩展。",
      "inference": "要倒推准备的是可追问的决策链：当时约束是什么、替代方案是什么、为什么这样选、实际结果和教训是什么。",
      "topics": ["个人职责与团队贡献边界", "架构决策与被放弃的方案", "真实测量、事故和回滚", "反馈后怎样修正判断"],
      "exercise": "原创练习：各写一页交付与故障档案，附图、关键时序及可以公开的事实；找同伴连续追问三层为什么。",
      "timebox": "建议自测：10 分钟讲解，20 分钟追问。",
      "checks": ["清楚区分本人负责与团队整体成果", "每个关键取舍都能解释至少一个替代方案", "数字有依据；不知道或不能披露的内容明确说明"],
      "confidence": "方向与官方一致；准备两份档案和追问深度是 OFABU 的训练设计。"
    },
    {
      "id": "collaboration", "title": "能在模糊目标下协作并解释取舍", "artifact": "三段真实案例，加一份面向招聘方的问题清单。", "sourceIds": ["O1", "E3", "E4"],
      "observation": "官方强调沟通、合作、反馈及使命认同；经历中也出现行为追问或任务理解偏差。",
      "inference": "准备应覆盖澄清假设、分歧处理、承认错误、用户影响及为什么选择该团队，而不是背一段统一的公司使命。",
      "topics": ["澄清需求与主动同步", "冲突、失败及反馈", "安全、隐私和用户影响", "对团队工作的具体理解"],
      "exercise": "原创练习：从真实经历整理技术分歧、失败后改进、风险取舍三个案例；用新约束追问，检查答案是否仍然成立。",
      "timebox": "建议自测：每个案例先讲 2 分钟，再接受 5 分钟追问。",
      "checks": ["讲清楚自己采取的行动及真实结果", "能说明对方立场，以及哪些新证据会改变决定", "确认具体团队、语言、AI 工具政策及考核形式，未知项不靠面经猜测"],
      "confidence": "通用方向有官方依据；具体问题及轮次并不确定。"
    }
  ],
  "recruiterQuestions": [
    "这份职位属于哪个具体团队与级别？公开 JD 和实际考核重点有无差异？",
    "有哪些轮次：现场编码、已有代码调试、设计、项目深挖或 take-home？",
    "每一轮允许哪些编程语言、IDE、文档和 AI 工具？",
    "设计轮关注产品 API、基础设施还是数据库内部？预计多大讨论范围？"
  ],
  "searchLog": [
    {"query": "OpenAI software engineer interview experience 2026 2025 onsite coding system design", "purpose": "发现英文 SWE 叙述与可能同源的转载"},
    {"query": "site.openai.com/careers software engineer backend", "purpose": "绑定真实公开职位，排除 Research Engineer 等其他岗位"},
    {"query": "site.openai.com Interview guide", "purpose": "用官方说明约束对流程、工具与能力的推断"},
    {"query": "OpenAI 面经 SDE 软件工程师 面试 2026 2025", "purpose": "发现中文原帖；仅使用可公开阅读部分"}
  ]
}