Business Systems Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as needed. Only include sections with real content. We must not repeat job title. Must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. We need to parse the posting. Key sections: - Intro description: "Salesforce sits at the center..." etc. That's about the role. Could be About the role. - "What you'll be doing" list: bullet points. - "Roughly speaking, the job splits about 80% project work and 20% day-to-day support." Could be part of responsibilities. - "What we're looking for": list of requirements. - "Strong signals": list of nice-to-have? Could be Skills. - "Who does well here": maybe Qualifications or Attributes? Could be part of Requirements. - "Why Resonate": maybe Benefits? Actually it's about company culture. Could be About the role? But we have separate Benefits and Pay sections later. - "Compensation & Benefits": includes base salary range, bonus, benefits list. - "About Resonate": company description. - "Resonate Attributes": list of attributes. - "Location": remote-first. We need to decide sections. We must include Pay if salary info present. Yes base salary range $100,000-$135,000, bonus program. So Pay section. Benefits: list of medical, dental, vision, HSA, disability, life insurance, 401k match, PTO, holidays, parental leave, wellbeing programs. So Benefits section. Schedule: maybe remote-first and flexible environment. Could be Schedule section: remote-first, flexible, little travel. We'll include. About the role: intro description plus maybe "What you'll be doing". Could combine. Responsibilities: the bullet list under "What you'll be doing". Also maybe the 80/20 split. Requirements: "What we're looking for" bullet list. Qualifications: maybe "Strong signals" and "Who does well here"? But we need to avoid duplication. Could treat Strong signals as Skills (nice-to-have). Who does well here as Qualifications (behavioral). Let's decide. Skills: list of technical skills: Salesforce CPQ, Power BI/Tableau, SQL, Git, Pardot, Datorama, Accounting Seed, Jira, Confluence, experience at smaller/mid-sized company. Qualifications: maybe the "Who does well here" traits: curious, comfortable being go-to, etc. But we need to ensure we don't create sections with filler. All have content. We must not include boilerplate like EEO, legal, etc. Remove "About Resonate" maybe? That's company description; could be part of About the role? But we already have About the role. Could treat "About Resonate" as separate section? Not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit everything into those. Thus we need to map content: - About the role: overview of role, purpose, context (Salesforce stack, owning stack, etc.) - Responsibilities: bullet list of duties (what you'll be doing) plus maybe 80/20 split. - Requirements: mandatory experience (5-8 years Salesforce admin, broader stack, owning function, project management instincts, communication, problem structuring). - Qualifications: maybe "Who does well here" traits (curious, comfortable being go-to, etc.) plus location remote-first? Actually location could be Schedule? But schedule is about work hours; location remote-first could be Schedule? Might be better to put location under Schedule? But schedule is about work schedule; remote-first is location. Could still fit under Schedule as "remote-first, flexible environment". We'll include. - Skills: Strong signals list (CPQ, Power BI/Tableau, SQL, Git, Pardot, Datorama, Accounting Seed, Jira, Confluence, experience at smaller/mid-sized). Also maybe "Strong project management instincts" already in Requirements; but we can keep. - Benefits: list of benefits. - Pay: salary range, bonus. - Schedule: remote-first, flexible, little travel. We must not repeat job title. No markdown. We must output only HTML fragment. Let's craft. We'll need

for each section heading. Inside sections, use

for prose,

