Director of Software Engineering

We need to produce HTML fragment with sections: About the role? Actually the posting includes "About SANS" (company description) and "Why SANS?" (culture), "What You'll Achieve at SANS" (role description), "What We're Looking For" (requirements), "Benefits and Perks of Working at SANS" (benefits), also salary info. Also "Flexibility and Balance at SANS" (schedule/remote). We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: - About SANS: company overview. Could map to "About the role"? Actually "About the role" is about the job, not company. But we have no explicit "About the role" section; we have "What You'll Achieve at SANS" describing role. That could be "Responsibilities". Also "Why SANS?" could be about culture but not required headings. We need to decide which headings to include based on content. We have responsibilities: list of duties under "As a Director Of Software Engineering, You Will ..." and bullet points. That's responsibilities. We have requirements: "What We're Looking For" includes education, experience, etc. That's qualifications/requirements/skills. We have benefits: "Benefits and Perks of Working at SANS" includes salary range, benefits details. We have schedule: "Flexibility and Balance at SANS" mentions primarily remote work environment, occasional in-person presence. We also have "About SANS" and "Why SANS?" maybe could be omitted as not matching headings. But we must preserve ALL substantive information; we cannot drop company description? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." However we also must not create sections with filler. We could embed company description in a

without a heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

for section headings (e.g. those). Likely we should only use those headings; other info can be in

without heading. But we need to preserve all substantive info, so we can include a paragraph about SANS before the sections. We also need to not repeat job title as heading; we don't. We need to not put Job ID/requisition numbers as headings; none. We need to remove boilerplate like EEO etc. So we should strip those. We need to output only HTML fragment. Let's extract content: Company description: "About SANS Founded in 1989, SANS Institute (SANS) began as a cooperative research and education organization. Over the next 25 years, it grew to become the most trusted and widely recognized provider of information security training and certification in the world. Today, SANS has served more than 300,000 cybersecurity professionals around the world, with more than 60,000 earning Global Information Assurance Certification (GIAC) security certificationsthe leading certification that provides assurance to employers that their people and prospective hires can do the job. At the heart of SANS is a community of practitioners, from auditors and network administrators to CISOs, who share their lessons learned and collaborate on solutions to the challenges they face. These experts, working across corporations, government agencies, and universities, come together to support and strengthen the global information security community." "Why SANS? At SANS, our culture is defined by three pillars: Mission, Brand, and People. Our Mission is to hire people who understand the importance fighting against cybersecurity threats. Our Brand reflects a commitment to delivering the highest quality training. Our People are grounded in a culture of fairness, honesty, customer focus, and a pragmatic approach." We could combine these into a paragraph about company and culture. Role description / responsibilities: "What Youll Achieve at SANS We are seeking a Director of Software Engineering to join our Product Development team. This role plays a key part in providing senior technical and organizational leadership for SANS Cloud Platform Engineering organization spanning platform core services (identity, product administration, and entitlements), DevOps tools and services, website engineering, and courseware & platform orchestration while serving as the engineering executive for Project CORE, SANS enrollment and entitlement modernization program. This role leads individual contributors and engineering teams through their managers and leads; owns shared engineering platforms, standards, tooling, and vendor relationships; and drives the architecture, delivery, and cross-functional coordination required to modernize SANS enrollment, entitlement, and administrative systems. The Director partners closely with Product, Operations, Sales, Finance, and fellow engineering directors to translate business strategy into secure, scalable, and maintainable systems." Then bullet list under "As a Director Of Software Engineering, You Will Lead, manage, and mentor individual contributors and engineering teams through managers and leads. Own engineering standards and best practices CI/CD, code quality, secure development and facilitate architecture governance across teams. Plan and balance engineering capacity against shifting business priorities, communicating trade-offs to stakeholders. Lead strategic modernization programs end to end: architecture, cross-team commitments, delivery planning, and executive reporting. Direct modernization of core product platforms enrollment, entitlement, identity, and product services including integration with enterprise systems and retirement of legacy tooling. Measure engineering effectiveness and drive continuous improvement across teams. Champion incident management discipline and publish regular engineering communications to stakeholders. Other duties as assigned." We can turn each sentence into

