Principal Technical Consultant – Cloud and Application Security

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, equal opportunity, etc). Must not include cookie/navigation/legal/EEO etc. Must not include duplicated lines. Must not include application instructions. Must not include filler like "commensurate with experience", "not specified", etc. Must not create Pay/Schedule/Benefits unless posting actually states them. Pay is present: "$250,000 - $300,000 a year". So we need Pay section. Benefits? Not explicitly listed; maybe not. Schedule? Not mentioned. So we omit Benefits and Schedule. We need sections: About the role (maybe from intro paragraphs). Responsibilities (Duties And Responsibilities). Requirements (maybe Domain Experience Required etc). Qualifications (Qualifications). Skills (maybe Technical Mastery etc). Could combine some. But we need to follow instruction: Use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have content: Intro about AHEAD, culture, etc. That could be About the role? Actually About the role could be description of role. The posting includes description of Principal Technical Consultants role, responsibilities, etc. So we can have About the role summarizing the role overview (first paragraphs). Then Responsibilities (Duties And Responsibilities). Then Requirements (Domain Experience Required etc). Then Qualifications (Qualifications). Then Skills (Technical Mastery etc). Then Pay (compensation). Possibly also include "Business Development" etc but that's within responsibilities. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details but can format as lists. We must not include boilerplate like "We are an equal opportunity employer..." etc. Must remove that. Also remove duplicated lines. We need to output only HTML fragment, no markdown fences. Let's extract content. Intro: "AHEAD builds platforms for digital business. By weaving together advances in cloud infrastructure, automation and analytics, and software delivery, we help enterprises deliver on the promise of digital transformation. At AHEAD, we prioritize creating a culture of belonging, where all perspectives and voices are represented, valued, respected, and heard. We create spaces to empower everyone to speak up, make change, and drive the culture at AHEAD." That's about company culture, not role. Could be part of About the role? Might be considered generic but it's substantive. We'll keep. Then description of Principal Technical Consultants: "Principal Technical Consultants are seasoned experts in information security, cloud security, application security and DevSecOps, threat management, and related technologies, with the ability to secure applications and APIs across the cloud-native software delivery lifecycle . Successful candidates support the Security team in Delivery, Business Development, and Practice Development. Principal Technical Consultants collaborate with a diverse team of consultants with varying skills to meet and exceed client expectations through scoped engagements. They effectively facilitate and lead client engagements remotely by guiding engagements toward scoped objectives and troubleshooting to effectively resolve project risks or issues. Principal Technical Consultants effectively lead client delivery engagements by executing the necessary project tasks, producing expected collateral, and presenting artifacts at any time throughout an engagement, while acting in a leadership capacity to the project team(s). Principal Technical Consultants also support business development activities alongside a sales specialist to qualify client needs and expectations or demonstrate a capability or skillset. They may be directly engaged in client-facing interactions to identify client needs and to produce and/or present sales proposals, leading client-visioning, or discovery sessions. Principal Technical Consultants may also collaborate with other AHEAD Practice areas to identify complex, cross-practice solution sets to achieve a client’s desired state or outcome. AHEAD Principal Technical Consultants leverage their visibility and experience to contribute to the continuous improvement and maturation of in-practice service offerings and capabilities. This includes proposing ideas for new offerings and/or changes to existing offerings or initiatives, as well as their corresponding GTM efforts. They are considered a technical leader within the practice and expected to positively impact the services portfolio and individuals on the team through thought leadership and mentorship." That's role overview. Then "Duties And Responsibilities The following are the expectations of a Principal Technical Consultant:" then bullet list: - Client Delivery Lead sessions of strategy, roadmap, design, and planning workshops for small to medium sized service engagements - Execute on project/program objectives, requirements gathering, project tasks/milestone, project status, dependencies, and timelines, to ensure engagements are delivered successfully and on time while meeting the business objectives - Creation and finalization of project deliverables, may perform peer review for collateral developed by others on a delivery team - Effective presentation of deliverables to project team members. - Knowledge of AHEAD’s project lifecycle management activities to effectively support delivery engagements throughout the duration of a project - Define and operationalize application security delivery plans, including secure SDLC controls, risk-based finding prioritization, developer enablement, metrics, and executive reporting. - Lead application security and threat modeling workshops covering secure architecture, abuse cases, application and API risks, and remediation planning. Then "Technical Mastery" bullet list: - Proficiency in technical troubleshooting; the ability to critically think about a problem and generate a creative solution with minimal oversight. - Deep knowledge of scripting, particularly with PowerShell and/or Python, and the ability to troubleshoot developed code. - Ability to triage and validate application security findings (SAST, DAST, SCA, secrets), distinguish exploitable issues from false positives, and recommend practical remediations. - Ability to effectively communicate aspects of a technical solution to a non-technical individual. - Capability to conduct research and utilize available resources to fill in technical knowledge gaps where ambiguity presents itself. Then "Business Development" bullet list: - Support business development pursuits through client discovery meetings - Represent service offerings during the sales cycle, including project scoping, proposal development, and presenting proposals to clients - Knowledge of AHEAD’s sales management lifecycle to effectively support sales opportunities throughout the duration of a proposal - Lead client discovery and/or visioning workshops to identify opportunities for cross-practice collaboration - Familiarity with AHEAD’s enterprise service portfolio to identify opportunities for cross-practice collaboration Then "Practice Development & Thought Leadership" bullet list: - Maintain subject matter expertise in a minimum of eight security domains or three security solutions - Participate in the development, enhancement, and standardization of AHEAD in-practice service offerings - Owns and/or enables more than one service capability - Process-focused technology thought leader and evangelist - Maintain a broad knowledge and understanding of current and future state IT trends, technologies, and standards - Lend support and mentorship to others Then "Domain Experience Required" with sub-sections: - Cloud Security Architecture & Risk Strategy (list) - CNAPP Tooling (list) - Cloud Platforms & Native Security Controls (list) - Security Frameworks & Governance (list) - DevSecOps and Application Security (list) Then "Qualifications" list: - Undergraduate degree in Computer Sciences or Business Management preferred, but not required - Minimum of 3+ years of leadership experience - 10+ years consulting experience, or commensurate work experience - Professional and/or technical certifications, including industry-recognized certifications which align to AHEAD’s Security service portfolio are preferred (e.g. CISSP, CCSP) - Application security certifications such as CSSLP, GIAC GWEB/GWAPT, OSCP, or equivalent are preferred. - Demonstrated experience establishing or maturing application security programs and mentoring engineers and security practitioners. - Excellent verbal and written communication skills - Comfortable addressing groups of people in virtual or in-person settings - Demonstrated Business Acumen Ability to solve complex, abstract problems - Excellent interpersonal skills, good listener, ability to connect with different personalities - Exhibit Executive presence with leadership characteristics - Demonstrated experience as a technology change agent. Then Pay: "$250,000 - $300,000 a year The compensation range indicated in this posting reflects the On-Target Earnings (“OTE”) for this role, which includes a base salary and any applicable target bonus amount. This OTE range may vary based on the candidate’s relevant experience, qualifications, and geographic location." We must not include filler like "commensurate with experience" but that's part of qualifications line; it's actual text. We can keep it. We must not include "commensurate with experience" as a heading; it's inside a paragraph. We must not include "Why AHEAD Through our daily work and internal groups like Moving Women AHEAD and" truncated; that's boilerplate? It's incomplete; likely part of EEO or something. We should remove that trailing incomplete sentence. Now we need to format. We'll have sections:

