Staff Engineer, Platform (R6019)

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to extract content. Let's parse the posting: - Intro: Shield AI description (mission, products, offices). That's about the company, maybe "About the role"? Actually "About the role" could be the description of the role. The job description: "We are looking for a Staff Platform Engineer to contribute to the Platform solutions and infrastructure that power Forge, the AI Factory..." That's the role description. So we can put that under

About the role

with paragraphs. - Responsibilities: The "What you'll do:" bullet list. That's responsibilities. - Key Outcomes maybe also responsibilities? Could be part of responsibilities or separate? The instruction says use headings for sections like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "Required qualifications" and "Preferred qualifications". Those could be under Requirements and Qualifications? Usually "Required qualifications" is Requirements, "Preferred qualifications" could be Qualifications or Skills. But we have separate headings: Requirements, Qualifications, Skills. We need to decide mapping. We have "Required qualifications:" list. That's likely Requirements. We have "Preferred qualifications:" list. That could be Qualifications (or Skills). The list includes many specific technologies; could be considered Skills. But we have also Skills heading. Perhaps we put Preferred qualifications under Skills. Or we could split: Requirements = Required qualifications; Qualifications = Preferred qualifications; Skills maybe not needed if we already covered. But we need to avoid empty sections. If we don't have specific content for Skills, we should not include it. We also have Pay: salary ranges given: "$160,000 - $290,000 a year San Diego, CA pay range: $160,000 - $240,000 San Mateo, CA pay range: $190,000 - $290,000". Also mention bonus, benefits, equity, temporary employee package. So we have Pay section. Benefits: mention "Bonus + Benefits + Equity" and "temporary benefits package". Not detailed but we have some mention. Could include Benefits section with that info. Schedule: mention "Full-time regular employee offer package" and "Temporary employee offer package". Also maybe schedule is full-time. So we can include Schedule section with that. We must not include boilerplate like EEO, AI tools statement, etc. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as in the posting, but we can reformat into HTML. We need to avoid placeholders like "commensurate with experience". Not present. We need to output only HTML fragment. Let's extract substantive content: Company description: "Shield AI is a venture-backed defense-tech company with the mission of protecting service members and civilians with intelligent systems. Its products include Hivemind autonomy software, V-BAT and X-BAT aircraft, and Aechelon simulation and synthetic reality technologies. With offices and facilities across the U.S., Europe, the Middle East, and Asia-Pacific, Shield AI’s technology actively supports operations worldwide. For more information, visit www.shield.ai . Follow Shield AI on LinkedIn , X , Instagram , and YouTube ." But that's maybe boilerplate? It's about the company, not the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description might be considered not boilerplate but maybe part of job posting. It's substantive info about the company. Should we keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. However, we need to decide where to put it. Could be part of About the role? Or maybe a separate section like "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role as introductory paragraph. Now the role description: "We are looking for a Staff Platform Engineer to contribute to the Platform solutions and infrastructure that power Forge, the AI Factory. These components provide distributed runtime capabilities that enable teams to reliably orchestrate workloads, process data, and underpin the workflows of building an AI Pilot. The Forge Platform Engineering team provides Kubernetes-native capabilities that support autonomy development, simulation, testing, training, evaluation, deployment, and operational workflows across commercial cloud, on-premises infrastructure, sovereign deployments, edge environments, and fully air-gapped systems. This is a hands-on technical leadership role. You will define platform architecture, implement production software, establish reusable operational patterns, and partner with teams across autonomy, ML, simulation, test, infrastructure, and product engineering. Success requires balancing developer productivity, reliability, extensibility, performance, portability, and long-term operational maintainability." That's substantive. Now Responsibilities: Under "What you'll do:" list items: - Build Kubernetes-native platform services: Develop and operate Kubernetes-based services, controllers, operators, deployment patterns, and runtime integrations that support distributed workloads across multiple environments. - Develop distributed orchestration capabilities: Design and build reusable primitives for authoring, scheduling, and scaling pipeline work. - Build reliable data-processing infrastructure: Develop platform capabilities for data storage, ingestion, validation, transformation, and governance. - Develop highly extensible platform components: The Forge Platform base provides standardized tooling around authentication, authorization, observation, networking, routing, secret management, and more to the services that are integrated on top of the ecosystem. - Create reference architectures: Establish recommended deployment patterns, operating profiles, capacity guidance, benchmarks, reliability practices, and distribution approaches across cloud providers, on-prem, edge, and air-gapped environments. - Advance observability and operability: Establish end-to-end metrics, logs, traces, structured events, dashboards, alerting, service-level objectives, operational diagnostics, and runbooks for workflows, pipelines, event streams, and platform services. - Partner with downstream teams: Work directly with autonomy, ML Ops, simulation, test, infrastructure, product, and customer-facing teams to turn recurring distributed-systems problems into reusable platform capabilities. We should keep each as

