Senior Customer Onboarding Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions. Must preserve all substantive info. We need to parse the posting. First part: "Get to Know Us Horizon3 is a fast-growing, remote cybersecurity company dedicated to the mission of enabling organizations to proactively find and fix and verify exploitable attack vectors before criminals exploit them. Our flagship product, the NodeZeroTM platform, delivers production-safe autonomous pentests and other key assessment operations that scale across the largest internal, external, cloud, and hybrid cloud environments. NodeZero has been adopted by organizations of all sizes, from small educational institutions to government agencies and Global 100 enterprises. It is used by ITOps/SecOps teams, consulting pentesters, and MSSPs and MSPs. We are a fusion of former U.S. Special Operations cyber operators, startup engineers, and formerly frustrated cybersecurity practitioners. We're committed to helping solve our common security problems: ineffective security tools, false positives resulting in alert fatigue, blind spots, "checkbox” security culture, cybersecurity skills shortage, and the long lead time and expense of hiring outside consultants. Collectively, we are a team of learn it alls, committed to a culture of respect, collaboration, ownership, and results." That's about the company. Could be "About the role"? Actually "About the role" is typical heading for role summary. The posting includes "Role Summary". So we can put that under

About the role

maybe. Or "Role Summary". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. We have: - About the role: could be the Role Summary paragraph. - Responsibilities: "What You Will Do" section. - Requirements: "Required Qualifications" maybe. - Qualifications: maybe "Preferred Qualifications"? Actually they separate Required and Preferred. Could treat Required as Requirements, Preferred as Qualifications? Or we could have Requirements (required) and Qualifications (preferred). Or we could combine. - Skills: maybe not explicit; but we could include technical skills under Requirements/Qualifications. - Benefits: "Perks of Horizon3" and "Compensation And Values" includes benefits and compensation. - Pay: "Compensation And Values" includes base salary range. - Schedule: maybe not explicit; there is "Hybrid & Remote Work" but not schedule specifics. Could omit schedule if no specific. We must not create sections with filler like "not specified". So only include sections where we have real content. Let's extract content. Company description: Could be placed under "About the role"? Actually "About the role" is about the role, not company. But we have no explicit "About the company" heading allowed. However we could still put company description under "About the role" as it's about the role context? Might be okay. But better to follow instruction: Use headings from list; we can choose which to include. If we don't have content for a heading, we omit it. We have: - Role Summary: we can put under

About the role

. - Responsibilities: under

Responsibilities

. - Requirements: under

Requirements

(Required Qualifications). - Qualifications: under

Qualifications

(Preferred Qualifications). - Benefits: under

Benefits

(Perks of Horizon3 + maybe compensation benefits). - Pay: under

Pay

