Loan Operations Success Manager
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 (the page already shows it) and 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. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Content:
- About Us: paragraph describing NEWITY.
- Job Summary: paragraph.
- Description & Responsibilities: list of responsibilities (multiple bullet-like sentences). They are separated by periods but each is a sentence. We should treat as list items.
- Experience leading a bank servicing or monitoring platform rollout... (these are qualifications? Actually they appear after responsibilities as part of description? Let's see: after responsibilities list, there is "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor.Familiarity with APIs, file-based interfaces, and servicing-data flows between core systems.Experience with RPA, rules engines, or AI-enabled servicing and monitoring tools.Early-stage experience spanning product, customer, and operations responsibilities.Lean, continuous-improvement mindset." This seems like qualifications or requirements.
Then "Qualifications:" heading with bullet points.
Then "Pay Range and Compensation Package:" with details.
Then "Equal Opportunity Statement:" which is boilerplate to remove.
We need to include sections: maybe About Us, Job Summary, Responsibilities, Qualifications, Pay/Benefits (since they gave pay and benefits). Also maybe Skills? Not separate.
We must not include sections with placeholder text.
We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We need to preserve all substantive info.
We need to remove boilerplate: Equal Opportunity Statement.
Also remove duplicated lines? Not seeing duplicates.
We need to fold minor metadata (like maybe "About Us:" is a heading? We can treat as section heading "About Us". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid "About Us". It says e.g. but not limited. We'll use About Us
.
Job Summary: we can have Job Summary
with paragraph.
Responsibilities: Responsibilities
with - items.
Qualifications:
Qualifications
with - items.
Pay and Benefits: maybe combine Pay and Benefits into one section? The instruction says we can have Pay, Benefits, Schedule sections. Since they gave both pay and benefits, we could have
Pay and Benefits
or separate Pay and Benefits. But they said prefer a few substantive sections over many thin ones. So combine into one section "Pay and Benefits". Use - for each benefit item.
We need to ensure we don't include placeholder text like "commensurate with experience". Not present.
Now extract content precisely.
About Us paragraph:
"NEWITY is America's source for small business capital. We’re building the latest software that is AI native, creating automated workflows with proprietary data sources delivering industry leading outcomes for our financial institution partners. As part of this enterprise technology suite, we will create a continuous loan-monitoring platform delivering value added outcomes to our partner financial institutions that automates covenant tracking, collateral monitoring, financial-statement collection, exception handling, and borrower engagement across SBA and commercial loan portfolios. Achieving our vision requires more than ambition. It demands resilience, collaboration, accountability, professionalism, and a relentless drive to improve. Our culture moves fast, fosters excellence, and rewards those who lean in. It’s not for everyone, but if you’re energized by challenge, motivated by impact, and ready to grow alongside teammates who share your commitment, there’s no better place to build your career."
Job Summary paragraph:
"We’re seeking a commercial loan-operations and servicing expert ready to shape how this work gets done. In this forward-deployed role, you’ll engage with our GTM team to support design partnerships and sales, partner with our product team to bring subject matter expertise to the product strategy, embed with each bank, configure the platform to its workflows, lead successful launches, and use customer insights to improve the entire process. Your edge is domain credibility. You understand loan servicing, monitoring, data sources, operational requirements and regulatory realities, and can speak the language of bank operators and leaders. You’re also technically fluent enough to configure software, work with data and integrations, and troubleshoot rollouts. This non-coding role blends subject matter expert, solutions engineer, and GTM influence."
Now responsibilities list: The text after "Description & Responsibilities:" includes sentences separated by periods. Let's extract each:
- Onboard customers by understanding their monitoring workflows and configuring the platform for SBA and commercial loan portfolios.
- Map bank processes—including covenant, collateral, financial-statement, tax, servicing-event, and exception monitoring—to configure and design solutions.
- Serve as the trusted rollout lead, training teams, troubleshooting issues, and driving successful go-lives.
- Define onboarding data and integration requirements, map system data flows, and partner with engineering on implementation.
- Serve as the loan-operations expert, testing the roadmap against servicing, monitoring, operational, and regulatory realities.
- Translate customer pain points into prioritized product feedback.
- Ensure the platform meets regulated-lending requirements.
- Refine positioning, scoping, and implementation playbooks as the GTM strategy matures.
- Build scalable onboarding playbooks, configuration templates, and training materials.
Now after that there is a block that seems like qualifications/experience: "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor.Familiarity with APIs, file-based interfaces, and servicing-data flows between core systems.Experience with RPA, rules engines, or AI-enabled servicing and monitoring tools.Early-stage experience spanning product, customer, and operations responsibilities.Lean, continuous-improvement mindset."
These are likely qualifications or requirements. However there is also a separate "Qualifications:" section with bullet points. We need to decide whether to treat the earlier block as part of Qualifications or maybe as "Requirements". The instruction says we can have sections like Requirements, Qualifications, Skills. We have a Qualifications section later. The earlier block could be considered "Requirements" or "Experience". Since we already have a Qualifications section, we could merge them into Qualifications (makes sense). But we must not duplicate content. The Qualifications section bullet points are:
- 7-10 years in loan servicing, portfolio management, special assets, or lending operations, with hands-on SBA, SMB and/or commercial lending exposure.
- Working knowledge of loan compliance and SOPs, the commercial loan lifecycle, covenant compliance, regulatory audit preparation and compliance and collateral monitoring (financial statements, insurance, UCC, taxes).
- AI curious – you are excited and ready to dive deep into how AI can solve some of the most complex workflows and data processes in financial services – yet you don’t need to be an expert today.
- Technical fluency: comfortable owning a software configuration, reasoning about data and integrations, and learning new tools quickly.[CR1]
- Strong critical-thinking and problem-solving skills, and the communication ability to be credible with both financial institution operators during GTM and implementations and a product/engineering team to convey valuable feedback.
- Comfort being customer-facing and embedded — you like being on-site (physically or virtually) making a rollout succeed.
We should combine the earlier experience bullets into Qualifications as well, maybe as additional items. However we need to avoid duplication. The earlier block includes items like "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor." etc. Those are not in the Qualifications bullet list. So we should add them.
Thus Qualifications section will have a list combining both sets.
Now Pay and Benefits:
"Pay Range and Compensation Package: Base Compensation: $90,000-120,000 + Performance Bonus. Comprehensive Health, Dental, and Vision Insurance. Retirement Plan with Company Contribution of 3%. Paid Time Off and Holidays. Professional Development Opportunities."
We need to create a Pay and Benefits section. Could list each as
- . The base compensation line includes base and bonus. We'll keep as one item.
Now we must remove Equal Opportunity Statement.
Now produce HTML.
Structure:
About Us
...
Job Summary
...
Responsibilities
- ...
...
Qualifications
- ...
...
Pay and Benefits
- Base Compensation: $90,000-120,000 + Performance Bonus.
- Comprehensive Health, Dental, and Vision Insurance.
- Retirement Plan with Company Contribution of 3%.
- Paid Time Off and Holidays.
- Professional Development Opportunities.
Check that we haven't missed any substantive info: The earlier block about "Experience leading a bank servicing..." etc we included in Qualifications. Also the "Lean, continuous-improvement mindset." from that block we need to include as a qualification item.
Also note there is a "[CR1]" after "Technical fluency: comfortable owning a software configuration, reasoning about data and integrations, and learning new tools quickly.[CR1]" We should keep the text but maybe remove the reference marker? It's part of the posting; we should preserve it. It's not boilerplate. We'll keep "[CR1]" as part of the sentence.
Now ensure we didn't include any duplicated lines. The responsibilities list includes "Serve as the trusted rollout lead, training teams, troubleshooting issues, and driving successful go-lives." Good.
Now check for any other sections like "Skills" not present; we won't add.
Now ensure we didn't include any placeholder like "commensurate with experience". Not present.
Now output only HTML fragment.
Let's craft the HTML.
We need to escape any HTML special characters? The text includes apostrophes, em dashes, etc. It's fine as plain text within HTML; we don't need to escape unless they are < or &. There's an ampersand in "SMB and/or". That's okay. There's an ampersand in "UCC". No. There's an ampersand in "RPA, rules engines, or AI-enabled". No. There's an ampersand in "Performance Bonus." No. There's an ampersand in "Health, Dental, and Vision". No. There's an ampersand in "SBA and/or". Actually there is "SMB and/or". That's an ampersand. In HTML, & is special; we need to escape as &. Similarly "and/or" includes &. So we need to
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About Us: paragraph describing NEWITY. - Job Summary: paragraph. - Description & Responsibilities: list of responsibilities (multiple bullet-like sentences). They are separated by periods but each is a sentence. We should treat as list items. - Experience leading a bank servicing or monitoring platform rollout... (these are qualifications? Actually they appear after responsibilities as part of description? Let's see: after responsibilities list, there is "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor.Familiarity with APIs, file-based interfaces, and servicing-data flows between core systems.Experience with RPA, rules engines, or AI-enabled servicing and monitoring tools.Early-stage experience spanning product, customer, and operations responsibilities.Lean, continuous-improvement mindset." This seems like qualifications or requirements. Then "Qualifications:" heading with bullet points. Then "Pay Range and Compensation Package:" with details. Then "Equal Opportunity Statement:" which is boilerplate to remove. We need to include sections: maybe About Us, Job Summary, Responsibilities, Qualifications, Pay/Benefits (since they gave pay and benefits). Also maybe Skills? Not separate. We must not include sections with placeholder text. We need to use
for each section heading.
We need to use - for any list of duties/requirements/benefits.
We need to use
for prose.
We need to preserve all substantive info.
We need to remove boilerplate: Equal Opportunity Statement.
Also remove duplicated lines? Not seeing duplicates.
We need to fold minor metadata (like maybe "About Us:" is a heading? We can treat as section heading "About Us". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid "About Us". It says e.g. but not limited. We'll use About Us
.
Job Summary: we can have Job Summary
with paragraph.
Responsibilities: Responsibilities
with - items.
Qualifications:
Qualifications
with - items.
Pay and Benefits: maybe combine Pay and Benefits into one section? The instruction says we can have Pay, Benefits, Schedule sections. Since they gave both pay and benefits, we could have
Pay and Benefits
or separate Pay and Benefits. But they said prefer a few substantive sections over many thin ones. So combine into one section "Pay and Benefits". Use - for each benefit item.
We need to ensure we don't include placeholder text like "commensurate with experience". Not present.
Now extract content precisely.
About Us paragraph:
"NEWITY is America's source for small business capital. We’re building the latest software that is AI native, creating automated workflows with proprietary data sources delivering industry leading outcomes for our financial institution partners. As part of this enterprise technology suite, we will create a continuous loan-monitoring platform delivering value added outcomes to our partner financial institutions that automates covenant tracking, collateral monitoring, financial-statement collection, exception handling, and borrower engagement across SBA and commercial loan portfolios. Achieving our vision requires more than ambition. It demands resilience, collaboration, accountability, professionalism, and a relentless drive to improve. Our culture moves fast, fosters excellence, and rewards those who lean in. It’s not for everyone, but if you’re energized by challenge, motivated by impact, and ready to grow alongside teammates who share your commitment, there’s no better place to build your career."
Job Summary paragraph:
"We’re seeking a commercial loan-operations and servicing expert ready to shape how this work gets done. In this forward-deployed role, you’ll engage with our GTM team to support design partnerships and sales, partner with our product team to bring subject matter expertise to the product strategy, embed with each bank, configure the platform to its workflows, lead successful launches, and use customer insights to improve the entire process. Your edge is domain credibility. You understand loan servicing, monitoring, data sources, operational requirements and regulatory realities, and can speak the language of bank operators and leaders. You’re also technically fluent enough to configure software, work with data and integrations, and troubleshoot rollouts. This non-coding role blends subject matter expert, solutions engineer, and GTM influence."
Now responsibilities list: The text after "Description & Responsibilities:" includes sentences separated by periods. Let's extract each:
- Onboard customers by understanding their monitoring workflows and configuring the platform for SBA and commercial loan portfolios.
- Map bank processes—including covenant, collateral, financial-statement, tax, servicing-event, and exception monitoring—to configure and design solutions.
- Serve as the trusted rollout lead, training teams, troubleshooting issues, and driving successful go-lives.
- Define onboarding data and integration requirements, map system data flows, and partner with engineering on implementation.
- Serve as the loan-operations expert, testing the roadmap against servicing, monitoring, operational, and regulatory realities.
- Translate customer pain points into prioritized product feedback.
- Ensure the platform meets regulated-lending requirements.
- Refine positioning, scoping, and implementation playbooks as the GTM strategy matures.
- Build scalable onboarding playbooks, configuration templates, and training materials.
Now after that there is a block that seems like qualifications/experience: "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor.Familiarity with APIs, file-based interfaces, and servicing-data flows between core systems.Experience with RPA, rules engines, or AI-enabled servicing and monitoring tools.Early-stage experience spanning product, customer, and operations responsibilities.Lean, continuous-improvement mindset."
These are likely qualifications or requirements. However there is also a separate "Qualifications:" section with bullet points. We need to decide whether to treat the earlier block as part of Qualifications or maybe as "Requirements". The instruction says we can have sections like Requirements, Qualifications, Skills. We have a Qualifications section later. The earlier block could be considered "Requirements" or "Experience". Since we already have a Qualifications section, we could merge them into Qualifications (makes sense). But we must not duplicate content. The Qualifications section bullet points are:
- 7-10 years in loan servicing, portfolio management, special assets, or lending operations, with hands-on SBA, SMB and/or commercial lending exposure.
- Working knowledge of loan compliance and SOPs, the commercial loan lifecycle, covenant compliance, regulatory audit preparation and compliance and collateral monitoring (financial statements, insurance, UCC, taxes).
- AI curious – you are excited and ready to dive deep into how AI can solve some of the most complex workflows and data processes in financial services – yet you don’t need to be an expert today.
- Technical fluency: comfortable owning a software configuration, reasoning about data and integrations, and learning new tools quickly.[CR1]
- Strong critical-thinking and problem-solving skills, and the communication ability to be credible with both financial institution operators during GTM and implementations and a product/engineering team to convey valuable feedback.
- Comfort being customer-facing and embedded — you like being on-site (physically or virtually) making a rollout succeed.
We should combine the earlier experience bullets into Qualifications as well, maybe as additional items. However we need to avoid duplication. The earlier block includes items like "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor." etc. Those are not in the Qualifications bullet list. So we should add them.
Thus Qualifications section will have a list combining both sets.
Now Pay and Benefits:
"Pay Range and Compensation Package: Base Compensation: $90,000-120,000 + Performance Bonus. Comprehensive Health, Dental, and Vision Insurance. Retirement Plan with Company Contribution of 3%. Paid Time Off and Holidays. Professional Development Opportunities."
We need to create a Pay and Benefits section. Could list each as
- . The base compensation line includes base and bonus. We'll keep as one item.
Now we must remove Equal Opportunity Statement.
Now produce HTML.
Structure:
About Us
...
Job Summary
...
Responsibilities
- ...
...
Qualifications
- ...
...
Pay and Benefits
- Base Compensation: $90,000-120,000 + Performance Bonus.
- Comprehensive Health, Dental, and Vision Insurance.
- Retirement Plan with Company Contribution of 3%.
- Paid Time Off and Holidays.
- Professional Development Opportunities.
Check that we haven't missed any substantive info: The earlier block about "Experience leading a bank servicing..." etc we included in Qualifications. Also the "Lean, continuous-improvement mindset." from that block we need to include as a qualification item.
Also note there is a "[CR1]" after "Technical fluency: comfortable owning a software configuration, reasoning about data and integrations, and learning new tools quickly.[CR1]" We should keep the text but maybe remove the reference marker? It's part of the posting; we should preserve it. It's not boilerplate. We'll keep "[CR1]" as part of the sentence.
Now ensure we didn't include any duplicated lines. The responsibilities list includes "Serve as the trusted rollout lead, training teams, troubleshooting issues, and driving successful go-lives." Good.
Now check for any other sections like "Skills" not present; we won't add.
Now ensure we didn't include any placeholder like "commensurate with experience". Not present.
Now output only HTML fragment.
Let's craft the HTML.
We need to escape any HTML special characters? The text includes apostrophes, em dashes, etc. It's fine as plain text within HTML; we don't need to escape unless they are < or &. There's an ampersand in "SMB and/or". That's okay. There's an ampersand in "UCC". No. There's an ampersand in "RPA, rules engines, or AI-enabled". No. There's an ampersand in "Performance Bonus." No. There's an ampersand in "Health, Dental, and Vision". No. There's an ampersand in "SBA and/or". Actually there is "SMB and/or". That's an ampersand. In HTML, & is special; we need to escape as &. Similarly "and/or" includes &. So we need to
for prose. We need to preserve all substantive info. We need to remove boilerplate: Equal Opportunity Statement. Also remove duplicated lines? Not seeing duplicates. We need to fold minor metadata (like maybe "About Us:" is a heading? We can treat as section heading "About Us". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid "About Us". It says e.g. but not limited. We'll use About Us
.
Job Summary: we can have Job Summary
with paragraph.
Responsibilities: Responsibilities
with - items.
Qualifications:
Qualifications
with - items.
Pay and Benefits: maybe combine Pay and Benefits into one section? The instruction says we can have Pay, Benefits, Schedule sections. Since they gave both pay and benefits, we could have
Pay and Benefits
or separate Pay and Benefits. But they said prefer a few substantive sections over many thin ones. So combine into one section "Pay and Benefits". Use - for each benefit item.
We need to ensure we don't include placeholder text like "commensurate with experience". Not present.
Now extract content precisely.
About Us paragraph:
"NEWITY is America's source for small business capital. We’re building the latest software that is AI native, creating automated workflows with proprietary data sources delivering industry leading outcomes for our financial institution partners. As part of this enterprise technology suite, we will create a continuous loan-monitoring platform delivering value added outcomes to our partner financial institutions that automates covenant tracking, collateral monitoring, financial-statement collection, exception handling, and borrower engagement across SBA and commercial loan portfolios. Achieving our vision requires more than ambition. It demands resilience, collaboration, accountability, professionalism, and a relentless drive to improve. Our culture moves fast, fosters excellence, and rewards those who lean in. It’s not for everyone, but if you’re energized by challenge, motivated by impact, and ready to grow alongside teammates who share your commitment, there’s no better place to build your career."
Job Summary paragraph:
"We’re seeking a commercial loan-operations and servicing expert ready to shape how this work gets done. In this forward-deployed role, you’ll engage with our GTM team to support design partnerships and sales, partner with our product team to bring subject matter expertise to the product strategy, embed with each bank, configure the platform to its workflows, lead successful launches, and use customer insights to improve the entire process. Your edge is domain credibility. You understand loan servicing, monitoring, data sources, operational requirements and regulatory realities, and can speak the language of bank operators and leaders. You’re also technically fluent enough to configure software, work with data and integrations, and troubleshoot rollouts. This non-coding role blends subject matter expert, solutions engineer, and GTM influence."
Now responsibilities list: The text after "Description & Responsibilities:" includes sentences separated by periods. Let's extract each:
- Onboard customers by understanding their monitoring workflows and configuring the platform for SBA and commercial loan portfolios.
- Map bank processes—including covenant, collateral, financial-statement, tax, servicing-event, and exception monitoring—to configure and design solutions.
- Serve as the trusted rollout lead, training teams, troubleshooting issues, and driving successful go-lives.
- Define onboarding data and integration requirements, map system data flows, and partner with engineering on implementation.
- Serve as the loan-operations expert, testing the roadmap against servicing, monitoring, operational, and regulatory realities.
- Translate customer pain points into prioritized product feedback.
- Ensure the platform meets regulated-lending requirements.
- Refine positioning, scoping, and implementation playbooks as the GTM strategy matures.
- Build scalable onboarding playbooks, configuration templates, and training materials.
Now after that there is a block that seems like qualifications/experience: "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor.Familiarity with APIs, file-based interfaces, and servicing-data flows between core systems.Experience with RPA, rules engines, or AI-enabled servicing and monitoring tools.Early-stage experience spanning product, customer, and operations responsibilities.Lean, continuous-improvement mindset."
These are likely qualifications or requirements. However there is also a separate "Qualifications:" section with bullet points. We need to decide whether to treat the earlier block as part of Qualifications or maybe as "Requirements". The instruction says we can have sections like Requirements, Qualifications, Skills. We have a Qualifications section later. The earlier block could be considered "Requirements" or "Experience". Since we already have a Qualifications section, we could merge them into Qualifications (makes sense). But we must not duplicate content. The Qualifications section bullet points are:
- 7-10 years in loan servicing, portfolio management, special assets, or lending operations, with hands-on SBA, SMB and/or commercial lending exposure.
- Working knowledge of loan compliance and SOPs, the commercial loan lifecycle, covenant compliance, regulatory audit preparation and compliance and collateral monitoring (financial statements, insurance, UCC, taxes).
- AI curious – you are excited and ready to dive deep into how AI can solve some of the most complex workflows and data processes in financial services – yet you don’t need to be an expert today.
- Technical fluency: comfortable owning a software configuration, reasoning about data and integrations, and learning new tools quickly.[CR1]
- Strong critical-thinking and problem-solving skills, and the communication ability to be credible with both financial institution operators during GTM and implementations and a product/engineering team to convey valuable feedback.
- Comfort being customer-facing and embedded — you like being on-site (physically or virtually) making a rollout succeed.
We should combine the earlier experience bullets into Qualifications as well, maybe as additional items. However we need to avoid duplication. The earlier block includes items like "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor." etc. Those are not in the Qualifications bullet list. So we should add them.
Thus Qualifications section will have a list combining both sets.
Now Pay and Benefits:
"Pay Range and Compensation Package: Base Compensation: $90,000-120,000 + Performance Bonus. Comprehensive Health, Dental, and Vision Insurance. Retirement Plan with Company Contribution of 3%. Paid Time Off and Holidays. Professional Development Opportunities."
We need to create a Pay and Benefits section. Could list each as
- . The base compensation line includes base and bonus. We'll keep as one item.
Now we must remove Equal Opportunity Statement.
Now produce HTML.
Structure:
About Us
...
Job Summary
...
Responsibilities
- ...
...
Qualifications
- ...
...
Pay and Benefits
- Base Compensation: $90,000-120,000 + Performance Bonus.
- Comprehensive Health, Dental, and Vision Insurance.
- Retirement Plan with Company Contribution of 3%.
- Paid Time Off and Holidays.
- Professional Development Opportunities.
Check that we haven't missed any substantive info: The earlier block about "Experience leading a bank servicing..." etc we included in Qualifications. Also the "Lean, continuous-improvement mindset." from that block we need to include as a qualification item.
Also note there is a "[CR1]" after "Technical fluency: comfortable owning a software configuration, reasoning about data and integrations, and learning new tools quickly.[CR1]" We should keep the text but maybe remove the reference marker? It's part of the posting; we should preserve it. It's not boilerplate. We'll keep "[CR1]" as part of the sentence.
Now ensure we didn't include any duplicated lines. The responsibilities list includes "Serve as the trusted rollout lead, training teams, troubleshooting issues, and driving successful go-lives." Good.
Now check for any other sections like "Skills" not present; we won't add.
Now ensure we didn't include any placeholder like "commensurate with experience". Not present.
Now output only HTML fragment.
Let's craft the HTML.
We need to escape any HTML special characters? The text includes apostrophes, em dashes, etc. It's fine as plain text within HTML; we don't need to escape unless they are < or &. There's an ampersand in "SMB and/or". That's okay. There's an ampersand in "UCC". No. There's an ampersand in "RPA, rules engines, or AI-enabled". No. There's an ampersand in "Performance Bonus." No. There's an ampersand in "Health, Dental, and Vision". No. There's an ampersand in "SBA and/or". Actually there is "SMB and/or". That's an ampersand. In HTML, & is special; we need to escape as &. Similarly "and/or" includes &. So we need to
Qualifications
with- items.
Pay and Benefits: maybe combine Pay and Benefits into one section? The instruction says we can have Pay, Benefits, Schedule sections. Since they gave both pay and benefits, we could have
Pay and Benefits
or separate Pay and Benefits. But they said prefer a few substantive sections over many thin ones. So combine into one section "Pay and Benefits". Use- for each benefit item. We need to ensure we don't include placeholder text like "commensurate with experience". Not present. Now extract content precisely. About Us paragraph: "NEWITY is America's source for small business capital. We’re building the latest software that is AI native, creating automated workflows with proprietary data sources delivering industry leading outcomes for our financial institution partners. As part of this enterprise technology suite, we will create a continuous loan-monitoring platform delivering value added outcomes to our partner financial institutions that automates covenant tracking, collateral monitoring, financial-statement collection, exception handling, and borrower engagement across SBA and commercial loan portfolios. Achieving our vision requires more than ambition. It demands resilience, collaboration, accountability, professionalism, and a relentless drive to improve. Our culture moves fast, fosters excellence, and rewards those who lean in. It’s not for everyone, but if you’re energized by challenge, motivated by impact, and ready to grow alongside teammates who share your commitment, there’s no better place to build your career." Job Summary paragraph: "We’re seeking a commercial loan-operations and servicing expert ready to shape how this work gets done. In this forward-deployed role, you’ll engage with our GTM team to support design partnerships and sales, partner with our product team to bring subject matter expertise to the product strategy, embed with each bank, configure the platform to its workflows, lead successful launches, and use customer insights to improve the entire process. Your edge is domain credibility. You understand loan servicing, monitoring, data sources, operational requirements and regulatory realities, and can speak the language of bank operators and leaders. You’re also technically fluent enough to configure software, work with data and integrations, and troubleshoot rollouts. This non-coding role blends subject matter expert, solutions engineer, and GTM influence." Now responsibilities list: The text after "Description & Responsibilities:" includes sentences separated by periods. Let's extract each: - Onboard customers by understanding their monitoring workflows and configuring the platform for SBA and commercial loan portfolios. - Map bank processes—including covenant, collateral, financial-statement, tax, servicing-event, and exception monitoring—to configure and design solutions. - Serve as the trusted rollout lead, training teams, troubleshooting issues, and driving successful go-lives. - Define onboarding data and integration requirements, map system data flows, and partner with engineering on implementation. - Serve as the loan-operations expert, testing the roadmap against servicing, monitoring, operational, and regulatory realities. - Translate customer pain points into prioritized product feedback. - Ensure the platform meets regulated-lending requirements. - Refine positioning, scoping, and implementation playbooks as the GTM strategy matures. - Build scalable onboarding playbooks, configuration templates, and training materials. Now after that there is a block that seems like qualifications/experience: "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor.Familiarity with APIs, file-based interfaces, and servicing-data flows between core systems.Experience with RPA, rules engines, or AI-enabled servicing and monitoring tools.Early-stage experience spanning product, customer, and operations responsibilities.Lean, continuous-improvement mindset." These are likely qualifications or requirements. However there is also a separate "Qualifications:" section with bullet points. We need to decide whether to treat the earlier block as part of Qualifications or maybe as "Requirements". The instruction says we can have sections like Requirements, Qualifications, Skills. We have a Qualifications section later. The earlier block could be considered "Requirements" or "Experience". Since we already have a Qualifications section, we could merge them into Qualifications (makes sense). But we must not duplicate content. The Qualifications section bullet points are: - 7-10 years in loan servicing, portfolio management, special assets, or lending operations, with hands-on SBA, SMB and/or commercial lending exposure. - Working knowledge of loan compliance and SOPs, the commercial loan lifecycle, covenant compliance, regulatory audit preparation and compliance and collateral monitoring (financial statements, insurance, UCC, taxes). - AI curious – you are excited and ready to dive deep into how AI can solve some of the most complex workflows and data processes in financial services – yet you don’t need to be an expert today. - Technical fluency: comfortable owning a software configuration, reasoning about data and integrations, and learning new tools quickly.[CR1] - Strong critical-thinking and problem-solving skills, and the communication ability to be credible with both financial institution operators during GTM and implementations and a product/engineering team to convey valuable feedback. - Comfort being customer-facing and embedded — you like being on-site (physically or virtually) making a rollout succeed. We should combine the earlier experience bullets into Qualifications as well, maybe as additional items. However we need to avoid duplication. The earlier block includes items like "Experience leading a bank servicing or monitoring platform rollout, internally or for a vendor." etc. Those are not in the Qualifications bullet list. So we should add them. Thus Qualifications section will have a list combining both sets. Now Pay and Benefits: "Pay Range and Compensation Package: Base Compensation: $90,000-120,000 + Performance Bonus. Comprehensive Health, Dental, and Vision Insurance. Retirement Plan with Company Contribution of 3%. Paid Time Off and Holidays. Professional Development Opportunities." We need to create a Pay and Benefits section. Could list each as
- . The base compensation line includes base and bonus. We'll keep as one item.
Now we must remove Equal Opportunity Statement.
Now produce HTML.
Structure:
About Us
...
Job Summary
...
Responsibilities
- ... ...
Qualifications
- ... ...
Pay and Benefits
- Base Compensation: $90,000-120,000 + Performance Bonus.
- Comprehensive Health, Dental, and Vision Insurance.
- Retirement Plan with Company Contribution of 3%.
- Paid Time Off and Holidays.
- Professional Development Opportunities.