Platform Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: description about company, role description, responsibilities list, qualifications and experience, nice to have, compensation & benefits (base salary range, benefits). Also maybe "About the role" could be the introductory paragraphs before responsibilities. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, export compliance, equal opportunity, accommodation request, etc. Also remove application instructions like "If you don’t meet 100%..." maybe that's not boilerplate but could be considered encouraging to apply; but it's not a section heading; we can keep as prose if it's substantive? It's more of encouragement; but we can keep as part of description. However we should remove "If you need a reasonable accommodation..." etc. Also remove "Export Compliance" and "Equal Opportunity". Also remove "If you don’t meet 100%..." maybe keep as it's motivational but not required; but it's not boilerplate; but we can keep as part of description.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must not create sections like Pay/Schedule/Benefits unless posting actually states them. It does state compensation & benefits: base salary range and benefits package. So we can have a Benefits section (maybe combine Pay and Benefits). The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to have Benefits heading and include both salary range and benefits. Or separate Pay and Benefits if we have both. The posting gives base salary range and benefits. So we could have Pay section with salary range, Benefits section with benefits. Or combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into one Benefits section that includes both salary and benefits. But they said include Pay and Benefits sections only if posting actually states them. It does state both. Could make two sections but that's thin. Better to have one Benefits section covering compensation and benefits.
We also need About the role: we can include the introductory paragraphs describing the role and team.
Responsibilities: list of duties.
Qualifications And Experience: we can treat as Requirements or Qualifications. The heading "Qualifications And Experience" is present. We can use
Qualifications
maybe. Or "Requirements". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use Qualifications heading.
Skills: maybe we can include Nice To Have as Skills? Or we could have Skills heading for technical proficiencies. The posting lists proficiency in at least one language, working knowledge of CI/CD, EKS, Datadog etc. Those could be under Skills. Nice To Have could be under Skills as well. But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one Qualifications section that includes both required and nice-to-have. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. It does have qualifications and experience, and also nice-to-have. Could make Qualifications section containing both required and nice-to-have.
We must not repeat job title as heading. No markdown.
Let's extract content:
Company description: "K2 is building the largest and highest-power satellites ever flown, unlocking performance levels previously out of reach across every orbit. Backed by over $1 billion in total funding from leading investors including Altimeter Capital, ICONIQ, Kleiner Perkins, Lightspeed Venture Partners, Redpoint Ventures, and T. Rowe Price — and with over $1 billion in signed contracts across commercial and US government customers, we're mass-producing the highest-power satellite platforms ever built for missions from LEO to deep space. The rise of heavy-lift launch vehicles is shifting the industry from an era of mass constraint to one of mass abundance, and we believe this new era demands a fundamentally different class of spacecraft. Engineered to survive the harshest radiation environments and to fully capitalize on today's and tomorrow's massive rockets, K2 satellites deliver unmatched capability at constellation scale and across multiple orbits. With multiple launches in 2027 and plans to scale to 100 satellites a year, we're Building Bigger — helping develop the solar system and build toward a Kardashev Type II (K2) civilization."
Then: "If you are a motivated individual who thrives in a fast-paced environment and you're excited about contributing to the success of a high-growth Series D-funded company, we'd love for you to apply. Our enterprise software team builds the digital backbone that powers K2 Space’s satellite design, manufacturing, and mission operations. We develop tools that connect engineering, production, and mission control into a seamless ecosystem — enabling our hardware to get from concept to orbit faster than ever before. As we continue to grow, we’re looking for a Senior Platform Engineer on our Enterprise Information Systems team, you must possess strong technical skills and a sense of empathy for your fellow engineers. You will work closely with other talented engineers, architects and senior stakeholders to design, implement, and deliver on our roadmap."
That's About the role.
Responsibilities list:
- Operational support for Amazon EKS self‑service functionalities
- maintain abstractions enabling scoped segmentation, governed namespace, automate workload scaling, multi-tenancy, adaptive ingress/egress, and traceable traffic
- Help implement observability standards so end‑to‑end request path and applied policies are visible (source, identity, route, outcome, saturation, cost) across environments
- Provide approachable docs & diagnostics (guides, diagrams, ‘why can’t this connect?’ flows) to shorten support loops
- Support code lifecycle and adoption including versioning, safe migrations, deprecations, usage telemetry, and proactive pruning of unused resources
- Build automated policies and processes to ensure good code deployment practices, code hygiene, good code test practices
Qualifications And Experience:
- BS in Computer Science (or equivalent) and 2-5 years of experience building and operating distributed systems
- Proficiency in at least one language (Go, TypeScript, Python, C#) and disciplined SCM workflows (branching, reviews, automated gates)
- Working knowledge of:
- CI/CD build pipeline with Github or Gitlab
- Amazon EKS for feature development and operational support
- Datadog, Splunk or OpenTelemetry
Nice To Have:
- Experience with developer connectivity abstractions: K8s CRDs/operators, guardrails (admission, lint, simulation) and automated tests
- Experience with infrastructure as code and delivery: Terraform or CDK, GitOps (GH Actions, Gitlab CI), progressive/canary rollouts, policy-as-code integration
- Familiarity in observability & SLOs (metrics, tracing, structured logs)
Compensation & Benefits:
- Base salary range for this role is $123,000 $160,000 + equity in the company
- Salary will be based on several factors including, but not limited to: knowledge and skills, education, and experience level
- Comprehensive benefits package including paid time off, medical/dental/vision/ coverage, life insurance, paid parental leave, and many other perks
Also there is encouragement: "If you don’t meet 100% of the preferred skills and experience, we encourage you to still apply! Building a spacecraft unlike any other requires a team unlike any other and non-traditional career twists and turns are encouraged!" Could keep as prose under About the role maybe.
We must remove EEO, export compliance, equal opportunity, accommodation request.
Now produce HTML:
About the role
... paragraphs ...
Responsibilities
- ...
...
Qualifications
... maybe combine required and nice-to-have as lists?
Could have two lists: Required Qualifications and Nice-to-Have Skills. But we could keep as one Qualifications section with subheadings? Not allowed to add extra headings beyond . Could use
with bold? Not needed. Could use
for required and another for nice-to-have within same section, but that's okay.
We need to preserve all substantive information. So we should include both required and nice-to-have details.
Thus:
Qualifications
Required:
- BS in Computer Science (or equivalent) and 2-5 years of experience building and operating distributed systems
- Proficiency in at least one language (Go, TypeScript, Python, C#) and disciplined SCM workflows (branching, reviews, automated gates)
- Working knowledge of:
- CI/CD build pipeline with Github or Gitlab
- Amazon EKS for feature development and operational support
- Datadog, Splunk or OpenTelemetry
Nice to have:
- Experience with developer connectivity abstractions: K8s CRDs/operators, guardrails (admission, lint, simulation) and automated tests
- Experience with infrastructure as code and delivery: Terraform or CDK, GitOps (GH Actions, Gitlab CI), progressive/canary rollouts, policy-as-code integration
- Familiarity in observability & SLOs (metrics, tracing, structured logs)
But note we cannot nest inside - ? Actually we can, but it's okay. However we might want to keep simple: just list items.
Simplify: Required qualifications as list items; Nice to have as separate list.
Now Benefits/Pay section:
Benefits and Compensation
Base salary range for this role is $123,000 – $160,000 + equity in the company. Salary will be based on several factors including, but not limited to: knowledge and skills, education, and experience level.
Comprehensive benefits package including paid time off, medical/dental/vision coverage, life insurance, paid parental leave, and many other perks.
Note: original had "$123,000 $160,000" missing a dash; we can format as "$123,000 – $160,000". Keep as is but maybe add dash for readability; but we must not invent info. Changing format might be considered altering? It's still same numbers; adding dash is not inventing, just punctuation. Probably okay.
Now About the role paragraph: combine the introductory paragraphs and the encouragement sentence.
Let's craft:
K2 is building the largest and highest-power satellites ever flown, unlocking performance levels previously out of reach across every orbit. Backed by over $1 billion in total funding from leading investors including Altimeter Capital, ICONIQ, Kleiner Perkins, Lightspeed Venture Partners, Redpoint Ventures, and T. Rowe Price — and with over $1 billion in signed contracts across commercial and US government customers, we're mass-producing the highest-power satellite platforms ever built for missions from LEO to deep space. The rise of heavy-lift launch vehicles is shifting the industry from an era of mass constraint to one of mass abundance, and we believe this new era demands a fundamentally different class of spacecraft. Engineered to survive the harshest radiation environments and to fully capitalize on today's and tomorrow's massive rockets, K2 satellites deliver unmatched capability at constellation scale and across multiple orbits. With multiple launches in 2027 and plans to scale to 100 satellites a year, we're Building Bigger — helping develop the solar system and build toward a Kardashev Type II (K2
for prose. We must not create sections like Pay/Schedule/Benefits unless posting actually states them. It does state compensation & benefits: base salary range and benefits package. So we can have a Benefits section (maybe combine Pay and Benefits). The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to have Benefits heading and include both salary range and benefits. Or separate Pay and Benefits if we have both. The posting gives base salary range and benefits. So we could have Pay section with salary range, Benefits section with benefits. Or combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into one Benefits section that includes both salary and benefits. But they said include Pay and Benefits sections only if posting actually states them. It does state both. Could make two sections but that's thin. Better to have one Benefits section covering compensation and benefits. We also need About the role: we can include the introductory paragraphs describing the role and team. Responsibilities: list of duties. Qualifications And Experience: we can treat as Requirements or Qualifications. The heading "Qualifications And Experience" is present. We can use
Qualifications
maybe. Or "Requirements". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use Qualifications heading. Skills: maybe we can include Nice To Have as Skills? Or we could have Skills heading for technical proficiencies. The posting lists proficiency in at least one language, working knowledge of CI/CD, EKS, Datadog etc. Those could be under Skills. Nice To Have could be under Skills as well. But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one Qualifications section that includes both required and nice-to-have. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. It does have qualifications and experience, and also nice-to-have. Could make Qualifications section containing both required and nice-to-have. We must not repeat job title as heading. No markdown. Let's extract content: Company description: "K2 is building the largest and highest-power satellites ever flown, unlocking performance levels previously out of reach across every orbit. Backed by over $1 billion in total funding from leading investors including Altimeter Capital, ICONIQ, Kleiner Perkins, Lightspeed Venture Partners, Redpoint Ventures, and T. Rowe Price — and with over $1 billion in signed contracts across commercial and US government customers, we're mass-producing the highest-power satellite platforms ever built for missions from LEO to deep space. The rise of heavy-lift launch vehicles is shifting the industry from an era of mass constraint to one of mass abundance, and we believe this new era demands a fundamentally different class of spacecraft. Engineered to survive the harshest radiation environments and to fully capitalize on today's and tomorrow's massive rockets, K2 satellites deliver unmatched capability at constellation scale and across multiple orbits. With multiple launches in 2027 and plans to scale to 100 satellites a year, we're Building Bigger — helping develop the solar system and build toward a Kardashev Type II (K2) civilization." Then: "If you are a motivated individual who thrives in a fast-paced environment and you're excited about contributing to the success of a high-growth Series D-funded company, we'd love for you to apply. Our enterprise software team builds the digital backbone that powers K2 Space’s satellite design, manufacturing, and mission operations. We develop tools that connect engineering, production, and mission control into a seamless ecosystem — enabling our hardware to get from concept to orbit faster than ever before. As we continue to grow, we’re looking for a Senior Platform Engineer on our Enterprise Information Systems team, you must possess strong technical skills and a sense of empathy for your fellow engineers. You will work closely with other talented engineers, architects and senior stakeholders to design, implement, and deliver on our roadmap." That's About the role. Responsibilities list: - Operational support for Amazon EKS self‑service functionalities - maintain abstractions enabling scoped segmentation, governed namespace, automate workload scaling, multi-tenancy, adaptive ingress/egress, and traceable traffic - Help implement observability standards so end‑to‑end request path and applied policies are visible (source, identity, route, outcome, saturation, cost) across environments - Provide approachable docs & diagnostics (guides, diagrams, ‘why can’t this connect?’ flows) to shorten support loops - Support code lifecycle and adoption including versioning, safe migrations, deprecations, usage telemetry, and proactive pruning of unused resources - Build automated policies and processes to ensure good code deployment practices, code hygiene, good code test practices Qualifications And Experience: - BS in Computer Science (or equivalent) and 2-5 years of experience building and operating distributed systems - Proficiency in at least one language (Go, TypeScript, Python, C#) and disciplined SCM workflows (branching, reviews, automated gates) - Working knowledge of: - CI/CD build pipeline with Github or Gitlab - Amazon EKS for feature development and operational support - Datadog, Splunk or OpenTelemetry Nice To Have: - Experience with developer connectivity abstractions: K8s CRDs/operators, guardrails (admission, lint, simulation) and automated tests - Experience with infrastructure as code and delivery: Terraform or CDK, GitOps (GH Actions, Gitlab CI), progressive/canary rollouts, policy-as-code integration - Familiarity in observability & SLOs (metrics, tracing, structured logs) Compensation & Benefits: - Base salary range for this role is $123,000 $160,000 + equity in the company - Salary will be based on several factors including, but not limited to: knowledge and skills, education, and experience level - Comprehensive benefits package including paid time off, medical/dental/vision/ coverage, life insurance, paid parental leave, and many other perks Also there is encouragement: "If you don’t meet 100% of the preferred skills and experience, we encourage you to still apply! Building a spacecraft unlike any other requires a team unlike any other and non-traditional career twists and turns are encouraged!" Could keep as prose under About the role maybe. We must remove EEO, export compliance, equal opportunity, accommodation request. Now produce HTML:About the role
... paragraphs ...
Responsibilities
- ... ...
Qualifications
... maybe combine required and nice-to-have as lists?
Could have two lists: Required Qualifications and Nice-to-Have Skills. But we could keep as one Qualifications section with subheadings? Not allowed to add extra headings beyond. Could use
with bold? Not needed. Could use
- for required and another
- BS in Computer Science (or equivalent) and 2-5 years of experience building and operating distributed systems
- Proficiency in at least one language (Go, TypeScript, Python, C#) and disciplined SCM workflows (branching, reviews, automated gates)
- Working knowledge of:
- CI/CD build pipeline with Github or Gitlab
- Amazon EKS for feature development and operational support
- Datadog, Splunk or OpenTelemetry
- Experience with developer connectivity abstractions: K8s CRDs/operators, guardrails (admission, lint, simulation) and automated tests
- Experience with infrastructure as code and delivery: Terraform or CDK, GitOps (GH Actions, Gitlab CI), progressive/canary rollouts, policy-as-code integration
- Familiarity in observability & SLOs (metrics, tracing, structured logs)
- ? Actually we can, but it's okay. However we might want to keep simple: just list items.
Simplify: Required qualifications as list items; Nice to have as separate list.
Now Benefits/Pay section:
Benefits and Compensation
Base salary range for this role is $123,000 – $160,000 + equity in the company. Salary will be based on several factors including, but not limited to: knowledge and skills, education, and experience level.
Comprehensive benefits package including paid time off, medical/dental/vision coverage, life insurance, paid parental leave, and many other perks.
Note: original had "$123,000 $160,000" missing a dash; we can format as "$123,000 – $160,000". Keep as is but maybe add dash for readability; but we must not invent info. Changing format might be considered altering? It's still same numbers; adding dash is not inventing, just punctuation. Probably okay. Now About the role paragraph: combine the introductory paragraphs and the encouragement sentence. Let's craft:K2 is building the largest and highest-power satellites ever flown, unlocking performance levels previously out of reach across every orbit. Backed by over $1 billion in total funding from leading investors including Altimeter Capital, ICONIQ, Kleiner Perkins, Lightspeed Venture Partners, Redpoint Ventures, and T. Rowe Price — and with over $1 billion in signed contracts across commercial and US government customers, we're mass-producing the highest-power satellite platforms ever built for missions from LEO to deep space. The rise of heavy-lift launch vehicles is shifting the industry from an era of mass constraint to one of mass abundance, and we believe this new era demands a fundamentally different class of spacecraft. Engineered to survive the harshest radiation environments and to fully capitalize on today's and tomorrow's massive rockets, K2 satellites deliver unmatched capability at constellation scale and across multiple orbits. With multiple launches in 2027 and plans to scale to 100 satellites a year, we're Building Bigger — helping develop the solar system and build toward a Kardashev Type II (K2
- for nice-to-have within same section, but that's okay.
We need to preserve all substantive information. So we should include both required and nice-to-have details.
Thus:
Qualifications
Required:
Nice to have:
- inside