Staff Platform Engineer
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not invent or summarize away detail. So we need to keep specifics.
Let's extract sections:
About The Role paragraph: "We are looking for a Staff Platform Engineer to join Horizon3’s Internal Platform Team (IPT) and shape the cloud and delivery foundations behind NodeZero. You will lead complex, cross-team initiatives; define platform direction; improve developer workflows; and establish standards that make our systems secure, reliable, and easier to operate. This is a hands-on technical leadership role for an engineer who enjoys solving ambiguous problems and building reusable platform capabilities."
That's prose.
Responsibilities: two sub-sections: Platform Strategy, Delivery & Operations and Technical Leadership & Collaboration. Each has bullet-like sentences separated by periods. We need to turn into list items. Probably each sentence after a semicolon? Better to split by periods that start with a capital letter after a semicolon? Let's just treat each bullet as a separate line starting with a capital letter after a period? The text:
"Platform Strategy, Delivery & Operations
Lead the design and evolution of AWS, Kubernetes/EKS, and shared platform services.
Define architecture for infrastructure automation, service delivery, regional capabilities, and ephemeral environments.
Build reusable platform capabilities, self-service workflows, and release-safety practices.
Evolve infrastructure-as-code and declarative approaches, including Terraform and Crossplane-related capabilities.
Improve platform reliability, observability, security, performance, and operability.
Participate in on-call and incident response, leading post-incident improvements."
Then "Technical Leadership & Collaboration
Drive high-impact initiatives across multiple teams and balance reliability, security, cost, developer experience, and delivery speed.
Establish platform standards, reduce technical debt, and guide design decisions.
Partner with feature teams to turn platform needs into durable solutions.
Mentor engineers and raise the technical bar across Engineering.
Improve documentation, runbooks, interfaces, and self-service paths.
Communicate clearly and build alignment across Platform, Application Engineering, Data Engineering, Product, Program Management, and Security."
We'll make a
with each line as - .
Requirements: "What You’ll Bring" includes Required Qualifications and Preferred Qualifications. We'll combine into a list? Could separate Required and Preferred as subheadings? But we only have headings for sections; we could keep as one list but note required vs preferred? Might lose nuance. Better to have two subsections under Requirements? But we only allowed headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "Requirements" for required qualifications and "Preferred Qualifications" as a separate section? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections. We'll put Required Qualifications under Requirements, Preferred Qualifications under Qualifications.
Thus:
Requirements
with list of required qualifications.
Qualifications
with list of preferred qualifications.
We must not repeat job title.
Now Benefits: "Perks of Horizon3" includes bullet points: Inclusive Team, Growth Opportunities, Innovative Culture, Hybrid & Remote Work, Competitive Compensation (with details). Also maybe "Travel Occasional travel may be required..." Not a perk; we could omit.
We'll make a list.
Pay: "Compensation And Values" includes base salary range and equity package. Also mentions compensation philosophy. We'll include that as prose maybe plus list? We'll put as
for prose and maybe
for details? The salary range is a specific detail; we can put in . Equity package mention.
We must not include filler like "commensurate with experience". Not present.
Now ensure we remove boilerplate: "Our Platform Stack" maybe not needed as a section; but it's substantive? It lists stack. Could be included under About the role? Might be considered part of role description. Could add as a separate section "Platform Stack"? Not in allowed headings list but we could maybe treat as part of Responsibilities? The instruction: Prefer a few substantive sections over many thin ones. So maybe we incorporate stack into Responsibilities or About the role. But we already have Responsibilities covering duties. The stack is more about tools; could be part of Requirements? Actually it's under "Our Platform Stack". Could be considered part of Requirements (tools used). Might be appropriate to include under Requirements as a list? But we already have Required Qualifications list; we could add a note about stack. However the instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the stack somewhere. Could add a section "Skills" maybe? The allowed headings include Skills. So we could put stack under Skills. That seems appropriate.
Thus we will have:
- About the role (p)
- Responsibilities (ul)
- Requirements (ul) for required qualifications
- Qualifications (ul) for preferred qualifications
- Skills (ul) for platform stack
- Benefits (ul) for perks
- Pay (p) for compensation details
We must not include Schedule.
Now let's extract each piece precisely.
About the role paragraph: exactly as above.
Responsibilities: list each line.
Let's copy lines:
Platform Strategy, Delivery & Operations
- Lead the design and evolution of AWS, Kubernetes/EKS, and shared platform services.
- Define architecture for infrastructure automation, service delivery, regional capabilities, and ephemeral environments.
- Build reusable platform capabilities, self-service workflows, and release-safety practices.
- Evolve infrastructure-as-code and declarative approaches, including Terraform and Crossplane-related capabilities.
- Improve platform reliability, observability, security, performance, and operability.
- Participate in on-call and incident response, leading post-incident improvements.
Technical Leadership & Collaboration
- Drive high-impact initiatives across multiple teams and balance reliability, security, cost, developer experience, and delivery speed.
- Establish platform standards, reduce technical debt, and guide design decisions.
- Partner with feature teams to turn platform needs into durable solutions.
- Mentor engineers and raise the technical bar across Engineering.
- Improve documentation, runbooks, interfaces, and self-service paths.
- Communicate clearly and build alignment across Platform, Application Engineering, Data Engineering, Product, Program Management, and Security.
We'll combine into one list.
Requirements (Required Qualifications):
- 8+ years in platform engineering, infrastructure engineering, SRE, DevOps, or software engineering with substantial production-platform ownership.
- Deep experience designing and operating cloud platforms, preferably AWS.
- Strong Kubernetes experience, including production operations, networking, reliability, and troubleshooting.
- Strong infrastructure-as-code and automation experience with Terraform, Crossplane, or comparable tools.
- Experience operating CI/CD and delivery infrastructure.
- Strong understanding of IAM, secrets, networking, ingress, and least privilege.
- Experience with distributed-systems observability and operational practices.
- Proficiency in Go and Python for platform services, developer tooling, or automation.
- Demonstrated success leading complex initiatives across multiple teams.
- Excellent communication, mentoring, and technical-influence skills.
Qualifications (Preferred Qualifications):
- Multi-region or multi-environment SaaS platform experience.
- Internal developer platform, declarative API, or Platform-as-a-Service experience.
- GitLab CI/CD, self-hosted runners, OpenTelemetry, or Datadog experience.
- Ephemeral-environment, automated-provisioning, or platform-lifecycle experience.
- Security-sensitive, regulated, or cybersecurity experience.
- Startup or high-growth company experience.
Skills (Platform Stack):
- AWS
- Kubernetes and EKS
- Terraform and Crossplane-related tooling
- GitLab and CI/CD pipelines
- OpenTelemetry and Datadog
- Linux, containers, networking, IAM, and secrets-management systems
- Go and Python for automation and platform services
Benefits (Perks of Horizon3):
- Inclusive Team: We value diversity and promote an inclusive culture where everyone can thrive.
- Growth Opportunities: Be part of a dynamic and growing team with numerous career development opportunities.
- Innovative Culture: Work in a collaborative environment that encourages creativity and out-of-the-box thinking.
- Hybrid & Remote Work: We embrace a mix of remote and hybrid work models depending on role and location, including our Chicago office, where some roles require regular in-office presence.
- Competitive Compensation: We offer competitive salary, equity and benefits. Our benefits include health, vision & dental insurance for you and your family, a flexible vacation policy, and generous parental leave.
Pay (Compensation And Values):
We need to include the paragraph: "At Horizon3, we believe that our people are our greatest asset, and our compensation philosophy reflects this core value. We are committed to fostering an environment where all employees feel valued, respected, and rewarded for their contributions. Our compensation structure is designed to be fair, competitive, and transparent, ensuring that every team member is recognized and compensated equitably across roles, levels, and locations. In accordance with various State’s transparency regulations, we provide the following salary range information for this position: Base salary range: $199,750 - $270,000 annually. The exact salary will be determined based on the selected candidate’s location, qualifications, experience, and relevant skills.Additional compensation: All full-time roles are eligible for an equity package in the form of stock options."
We'll put as
. Ensure we keep the exact text but maybe remove extra spaces. We'll keep as is.
Now ensure we didn't include any boilerplate like EEO etc. We omitted those sections.
Now produce HTML fragment:
About the role
We are looking for a Staff Platform Engineer to join Horizon3’s Internal Platform Team (IPT) and shape the cloud and delivery foundations behind NodeZero. You will lead complex, cross-team initiatives; define platform direction; improve developer workflows; and establish standards that make our systems secure, reliable, and easier to operate. This is a hands-on technical leadership role for an engineer who enjoys solving ambiguous problems and building reusable platform capabilities.
Responsibilities
for prose. We must not invent or summarize away detail. So we need to keep specifics. Let's extract sections: About The Role paragraph: "We are looking for a Staff Platform Engineer to join Horizon3’s Internal Platform Team (IPT) and shape the cloud and delivery foundations behind NodeZero. You will lead complex, cross-team initiatives; define platform direction; improve developer workflows; and establish standards that make our systems secure, reliable, and easier to operate. This is a hands-on technical leadership role for an engineer who enjoys solving ambiguous problems and building reusable platform capabilities." That's prose. Responsibilities: two sub-sections: Platform Strategy, Delivery & Operations and Technical Leadership & Collaboration. Each has bullet-like sentences separated by periods. We need to turn into list items. Probably each sentence after a semicolon? Better to split by periods that start with a capital letter after a semicolon? Let's just treat each bullet as a separate line starting with a capital letter after a period? The text: "Platform Strategy, Delivery & Operations Lead the design and evolution of AWS, Kubernetes/EKS, and shared platform services. Define architecture for infrastructure automation, service delivery, regional capabilities, and ephemeral environments. Build reusable platform capabilities, self-service workflows, and release-safety practices. Evolve infrastructure-as-code and declarative approaches, including Terraform and Crossplane-related capabilities. Improve platform reliability, observability, security, performance, and operability. Participate in on-call and incident response, leading post-incident improvements." Then "Technical Leadership & Collaboration Drive high-impact initiatives across multiple teams and balance reliability, security, cost, developer experience, and delivery speed. Establish platform standards, reduce technical debt, and guide design decisions. Partner with feature teams to turn platform needs into durable solutions. Mentor engineers and raise the technical bar across Engineering. Improve documentation, runbooks, interfaces, and self-service paths. Communicate clearly and build alignment across Platform, Application Engineering, Data Engineering, Product, Program Management, and Security." We'll make a
- with each line as
- .
Requirements: "What You’ll Bring" includes Required Qualifications and Preferred Qualifications. We'll combine into a list? Could separate Required and Preferred as subheadings? But we only have headings for sections; we could keep as one list but note required vs preferred? Might lose nuance. Better to have two subsections under Requirements? But we only allowed headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "Requirements" for required qualifications and "Preferred Qualifications" as a separate section? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections. We'll put Required Qualifications under Requirements, Preferred Qualifications under Qualifications. Thus:
Requirements
with list of required qualifications.Qualifications
with list of preferred qualifications. We must not repeat job title. Now Benefits: "Perks of Horizon3" includes bullet points: Inclusive Team, Growth Opportunities, Innovative Culture, Hybrid & Remote Work, Competitive Compensation (with details). Also maybe "Travel Occasional travel may be required..." Not a perk; we could omit. We'll make a list. Pay: "Compensation And Values" includes base salary range and equity package. Also mentions compensation philosophy. We'll include that as prose maybe plus list? We'll put asfor prose and maybe
- for details? The salary range is a specific detail; we can put in
. Equity package mention. We must not include filler like "commensurate with experience". Not present. Now ensure we remove boilerplate: "Our Platform Stack" maybe not needed as a section; but it's substantive? It lists stack. Could be included under About the role? Might be considered part of role description. Could add as a separate section "Platform Stack"? Not in allowed headings list but we could maybe treat as part of Responsibilities? The instruction: Prefer a few substantive sections over many thin ones. So maybe we incorporate stack into Responsibilities or About the role. But we already have Responsibilities covering duties. The stack is more about tools; could be part of Requirements? Actually it's under "Our Platform Stack". Could be considered part of Requirements (tools used). Might be appropriate to include under Requirements as a list? But we already have Required Qualifications list; we could add a note about stack. However the instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the stack somewhere. Could add a section "Skills" maybe? The allowed headings include Skills. So we could put stack under Skills. That seems appropriate. Thus we will have: - About the role (p) - Responsibilities (ul) - Requirements (ul) for required qualifications - Qualifications (ul) for preferred qualifications - Skills (ul) for platform stack - Benefits (ul) for perks - Pay (p) for compensation details We must not include Schedule. Now let's extract each piece precisely. About the role paragraph: exactly as above. Responsibilities: list each line. Let's copy lines: Platform Strategy, Delivery & Operations - Lead the design and evolution of AWS, Kubernetes/EKS, and shared platform services. - Define architecture for infrastructure automation, service delivery, regional capabilities, and ephemeral environments. - Build reusable platform capabilities, self-service workflows, and release-safety practices. - Evolve infrastructure-as-code and declarative approaches, including Terraform and Crossplane-related capabilities. - Improve platform reliability, observability, security, performance, and operability. - Participate in on-call and incident response, leading post-incident improvements. Technical Leadership & Collaboration - Drive high-impact initiatives across multiple teams and balance reliability, security, cost, developer experience, and delivery speed. - Establish platform standards, reduce technical debt, and guide design decisions. - Partner with feature teams to turn platform needs into durable solutions. - Mentor engineers and raise the technical bar across Engineering. - Improve documentation, runbooks, interfaces, and self-service paths. - Communicate clearly and build alignment across Platform, Application Engineering, Data Engineering, Product, Program Management, and Security. We'll combine into one list. Requirements (Required Qualifications): - 8+ years in platform engineering, infrastructure engineering, SRE, DevOps, or software engineering with substantial production-platform ownership. - Deep experience designing and operating cloud platforms, preferably AWS. - Strong Kubernetes experience, including production operations, networking, reliability, and troubleshooting. - Strong infrastructure-as-code and automation experience with Terraform, Crossplane, or comparable tools. - Experience operating CI/CD and delivery infrastructure. - Strong understanding of IAM, secrets, networking, ingress, and least privilege. - Experience with distributed-systems observability and operational practices. - Proficiency in Go and Python for platform services, developer tooling, or automation. - Demonstrated success leading complex initiatives across multiple teams. - Excellent communication, mentoring, and technical-influence skills. Qualifications (Preferred Qualifications): - Multi-region or multi-environment SaaS platform experience. - Internal developer platform, declarative API, or Platform-as-a-Service experience. - GitLab CI/CD, self-hosted runners, OpenTelemetry, or Datadog experience. - Ephemeral-environment, automated-provisioning, or platform-lifecycle experience. - Security-sensitive, regulated, or cybersecurity experience. - Startup or high-growth company experience. Skills (Platform Stack): - AWS - Kubernetes and EKS - Terraform and Crossplane-related tooling - GitLab and CI/CD pipelines - OpenTelemetry and Datadog - Linux, containers, networking, IAM, and secrets-management systems - Go and Python for automation and platform services Benefits (Perks of Horizon3): - Inclusive Team: We value diversity and promote an inclusive culture where everyone can thrive. - Growth Opportunities: Be part of a dynamic and growing team with numerous career development opportunities. - Innovative Culture: Work in a collaborative environment that encourages creativity and out-of-the-box thinking. - Hybrid & Remote Work: We embrace a mix of remote and hybrid work models depending on role and location, including our Chicago office, where some roles require regular in-office presence. - Competitive Compensation: We offer competitive salary, equity and benefits. Our benefits include health, vision & dental insurance for you and your family, a flexible vacation policy, and generous parental leave. Pay (Compensation And Values): We need to include the paragraph: "At Horizon3, we believe that our people are our greatest asset, and our compensation philosophy reflects this core value. We are committed to fostering an environment where all employees feel valued, respected, and rewarded for their contributions. Our compensation structure is designed to be fair, competitive, and transparent, ensuring that every team member is recognized and compensated equitably across roles, levels, and locations. In accordance with various State’s transparency regulations, we provide the following salary range information for this position: Base salary range: $199,750 - $270,000 annually. The exact salary will be determined based on the selected candidate’s location, qualifications, experience, and relevant skills.Additional compensation: All full-time roles are eligible for an equity package in the form of stock options." We'll put as
. Ensure we keep the exact text but maybe remove extra spaces. We'll keep as is. Now ensure we didn't include any boilerplate like EEO etc. We omitted those sections. Now produce HTML fragment:
About the role
We are looking for a Staff Platform Engineer to join Horizon3’s Internal Platform Team (IPT) and shape the cloud and delivery foundations behind NodeZero. You will lead complex, cross-team initiatives; define platform direction; improve developer workflows; and establish standards that make our systems secure, reliable, and easier to operate. This is a hands-on technical leadership role for an engineer who enjoys solving ambiguous problems and building reusable platform capabilities.
Responsibilities