Senior Onboarding Manager

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have compensation info: $135,000 - $155,000 (Base and Bonus). That's Pay. Also location remote, USA maybe schedule? Not given. Benefits? Not given. So we include Pay section only if present. Also maybe Benefits not present. Schedule not present. So we will have sections: About the role (maybe from description), Responsibilities (What You'll Do), Requirements (What You Bring), Qualifications? Might overlap. But we need to follow instruction: use headings only when posting has real, specific content. We have content for About the role (the introductory paragraph). Responsibilities (What You'll Do). Requirements (What You Bring). Possibly Qualifications could be same as Requirements but we should not duplicate. Could combine Requirements and Qualifications? But we need separate headings only if content. We could treat "What You Bring" as Requirements. Qualifications maybe not separate. Skills maybe from bullet list? There's a list of skills in What You Bring: strong consultative, etc. Could put under Skills. But we already have Requirements. Might be okay to have Requirements and Skills separate if we can extract skill list. Let's parse. Posting includes: Location: Remote, USA Compensation: $135,000 - $155,000 (Base and Bonus) As a Sr. Onboarding Manager at Eltropy, you will be part of a high-impact team guiding financial institutions through the onboarding and adoption of our AI-powered communication platform. We are looking for a Sr. Onboarding Manager with 4+ years of experience delivering SaaS or technical solutions, strong consultative and discovery skills, a track record of building trusted relationships with customer stakeholders, and the ability to independently own complex, multi-product deployments with minimal oversight. In this role, you will lead customer onboarding projects end-to-end from post-sale discovery and design through configuration, deployment, and go-live, implementing integrations with core banking, lending, and other financial services systems. You'll act as a strategic advisor to your customers, translating business goals into technical implementation plans, while mentoring less experienced team members and building a strong foundation for enterprise software delivery leadership. What You'll Do Consultative Discovery & Solution Design - Lead post-sale discovery sessions... - Translate discovery findings... - Facilitate alignment conversations... - Identify risks or gaps... Implementation & Deployment - Own onboarding... - Lead configuration and testing... - Drive complex, multi-system deployments... - Troubleshoot implementation issues... - Apply deployment experience... Relationship Management - Build trusted, long-term relationships... - Serve as a strategic point of contact... - Manage expectations... Platform & Domain Expertise - Maintain deep expertise... - Apply strong working knowledge... Customer Training & Enablement - Lead delivery of customer training... - Build and customize training resources... - Use tools like WalkMe... Be the Voice of the Customer - Advocate for customer needs... - Identify and communicate product... Testing & Quality Assurance - Lead testing of new releases... - Report bugs, provide feedback... What You Bring 5+ years of experience implementing or delivering enterprise SaaS solutions, with direct deployment experience Demonstrated experience running consultative discovery and solution design conversations with customer stakeholders Strong track record of building and sustaining customer relationships through complex, multi-stakeholder projects High degree of technical aptitude, with comfort owning ambiguous or evolving requirements Proven ability to manage customer timelines, dependencies, and competing priorities with minimal oversight Passion for software technology and project management Strong customer empathy and communication skills, including with senior stakeholders Problem-solving mindset with strong attention to detail Bias for action — comfortable rolling up your sleeves on configuration, testing, and training while also operating strategically Eagerness to deepen expertise in SaaS, AI, and the financial technology landscape Strong interest in community banking, credit unions, and fintech Bonus (Not Required) Native Spanish fluency Familiarity with concepts like APIs, DNS, VPN, and sFTP Why Join Eltropy? - Be part of a fast-growing, mission-driven fintech company - Receive mentorship from experienced technical project managers - Develop valuable skills in enterprise SaaS, customer success, and implementation - Work with leading community financial institutions to bring modern solutions to real people About Eltropy Www.eltropy.com Eltropy is on a mission to disrupt the way people access financial services. Eltropy enables financial institutions to digitally engage in a secure and compliant way. Using our world-class digital communications platform, community financial institutions can improve operations, engagement and productivity. CFIs (Community Banks and Credit Unions) use Eltropy to communicate with consumers via Text, Video, Secure Chat, co-browsing, screen sharing and chatbot technology — all integrated in a single platform bolstered by AI, skill-based routing and other contact center capabilities. Eltropy Values Customers are our North Star No Fear - Tell the truth Team of Owners We need to remove boilerplate: EEO etc. We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Skills?, Benefits?, Pay, Schedule. We have Pay: compensation. We have About the role: the introductory paragraph(s) before What You'll Do. Responsibilities: What You'll Do (list of duties). Could be multiple subheadings but we just need a

• list. Requirements: What You Bring (list of qualifications/experience). Could be
  • . Skills: maybe we could extract skill set from What You Bring (consultative, technical aptitude, etc.) but that overlaps. Might be better to have Skills section separate if we can list skills like "consultative and discovery skills", "building trusted relationships", "technical aptitude", "project management", "communication", "problem-solving", "bias for action", "interest in SaaS, AI, fintech". But we already have those in Requirements. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But headings are predefined; we can choose to include only those with content. Could include Requirements and not Skills. Or include Skills and not Requirements. Which is more appropriate? The posting has explicit "What You Bring" which is requirements/experience. That's more like Requirements. Skills are also there but could be considered part of Requirements. I'd choose Requirements. Thus sections: About the role, Responsibilities, Requirements, Pay. We need to ensure we don't repeat job title as heading. Good. We need to not include Job ID etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from What You'll Do and What You Bring, and the compensation line, and the About Eltropy description (maybe part of About the role). Also include "Why Join Eltropy?" maybe could be Benefits? But it's not benefits; it's reasons to join. Could be considered Benefits? The instruction says include Benefits section only if posting actually states them. "Why Join Eltropy?" lists benefits like mentorship, develop valuable skills, work with leading institutions. That's akin to benefits. Could treat as Benefits section. However the instruction: Benefits, Pay, Schedule are headings we can use if posting actually states them. The "Why Join Eltropy?" is basically benefits/perks. So we should include a Benefits section with those bullet points. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We must not include Schedule (not present). Good. Now we need to format. We need

    for each section heading. Inside each section, we put

    for prose,

    • for lists. We need to preserve all substantive information: include the location? Location is remote, USA. Could be included in About the role paragraph? Might be better to include as a short

      under About the role? The location is not a heading; we can fold minor metadata into a short

      or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So location is minor metadata; we can include a short

      maybe after the About the role heading. Similarly compensation is Pay section. Now let's craft. About the role heading:

      About the role

      Then a

      containing the introductory paragraph(s): "As a Sr. Onboarding Manager at Eltropy, you will be part of a high-impact team guiding financial institutions through the onboarding and adoption of our AI-powered communication platform. We are looking for a Sr. Onboarding Manager with 4+ years of experience delivering SaaS or technical solutions, strong consultative and discovery skills, a track record of building trusted relationships with customer stakeholders, and the ability to independently own complex, multi-product deployments with minimal oversight. In this role, you will lead customer onboarding projects end-to-end from post-sale discovery and design through configuration, deployment, and go-live, implementing integrations with core banking, lending, and other financial services systems. You'll act as a strategic advisor to your customers, translating business goals into technical implementation plans, while mentoring less experienced team members and building a strong foundation for enterprise software delivery leadership." Also maybe include location as a short

      : "

      Location: Remote, USA

      " but we could incorporate into same paragraph. Better separate short

      . Now Responsibilities:

      Responsibilities

      then a
      with each bullet from What You'll Do. Need to capture all bullet points grouped under subheadings? The posting has subheadings like Consultative Discovery & Solution Design, Implementation & Deployment, Relationship Management, Platform & Domain Expertise, Customer Training & Enablement, Be the Voice of the Customer, Testing & Quality Assurance. We could either keep them as separate
      • items, but we lose the subheading context. However we could embed subheading as part of
      • text. Eg "
      • Consultative Discovery & Solution Design: Lead post-sale discovery sessions ..." That preserves info. We need to include all bullet points. Let's list them: Consultative Discovery & Solution Design - Lead post-sale discovery sessions with customer stakeholders to understand business goals, current workflows, and success criteria - Translate discovery findings into a tailored implementation and solution design, aligning configuration decisions to the customer's operational reality - Facilitate alignment conversations across customer teams (operations, IT, compliance) to drive consensus on scope and timeline - Identify risks or gaps in requirements early and design around them before implementation begins Implementation & Deployment - Own onboarding of new customers onto the Eltropy platform, including our AI-powered Voice and Digital Agents - Lead configuration and testing of SaaS instances and communication flows across voice, video, text messaging, and chat channels - Drive complex, multi-system deployments, coordinating tasks, schedules, and stakeholders to ensure timely go-lives with quality - Troubleshoot implementation issues independently, partnering with technical teams as needed on escalations - Apply deployment experience across core banking, lending, collections, telephony, and other financial services systems to anticipate integration challenges Relationship Management - Build trusted, long-term relationships with customer stakeholders - Serve as a strategic point of contact, balancing customer advocacy with Eltropy's delivery standards during the onboarding phase of the customers journey - Manage expectations proactively through clear, consistent communication on progress, risk, and timeline Platform & Domain Expertise - Maintain deep expertise on Eltropy's platform capabilities including Voice, Video, Text, Secure Chat, Co-browsing, AI Assistants, AI Agents, and Conversation Intelligence - Apply strong working knowledge of financial services processes for lending, new accounts, collections, and consumer engagement to inform solution design Customer Training & Enablement - Lead delivery of customer training using AI-generated video, virtual sessions, documentation, and tutorials - Build and