(Base salary range). - Schedule: maybe not present; we have Hybrid & Remote Work but not schedule like hours. Could we treat that as Schedule? The instruction says use Schedule heading if posting actually states them. It mentions "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." That is about work arrangement, not schedule (hours). Might be considered schedule? Probably not. Safer to omit Schedule if not explicit. - Skills: maybe not separate; we could embed skills within Requirements/Qualifications. But we could still create a Skills section if we have explicit skill list. The posting includes many technical skills: Linux, Docker, Kubernetes, AWS/Azure/GCP, IaC, networking, scripting, identity, database literacy, etc. Those could be considered skills. However we already have Requirements and Qualifications covering them. To avoid duplication, we could omit Skills section. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can organize them under headings. Must not lose any detail. Thus we need to include: - Company description (Get to Know Us ...) maybe under About the role? But that is about company not role. However we could still include it as a paragraph under About the role heading; it's still substantive. - Role Summary paragraph. - Responsibilities bullet list (What You Will Do) with sub-bullets. - Required Qualifications bullet list. - Preferred Qualifications bullet list. - Perks of Horizon3 bullet list. - Compensation And Values paragraph (including base salary range, equity, benefits description). - Hybrid & Remote Work paragraph (maybe under Benefits? Could be its own section but not in list; we could incorporate into Benefits or maybe under a separate heading like "Work Arrangement" but not allowed. Could put under Benefits as part of perks. - Other Duties and Application Note etc are boilerplate? "Other Duties" is generic; maybe we should remove as boilerplate? It says "Other Duties Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities that are required of the employee. Duties, responsibilities, and activities may change at any time with or without notice." That's generic boilerplate; we should remove. - Application Note about redacting age-identifying info: also boilerplate; remove. Thus we keep substantive sections. Now produce HTML. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include / or markdown. Let's craft. First heading:

  About the role

  Under it, we need paragraphs: company description + Role Summary. We could combine into one

  containing both? Better separate paragraphs: first

  company description, second

  Role Summary. But note: The instruction says use

  for prose. So each paragraph separate. Now Responsibilities:

  Responsibilities

  Then we need a list. The "What You Will Do" includes: - Own the onboarding - Lead kickoff with the customer and internal account team. - Confirm scope, environments, owners, identity/access path, compliance constraints, and go-live criteria. - Project-manage the 30-day plan. - Track blockers (credentials, firewall changes, IdP claims, change windows). - Provide best practices expertise and assist in deployment and optimization of the customer environment. - Ensure successful production deployment against the customers initial testing goals as success criteria for the onboarding. - Technical Implementation - Diagnose and resolve implementation failures across cloud infrastructure, networking, and security with the same rigor used on escalated support tickets. - Perform root-cause analysis on first-time integration and deployment issues so the same failure does not recur after handoff. - Work in Linux production environments: server configuration, performance tuning, security hardening, and troubleshooting. - Deploy and manage containerized workloads with Docker and orchestrated environments such as Kubernetes. - Provision and troubleshoot pentest configuration AWS, Azure, or GCP. - Assist in troubleshooting network issues that commonly block go-live: TCP/IP, firewalls, VPNs, load balancers, etc. - Configure and validate identity paths required for onboarding: RBAC, SSO (OAuth, SAML), and directory services (Active Directory, LDAP). - Apply NodeZero expertise in scoping and configuring initial tests. - Work Across The Company - Collaborate with CS, Engineering, Product, and Sales to unblock implementation issues that are bigger than a single customer. - Advocate for customer specific changes or product improvements as required. - Mentor junior onboarding or support engineers on first-time deployment patterns. - Stay current on cloud, container, and security practices. We need to represent as
  • . Could nest sublists? The instruction says use
    • for any list of duties/requirements/benefits. It doesn't forbid nesting. We can have top-level items for each major bucket, and sub-items as nested
      . That's okay. Now Requirements:

      Requirements

      List from Required Qualifications: - Bachelor’s degree in Computer Science, Information Technology, Engineering, or a related field, or equivalent professional experience. - 5+ years in technical support, systems administration, cloud operations, implementation, or a similar enterprise role, ideally supporting large-scale or Fortune 500 deployments. - Background in cybersecurity, including threat detection, vulnerability management, encryption standards, and compliance frameworks such as SOC 2 or GDPR. - Strong Linux administration in production: configuration, performance tuning, hardening, and troubleshooting. - Hands-on Docker and containerization experience, including building, deploying, and managing applications in orchestrated environments (Kubernetes or similar). - Solid working knowledge of AWS, Azure, or GCP and IaC tools such as Terraform, Ansible, or CloudFormation. - In-depth networking fundamentals: TCP/IP, firewalls, VPNs, load balancers, and tools such as Wireshark and tcpdump. - Basic scripting in Bash, Python, or PowerShell for automation, diagnostics, and workflow support. - Demonstrated self-learning: labs, certifications (for example AWS Solutions Architect, Linux+, or equivalent), personal projects, or open-source work. - Experience comparable to a junior cloud administrator in an enterprise setting: multi-tenant environments, resource allocation, and compliance requirements. - Familiarity with identity management: RBAC, SSO (OAuth, SAML), and directory services (Active Directory, LDAP). - Basic database literacy: relational vs. schemaless stores, schema, querying, and light administration. - Ability to run a customer-facing technical engagement to a 30-day finish line with minimal supervision. Now Qualifications:

      Qualifications

      List from Preferred Qualifications: - Proven experience integrating and troubleshooting APIs, including REST services, authentication mechanisms, and API-driven automations in enterprise applications. - Familiarity with observability tools such as Datadog for monitoring, logging, and alerting in distributed systems. - Basic experience with managed databases such as Amazon RDS: setup, backups, scaling, and query optimization. - Broader coding ability in Python, JavaScript, or Go, including custom tools or scripts that automate implementation or support work. - Prior onboarding, professional services, or TAM work with a defined time-to-go-live. - Experience creating reusable assets: validation scripts, Terraform modules, Datadog dashboard/alert packs, and customer-ready runbooks. Now Benefits:

      Benefits

      From "Perks of Horizon3" and also benefits described in Compensation And Values (health, vision & dental insurance, flexible vacation policy, generous parental leave). Also Hybrid & Remote Work could be included. Let's list: - 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