Mid-Market Vendor Services Manager
Ncontracts · United States · 1 mo ago
RemoteRemoteOTHR$55k–$65k/yrPart-time
We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" and "THE ROLE" etc. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: Who We Are (company overview). That could be "About the role"? Actually "About the role" is generic; but we have "Who We Are" describing company. Could map to "About the role"? Probably better to use "About the role" heading for company overview? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should use those exact headings when appropriate. We have content for responsibilities (What You Do). We have qualifications (Preferred, Required). We have benefits (We Offer). We have compensation range (Compensation Range). We have schedule? Not specified. So we should not include Schedule heading. Pay: we have compensation range, so we can include Pay heading. Benefits: we have benefits list. Skills: maybe Core Competencies could be Skills. Qualifications: maybe Preferred/Required. Responsibilities: What You Do. About the role: maybe Who We Are? Or we could omit About the role if not specific? But we have company overview; could be considered "About the role"? Actually "About the role" usually describes the role, not company. But we have "THE ROLE" heading describing role. Could map that to "About the role". However they said do NOT repeat the job title as a heading. The job title is Mid-Market Vendor Services Manager. We are not using that as heading. So we can use "About the role" heading to contain the description of the role (THE ROLE). Then Responsibilities: What You Do. Qualifications: Preferred and Required. Skills: Core Competencies. Benefits: We Offer. Pay: Compensation Range.
We must not include boilerplate like EEO, Other Duties, etc. Remove those.
We must preserve all substantive information. So we need to include all details from Who We Are, THE ROLE, What You Do (broken into subparts), Core Competencies, Preferred/Required, We Offer benefits list, Compensation Range.
We need to format using
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: Who We Are (company overview). That could be "About the role"? Actually "About the role" is generic; but we have "Who We Are" describing company. Could map to "About the role"? Probably better to use "About the role" heading for company overview? But they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should use those exact headings when appropriate. We have content for responsibilities (What You Do). We have qualifications (Preferred, Required). We have benefits (We Offer). We have compensation range (Compensation Range). We have schedule? Not specified. So we should not include Schedule heading. Pay: we have compensation range, so we can include Pay heading. Benefits: we have benefits list. Skills: maybe Core Competencies could be Skills. Qualifications: maybe Preferred/Required. Responsibilities: What You Do. About the role: maybe Who We Are? Or we could omit About the role if not specific? But we have company overview; could be considered "About the role"? Actually "About the role" usually describes the role, not company. But we have "THE ROLE" heading describing role. Could map that to "About the role". However they said do NOT repeat the job title as a heading. The job title is Mid-Market Vendor Services Manager. We are not using that as heading. So we can use "About the role" heading to contain the description of the role (THE ROLE). Then Responsibilities: What You Do. Qualifications: Preferred and Required. Skills: Core Competencies. Benefits: We Offer. Pay: Compensation Range.
We must not include boilerplate like EEO, Other Duties, etc. Remove those.
We must preserve all substantive information. So we need to include all details from Who We Are, THE ROLE, What You Do (broken into subparts), Core Competencies, Preferred/Required, We Offer benefits list, Compensation Range.
We need to format using for each section heading, then content: use
for prose,
- for lists.
We need to decide how to split content.
Section: About the role (
About the role
) containing the description from "THE ROLE": The Mid-Market Vendor Services Manager is responsible for managing a high-volume portfolio... etc. Also maybe include "Who We Are"? Actually "Who We Are" is company overview; maybe could be part of About the role? But they said About the role heading for e.g. About the role, Responsibilities... So we could put company overview under About the role as well? Might be okay. But we have separate "Who We Are" which is about company. Could we treat that as "About the role"? Might be mixing. However we could also create a separate section like "About the company" but not allowed headings list. So we must either incorporate it into About the role or omit. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use those for section headings. Likely they expect us to use those headings only. So we should map content to those headings. So we need to decide where to put company overview. Could be under About the role (makes sense as context). Or we could omit it if not fitting. But we must preserve ALL substantive information. So we need to include it somewhere. Putting it under About the role is acceptable. Thus About the role section will contain both company overview and role description. Responsibilities: What You Do (list of duties). We'll break into bullet points. Qualifications: Preferred and Required. Could combine into one list with headings? But we need to use
- for any list. We could have two subheadings? Not allowed because only h3 headings. Could we embed paragraphs with bold? Probably okay to have paragraphs describing Preferred and Required. But we need to preserve details. Could do
Preferred: ...
andRequired: ...
. That's okay. Skills: Core Competencies (list). Use ul. Benefits: We Offer list. Pay: Compensation Range. We must not include Schedule. We must not include boilerplate like EEO, Other Duties, etc. We must not include duplicated lines. Let's extract content. Who We Are: "Headquartered in Nashville, Tennessee, Ncontracts leads the industry in integrated risk management and compliance solutions, serving over 5,000 financial institutions nationwide. As an eight-time Inc. 5000 Fastest Growing Companies honoree and consistent year-over-year recipient of "Best Places to Work" awards, we offer a thriving, work environment where career growth and life-work balance go hand in hand. At Ncontracts, you'll join a team of industry experts dedicated to strengthening the financial services sector through innovation and thought leadership. We're seeking creative, collaborative, and self-driven professionals across all areas of our business - from developing cutting-edge solutions to sales, marketing, customer support, and beyond. Join us in our mission to make the financial industry stronger and more resilient, while advancing your career in a supportive, dynamic environment that values your unique skills and perspectives." THE ROLE: "The Mid-Market Vendor Services Manager is responsible for managing a high-volume portfolio of mid-market and other high-value client accounts, ensuring successful delivery of Ncontracts’ Vendor Compliance Services. This role focuses on driving service execution, maximizing product adoption, strengthening client relationships, and supporting overall retention and account health. The ideal candidate brings strong customer-facing experience, exceptional communication skills, and a deep desire to learn and understand vendor management and third-party risk programs." What You Do (list): - Client Relationship Management - Serve as the TPRM primary point of contact for an assigned portfolio of mid-market and other high-value client accounts. - Build strong, trusted relationships with compliance officers, risk managers, and vendor management leads. - Guide clients through their post-sales lifecycle, ensuring clarity on service timelines, deliverables, and ongoing expectations. - Respond to client inquiries and provide guidance on vendor management best practices. - Identify account risks, service gaps, and opportunities for optimization. - Service Delivery Execution - Coordinate the gathering of due diligence documentation with our Vendor Operations Team to meet client expectations. - Assign and oversee work completed by TPRM Specialists, ensuring accuracy and timeliness. - Monitor progress and communicate key updates, vendor issues, and service completion to clients. - Support client vendor services onboarding, annual service cycles, and training initiatives as needed. - Identify opportunities for account growth, including additional tiers, monitoring services, and one-time reviews. - Cross-Functional Collaboration - Partner with internal teams including Implementation, Customer Success, Vendor Operations, Risk Analysts, and Product to support seamless service delivery. - Maintain strong working knowledge of Ncontracts’ TPRM software suite and Vendor Management services. - Recommend process improvements and best practices aligned with regulatory expectations and industry trends. Core Competencies (list): - Strong interpersonal and communication skills, with the ability to engage confidently and professionally across a range of client stakeholders. - Exceptional customer service mindset with the ability to manage complex situations professionally and efficiently. - Highly organized, detail-oriented, and able to manage multiple priorities in a fast-paced environment. - Strong problem-solving skills and the ability to influence cross-functional teams. - Ability to deliver product training, explain system functionality, and stay current on product updates. - Aptitude for identifying cross-sell and up-sell opportunities and routing them appropriately. Preferred: - Demonstrated experience working with compliance, risk, or operational stakeholders. - Bachelor’s degree or equivalent experience in a related field. - Professional certifications in Vendor Management, Risk Management, or related fields. Required: - 3+ years of experience in customer success, account management, or a related client-facing role. - Experience managing multiple client accounts or projects simultaneously. - Comfort operating in a fast-paced, deadline-driven environment. We Offer (benefits list): - All Regular Full-time Team Members - A fun, fast-paced work environment - Responsible PTO Plan that meets or exceeds state and local medical and family leave laws - 11 paid holidays - Community and social events to keep you connected and engaged - Mental Health Benefits - Medical, Dental and Vision insurance - Company-paid Group Life Insurance, Short- and Long-Term Disability - Flexible Spending Account & Health Savings Account - Aflac Benefits – Critical Illness, Cancer Protection, & Hospital Choice - Pet Insurance - 401 (k) with company match with eligibility on Day 1 of employment - 2 Paid Volunteer Time Off Days - And much more! - Part-Time and Contractor positions are not eligible for company benefits, including paid time off, health insurance, and other employee benefit programs. - Full-time temporary employees are eligible for certain group benefits after a waiting period; specific eligibility timing will be provided at the time of offer. We need to preserve all that. However note that the first bullet "All Regular Full-time Team Members" is a heading; we could keep as a paragraph then list. Compensation Range: $55K - $65K. Now produce HTML. We must not include any markdown code fences. Just raw HTML. We'll structure:About the role
... company overview + role description ...
Responsibilities
- ... maybe we need to nest subpoints? Could use nested ul? The instruction: use
- for any list of duties/requirements/benefits. It didn't forbid nested lists. We can do nested lists for sub-bullets. That's fine.
We'll produce:
- Client Relationship Management
- Serve as the TPRM primary point of contact... ...
...
- Client Relationship Management
Qualifications
Preferred: ...
Required: ...
Skills
- ...
Benefits
All Regular Full-time Team Members:
- A fun, fast-paced work environment ...
Part-Time and Contractor positions are not eligible for company benefits, including paid time off, health insurance, and other employee benefit programs.
Full-time temporary employees are eligible for certain group benefits after a waiting period; specific eligibility timing will be provided at the time of offer.
Pay
Compensation Range: $55K - $65K
Make sure no extra whitespace issues. Let's craft the content precisely. Company overview + role description combined: "Headquartered in Nashville, Tennessee, Ncontracts leads the industry in integrated risk management and compliance solutions, serving over 5,000 financial institutions nationwide. As an eight-time Inc. 5000 Fastest Growing Companies honoree and consistent year-over-year recipient of "Best Places to Work" awards, we offer a thriving work environment where career growth and life-work balance go hand in hand. At Ncontracts, you'll join a team of industry experts dedicated to strengthening the financial services sector through innovation and thought - for any list of duties/requirements/benefits. It didn't forbid nested lists. We can do nested lists for sub-bullets. That's fine.
We'll produce:
- ... maybe we need to nest subpoints? Could use nested ul? The instruction: use
- for any list. We could have two subheadings? Not allowed because only h3 headings. Could we embed paragraphs with bold? Probably okay to have paragraphs describing Preferred and Required. But we need to preserve details. Could do