About the role

with paragraphs: intro + role overview.

Responsibilities

with

• for each duty.

  Requirements

  maybe combine Domain Experience Required subsections? Could be separate sections but we only have h3 headings list; we could use h3 for Requirements and then inside we can have subheadings? Not allowed? Only h3 for section headings; we could still use

  but not specified. Safer to keep only h3 sections; we can embed subheadings as or

  but not as headings. We'll just list items under Requirements. But we have many detailed requirements; we can break into sub-sections using

  maybe but not prohibited. The instruction only says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use

  for main sections and use

  or

  for subcategories. We'll have:

  Requirements

  then maybe

  Cloud Security Architecture & Risk Strategy:

  then
  etc. Similarly for Qualifications and Skills. Skills: we can combine Technical Mastery, Business Development, Practice Development & Thought Leadership into Skills section. But we also have Domain Experience Required which is more like requirements. Thus sections: - About the role - Responsibilities - Requirements (includes Domain Experience Required) - Qualifications - Skills (Technical Mastery, Business Development, Practice Development & Thought Leadership) - Pay We must not include Benefits or Schedule. Now we need to ensure we preserve all substantive info. Let's extract each bullet. I'll copy the bullets exactly as in text. From Duties And Responsibilities: - Client Delivery Lead sessions of strategy, roadmap, design, and planning workshops for small to medium sized service engagements - Execute on project/program objectives, requirements gathering, project tasks/milestone, project status, dependencies, and timelines, to ensure engagements are delivered successfully and on time while meeting the business objectives - Creation and finalization of project deliverables, may perform peer review for collateral developed by others on a delivery team - Effective presentation of deliverables to project team members. - Knowledge of AHEAD’s project lifecycle management activities to effectively support delivery engagements throughout the duration of a project - Define and operationalize application security delivery plans, including secure SDLC controls, risk-based finding prioritization, developer enablement, metrics, and executive reporting. - Lead application security and threat modeling workshops covering secure architecture, abuse cases, application and API risks, and remediation planning. Note: some lines end with period; we keep. Technical Mastery bullets: - Proficiency in technical troubleshooting; the ability to critically think about a problem and generate a creative solution with minimal oversight. - Deep knowledge of scripting, particularly with PowerShell and/or Python, and the ability to troubleshoot developed code. - Ability to triage and validate application security findings (SAST, DAST, SCA, secrets),