Senior Manager, Engineering

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Sections present: - About Gray Swan (company description) – not a required heading but could be "About the role"? Actually "About Gray Swan" is about company. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings if applicable. We have: - About Gray Swan (company mission) – could go under "About the role"? Not exactly. But maybe we can include a short paragraph about company under "About the role"? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are possible headings; we should include only those that have content. The posting includes "About Gray Swan" and "About Learn more about how we work." That seems like company overview. Could be placed under "About the role"? Not ideal but maybe we can treat as "About the role" includes description of role and company? The role description is under "The Role". So we could have:

About the role

with paragraph describing the role (the role overview). Then separate sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract responsibilities: bullet list under "What You’ll Do:" includes many items. Requirements: maybe "Who You Are:" includes experience etc. Could be split into Requirements and Qualifications? The instruction distinguishes Requirements and Qualifications; we need to decide what goes where. Usually Requirements are mandatory, Qualifications are preferred. In posting, "Who You Are:" includes required experience (7+ years, 2+ years managing, strong technical background, etc.) Then "Bonus Points If You Have:" includes preferred qualifications. So we can put mandatory under Requirements, and bonus under Qualifications (or Skills?). Also Skills could be separate for technical skills. We have also "You’ll Thrive Here If You:" which is more about cultural fit; could be part of Skills or maybe omitted? It's not strictly required but could be considered as "Skills"? Might be better to include under "Skills" as behavioral traits. Benefits: listed under "What we offer:" includes compensation and benefits. Pay: salary range $255,000 - $315,000 plus performance based bonus and meaningful equity package. Benefits: 401k with up to 4% matching, 28 days annual leave (vacation + holidays), Health, dental, and vision coverage, Catered lunches (Pittsburgh office), Flexible work arrangements, Visa sponsorship available for exceptional candidates. Schedule: not mentioned; we should not create Schedule section if no content. We also have "About Learn more about how we work." That's just a link; we can ignore as boilerplate? It's not substantive; we can drop. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep the details exactly as given, but we can format as HTML lists/paragraphs. We must not repeat job title as heading. The job title is "Engineering Manager, Enterprise". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Interview Process 🔎 ..." and "How To Apply ..." which are application instructions; we should remove those. Also the bullet list of interview steps and "How To Apply" should be removed. Thus final HTML should contain sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "About the role" includes company description? Might be better to have separate "About the role" for role overview and maybe a short paragraph about company? But we have "About Gray Swan" separate; we could incorporate that into "About the role" as context. However the instruction says use headings like About the role, Responsibilities, etc. It didn't forbid adding other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings; we should stick to those. So we need to map all content into those categories. Thus: - About the role: include description of the role and maybe company mission? The role description includes "The Role Gray Swan is looking for an Engineering Manager, Enterprise to lead the team ...". Also we could include the company mission paragraph as part of About the role? It's about Gray Swan, not the role. But we could still include it there as background. The instruction says preserve ALL substantive information; we can put it there. - Responsibilities: list from "What You’ll Do:". - Requirements: mandatory from "Who You Are:" (7+ years experience building enterprise solutions..., 2+ years managing..., Strong technical background..., Strong programming experience..., Experience operating production services on Kubernetes..., Deep understanding..., Experience designing and operating APIs..., Strong understanding..., Comfortable diving..., A strong people leader..., Able to balance..., Excited to work...). That's a lot; we can keep as list. - Qualifications: bonus points: "Experience managing infrastructure or platform teams supporting machine learning or LLM workloads. Experience with infrastructure-as-code tools such as Terraform. Experience with Kafka, Redis, PostgreSQL, ClickHouse, or similar distributed data systems. Experience building internal developer platforms or platform engineering organizations. Knowledge of cloud security, infrastructure hardening, or zero-trust architectures. Experience scaling infrastructure through a period of rapid company or product growth. Previous experience at a high-growth startup or building products from zero to one. Interest in AI safety, cybersecurity, or adversarial machine learning." - Skills: maybe from "You’ll Thrive Here If You:" includes: lead from front, technically curious, build great teams, think at scale, balance strategy with execution, collaborate across disciplines, excited by mission and startup environment. Also maybe technical skills list? But we already have technical skills in Requirements/Qualifications. Could also include "Strong programming experience in C/C++, Go, Python, Rust, Java, or a similar language." That's already in Requirements. So Skills could be behavioral traits. - Benefits: list as described. - Pay: salary range and bonus/equity. - Schedule: none, so omit. We must not create empty sections. Now produce HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We need to ensure we don't duplicate content. Let's craft. About the role paragraph: combine company mission and role overview. Company mission: "Gray Swan is on a mission to empower the world to use AI safely and securely. We evaluate AI models for the leading frontier labs along with building real-time threat detection and adaptive adversarial red teaming agents for teams deploying AI. We're a team of approximately 60 people, well-funded, growing quickly. Our work directly influences how the world deploys AI agents and systems at scale." Role overview: "Gray Swan is looking for an Engineering Manager, Enterprise to lead the team responsible for building and scaling the systems that power our AI security platform. You'll combine strong technical judgment with people leadership to help design the enterprise experience, including infrastructure, backend services, and cloud architecture that enable Gray Swan to build AI systems and for customers to safely deploy frontier AI models at scale. This role is ideal for an engineering leader who enjoys solving complex infrastructure challenges while building and developing a high-performing team. You'll work closely with machine learning engineers, product engineers, and security researchers to ensure our platform remains fast, resilient, secure, and scalable as we grow. You'll have significant ownership over foundational systems, technical strategy, and team development. As one of the leaders shaping Gray Swan's infrastructure organization, you'll have the opportunity to influence architecture, engineering practices, and how we build and operate systems in a rapidly evolving AI startup." We can combine into one or two paragraphs. Responsibilities list: items from "What You’ll Do:" each as
• . Let's list them: - Lead, mentor, and develop a team of infrastructure engineers, creating a culture of ownership, technical excellence, and continuous improvement. - Set technical direction and priorities for enterprise solutions in partnership with engineering leadership and other technical teams. - Oversee the design, development, and operation of highly available backend services and distributed systems that power Gray Swan's AI security platform. - Guide the team in owning and scaling cloud infrastructure across Kubernetes, AWS, GCP, Azure, networking, storage, and compute. - Drive the development of internal platform services, infrastructure tooling, and systems that improve developer productivity and reliability. - Establish and improve engineering practices around observability, monitoring, incident response, deployment, and operational excellence. - Partner closely with machine learning, security, and product engineering teams to build infrastructure capable of supporting increasingly complex AI workloads. - Identify and address opportunities to improve system performance, reliability, scalability, and infrastructure efficiency. - Help define long-term architecture and technical strategy while balancing immediate product and engineering priorities. - Participate in hiring and help build a world-class infrastructure engineering organization. - Provide technical guidance during complex production incidents and ensure the team learns from failures through effective post-incident reviews. - Communicate infrastructure strategy, tradeoffs, risks, and priorities clearly across engineering and company leadership. Requirements list: from "Who You Are:" mandatory. Let's extract each sentence as bullet: - 7+ years of experience building enterprise solutions with experience implementing backend infrastructure or distributed systems in production environments. - 2+ years of experience managing, mentoring, or leading software engineering teams. - Strong technical background in infrastructure, distributed systems, backend engineering, or platform engineering. - Strong programming experience in C/C++, Go, Python, Rust, Java, or a similar language. - Experience operating production services on Kubernetes and modern cloud platforms such as AWS, GCP, and Azure. - Deep understanding of networking, distributed systems, containers, service orchestration, and scalable architectures. - Experience designing and operating APIs, microservices, asynchronous systems, and event-driven architectures. - Strong understanding of reliability, observability, security, and performance at scale. - Comfortable diving into complex technical problems and debugging production systems alongside your team. - A strong people leader who enjoys coaching engineers, providing feedback, and helping individuals grow. - Able to balance technical depth with effective delegation and team leadership. - Excited to work in a fast-moving startup where you will have significant ownership and ambiguity. Qualifications list: bonus points. - Experience managing infrastructure or platform teams supporting machine learning or LLM workloads. - Experience with infrastructure-as-code tools such as Terraform. - Experience with Kafka, Redis, PostgreSQL, ClickHouse, or similar distributed data systems. - Experience building internal developer platforms or platform engineering organizations. - Knowledge of cloud security, infrastructure hardening, or zero-trust architectures. - Experience scaling infrastructure through a period of rapid company or product growth. - Previous experience at a high-growth startup or building products from zero to one. - Interest in AI safety, cybersecurity, or adversarial machine learning. Skills list: from "You’ll Thrive Here If You:" maybe also include some soft skills. - You lead from the front. - You're technically curious, comfortable getting into the details when needed, and know how to empower engineers without becoming a bottleneck. - You build great teams. - You care deeply about developing engineers, creating a strong team culture, and giving people the ownership and autonomy they need to do their best work. - You think at scale. - You enjoy designing resilient infrastructure, making thoughtful architectural decisions, and building systems that are secure, observable, and built to grow. - You balance strategy with execution. - You can zoom out to define long-term technical direction while staying close enough to the work