Partner Account Manager - Nebraska

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include sections only when posting has real specific content. Must preserve all substantive info. No invented or summarized away detail. No filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Compensation details (OTE $133k base $66.5k variable $66.5k). So we can have Pay section. Benefits are listed: 401(k) match, health plans, dental, vision, time off, parental leave, Addition Wealth, Lyra, Carrot, Candidly, monthly WFH stipend, quarterly lifestyle stipend, team-building experiences, awards etc. So Benefits section. Schedule? Not mentioned explicitly. There's travel: Ability to be In the field 3 days/week. That's schedule/travel. Could be considered Schedule? Might be better to include a "Travel" or "Schedule" section if we have specifics. The instruction says include Schedule section only if posting actually states them. It does mention travel 3 days/week. That's schedule-related. Could put under a "Schedule" heading with that detail. Or we could incorporate travel under Responsibilities? Probably better to have a Schedule section with that detail. We need sections: About the role (the paragraph after "About The Role"), Responsibilities (the bullet list under "What You Get To Do Every Day"), Requirements/Qualifications/Skills (the bullet list under "What you bring to the role" plus maybe "Travel" etc). Could separate into Requirements and Skills? The instruction says use headings for those categories if content exists. We have a list of qualifications: experience, proven track record, passionate, dynamic, resilient, solutions-oriented, communication, tech-savvy, growth mindset, coachable, travel. Those could be under Requirements or Skills. We could combine into a single "Requirements" section with

  . Or split into Requirements and Skills if we want. But better to keep few substantive sections. Could have About the role, Responsibilities, Requirements (including skills and travel), Benefits, Pay. That seems sufficient. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: equal opportunity, accommodation, fraud warning, etc. Also remove awards list? Awards are substantive? They are accolades; could be included maybe under a section like "Awards" but not in allowed headings list. The allowed headings are limited to those; we could omit awards as not required. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit awards. Also remove mission paragraph at start? That's substantive about company mission; could be included in About the role? Actually About the role section should be about the role, not company mission. The opening paragraph about Human Interest mission is company overview; could be included maybe as a brief intro before About the role? But we have no heading for company overview. Could we include it as a

  before the first heading? The instruction: Output ONLY the HTML fragment. It didn't forbid a leading paragraph without heading. It said use

  for section headings (e.g. About the role, Responsibilities...). It didn't say we must have headings only; we can have prose outside headings. Probably okay to include a brief intro as

  . But we must preserve ALL substantive information; the mission statement is substantive. So include it as a

  before the first heading. Similarly, the "Our operating principles" list is substantive; could be included maybe as a section? Not in allowed headings; but we could include as a

  or

  without heading? Probably better to include as a

  summarizing? But we cannot invent or summarize away detail; we must preserve all substantive info. The operating principles list is detailed; we could include as an

  without a heading? The instruction says use
  • for any list of duties/requirements/benefits. It didn't forbid using lists for other things, but we should follow semantics. Could include as a
    under a heading like "Operating Principles" but that's not in allowed headings list. However the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive? It says use

    for section headings (e.g. ...). Likely they expect only those headings. Safer to restrict to those headings. So we may need to omit operating principles list or incorporate into About the role? Could embed as a

    describing that we have operating principles that include customer obsession, long-term orientation, etc. But that would be summarizing, losing detail. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot drop details. However we could include them as a

    without a heading? That might be okay because it's not a section heading; it's just a list. The instruction didn't forbid lists outside headings. It said use
    • for any list of duties/requirements/benefits. It didn't say you cannot use lists for other things. But to be safe, we could include the operating principles as a
      without a heading, but that might be considered a section without heading. Might be okay. Similarly awards list could be included as a
      without heading. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe we should keep sections limited to those headings and put other info as prose paragraphs. We need to decide: Is it acceptable to omit operating principles and awards? That would be losing substantive info, violating "Preserve ALL substantive information". So we must include them somehow. We could include them as part of a

      paragraph that lists them in prose, preserving the detail (though not as bullet list). That would still preserve the information (just not as list). The instruction about using

      • for any list of duties/requirements/benefits suggests that if we have a list, we should use ul/li. But operating principles is a list; we could use ul/li. It's not duties/requirements/benefits but still a list. The instruction didn't restrict to only those categories; it's just an example. So we can use ul/li for any list. So we can include a
        for operating principles and awards without a heading? Might be okay but then we have a list without a heading; maybe we should give it a heading like "Operating Principles" but that's not in the allowed list. However the instruction says "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could add other headings if needed, but they said prefer few substantive sections. Adding extra headings for operating principles and awards would increase sections. Could combine them into one section like "Company Culture" with sublists? But that would be a heading not in examples. Might be okay. Given the ambiguity, I think safest is to follow the instruction strictly: only use those headings for sections. For other info, we can embed in paragraphs (

        ) without headings. That way we preserve info but not as lists. However the instruction says use

        • for any list of duties/requirements/benefits. It doesn't say we must use lists for other lists; we could still use paragraphs. But to preserve detail, we could convert list items into sentences separated by commas or semicolons within a paragraph. That would preserve the info albeit not as list. That might be acceptable. Let's do that: For operating principles, we can write a paragraph: "Our operating principles include: Customer obsession: we're all about creating amazing experiences for our customers... Long-Term Orientation: we're not just playing for today... Autonomous and Accountable Teams: we trust our team members... An Escalating Bar for Talent and Performance... Fundamental Optimism: we see the glass as half full..." That preserves the detail. Similarly awards: we can list them in a paragraph. Thus we will have sections: About the role (maybe after intro paragraph), Responsibilities, Requirements (including skills and travel), Benefits, Pay. Possibly also a short intro paragraph about company mission before About the role. We must not repeat job title as heading. Job title is Partner Account Manager. We'll not use that as heading. Now craft HTML. Start with a

          for company mission overview: "Human Interest is on a mission to ensure that people in all lines of work have access to retirement benefits. More than half of all working Americans are not saving enough for their future. Too often, it’s because they are employed by a company that doesn’t offer a retirement plan. Human Interest is changing that by making it affordable and accessible for small and medium-sized businesses to offer employees a path to financial independence through retirement savings. We’re a high-growth fintech company changing the retirement industry. We are backed by a number of investors. This includes funding from Marshall Wace and Baillie Gifford, as well as top investors such as BlackRock, TPG (The Rise Fund), SoftBank, Glynn Capital, NewView Capital, USVP, Wing, Uncork, and more." Then

          About the role

          with paragraph: "Our Partnership Program is a key initiative for the company. The Partner Account Manager’s primary duty is to engage, build and develop Human Interest’s key accounts and growth opportunities. We're looking for a forward-thinking, meticulously organized, and self-motivated sales professional who can thrive in a fast-paced environment. You'll accelerate our partner relationships to help us exponentially reach more small and medium businesses across the United States, which is essential to our growth. This role requires someone who is proactive, creative, and can exercise their own discretion and judgment to create their own solutions when needed." Then

          Responsibilities

          with
          • items from "What You Get To Do Every Day": list each bullet. Bullets: - Develop, build, and amplify referral relationships with tech partners, human capital management partners, benefit brokers, CPA's and financial advisors in the SMB space - Create and build strategic referral networks and partnerships focused on lead generation and new partnership opportunities - Proactively identify and resolve emerging issues and offer solutions by working cross-functionally with Sales, Product, Marketing, Legal and Finance - Collaborate with Partner Marketing to innovate and execute unique initiatives to promote partner sales (e.g, educational events, email, webinars, etc.) - Work with partners to establish business goals and performance metrics (e.g, depth of sales pipeline and revenue generation) to develop and execute effective go-to-market strategies and demand-generation activities Make sure to preserve punctuation. Then

            Requirements

            (or could be Qualifications/Skills). We'll combine experience, traits, tech-savvy, travel. Use
            • . List: - 2+ years of experience building, developing, and maintaining relationships with tech and human capital management (HCM) partners, benefit brokers, CPA's and financial advisors in the SMB space (including territory sales and business development) - Successful - Proven track record of success in a quota driven sales environment - Passionate - You are a highly motivated individual contributor and relationship builder that can operate independently - Dynamic - You can thrive in a fast-paced, and ever-changing environment - Resilient—You bounce back from setbacks quickly, are resourceful, and find creative ways to get things done. - Solutions-oriented - Willingness to get your hands