• for lists. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tools, percentages, etc. Let's extract details. About the role: from first paragraph: "Salesforce sits at the center of this job, but it is nowhere near the whole of it. Resonate helps enterprise brands understand not just who their customers are, but why they behave the way they do. Behind that sits a business systems stack that must hold up: Salesforce Sales Cloud, Power BI, ChurnZero, ZoomInfo, Salesloft, DocuSign, Pardot, Datorama. This role owns it. You will be hands-on in Salesforce daily, and you will also be the person who understands how all of it connects, what happens when data moves between systems, and what to do when something breaks. It comes with real latitude. This is a standalone role, so you take a problem from the first stakeholder conversation through to the build and you're the one accountable for it. If you like owning a stack rather than specializing in one corner of it, this is the job." We'll put that as prose. Responsibilities: bullet list from "What you'll be doing". Let's capture each bullet: - Owning Salesforce Sales Cloud day-to-day: administration, configuration, and Flow-based automation, plus the user access and security side of it, from profiles and permission sets to sharing rules, role hierarchy, and licenses - Improving a well-established Salesforce org by refactoring legacy automation and working through technical debt, so the org gets healthier over time rather than heavier - Maintaining and extending the wider business systems stack, including Power BI, ChurnZero, ZoomInfo, Salesloft, DocuSign, Account Engagement (Pardot), and Marketing Cloud Intelligence (Datorama), with enough working knowledge to administer, troubleshoot, and understand how data flows between them and Salesforce - Partnering with Sales, Marketing, Finance, and Customer Success to get to the problem behind the request, not just the request itself, and designing the solution from there - Running system enhancements and integration projects end-to-end: scoping, prioritization, build, testing, rollout, and documentation, with several moving at once and no dedicated PM to hand them to - Translating in both directions, giving technical partners requirements clear enough that they are not guessing at the ask, and turning technical constraints into something non-technical stakeholders can act on - Keeping data integrity, data quality, and documentation in good shape across connected systems, so what you build is still understandable a year from now Also "Roughly speaking, the job splits about 80% project work and 20% day-to-day support." Could be a separate sentence after list. We'll include as a

  after list. Requirements: from "What we're looking for": - You'll need 5-8 years of hands-on experience administering and configuring Salesforce in a growing organization, including Flow and process automation - Demonstrated experience supporting a broader business systems stack beyond Salesforce, whether that is reporting tools, sales engagement, e-signature, or marketing and data platforms - A track record of owning a business systems function largely independently, including the judgment to know what you resolve yourself and what gets escalated - Strong project management instincts: you can scope, sequence, and deliver a multi-step initiative without a dedicated PM keeping you on track - The ability to bring structure to a loosely defined problem without over-engineering the answer - Communication that works for technical and non-technical audiences, because you will be moving between both in the same day We'll list. Qualifications: from "Who does well here": - You are curious about how systems talk to each other, and you are not content to stay inside one platform. - When a request comes in from Sales or Finance, you can sit in that conversation, work out what is really being asked for, and then go and build it yourself. - Both halves of that are the job, and people who enjoy only one half tend to find this role frustrating. - You are comfortable being the person others come to, and comfortable saying when something will take longer than hoped. - You like the kind of environment where you can see the effect of your work on how the business runs, and where an org you improve today is an org you are still working in next year. We'll list. Skills: from "Strong signals": - Salesforce CPQ, which we are happy to teach if you have not worked in it - Power BI, or Tableau as a stand-in, at the level of maintaining and extending reporting rather than building a function from scratch - SQL, and Git or another version control setup - Account Engagement (Pardot), Marketing Cloud Intelligence (Datorama), or Accounting Seed - Jira and Confluence - Time at a smaller or mid-sized company where the role demanded broad ownership, closer to a builder who owns a stack than a specialist on a team We'll list. Benefits: from "Compensation & Benefits" paragraph after salary: list: - Medical, dental, and vision coverage, including HSA - Company-paid disability and life insurance with a life insurance buy-up option - a 401(k) with company match - Flexible PTO plus 10 paid holidays - Paid parental leave - Access to wellbeing and employee assistance programs, including free and unlimited access to 20+ health professionals and wellbeing coaches for you and your family members. We'll list. Pay: from same section: - The base salary range for this role is $100,000-$135,000. - This role is also eligible for our annual bonus program, tied to company performance. - Where an offer lands within the range depends on your experience, skills, qualifications, and location. We'll put as prose. Schedule: from Location section: remote-first, flexible environment, little travel, offices in Reston VA, NYC, DC. We'll summarize: remote-first approach, flexible environment, little travel, offices in Reston, VA; New York City; Washington, D.C. We'll put as prose. We must not include boilerplate like EEO, legal, etc. Remove "About Resonate" company description? That's substantive but not in allowed headings. Could we incorporate into About the role? It's about company, not role. Might be okay to omit? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company description. But we don't have a heading for it. Could we put it under About the role? That might be stretching but it's still about the role context? The About the role section could include company description as part of role context. It's permissible to include company info in About the role. We'll add a paragraph after the role overview describing Resonate. Thus About the role will include both role description and company overview. Let's craft HTML. We'll need to ensure no stray text outside tags. We'll produce:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Roughly speaking, the job splits about 80% project work and 20% day-to-day support.

  Requirements

  ...

  Qualifications

  ...

  Skills

  ...

  Benefits

  ...

  Pay

  ...