platform-engineering skillA
platform-engineering is agent-read markdown (skill) from yuecao365/offercome: 平台工程深挖：IaC、K8s 运维、容量与成本、灾备多活、内部开发者平台、GPU 集群、多云。.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## 面试官在意什么 这本是 SRE 往平台方向的深挖：把基础设施做成产品给几十个团队用。面试官看的是规模与代价：IaC 漂移怎么治、容量怎么规划、成本怎么归因到团队、灾备演练过没有、平台的抽象泄漏了什么。2026 年多了 GPU 集群与 AI 负载：调度、利用率、配额与成本成了平台团队的新 KPI。 ## 项目 / 实习怎么深挖 简历上出现下面这类经历时从哪里切、追什么。追到候选人能说出机制、数字的来源与一次真实的故障或取舍才算实；只有框架名与结论、说不出自己那一段的，记为危险信号。通用的追问方法见 project-deep-dive。 - 简历出现 Terraform / IaC / GitOps → 追漂移怎么发现、状态怎么管、一次 apply 出事故的经历、审批流程 - 简历出现容量 / 成本 → 追成本归因到哪一级、省了多少、怎么防止反弹、利用率数字 - 简历出现灾备 / 多活 → 追 RPO / RTO、演练频率、上次演练发现了什么 - 简历出现内部平台 / 开发者门户 → 追用户是谁、采用率、抽象泄漏了什么、平台团队怎么接需求 - 简历出现 GPU 集群 → 追调度策略、利用率、配额与抢占、故障率 - 简历出现多云 / 混合云 → 追为什么多云、抽象在哪一层、成本与复杂度 ## 常见失守与危险信号 - 基础设施即代码与配置管理：手工改线上再补代码；不知道状态漂移；没有审批与计划预览 - 容量规划与成本治理：容量拍脑袋；成本只看总账不归因；省成本靠砍资源不看利用率 - 高可用与灾备架构：只说"两地三中心"；从没演练；RPO / RTO 没有数字 - 自动化与平台化思维：把脚本堆成平台；没有用户视角；抽象泄漏一堆 - 编排平台运维：升级靠祈祷；不知道控制面与数据面的故障差别 - 内部开发者平台：平台没人用；接口设计不考虑自服务；文档缺失 - GPU 集群与 AI 负载：GPU 利用率不监控；调度还用 CPU 的思路；配额与抢占没有策略 - 多云与供应商锁定：为多云而多云；抽象层成本比收益高 ## 常考主题清单 只列名字、阶梯与答实的标志，作"问到哪一层算实"的参考；问哪些、问几道由这份 JD 与这份简历定，不是配额。 ### 编排平台运维（Kubernetes 视角） - 阶梯：Pod、Deployment、Service 分别解决什么 → 调度、探针、资源 request/limit、HPA 的机制 → Pod Pending/CrashLoopBackOff/Evicted 各怎么查、节点 NotReady 怎么处理 → 集群规模、多集群、升级策略与平台自治程度的取舍（细节交给 infra-k8s 包） …
Read the whole file at its exact version.
How to install
mdr add yuecao365/offercome/platform-engineering@git:20260920.a4843f5mdr add yuecao365/offercome/platform-engineering@sha256:47013af1d5402eabPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_zff6plssijtt3xpp)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6402 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yuecao365/offercome · 23 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zff6plssijtt3xpp GET https://markdownregistry.com/api/v1/resolve?ref=yuecao365/offercome/platform-engineering GET https://markdownregistry.com/api/v1/blob/47013af1d5402eabcf6265ba5de95ac2380b3501ff6c78b8f27d6b0e0b5abe0a
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from yuecao365/offercome
Every file in yuecao365/offercome