Portfolio Lead
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to extract substantive content: The job description includes:
- Opening paragraph: "Are you passionate about building strong client partnerships while leading the successful delivery of innovative technology solutions? We're looking for an experienced Portfolio Lead, to oversee a portfolio of insurance technology engagements, ensuring exceptional customer outcomes, operational excellence, and long-term business growth. In this highly visible leadership role, you'll serve as a trusted advisor to clients, guide cross-functional teams, and provide strategic oversight across multiple programs and initiatives. This is an exciting opportunity to make a direct impact on customer success while helping organizations leverage technology to solve complex business challenges."
That's prose about role.
- Responsibilities Summary/Objective: "Effectively manage and drive a portfolio of customer engagements across our insurance technology solutions. This leader will be responsible for ensuring successful delivery, strong client relationships, and strategic alignment with business objectives. This role combines deep insurance domain expertise with technology delivery leadership and strong client-facing skills."
- Essential Functions: list bullet points:
Own end-to-end accountability for a portfolio of insurance technology customer engagements.
Provide strategic oversight across multiple programs and projects.
Identify cross-program risks and drive mitigation strategies.
Serve as executive point of contact for key clients.
Build trusted relationships with internal and external stakeholders.
Ensure high customer satisfaction and long-term partnership growth.
Ensure on-time, on-budget, high-quality delivery across engagements.
Drive adherence to delivery methodologies (Agile, Hybrid, Waterfall as applicable).
- Competencies: list: Strategic thinking, Strong communication skills, Exceptional organization and tech-savviness, Quick learner, Collaborative team player, Negotiation & influence.
- Qualifications Requirements: "Effective Customer Relationship Management Familiarity with cloud-based software platforms and modern architecture"
- Preferred Education and Experience: list: 5+ Years of Technology Project Management, 5+ Years of Experience in company-to-company relationship management, Bachelor’s degree or better, Proven technology project management experience, Proven customer relationship management experience, Life and Annuity Industry Experience is strongly preferred.
- About Us: description of Verisk, history, etc. This is company info; could be placed under "About the role"? Actually "About Us" is separate but we can treat as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could map:
- About the role: opening paragraph + maybe responsibilities summary? But we have separate Responsibilities section. So About the role could be the introductory paragraph describing the role.
- Responsibilities: include the Responsibilities Summary/Objective and Essential Functions (maybe combine). Could also include Competencies? Competencies could be Skills.
- Qualifications: include Requirements and Preferred Education and Experience.
- Skills: could be Competencies list.
- Benefits: The posting mentions benefits: "Verisk invests in a benefits package for all employees that includes the following: Health Insurance, a Retirement Plan, Disability benefits, and a Paid Time Off program. We offer a competitive total rewards package that includes base salary determined based on role, experience, skill set, and location." That's substantive benefits info. So we should include Benefits section with list.
- Pay: Not specified exact numbers, just "competitive total rewards package that includes base salary determined based on role, experience, skill set, and location." That's vague but still mentions base salary determined etc. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits, but for Pay it only says base salary determined based on role, experience, skill set, and location. That is still stating something about pay (that it's competitive, based on factors). Is that considered real specific content? It's not a number but it's a statement. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "competitive total rewards package that includes base salary determined based on role, experience, skill set, and location." is not filler like "commensurate with experience"? It's somewhat generic but still states that salary is based on role, experience, skill set, location. Might be considered substantive enough? However they said prefer a few substantive sections over many thin ones. Could include Pay section with that statement. But we also have Benefits section already. Could combine Pay and Benefits? But they said use headings for Benefits, Pay, Schedule separately. Might be okay to include Pay with that statement.
- Schedule: Not mentioned. So omit.
- Also need to remove boilerplate: EEO statements, unsolicited resume notice, privacy notice, etc. Also remove duplicated lines.
We must output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
...
Responsibilities
- ... (maybe combine summary and essential functions)
We could also separate summary as then list.
But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for responsibilities we can have a prose summary then a list of essential functions.
Similarly for Qualifications: maybe a prose then list.
Skills: list of competencies.
Benefits: list.
Pay: maybe a prose.
Let's extract exact text.
Opening paragraph: "Are you passionate about building strong client partnerships while leading the successful delivery of innovative technology solutions? We're looking for an experienced Portfolio Lead, to oversee a portfolio of insurance technology engagements, ensuring exceptional customer outcomes, operational excellence, and long-term business growth. In this highly visible leadership role, you'll serve as a trusted advisor to clients, guide cross-functional teams, and provide strategic oversight across multiple programs and initiatives. This is an exciting opportunity to make a direct impact on customer success while helping organizations leverage technology to solve complex business challenges."
We keep that as prose.
Responsibilities Summary/Objective: "Effectively manage and drive a portfolio of customer engagements across our insurance technology solutions. This leader will be responsible for ensuring successful delivery, strong client relationships, and strategic alignment with business objectives. This role combines deep insurance domain expertise with technology delivery leadership and strong client-facing skills."
That's prose.
Essential Functions list:
- Own end-to-end accountability for a portfolio of insurance technology customer engagements.
- Provide strategic oversight across multiple programs and projects.
- Identify cross-program risks and drive mitigation strategies.
- Serve as executive point of contact for key clients.
- Build trusted relationships with internal and external stakeholders.
- Ensure high customer satisfaction and long-term partnership growth.
- Ensure on-time, on-budget, high-quality delivery across engagements.
- Drive adherence to delivery methodologies (Agile, Hybrid, Waterfall as applicable).
Competencies list:
- Strategic thinking
- Strong communication skills
- Exceptional organization and tech-savviness
- Quick learner
- Collaborative team player
- Negotiation & influence
Qualifications Requirements: "Effective Customer Relationship Management Familiarity with cloud-based software platforms and modern architecture"
Preferred Education and Experience list:
- 5+ Years of Technology Project Management
- 5+ Years of Experience in company-to-company relationship management
- Bachelor’s degree or better
- Proven technology project management experience
- Proven customer relationship management experience
- Life and Annuity Industry Experience is strongly preferred
About Us: Could be considered "About the role"? Actually it's about company. Might be better to include as a separate section "About Verisk" but not in allowed headings. The instruction only gave examples but not limited to those? 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 where applicable. "About Us" could be considered "About the role"? Not exactly. But we could incorporate company description into About the role? Might be stretching. However we could omit About Us as it's not directly about the role, but it's substantive info about employer. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to put? Could create a section "About the company" but not in list. However they said use those headings as examples; maybe we can still use other headings if needed, but they'd prefer those. Safer to include it under a heading like "About Verisk" using . It's not prohibited. The instruction didn't forbid other headings, just gave examples. So we can add About Verisk.
But we must avoid boilerplate like EEO etc. The About Us section includes some boilderplate like "Verisk Analytics is an equal opportunity employer." etc. We need to remove those. Also remove unsolicited resume notice, privacy notice, etc.
Thus we keep the descriptive part about Verisk: "For over 50 years, Verisk has been the leading data analytics and technology partner to the global insurance industry by delivering value to our clients through expertise and scale. We empower communities and businesses to make better decisions on risk, faster. At Verisk, you'll have the chance to use your voice and build a rewarding career that's as unique as you are, with work flexibility and the support, coaching, and training you need to succeed. For the eighth consecutive year, Verisk is proudly recognized as a Great Place to Work® for outstanding workplace culture in the US, the fourth consecutive year in the UK, Spain, and India, and the second consecutive year in Poland. In addition, we’ve been recognized by The Wall Street Journal as one of the Best-Managed Companies and by Forbes as a World’s Best Employer, testaments to the value we place on workplace culture. We’re 7,000 people strong. We relentlessly and ethically pursue innovation. And we are looking for people like you to help us translate big data into big ideas. Join us and create an exceptional experience for yourself and a better tomorrow for future generations."
Then list of Verisk Businesses: Underwriting Solutions, Claims Solutions, Property and Restoration Solutions, Specialty Business Solutions, Catastrophe and Risk Solutions, Marketing Solutions, Life Insurance Solutions, Verisk Maplecroft. That's substantive.
We should keep that as a list maybe.
Now Benefits: "Verisk invests in a benefits package for all employees that includes the following: Health Insurance, a Retirement Plan, Disability benefits, and a Paid Time Off program. We offer a competitive total rewards package that includes base salary determined based on role, experience, skill set, and location."
We could split: Benefits list: Health Insurance, Retirement Plan, Disability benefits, Paid Time Off program. Then Pay: base salary determined based on role, experience, skill set, location (competitive total rewards). We'll keep Pay section with that sentence.
Now we need to ensure we don't include duplicated lines. Also remove any application instructions (none visible). Remove cookie
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: The job description includes: - Opening paragraph: "Are you passionate about building strong client partnerships while leading the successful delivery of innovative technology solutions? We're looking for an experienced Portfolio Lead, to oversee a portfolio of insurance technology engagements, ensuring exceptional customer outcomes, operational excellence, and long-term business growth. In this highly visible leadership role, you'll serve as a trusted advisor to clients, guide cross-functional teams, and provide strategic oversight across multiple programs and initiatives. This is an exciting opportunity to make a direct impact on customer success while helping organizations leverage technology to solve complex business challenges." That's prose about role. - Responsibilities Summary/Objective: "Effectively manage and drive a portfolio of customer engagements across our insurance technology solutions. This leader will be responsible for ensuring successful delivery, strong client relationships, and strategic alignment with business objectives. This role combines deep insurance domain expertise with technology delivery leadership and strong client-facing skills." - Essential Functions: list bullet points: Own end-to-end accountability for a portfolio of insurance technology customer engagements. Provide strategic oversight across multiple programs and projects. Identify cross-program risks and drive mitigation strategies. Serve as executive point of contact for key clients. Build trusted relationships with internal and external stakeholders. Ensure high customer satisfaction and long-term partnership growth. Ensure on-time, on-budget, high-quality delivery across engagements. Drive adherence to delivery methodologies (Agile, Hybrid, Waterfall as applicable). - Competencies: list: Strategic thinking, Strong communication skills, Exceptional organization and tech-savviness, Quick learner, Collaborative team player, Negotiation & influence. - Qualifications Requirements: "Effective Customer Relationship Management Familiarity with cloud-based software platforms and modern architecture" - Preferred Education and Experience: list: 5+ Years of Technology Project Management, 5+ Years of Experience in company-to-company relationship management, Bachelor’s degree or better, Proven technology project management experience, Proven customer relationship management experience, Life and Annuity Industry Experience is strongly preferred. - About Us: description of Verisk, history, etc. This is company info; could be placed under "About the role"? Actually "About Us" is separate but we can treat as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could map: - About the role: opening paragraph + maybe responsibilities summary? But we have separate Responsibilities section. So About the role could be the introductory paragraph describing the role. - Responsibilities: include the Responsibilities Summary/Objective and Essential Functions (maybe combine). Could also include Competencies? Competencies could be Skills. - Qualifications: include Requirements and Preferred Education and Experience. - Skills: could be Competencies list. - Benefits: The posting mentions benefits: "Verisk invests in a benefits package for all employees that includes the following: Health Insurance, a Retirement Plan, Disability benefits, and a Paid Time Off program. We offer a competitive total rewards package that includes base salary determined based on role, experience, skill set, and location." That's substantive benefits info. So we should include Benefits section with list. - Pay: Not specified exact numbers, just "competitive total rewards package that includes base salary determined based on role, experience, skill set, and location." That's vague but still mentions base salary determined etc. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits, but for Pay it only says base salary determined based on role, experience, skill set, and location. That is still stating something about pay (that it's competitive, based on factors). Is that considered real specific content? It's not a number but it's a statement. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The phrase "competitive total rewards package that includes base salary determined based on role, experience, skill set, and location." is not filler like "commensurate with experience"? It's somewhat generic but still states that salary is based on role, experience, skill set, location. Might be considered substantive enough? However they said prefer a few substantive sections over many thin ones. Could include Pay section with that statement. But we also have Benefits section already. Could combine Pay and Benefits? But they said use headings for Benefits, Pay, Schedule separately. Might be okay to include Pay with that statement. - Schedule: Not mentioned. So omit. - Also need to remove boilerplate: EEO statements, unsolicited resume notice, privacy notice, etc. Also remove duplicated lines. We must output only HTML fragment, no /, no markdown fences. We'll structure:
About the role
...
Responsibilities
- ... (maybe combine summary and essential functions)
then list. But instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for responsibilities we can have a prose summary then a list of essential functions. Similarly for Qualifications: maybe a prose then list. Skills: list of competencies. Benefits: list. Pay: maybe a prose. Let's extract exact text. Opening paragraph: "Are you passionate about building strong client partnerships while leading the successful delivery of innovative technology solutions? We're looking for an experienced Portfolio Lead, to oversee a portfolio of insurance technology engagements, ensuring exceptional customer outcomes, operational excellence, and long-term business growth. In this highly visible leadership role, you'll serve as a trusted advisor to clients, guide cross-functional teams, and provide strategic oversight across multiple programs and initiatives. This is an exciting opportunity to make a direct impact on customer success while helping organizations leverage technology to solve complex business challenges." We keep that as prose. Responsibilities Summary/Objective: "Effectively manage and drive a portfolio of customer engagements across our insurance technology solutions. This leader will be responsible for ensuring successful delivery, strong client relationships, and strategic alignment with business objectives. This role combines deep insurance domain expertise with technology delivery leadership and strong client-facing skills." That's prose. Essential Functions list: - Own end-to-end accountability for a portfolio of insurance technology customer engagements. - Provide strategic oversight across multiple programs and projects. - Identify cross-program risks and drive mitigation strategies. - Serve as executive point of contact for key clients. - Build trusted relationships with internal and external stakeholders. - Ensure high customer satisfaction and long-term partnership growth. - Ensure on-time, on-budget, high-quality delivery across engagements. - Drive adherence to delivery methodologies (Agile, Hybrid, Waterfall as applicable). Competencies list: - Strategic thinking - Strong communication skills - Exceptional organization and tech-savviness - Quick learner - Collaborative team player - Negotiation & influence Qualifications Requirements: "Effective Customer Relationship Management Familiarity with cloud-based software platforms and modern architecture" Preferred Education and Experience list: - 5+ Years of Technology Project Management - 5+ Years of Experience in company-to-company relationship management - Bachelor’s degree or better - Proven technology project management experience - Proven customer relationship management experience - Life and Annuity Industry Experience is strongly preferred About Us: Could be considered "About the role"? Actually it's about company. Might be better to include as a separate section "About Verisk" but not in allowed headings. The instruction only gave examples but not limited to those? 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 where applicable. "About Us" could be considered "About the role"? Not exactly. But we could incorporate company description into About the role? Might be stretching. However we could omit About Us as it's not directly about the role, but it's substantive info about employer. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to put? Could create a section "About the company" but not in list. However they said use those headings as examples; maybe we can still use other headings if needed, but they'd prefer those. Safer to include it under a heading like "About Verisk" using
. It's not prohibited. The instruction didn't forbid other headings, just gave examples. So we can add About Verisk. But we must avoid boilerplate like EEO etc. The About Us section includes some boilderplate like "Verisk Analytics is an equal opportunity employer." etc. We need to remove those. Also remove unsolicited resume notice, privacy notice, etc. Thus we keep the descriptive part about Verisk: "For over 50 years, Verisk has been the leading data analytics and technology partner to the global insurance industry by delivering value to our clients through expertise and scale. We empower communities and businesses to make better decisions on risk, faster. At Verisk, you'll have the chance to use your voice and build a rewarding career that's as unique as you are, with work flexibility and the support, coaching, and training you need to succeed. For the eighth consecutive year, Verisk is proudly recognized as a Great Place to Work® for outstanding workplace culture in the US, the fourth consecutive year in the UK, Spain, and India, and the second consecutive year in Poland. In addition, we’ve been recognized by The Wall Street Journal as one of the Best-Managed Companies and by Forbes as a World’s Best Employer, testaments to the value we place on workplace culture. We’re 7,000 people strong. We relentlessly and ethically pursue innovation. And we are looking for people like you to help us translate big data into big ideas. Join us and create an exceptional experience for yourself and a better tomorrow for future generations." Then list of Verisk Businesses: Underwriting Solutions, Claims Solutions, Property and Restoration Solutions, Specialty Business Solutions, Catastrophe and Risk Solutions, Marketing Solutions, Life Insurance Solutions, Verisk Maplecroft. That's substantive. We should keep that as a list maybe. Now Benefits: "Verisk invests in a benefits package for all employees that includes the following: Health Insurance, a Retirement Plan, Disability benefits, and a Paid Time Off program. We offer a competitive total rewards package that includes base salary determined based on role, experience, skill set, and location." We could split: Benefits list: Health Insurance, Retirement Plan, Disability benefits, Paid Time Off program. Then Pay: base salary determined based on role, experience, skill set, location (competitive total rewards). We'll keep Pay section with that sentence. Now we need to ensure we don't include duplicated lines. Also remove any application instructions (none visible). Remove cookie