Managing Director- Cybersecurity
PPT Consulting · New York, United States · 3 wk ago
Business Development$200k–$280k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading. Only include sections when posting has real specific content. We have:
- About the role: The job description includes description of role. Could be "About the role" heading with paragraph summarizing role? The posting includes "Job Description" paragraph: "As a Managing Director within Sia’s Cybersecurity Business Line, this role is responsible for driving the growth...". That is about the role. So we can put that in
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include both Requirements and Qualifications if content exists. The posting has "Qualifications" bullet list. Could treat that as Qualifications. Requirements maybe not explicit; but we could treat the same list as Requirements? However we should not create empty sections. So we will include Qualifications heading with the list. Possibly also Requirements heading if there are any explicit requirements like work authorization etc. There's "Work Authorization" and "Our Commitment" etc. Those could be considered Requirements? But they are more like eligibility. Might be better to put them under Requirements? However they are not exactly requirements but still. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine work authorization etc into a short paragraph under Requirements? But we have Qualifications already. Could add Requirements heading with work authorization and maybe "Additional information" etc. But we need to avoid filler. Let's see: The posting includes "Additional information" then "Compensation & Benefits". Then "Workplace", "Work Authorization", "Our Commitment". Those are substantive. Could be placed under Requirements? But they'd be more like "Additional Information". Since we don't have a heading for Additional information, we could fold them into Requirements or Qualifications? Might be better to create a section "Requirements" for work authorization and maybe "Additional information". However the instruction says we can use those headings as examples, not mandatory. We can also create other headings if needed? It says use
for each heading. Only include sections when posting has real specific content. We have:
- About the role: The job description includes description of role. Could be "About the role" heading with paragraph summarizing role? The posting includes "Job Description" paragraph: "As a Managing Director within Sia’s Cybersecurity Business Line, this role is responsible for driving the growth...". That is about the role. So we can put that in About the role
then
...
. - Responsibilities: There's a list of responsibilities under "Key Responsibilities" with bullet points. So we can haveResponsibilities
then- ... ...
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include both Requirements and Qualifications if content exists. The posting has "Qualifications" bullet list. Could treat that as Qualifications. Requirements maybe not explicit; but we could treat the same list as Requirements? However we should not create empty sections. So we will include Qualifications heading with the list. Possibly also Requirements heading if there are any explicit requirements like work authorization etc. There's "Work Authorization" and "Our Commitment" etc. Those could be considered Requirements? But they are more like eligibility. Might be better to put them under Requirements? However they are not exactly requirements but still. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine work authorization etc into a short paragraph under Requirements? But we have Qualifications already. Could add Requirements heading with work authorization and maybe "Additional information" etc. But we need to avoid filler. Let's see: The posting includes "Additional information" then "Compensation & Benefits". Then "Workplace", "Work Authorization", "Our Commitment". Those are substantive. Could be placed under Requirements? But they'd be more like "Additional Information". Since we don't have a heading for Additional information, we could fold them into Requirements or Qualifications? Might be better to create a section "Requirements" for work authorization and maybe "Additional information". However the instruction says we can use those headings as examples, not mandatory. We can also create other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't forbid other headings, but likely they expect only those. We'll stick to those.
Thus we will have:
- About the role (paragraph from Job Description)
- Responsibilities (list from Key Responsibilities)
- Qualifications (list from Qualifications)
- Benefits (list from Compensation & Benefits)
- Pay (the base salary range and bonus info)
- Schedule (Workplace: flexible model, expected in office at least three days per week)
- Possibly Requirements: we could include Work Authorization and maybe "Our Commitment"? But that's more about EEO. Could be omitted as boilerplate? The instruction says remove EEO/equal-opportunity boilerplate. So we should drop "Our Commitment" EEO lines. Work Authorization is not boilerplate; it's a requirement. Could be placed under Requirements. We'll include Requirements heading with paragraph about Work Authorization and maybe "Applicants must be legally authorized to work in the United States...". Also maybe "Management is expected to be in the office at least three days per week" is schedule, not requirement. So Requirements: Work Authorization.
We also have "Additional information" heading but we already used Compensation & Benefits etc.
We must not repeat job title as heading. No Job ID.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove "I'm interested", "Share this job", "Company Description", "About Sia" maybe? Actually "Company Description About Sia" is substantive about the company; could be considered part of About the role? But we already have About the role. The company description could be omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep company description? It's about Sia. Could be placed under About the role? But About the role is about the role, not company. However we could add a section "About the company"? Not in allowed headings. But we could fold into About the role? Might be okay to include a brief paragraph about Sia under About the role? But the instruction says About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company description under About the role? Might be weird but acceptable. However we already have a paragraph about the role from Job Description. We could combine both: first paragraph about Sia, then paragraph about role. That preserves all.
Let's extract company description: "About Sia Sia is a next-generation, global management consulting group. Founded in 1999, we were born digital. Today our strategy and management capabilities are augmented by data science, enhanced by creativity, and driven by responsibility. We're optimists for change, and we help clients initiate, navigate, and benefit from transformation. We believe optimism is a force multiplier, helping clients mitigate downside and maximize opportunity. With expertise across a broad range of sectors and services, our 3,000 consultants serve clients worldwide from 48 locations in 19 countries. Our expertise delivers results. Our optimism transforms outcomes. Sia’s Cybersecurity team is the powerhouse of our firm’s innovation. With over 100 experts worldwide, we tackle projects from proof-of-concept to large-scale deployment, always pushing the boundaries of AI capabilities. By joining Sia’s Cybersecurity team, you’ll step into a vibrant, collaborative environment that nurtures professional growth and empowers you to shape the future of consulting."
That's substantive. We'll include that as part of About the role.
Now Responsibilities: list items from "Key Responsibilities". Let's capture each bullet:
- Lead complex cybersecurity engagements from strategy through execution, serving as the senior executive accountable for delivery and client impact.
- Provide executive-level guidance on cybersecurity governance, cyber resilience, and cyber transformation to Boards and C-suite leaders.
- Lead delivery excellence by ensuring technical rigor, quality assurance, and consistency across engagements while driving optimized staffing and efficient delivery management.
- Business Development: Drive substantial revenue growth by originating new business through proactive client acquisition, expanding existing relationships, and managing strategic accounts.
- Drive the hub’s cybersecurity business expansion by leading go-to-market strategy, commercial prospecting, pre-sales engagement, client sales discussions, and development of tailored solution offerings.
- Champion cross-Business Line collaboration by identifying and facilitating opportunities to bring complementary Sia expertise (e.g., Risk, Data, Strategy) into client engagements, maximizing the firm's overall value proposition.
- People Leadership and Team Development Provide, oversight, and mentorship to project teams, ensuring high-quality delivery and alignment with client objectives. (Note: there is a typo: "Provide, oversight, and mentorship". We'll keep as is.)
- Foster a culture of collaboration, accountability, and continuous learning across engagements and internal initiatives.
- Attract, develop and retain top talent by actively coaching team members, supporting professional growth, and contributing to performance management.
- Implement the Business Line strategy and actively promote the firm’s mission, vision, culture and purpose
- Participate in the major cybersecurity trade shows attended by C-Level executives
- Drive the achievement of relevant cybersecurity clearances
- Thought Leadership & Market Presence Shape a differentiated point of view on industry trends, emerging technologies, and enterprise transformation, and represent Sia as a recognized voice through conferences, panels, and executive forums.
- Build market credibility through advisory roles, council memberships, and active leadership in professional organizations.
Also there is sentence: "This job description is not intended to be all inclusive. Duties, responsibilities, and qualifications may be added, deleted, or modified at any time based on business needs." That's boilerplate? Might be considered generic; but it's substantive? It's a disclaimer. Might be okay to keep? The instruction says remove duplicated lines, but not necessarily disclaimer. However it's generic; but we could keep it as part of Responsibilities? Might be considered filler. I'd say we can omit as it's not specific detail. But to be safe, we could include as a paragraph after list? It's not a list item. Might be considered boilerplate but it's about the job description. I'd lean to omit because it's not specific to role. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." This line is substantive in that it says duties may change. It's generic but still info. I'd include as a paragraph after the list.
Now Qualifications: bullet list:
- 10+ years of experience in cybersecurity, technology risk, or information security.
- 7+ years in a senior leadership role within a consulting firm
- Experience leading large-scale enterprise cybersecurity transformations.
- Certifications such as CISSP, CISM, CRISC, or cloud security certifications are strongly preferred.
We'll put those as - ...
Now Benefits: from "Compensation & Benefits" section after "Compensation Base Salary...". Actually Benefits list includes:
- Medical, dental, and vision coverage
- Company-paid life and AD&D insurance; voluntary supplemental insurance and EAP at no cost
- 401(k) with company match and immediate vesting; HSA and FSA
- College savings and student loan repayment programs
- Paid parental leave
- Generous PTO, nine company holidays, and one floating holiday
- Monthly cell phone stipend
- Well-being and professional development programs
- Benefits are subject to applicable plan terms and eligibility requirements. (That's a note; we can include as part of benefits paragraph.)
We'll put as list.
Now Pay: from "Compensation Base Salary: $200,000–$280,000. Actual compensation within this range will be determined based on experience, qualifications, geographic location, and other job-related factors permitted by applicable law. Personal Sales Bonus (uncapped) Annual Performance Bonus (appraisal)". We'll put as paragraph.
Now Schedule: from "Workplace Sia embraces a flexible workplace model that balances autonomy with in-person connection. Management is expected to be in the office at least three days per week, serving as culture carriers who mentor teams, strengthen client relationships, and lead by example." We'll put as paragraph.
Now Requirements: from "Work Authorization Applicants must be legally authorized to work in the United States at the time of application and throughout their employment. This position is not eligible for employment visa sponsorship now or in the future." We'll put as paragraph.
We should also maybe include "Additional information" but we already captured compensation etc.
Now ensure we don't include duplicated lines: The posting had "I'm interested" repeated; we removed.
Now output HTML fragment: start with
About the role
then ... company description + role description paragraph(s). We need to combine them into maybe two paragraphs? Could be one paragraph with both? Better to separate: first paragraph company description, second paragraph role description. Both under same heading? That's okay.
Then <
- ...
Now Benefits: from "Compensation & Benefits" section after "Compensation Base Salary...". Actually Benefits list includes:
- Medical, dental, and vision coverage
- Company-paid life and AD&D insurance; voluntary supplemental insurance and EAP at no cost
- 401(k) with company match and immediate vesting; HSA and FSA
- College savings and student loan repayment programs
- Paid parental leave
- Generous PTO, nine company holidays, and one floating holiday
- Monthly cell phone stipend
- Well-being and professional development programs
- Benefits are subject to applicable plan terms and eligibility requirements. (That's a note; we can include as part of benefits paragraph.)
We'll put as list.
Now Pay: from "Compensation Base Salary: $200,000–$280,000. Actual compensation within this range will be determined based on experience, qualifications, geographic location, and other job-related factors permitted by applicable law. Personal Sales Bonus (uncapped) Annual Performance Bonus (appraisal)". We'll put as paragraph.
Now Schedule: from "Workplace Sia embraces a flexible workplace model that balances autonomy with in-person connection. Management is expected to be in the office at least three days per week, serving as culture carriers who mentor teams, strengthen client relationships, and lead by example." We'll put as paragraph.
Now Requirements: from "Work Authorization Applicants must be legally authorized to work in the United States at the time of application and throughout their employment. This position is not eligible for employment visa sponsorship now or in the future." We'll put as paragraph.
We should also maybe include "Additional information" but we already captured compensation etc.
Now ensure we don't include duplicated lines: The posting had "I'm interested" repeated; we removed.
Now output HTML fragment: start with
About the role
then... company description + role description paragraph(s). We need to combine them into maybe two paragraphs? Could be one paragraph with both? Better to separate: first paragraph company description, second paragraph role description. Both under same heading? That's okay. Then <