Sr. Implementation Manager - Grants

We need to output HTML fragment with sections for headings where there is real content. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We must not include Job ID etc. Remove boilerplate like EEO, accessibility, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Keep substantive info. We need to parse the posting. Sections: - About the role: The first paragraph: "The Opportunity We are seeking a Senior Implementation Manager, independently motivated and ready to make our high-functioning Implementation Team even better. As a Sr. Implementation Manager, you will be our new customers’ primary contact, overseeing the onboarding process from end-to-end. This is a multi-faceted set of responsibilities including requirements gathering, configuration of our SaaS products to meet those requirements, carrying out basic project management activities, and ensuring a smooth transition from sales to adoption. You will collaborate closely with cross-functional teams, including sales, product management, customer success, and technical support, to deliver exceptional client experiences and drive customer satisfaction." That's about the role. - Responsibilities: The "What You'll Do" section with bullet points: Client Onboarding, Project Management, Product Configuration, Cross-Functional Collaboration, Training and Documentation, Issue Resolution, Continuous Improvement. Each has description. We'll put as

• each bullet. - Requirements/Qualifications/Skills: The "What You Bring" section includes education, experience, skills. Could split into Requirements (education, experience) and Qualifications/Skills. But we can combine into one section maybe "Requirements". However guidelines: Use headings only when posting has real specific content. We have content for Requirements (Bachelor's degree..., 5+ years..., Strong understanding..., Excellent communication..., Technical aptitude..., Strong problem-solving..., Design and documentation..., Experience with CRM..., Familiarity with Jira...). Also there are "plus" items. Could treat as Requirements and Skills. But we can put all under "Requirements". Or separate "Qualifications" and "Skills". Let's decide: Use "Requirements" for education and experience, "Skills" for technical aptitude, communication, problem-solving, etc. But we need to avoid thin sections. Might be okay to have both. But we also have "Location & Travel" and "AI Mindset at Euna Solutions", "Life at Euna Solutions", "About Euna Solutions". Those could be sections like "About the Company" maybe. But headings limited to list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add other headings. So we must fit content into those allowed headings. If content doesn't match, we may need to omit or incorporate into existing sections if relevant. For example, "Location & Travel" could go under "Schedule"? Not really. But we could treat location as part of "Schedule"? Not ideal. However guidelines: include a section ONLY when posting has real specific content for it — never emit a heading followed by filler/placeholder text. We must not create sections like Benefits, Pay, Schedule unless posting actually states them. The posting does not mention benefits, pay, schedule specifics beyond hybrid schedule (3 days/week in office). That's schedule info. So we could include a Schedule section with that detail. Benefits not mentioned, so omit Benefits and Pay. Also we could include Qualifications maybe for education/experience, Skills for technical abilities. Let's map: - About the role: intro paragraph. - Responsibilities: What You'll Do bullet list. - Qualifications: Bachelor's degree, 5+ years experience, strong understanding of software implementation processes, excellent communication/interpersonal skills, ability to lead workshop, etc. Could also include "Strong problem-solving and analytical skills". Might be better as Skills. - Skills: Technical aptitude, Excel, ability to author reports (SSRS/PowerBI), experience with CRM/ERP/GovTech, familiarity with Jira etc. - Schedule: Location & Travel: hybrid 3 days/week in Atlanta office (Tue, Wed, Thu). Also mention standard hours on those days, remaining days depend on role/manager. Also mention Eunafier Days etc. That's more about culture but could be schedule/benefits? Eunafier Days is extra day off twice a year - that's a benefit. Actually that is a benefit (extra day). Philanthropy Time (up to eight hours a year). Those are benefits. So we could include Benefits section covering Eunafier Days, Philanthropy Time, maybe also mention hybrid work? But hybrid is schedule. We'll put schedule for hybrid days, and benefits for extra time off and philanthropy. But we must not invent details; we have those specifics. Thus: - Schedule: hybrid 3 days/week in Atlanta office (Tuesday, Wednesday & Thursday); standard hours on those days; remaining days flexible per role/manager. - Benefits: Eunafier Days (extra day tacked onto a long weekend twice a year); Philanthropy Time (up to eight hours a year to spend on causes); Engagement Committee philanthropic activities; maybe also mention "Room to grow" (development budget, mentorship). That's more like development benefits. Could include. But we must avoid filler. We have specifics. Now also "About Euna Solutions" description could go under "About the role"? Not really. Could be omitted as not required headings. But we might include as part of "About the role"? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; we could also use other headings but they gave examples. Safer to stick to those. Thus we need to fit all content into those headings. We can put company description under "About the role"? Might be odd but could be included as part of role context. However "About the role" is about the role, not company. But we could still include a brief description of company as part of role context. Might be acceptable. Alternatively we could omit company description if not fitting headings. But we must preserve ALL substantive information; cannot omit. So we need to include it somewhere. Perhaps we can add a section "About the role" and include both role description and company overview. That would preserve info. Thus:

  About the role

  ... role description ...

  About Euna Solutions: ...

  That seems okay. Now responsibilities bullet list. Qualifications: education + experience + core competencies. Skills: technical abilities, tools. Schedule: hybrid details. Benefits: Eunafier Days, Philanthropy Time, Engagement Committee, Philanthropy Time, Room to grow (development budget, mentorship). Also maybe mention "AI Mindset at Euna Solutions" as benefit? Could be under benefits as encouragement to use AI. But that's more culture. Could include under Benefits as "AI Mindset: encouragement to leverage AI tools". We'll include. Now ensure we don't repeat job title. No mention of Job ID. Now produce HTML fragment. Let's craft. We'll need to escape any HTML special characters? Not needed. Structure:

  About the role

  The Opportunity We are seeking a Senior Implementation Manager, independently motivated and ready to make our high-functioning Implementation Team even better. As a Sr. Implementation Manager, you will be our new customers’ primary contact, overseeing the onboarding process from end-to-end. This is a multi-faceted set of responsibilities including requirements gathering, configuration of our SaaS products to meet those requirements, carrying out basic project management activities, and ensuring a smooth transition from sales to adoption. You will collaborate closely with cross-functional teams, including sales, product management, customer success, and technical support, to deliver exceptional client experiences and drive customer satisfaction.

  About Euna Solutions: Euna Solutions® is the leading provider of purpose-built, cloud-based software designed to streamline procurement, budgeting, payments, and grants management for public sector and government organizations. Euna's AI-powered features and intelligent automation help organizations make better-informed decisions, ensure compliance, empower collaboration, and reduce administrative burden. Euna's full-cycle financial suite supports more than 3,600 organizations across North America in building trust, enabling transparency, and driving positive community impact. Recognized on Government Technology's GovTech 100 list, Euna Solutions is committed to advancing public sector innovation.

  Responsibilities

  • Client Onboarding: Serve as the primary point of contact for clients during the onboarding process. Conduct kickoff meetings, gather business processes and resulting requirements, and provide expert guidance on best practices for implementing and configuring our SaaS products to meet their unique needs.
  • Project Management: Carry out basic project management activities, notably ensuring the work you are delivering falls within the scope of the implementation, that there are well planned & reliable communications, that you continuously evaluate points of risk and opportunity, and providing customer advice and assistance with their change management.
  • Product Configuration: Customize system settings, workflows, and integrations to align with client requirements while using out-of-the-box functionality to minimize customizations whenever possible. Depending on the product you may also: Work extensively in Excel to prepare data and carry out initial data load; Write simple scripts; Author ad hoc reports on behalf of the customer.
  • Cross-Functional Collaboration: Work closely with sales, product management, customer success, and technical support teams to ensure a seamless transition from the sales cycle to adoption. Foster strong relationships with internal stakeholders, using effective communication to influence product design and customer life-cycle to deliver a coherent, high quality, client experience.
  • Training and Documentation: Engage the project team to develop and deliver comprehensive training sessions to educate clients on the features and functionalities of our SaaS products. Create and maintain implementation documentation, user guides, and knowledge base articles to support clients throughout the onboarding process ensuring the customer’s complete adoption of their product.
  • Issue Resolution: Identify and address implementation challenges, working closely with internal teams to troubleshoot and resolve issues promptly. Escalate complex problems to appropriate departments and provide timely updates to clients, ensuring their concerns are addressed effectively.
  • Continuous Improvement: Actively contributes to the enhancement of implementation processes and methodologies.

  Qualifications

  • Bachelor's degree in a relevant field (e.g., Business, Computer Science, Information Systems) or equivalent practical experience.
  • 5+ years of experience in a client-facing implementation role, preferably in the SaaS industry.
  • Strong understanding of software implementation processes, methodologies, and best practices.
  • Excellent communication and interpersonal skills, with the ability to build rapport, effectively collaborate with clients and internal teams, and be able to take the lead in a workshop environment.
  • Strong problem-solving and analytical skills – high comfort level with Excel is a plus.

  Skills

  • Technical aptitude with the ability to quickly learn and navigate new software applications, and the ability to identify and address implementation challenges effectively.
  • Design and documentation of reports generated from relational databases – ability to author reports (SSRS or PowerBI) a significant plus.
  • Experience with CRM, ERP, or other enterprise software implementations, particularly GovTech, is a plus.
  • Familiarity with Jira, Cloud Coach, Autotask, Asana, or similar software for project tracking and time management is a plus.

  Schedule

  • Hybrid position: 3 days/week in the Atlanta, GA office (Tuesday, Wednesday & Thursday) with standard hours on those days.
  • Remaining work days are flexible depending on role and manager.