under a

. Now Key Outcomes: This could be considered part of Responsibilities or maybe separate but we don't have a heading for Outcomes. Could incorporate into Responsibilities as additional bullet points? The instruction says we should not invent sections; we can include them under Responsibilities if appropriate. But we might also create a separate section like "Key Outcomes" but not allowed heading. So we should incorporate into Responsibilities maybe as additional bullet points. Key Outcomes bullet list: - The Forge Platform continues to improve in KPIs around reliability, scalability, operational use cases, and customer adoption. - New services from downstream teams are guided to successful platform integration. - Shared distributed services have clear ownership, repeatable deployment patterns, tested recovery procedures, practical observability, and well-defined operational standards. - The Platform is demonstrated, evaluated, and benchmarked across a wide variety of operational environments. - Interfaces are maintained for long periods of time to instill customer confidence and reduce upgrade burdens. We can add these as
• under Responsibilities as well. Now Required qualifications: list: - Significant experience designing and operating production distributed systems, cloud-native platforms, backend infrastructure, or data-intensive services. - Strong software engineering skills and a record of delivering production systems in Go and Python. - Deep understanding of distributed-systems fundamentals, including failure handling, idempotency, consistency tradeoffs, retries, ordering, delivery semantics, backpressure, partitioning, state management, and fault tolerance. - Experience designing or operating workflow orchestration, distributed job execution, asynchronous processing, event-driven systems, or long-running service workflows. - Ability to define architecture and technical standards while remaining hands-on in implementation, production troubleshooting, performance analysis, and reliability improvement. - Experience working across multiple teams to turn recurring infrastructure needs into reusable, well-documented platform capabilities. - Clear technical communication and the ability to make complex distributed-systems architecture understandable to both specialists and downstream users. Now Preferred qualifications: list (beneficial but not required): - Experience in any of the following is beneficial but not required: Kubernetes controllers, operators, Custom Resource Definitions, admission control, scheduling extensions, KubeRay, or workload-management systems. - Distributed execution and workflow technologies such as Ray, Temporal, Argo Workflows, Flyte, Dagster, Airflow, Prefect, Kubernetes Jobs, or comparable systems. - Durable messaging and event-streaming technologies such as NATS JetStream, Kafka, Redpanda, Pulsar, RabbitMQ, SQS/SNS, or comparable systems. - ETL/ELT, batch processing, event-driven data pipelines, CDC, schema evolution, data validation, artifact processing, or large-file transfer workflows. - Service networking technologies and practices such as Envoy, service meshes, Kubernetes networking, and CNI plugins. - Observability software such as OpenTelemetry, Prometheus, Grafana, Loki, Tempo, Jaeger, distributed tracing, structured logging, SLOs, service-level indicators, alerting, and incident-management practices. - Terraform, Helm, ArgoCD, GitOps, Kubernetes package management, repeatable platform distribution, and Infrastructure as Code. Now Why join us: paragraph about Platform Engineering foundational etc. That's maybe more about role benefits; could be part of About the role or Benefits? It's more about why join. Could be placed under About the role as additional paragraph. Now Pay: salary ranges: "$160,000 - $290,000 a year San Diego, CA pay range: $160,000 - $240,000 San Mateo, CA pay range: $190,000 - $290,000" Also mention "#LD" maybe irrelevant. Then "Full-time regular employee offer package: Pay within range listed + Bonus + Benefits + Equity Temporary employee offer package: Pay within range listed above + temporary benefits package (applicable after 60 days of employment) Salary compensation is influenced by a wide array of factors including but not limited to skill set, level of experience, licenses and certifications, and specific work location. All offers are contingent on a cleared background and possible reference check. Military fellows and part-time employees are not eligible for benefits. Please speak to your talent acquisition representative for more information." We need to keep substantive info: pay ranges, bonus, benefits, equity, temporary benefits after 60 days, factors influencing salary, offers contingent on background check, military fellows and part-time not eligible for benefits. We should not include "Please speak to your talent acquisition representative for more information." That's application instruction? Might be considered instruction; we should remove application instructions. So we can drop that sentence. Now Benefits: we have mention of Bonus + Benefits + Equity, temporary benefits package. Not detailed but we can include that. Schedule: Full-time regular employee, Temporary employee offer package. So schedule: Full-time regular, Temporary (maybe contract). We can note that. Now we must not include boilerplate like EEO statement, AI tools statement, etc. Remove those. Now we need to output HTML fragment with sections as needed. Let's decide sections: - About the role: include company description + role description + "Why join us" paragraph maybe. - Responsibilities: include "What you'll do:" bullets + Key Outcomes bullets. - Requirements: Required qualifications list. - Qualifications: Preferred qualifications list (or maybe Skills). Since we have Skills heading, we could put Preferred qualifications under Skills. But we have both Qualifications and Skills headings; we need to decide which to use. The Preferred