. Requirements/Qualifications/Skills: "What Were Looking For Every SANS employee brings something unique. For this role, were looking for candidates with: BS or MS in Computer Science, related technical field, or equivalent industry experience. At least 10 years of software engineering experience, including 5+ years leading engineering teams and 3+ years managing through engineering managers or leads. Demonstrated success leading a large, multi-team modernization or systems-integration program from design through delivery. Strong technical acumen with prior hands-on development experience and the ability to guide architectural decisions across services, integrations, and data flows. Experience with modern AI development techniques and best practices. Experience with enterprise business systems and integrations (e.g., Salesforce/Service Cloud, identity providers, payment/order management). Experience with cloud infrastructure and DevOps practices, including AWS, CI/CD pipelines, containerization, and infrastructure as code. Experience managing vendor relationships, software procurement, licensing, and budgets. Experience with Agile, SDLC, and modern development standards and best practices. Excellent written and verbal communication skills, including executive-level reporting and cross-functional coordination. Unrestricted authorization to work in the USA; visa sponsorship is not available." Preferred qualifications: "Preferred Qualifications Include Experience in education technology, training delivery platforms, or certification systems. Experience facilitating architecture governance (architecture councils, RFC processes, engineering standards). Familiarity with identity and access management platforms (PingIdentity, Entra ID) and entitlement modeling. Experience integrating AI-assisted development tooling and governing its safe, cost-effective adoption. Interest in a security-first mindset and secure coding practices. Ability and passion for developing both individuals and teams." We could combine required and preferred into Requirements section, maybe separate sub-sections? But we only have headings: Requirements, Qualifications, Skills. Could split: Requirements (education, years experience), Qualifications (specific experiences), Skills (technical skills). But we need to avoid filler. Let's decide to use: -

Requirements

: education, years experience, leadership experience, success leading modernization programs. -

Qualifications

: technical acumen, hands-on development, ability to guide architecture, experience with AI dev techniques, enterprise systems, cloud/DevOps, vendor management, Agile/SDLC, communication skills, work authorization. -

Skills

: maybe list of specific technical skills: AI development techniques, enterprise systems (Salesforce/Service Cloud, identity providers, payment/order management), cloud infrastructure (AWS, CI/CD, containerization, IaC), vendor relationships, etc. But that may duplicate. Alternatively we could just have one

Requirements

containing all bullet points (both required and preferred). The instruction says prefer a few substantive sections over many thin ones. So maybe just Requirements and Benefits and Pay and Schedule. We have Pay: salary range $200,000 to $240,000 OTE. We have Benefits: comprehensive benefits package details. We have Schedule: primarily remote work environment, occasional in-person presence. Thus sections: About SANS (maybe as a preamble

without heading), Responsibilities, Requirements, Benefits, Pay, Schedule. But we need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Since we are not using About the role, we could use About SANS as a

without heading. That's okay. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does. Thus produce:

About SANS ...

Responsibilities

• ...
...

Requirements

• ...
...

Benefits

• ...
...

Pay

The expected salary range for this position is $200,000 to $240,000 OTE (comprised of base salary and bonus), depending on geographic location, skills, and experience.

Schedule

As a primarily remote work environment, we are committed to maintaining strong connections, collaboration, and a vibrant culture across virtual teams. While most roles operate remotely, some positions may require occasional in-person presence depending on role-specific or business needs.

We need to ensure we preserve all substantive information: include company description, culture pillars maybe? We omitted "Why SANS?" culture pillars. That is substantive. Should we include it? Could add a paragraph after About SANS: "Why SANS? At SANS, our culture is defined by three pillars: Mission, Brand, and People. Our Mission is to hire people who understand the importance fighting against cybersecurity threats. Our Brand reflects a commitment to delivering the highest quality training. Our People are grounded in a culture of fairness, honesty, customer focus, and a pragmatic approach." We can include that as a

as well. Also we need to include details about role: "What Youll Achieve at SANS We are seeking a Director of Software Engineering..." That's part of responsibilities; we already have responsibilities bullet list but also the preceding paragraph describing role. Should include that as part of responsibilities maybe as a

before the

. The instruction: use

for prose. So we can have a

describing the role, then

for duties. Similarly for requirements we have a paragraph intro: "What Were Looking For Every SANS employee brings something unique. For this role, were looking for candidates with:" then list. We can include that as a

then

. Benefits: we have a paragraph intro: "Benefits and Perks of Working at SANS We are committed to fair and equitable compensation..." then details. We'll include that as

then

for bullet points. We need to extract bullet points for benefits: The text lists: - Financial Benefits: Competitive base salary, bonus opportunities, and a 401(k) plan with company match. - Health & Wellness: Robust medical, dental, and vision plans; company-provided short term disability; optional long-term disability, supplemental life and AD&D insurance for employees and dependents; voluntary benefits including accident insurance and identity theft protection; fitness and wellness programs; and a company paid employee assistance program (EAP). - Time Off & Flexibility: Generous paid time off, including volunteer time