Support Account Manager

We need to output HTML fragment with sections: About the role (already present), Responsibilities (What You’ll Do), Requirements/Qualifications (What You Should Bring), Benefits (maybe mention benefits), Pay (salary range), maybe Schedule (full-time). Also include About Us? 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 (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. We need to include sections for which there is real content. We have: - About Us: description of company. Should we include? The instruction says use headings like About the role, Responsibilities, etc. It didn't list About Us as a heading example, but we could include if we want. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings; we could still include other headings? Probably they want only those headings. The About Us is not listed; maybe we should omit it because it's not required? But we need to preserve ALL substantive information. However we could incorporate About Us into a

without a heading? The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for sections. The About Us could be a

without heading. However they said "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." So we can have other headings if needed, but better to stick to given ones. We have content: - About The Role: description. That's a heading "About the role". We'll put

About the role

then

with that paragraph. - What You’ll Do: responsibilities. That's a heading "Responsibilities". We'll list bullet points. - What You Should Bring: qualifications/requirements/skills. Could be split into Requirements and Skills? The posting includes: Demonstrated experience..., Proven ability..., Collaborative..., Skilled..., Excellent communication..., Bachelor’s..., Empathy ownership... This is a mix. We could put under "Requirements" or "Qualifications". Since they said we can have Requirements, Qualifications, Skills sections. We could combine into one section "Requirements" with

• . Or we could split: Requirements (experience, ability to manage priorities, collaborative attitude), Skills (SLA management, communication, problem solving), Qualifications (degree). But to avoid many thin sections, we can combine into one "Requirements" section with all items. - Benefits: The posting mentions "Kyriba also offers a comprehensive range of health, welfare and wellbeing benefits designed to support both your professional and personal life." That's substantive. So we can have Benefits section with

  describing that. - Pay: The posting includes salary range: "$80,400.00 - $101,700.00 based on a full-time schedule." Also mentions variable compensation and long-term incentive. So we have Pay section. - Schedule: The posting mentions full-time schedule. So we could have Schedule section with "Full-time". However they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time schedule, so we can include Schedule. But we need to avoid filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, accommodation request, privacy policy, etc. Also remove duplicated lines. We need to preserve all substantive information: About Us description, About The Role, What You’ll Do, What You Should Bring, Values? The values section: "Our Values Guide Everything We Do" with bullet points. That's substantive. Should we include? The instruction didn't list Values as a heading example, but we could include as a section maybe "Values". However they said prefer a few substantive sections over many thin ones. Values could be its own section. But we could incorporate values into About Us or another section? Might be better to have a "Values" section. However they didn't forbid other headings; they just gave examples. I'd include a Values section. But we need to check if we should include About Us. It's substantive. Could be a section "About Us". Not in examples but we can include. But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the expected headings; maybe they want only those. However they didn't forbid others, but they said "Prefer a few substantive sections over many thin ones." If we add many sections like About Us, Values, etc., that could be many thin ones. But we already have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's 6 sections. Adding About Us and Values would be 8. Might be okay. But we need to ensure we don't create sections with filler. All have content. Let's decide to include: - About Us (maybe as

  About Us

  ) - About the role - Responsibilities - Requirements (or Qualifications) - Benefits - Pay - Schedule - Values (optional) But we need to avoid duplication: The "About Us" paragraph is at start. The "About The Role" is separate. We must not repeat job title as heading. We must not include Job ID etc. We need to output only HTML fragment. Let's extract content precisely. About Us paragraph: "Dream Big. Go Beyond. Be Unstoppable. About Us Kyriba is a global fintech leader empowering CFOs and finance teams with cloud-based treasury, payments, risk management and working capital solutions. We serve 3,000+ customers worldwide, managing $15 trillion in payments annually and helping businesses optimize liquidity performance across the enterprise. We're on a mission to become the most sought-after cloud technology company globally. We think big, innovate relentlessly, and challenge the status quo every day. If you are a problem-solver who’s ready to push boundaries and achieve more than you thought possible-you'll find an exceptional career within an extraordinary business." Note: There's a repeated "Dream Big. Go Beyond. Be Unstoppable." at start; that's like a tagline. We'll keep it as part of About Us. About The Role paragraph: "As a Support Account Manager (SAM), you will be the trusted advocate for our Premium and Platinum customers for products such as deal capture, financial transactions, loans, debt ensuring a seamless support experience, proactive engagement, and consistent customer satisfaction. Your work will drive exceptional outcomes for our clients, supporting their success and loyalty while advancing Kyriba's customer-centric mission." What You’ll Do (responsibilities) bullet points: - Act as the primary support liaison for assigned Premium/Platinum accounts, reflecting professionalism and customer-centricity in every interaction. - Own the customer support experience end-to-end, including SLA monitoring, case workflow, and renewal support. - Partner closely with Account Managers, Support Managers, and Technical teams to ensure seamless customer experience and effective issue resolution. - Anticipate risks, proactively address recurring issues, and identify opportunities for product adoption or service improvement. - Represent customer needs internally, escalating and relaying feedback to product and leadership teams. - Deliver regular executive dashboards, case summaries, and health reports to both customers and internal stakeholders. What You Should Bring (qualifications/skills) bullet points: - Demonstrated experience in customer success, account management, or support roles within SaaS or technology environments. - Proven ability to manage multiple priorities, with strong organizational and time management skills. - Collaborative, customer-first attitude with passion for delivering exceptional service experiences. - Skilled in SLA management, escalation handling, and translating technical data into business insights. - Excellent communication, relationship building, and problem solving skills. - Bachelor’s or Graduate degree in Business, Finance, Computer Science, or related field, or equivalent experience. - Empathy ownership, accountability, and a continuous improvement mindset. Values section: list of values with descriptions. Values: - Think Big & Constantly Innovate: We have the confidence to think big, embrace change, challenge the status quo, and continuously evolve - incorporating new technologies and driving industry progress. - Put our Customers’ Outcomes First: We are passionate about delivering the highest value for our customers and supporting them with end-to-end care throughout their journey with us. - Act with Integrity: Integrity is at the heart of everything we do. We take personal responsibility for our actions, own our decisions, and honour each other’s contributions. We empower each other through honesty, respect, trust and transparency. - Work as One Team: We are driven by our common goals and share in each other’s successes and failures, learning and working together as a team where everyone can bring their best selves. - Strive for Excellence while Having Fun: We enjoy tackling new challenges together, and revel in continuous improvement as we deliver, with ultimate professionalism, the very best for our customers, while exceeding our own expectations. Benefits: "Kyriba also offers a comprehensive range of health, welfare and wellbeing benefits designed to support both your professional and personal life." Pay: "At Kyriba we value pay transparency and fairness. For new hires, the annual base salary range for this role is $80,400.00 - $101,700.00 based on a full-time schedule. Salary can progress beyond this range through sustained performance and demonstrated success in the role. In addition to base pay, this position may be eligible for variable compensation (eg. performance bonus or commission-based plan) and a long-term incentive. The final package will be determined by factors such as skills, experience and qualifications." Schedule: The phrase "based on a full-time schedule" indicates schedule is full-time. Could also mention full-time. We could combine Pay and Schedule: but they said prefer few sections; we could have Pay section that includes schedule info. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule (full-time). We could include Schedule section with just "Full-time". Or we could incorporate schedule into Pay section. To avoid many thin sections, maybe we include Pay section that mentions base salary range and full-time schedule, and also variable compensation. Then we don't need separate Schedule section. That would be fewer sections. Thus sections: About Us, About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay, Values. That's 7 sections. We need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML. We'll use

  for each heading. Inside each section, use

  for prose,

  • for lists. For About Us: we have a few sentences; we can put in

    . For About the role:

    . For Responsibilities:

    • each. For Requirements: we could call it "Requirements". Use
      • each. For Benefits:

        . For Pay: