Advisory Solution Consultant, Integrated Risk Management

We need to output HTML fragment with sections: About the role? Actually we have company description, job description, responsibilities (What You Get To Do), qualifications, maybe additional info like travel, etc. We must not repeat job title as heading. We must not include boilerplate like EEO, legal, scam warning, application instructions, etc. Also we must not include sections with placeholder text like "commensurate with experience". We need to include sections only when posting has real, specific content. We need to parse the posting: Company Description: paragraph about ServiceNow. Job Description: description of role. What You Get To Do In This Role: bullet list of responsibilities. Qualifications: list of requirements. Additional Information: includes EEO, flexible work, accommodation, export control, fraud warning, etc. We must remove boilerplate EEO, legal, scam warning, etc. But we may keep "Willing to travel up to 25%" as part of qualifications or maybe a separate section like "Travel". Also "Additional Information" includes "ServiceNow is an Equal Employment Opportunity Employer..." which we must remove. Also "At ServiceNow, we lead with flexibility and trust..." maybe we can keep flexibility statement? It's not boilerplate? It's about work personas. Might be considered generic but it's specific to ServiceNow. However guidelines: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The flexibility statement is not EEO or legal; it's about work culture. Could keep as a short paragraph under maybe "Work Environment" or similar. But we need to decide if we should create a section for it. The instruction: Prefer a few substantive sections over many thin ones. So maybe we incorporate travel and flexibility into Qualifications or Additional Info as a paragraph. We must not include sections like Benefits, Pay, Schedule unless posting actually states them. It does not mention benefits, pay, schedule. So we omit those. We must not repeat job title as heading. We must use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use headings like About the role, Responsibilities, Qualifications, maybe Skills? But we have qualifications list; we can use "Qualifications". Also maybe "Responsibilities". Also maybe "Company Overview". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings. We need to preserve all substantive information. So we need to include company description paragraph, role description paragraph, responsibilities bullet list, qualifications bullet list, travel statement, maybe flexibility statement. We must not include duplicated lines. Let's extract substantive content: Company Description: "At ServiceNow, our technology makes the world work for everyone, and our people make it possible. We move fast because the world can’t wait, and we innovate in ways no one else can for our customers and communities. By joining ServiceNow, you are part of an ambitious team of change makers who have a restless curiosity and a drive for ingenuity. We know that your best work happens when you live your best life and share your unique talents, so we do everything we can to make that possible. We dream big together, supporting each other to make our individual and collective dreams come true. The future is ours, and it starts with you. With more than 7,700+ customers, we serve approximately 85% of the Fortune 500, and we're proud to be one of FORTUNE's 100 Best Companies to Work For® and World's Most Admired Companies®. Learn more on Life at Now blog and hear from our employees about their experiences working at ServiceNow." Unsure if you meet all the qualifications... etc. That's encouragement to apply; maybe we can keep as part of company description? It's more about encouraging to apply; but it's not boilerplate? It's a generic encouragement but still part of posting. Might keep as a paragraph. But we need to remove application instructions. The encouragement to apply is not exactly instruction but could be considered generic. However it's not a legal boilerplate. Might keep. Job Description: "ServiceNow is seeking driven Presales Risk Solution Consultants. This is a hands-on presales SC capable of going wide and deep on solution development and positioning. The Risk Solution Consultant will provide solution leadership and expertise to support customers during the sales engagement and will participate in acquiring and retaining customers by leveraging Integrated Risk Management solutions." What You Get To Do In This Role: list of responsibilities (bullet points). Let's extract each: - Responsible for creating innovative solutions leveraging ServiceNow’s Integrated Risk Management Solutions - Review customer’s current business processes and translate to customer pain points - Respond to customer questions relating to ServiceNow IRM solution - This role is pivotal in providing our growing customer base with lessons learned, strategies, and advice to enhance real-world integrated risk programs. - Develop and contribute to sales campaigns focused on IRM and GRC Solutions - Contribute and maintain a showcase of IRM solutions created on the ServiceNow platform - Help develop programs that enable other Solution Consultants to demonstrate the value of IRM on the ServiceNow platform - Configure solution environments to address customer requirements and business issues - Collaborate with Product Management and Development team members to enhance ServiceNow products with new capabilities that address customer needs - Share best practices and known solutions with other Solution Consultants to improve the quality and efficiency of the other team members - Stay current on competitive analyses and understand differentiators between ServiceNow and its competitors. - Supporting Marketing events – user conferences, trade shows, analyst demonstrations, webinars, etc. Qualifications: bullet list: - In order to be successful in this role, we need someone who has: - 5+ years of pre-sales solution consulting or sales engineering experience in Integrated Risk Management or Governance, Risk & Compliance (GRC) solutions and programs - Work experience or strong understanding of risk management, policy & compliance management, business continuity, crisis planning, disaster recovery, vendor risk/third party supply chain management, privacy management, regulatory change management - Strong working knowledge of GRC processes and solutions such as Archer or MetricStream, IBM OpenPages, OneTrust - Experience in regulatory compliance for vertical-specific requirements within financial services vertical - Ability to architect and effectively communicate solutions to business challenges - Experience working in a large government or corporate enterprise environment. - Responsible for understanding business and technical problems addressed by the products including applicable regulations, business drivers, and evolving business needs, etc. - A Bachelor’s degree or equivalent training in and 3-5 years of experience is required. - Must have strong written and oral communication skills and be self-directed and independent - Willing to travel up to 25% Note: The "A Bachelor’s degree or equivalent training in and 3-5 years of experience is required." seems missing field; maybe it's "A Bachelor’s degree or equivalent training in [related field] and 3-5 years of experience is required." We'll keep as is. Additional Information: we need to keep maybe flexibility statement: "At ServiceNow, we lead with flexibility and trust in our distributed world of work. Click here to learn about our work personas: flexible, remote and required-in-office." This is not EEO; it's about work flexibility. Could keep as a short paragraph under maybe "Work Environment". Also the accommodation contact: "If you require a reasonable accommodation to complete any part of the application process, or are limited in the ability or unable to access or use this online application process and need an alternative method for applying, you may contact us at talent.acquisition@servicenow.com for assistance." This is about accommodation; could be considered part of application instructions? It's about accommodation request; maybe we keep as it's substantive? However guidelines: remove application instructions. This is about accommodation request; might be considered part of application process. Safer to remove? The instruction says remove application instructions. The accommodation request is not exactly instruction to apply but a provision for accommodation. Might be considered part of EEO/accommodation statement; could be considered boilerplate? It's specific contact email. Might be considered part of application instructions. Safer to remove. Export control warning: remove. Fraud warning: remove. Fortune copyright: remove. Thus we keep company description, job description, responsibilities, qualifications, travel statement, flexibility statement. We need to format with

