Director of Software Engineering
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "SANS is an Equal Employment Opportunity Employer" etc. Also remove "US Job Seekers: Click here..." etc. Also remove "Employment eligibility in the United States is required. SANS does not provide visa sponsorship for this position." Might be considered boilerplate but it's about visa sponsorship; maybe keep as part of requirements? The posting says "Unrestricted authorization to work in the USA; visa sponsorship is not available." That's a requirement; we should keep that. The later repeated statement can be removed as duplicate.
We need to include sections only when there is real specific content. So we will have sections: About the role? Actually "What You’ll Achieve At SANS" could be "About the role" or "Responsibilities". The posting includes responsibilities under "As a Director Of Software Engineering, You Will ..." That's a list. So we can have a section "Responsibilities". Also "What We’re Looking For" is requirements/qualifications. Could split into "Qualifications" and "Preferred Qualifications". But we can combine? The instruction: prefer a few substantive sections over many thin ones. So maybe have "Responsibilities", "Requirements", "Preferred Qualifications", "Benefits", "Pay", "Schedule". Also maybe "About SANS" is company overview; could be "About the company" but not required. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include About the role (maybe a brief summary). But we must not repeat job title as heading. "About the role" is okay.
We need to decide what to put under each.
Let's extract content:
About SANS: description of company, mission, etc. Could be placed under "About the role"? Actually "About the role" maybe a brief summary of the role. But we have "What You’ll Achieve At SANS" which is more about role. The "About SANS" is company overview; could be placed under "About the role" or maybe we omit because not required? The instruction says we can include sections only when posting has real specific content. The posting does have "About SANS" and "Why SANS?" which is company culture. Could be considered "About the role" or maybe we can create a section "About SANS". But the allowed headings list does not include "About SANS". However we can still use
for any section heading; the instruction gave examples but not exclusive. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those examples but not limited to them. Safer to stick to those headings.
Thus we can map:
- About the role: maybe a brief summary: "Director of Software Engineering to join Product Development team..." etc. Could combine the first paragraph after "What You’ll Achieve At SANS". Actually that paragraph describes the role. So we can put that under About the role.
- Responsibilities: the bullet list under "As a Director Of Software Engineering, You Will ..." (the list of duties). Use - .
- Requirements: the "What We’re Looking For" list (mandatory). Use
- .
- Preferred Qualifications: the "Preferred Qualifications Include" list. Use
- .
- Benefits: the "Benefits And Perks Of Working At SANS" section. Use
- for each benefit category? It has subcategories: Financial Benefits, Health & Wellness, Time Off & Flexibility, Learning & Development, Flexibility and Balance at SANS (maybe separate). Could break into list items.
- Pay: the salary range: "$200,000 to $240,000 OTE (comprised of base salary and bonus), depending on geographic location, skills, and experience." Also mention pay equity and transparency. Use
.
- Schedule: remote work info: "As a primarily remote work environment, we are committed to maintaining strong connections..." Also "While most roles operate remotely, some positions may require occasional in-person presence depending on role-specific or business needs." Use
.
We must remove boilerplate: EEO statements, visa sponsorship repeated, etc. Keep the unrestricted authorization line (maybe under Requirements). Also we should keep "Unrestricted authorization to work in the USA; visa sponsorship is not available." as a requirement.
We must not include duplicated lines. Ensure we don't repeat same content.
Now craft HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Preferred Qualifications
- ...
...
Benefits
- 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.
- Learning & Development: Access to professional development and SANS training opportunities.
- Flexibility and Balance at SANS: 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.
But note that Flexibility and Balance at SANS overlaps with Schedule; maybe we should separate Schedule section. However we already have schedule info there. Could move remote work to Schedule section and keep Benefits more focused on compensation/health/time off/learning. Let's separate.
Thus Benefits section includes Financial, Health & Wellness, Time Off & Flexibility, Learning & Development.
Schedule section includes remote work statement.
Pay section includes salary range.
Now ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment only.
Check for any leftover boilerplate: removed EEO, visa sponsorship repeated, "SANS is an Equal Employment Opportunity Employer", "US Job Seekers: Click here", "Employment eligibility in the United States is required. SANS does not provide visa sponsorship for this position." (duplicate). Keep only one mention of visa sponsorship under Requirements.
Now write.
Let's draft About the role paragraph: combine from "What You’ll Achieve At SANS" first paragraph: "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."
That's good.
Now Responsibilities list: from "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 need to split into list items. Each sentence before a capital letter? We'll split at each major clause separated by a period. Let's create items:
- 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.
- Perform other duties as assigned.
Now Requirements list: from "What We’re Looking For" bullet points (the mandatory). Let's list:
- 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.
Now Preferred Qualifications list:
- 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.
Now Benefits list (financial, health, time off, learning):
- 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
for prose. We must preserve all substantive info, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "SANS is an Equal Employment Opportunity Employer" etc. Also remove "US Job Seekers: Click here..." etc. Also remove "Employment eligibility in the United States is required. SANS does not provide visa sponsorship for this position." Might be considered boilerplate but it's about visa sponsorship; maybe keep as part of requirements? The posting says "Unrestricted authorization to work in the USA; visa sponsorship is not available." That's a requirement; we should keep that. The later repeated statement can be removed as duplicate. We need to include sections only when there is real specific content. So we will have sections: About the role? Actually "What You’ll Achieve At SANS" could be "About the role" or "Responsibilities". The posting includes responsibilities under "As a Director Of Software Engineering, You Will ..." That's a list. So we can have a section "Responsibilities". Also "What We’re Looking For" is requirements/qualifications. Could split into "Qualifications" and "Preferred Qualifications". But we can combine? The instruction: prefer a few substantive sections over many thin ones. So maybe have "Responsibilities", "Requirements", "Preferred Qualifications", "Benefits", "Pay", "Schedule". Also maybe "About SANS" is company overview; could be "About the company" but not required. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include About the role (maybe a brief summary). But we must not repeat job title as heading. "About the role" is okay. We need to decide what to put under each. Let's extract content: About SANS: description of company, mission, etc. Could be placed under "About the role"? Actually "About the role" maybe a brief summary of the role. But we have "What You’ll Achieve At SANS" which is more about role. The "About SANS" is company overview; could be placed under "About the role" or maybe we omit because not required? The instruction says we can include sections only when posting has real specific content. The posting does have "About SANS" and "Why SANS?" which is company culture. Could be considered "About the role" or maybe we can create a section "About SANS". But the allowed headings list does not include "About SANS". However we can still use
for any section heading; the instruction gave examples but not exclusive. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those examples but not limited to them. Safer to stick to those headings.
Thus we can map:
- About the role: maybe a brief summary: "Director of Software Engineering to join Product Development team..." etc. Could combine the first paragraph after "What You’ll Achieve At SANS". Actually that paragraph describes the role. So we can put that under About the role.
- Responsibilities: the bullet list under "As a Director Of Software Engineering, You Will ..." (the list of duties). Use - .
- Requirements: the "What We’re Looking For" list (mandatory). Use
- .
- Preferred Qualifications: the "Preferred Qualifications Include" list. Use
- .
- Benefits: the "Benefits And Perks Of Working At SANS" section. Use
- for each benefit category? It has subcategories: Financial Benefits, Health & Wellness, Time Off & Flexibility, Learning & Development, Flexibility and Balance at SANS (maybe separate). Could break into list items.
- Pay: the salary range: "$200,000 to $240,000 OTE (comprised of base salary and bonus), depending on geographic location, skills, and experience." Also mention pay equity and transparency. Use
.
- Schedule: remote work info: "As a primarily remote work environment, we are committed to maintaining strong connections..." Also "While most roles operate remotely, some positions may require occasional in-person presence depending on role-specific or business needs." Use
.
We must remove boilerplate: EEO statements, visa sponsorship repeated, etc. Keep the unrestricted authorization line (maybe under Requirements). Also we should keep "Unrestricted authorization to work in the USA; visa sponsorship is not available." as a requirement.
We must not include duplicated lines. Ensure we don't repeat same content.
Now craft HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Preferred Qualifications
- ...
...
Benefits
- 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.
- Learning & Development: Access to professional development and SANS training opportunities.
- Flexibility and Balance at SANS: 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.
But note that Flexibility and Balance at SANS overlaps with Schedule; maybe we should separate Schedule section. However we already have schedule info there. Could move remote work to Schedule section and keep Benefits more focused on compensation/health/time off/learning. Let's separate.
Thus Benefits section includes Financial, Health & Wellness, Time Off & Flexibility, Learning & Development.
Schedule section includes remote work statement.
Pay section includes salary range.
Now ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment only.
Check for any leftover boilerplate: removed EEO, visa sponsorship repeated, "SANS is an Equal Employment Opportunity Employer", "US Job Seekers: Click here", "Employment eligibility in the United States is required. SANS does not provide visa sponsorship for this position." (duplicate). Keep only one mention of visa sponsorship under Requirements.
Now write.
Let's draft About the role paragraph: combine from "What You’ll Achieve At SANS" first paragraph: "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."
That's good.
Now Responsibilities list: from "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 need to split into list items. Each sentence before a capital letter? We'll split at each major clause separated by a period. Let's create items:
- 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.
- Perform other duties as assigned.
Now Requirements list: from "What We’re Looking For" bullet points (the mandatory). Let's list:
- 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.
Now Preferred Qualifications list:
- 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.
Now Benefits list (financial, health, time off, learning):
- 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
- .
- Requirements: the "What We’re Looking For" list (mandatory). Use
- .
- Preferred Qualifications: the "Preferred Qualifications Include" list. Use
- .
- Benefits: the "Benefits And Perks Of Working At SANS" section. Use
- for each benefit category? It has subcategories: Financial Benefits, Health & Wellness, Time Off & Flexibility, Learning & Development, Flexibility and Balance at SANS (maybe separate). Could break into list items.
- Pay: the salary range: "$200,000 to $240,000 OTE (comprised of base salary and bonus), depending on geographic location, skills, and experience." Also mention pay equity and transparency. Use
. - Schedule: remote work info: "As a primarily remote work environment, we are committed to maintaining strong connections..." Also "While most roles operate remotely, some positions may require occasional in-person presence depending on role-specific or business needs." Use
. We must remove boilerplate: EEO statements, visa sponsorship repeated, etc. Keep the unrestricted authorization line (maybe under Requirements). Also we should keep "Unrestricted authorization to work in the USA; visa sponsorship is not available." as a requirement. We must not include duplicated lines. Ensure we don't repeat same content. Now craft HTML. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Preferred Qualifications
- ... ...
Benefits
- 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.
- Learning & Development: Access to professional development and SANS training opportunities.
- Flexibility and Balance at SANS: 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.
- for each benefit category? It has subcategories: Financial Benefits, Health & Wellness, Time Off & Flexibility, Learning & Development, Flexibility and Balance at SANS (maybe separate). Could break into list items.
- Pay: the salary range: "$200,000 to $240,000 OTE (comprised of base salary and bonus), depending on geographic location, skills, and experience." Also mention pay equity and transparency. Use
- .
- Benefits: the "Benefits And Perks Of Working At SANS" section. Use
- .
- Preferred Qualifications: the "Preferred Qualifications Include" list. Use