headings. Possible sections: - About ServiceNow (or Company Description) -> heading About the role? Actually About the role is for role description; but we have company description separate. Could use "About ServiceNow" as heading, but the list of examples includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not exactly company description. But we can still use About the role for role description; company description could be a

without heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Probably we should stick to those headings where applicable. So we could have:

About the role

containing job description paragraph.

Responsibilities

with

• list.

  Qualifications

  with
  • list (including travel maybe as separate bullet or separate paragraph). We might also include a

    About ServiceNow

    but not in examples. However we could treat company description as part of About the role? Actually About the role is for role description; company description is separate. Could we put company description as a

    before any heading? The instruction says output ONLY the HTML fragment; we can have a

    for company description without heading. That's acceptable. Thus structure:

    Company description paragraph(s)

    About the role

    Job description paragraph(s)

    Responsibilities

    ...

    Qualifications

    ...
    Maybe also include a

    Work Environment

    for flexibility statement. But not in examples; but we could still use

    Work Environment

    as it's 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 suggests using those examples. Safer to stick to those. Could incorporate flexibility statement into Qualifications as a bullet or paragraph. Travel statement: "Willing to travel up to 25%". Could be a bullet under Qualifications. Thus Qualifications list includes that. Now we need to ensure we don't include any boilerplate. Let's craft the HTML. Company description: combine paragraphs maybe two paragraphs: first big paragraph, second about encouraging to apply? The encouragement paragraph: "Unsure if you meet all the qualifications of a job description but are deeply excited about the role? We still encourage you to apply! At ServiceNow, we are committed to creating an inclusive environment where all voices are heard, valued, and respected. We welcome all candidates, including individuals from non-traditional, varied backgrounds, that might not come from a typical path connected to this role. We believe skills and experience are transferrable, and the desire to dream big makes for great candidates." This is not boilerplate; it's encouraging to apply and inclusive statement. Could keep as part of company description or separate section like "Our Culture". But we might keep as part of company description. Thus we will have two

    elements for company description. Now About the role: paragraph: "ServiceNow is seeking driven Presales Risk Solution Consultants. This is a hands-on presales SC capable of going wide and deep on solution development and positioning. The Risk Solution Consultant will provide solution leadership and expertise to support customers during the sales engagement and will participate in acquiring and retaining customers by leveraging Integrated Risk Management solutions