Integration Specialist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key parts: - Intro: HR Acuity’s Professional Services group is seeking a highly skilled and experienced Integration Specialist... (description). This is about the role. - About HR Acuity®: description of company, values. - About Us: more description. - What You’ll Do: list of duties. - What We Offer: benefits/culture. - What Does Success Look Like?: maybe not a standard heading but could be considered part of responsibilities? It's more like success metrics. Could be omitted or included under Responsibilities? Probably not needed. - Then list of qualifications/experience: "3+ years of experience..." etc. That's requirements/qualifications/skills. - Compensation: pay range. - Benefits: list of benefits. - Perks: duplicate of benefits? Might be considered benefits. - Learning and Development: maybe a section? Could be considered Benefits or separate? The instruction: include a section ONLY when posting has real, specific content for it. Learning and Development has content (Onboarding, Manager training, etc). Could be a section "Learning and Development". However allowed headings list includes Benefits, Pay, Schedule, etc. Not Learning and Development. But we could still use

for any section heading? 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 list. Likely we should stick to those headings. So we may not include Learning and Development as a separate heading; we could fold into Benefits or maybe omit. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to output only HTML fragment. Let's extract substantive content: - About the role: The introductory paragraph describing role: "HR Acuity’s Professional Services group is seeking a highly skilled and experienced Integration Specialist to join our team. This role is pivotal in working with our customers during and after implementation, ensuring seamless integration setup, technical expertise, and optimizing integration performance, all of which directly impacts customer satisfaction and HR Acuity’s success. You will collaborate closely with internal teams, including Product Management and Engineering, to influence the development of new tooling and raise/resolve technical issues. Additionally, you will provide training and support to our customer-facing teams, ensuring they are well-equipped to assist clients with integration-related matters." - About HR Acuity: description of company values, mission, inclusive workplace. Could be under "About the role"? Might be separate "About HR Acuity". But allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About HR Acuity" maybe not needed; could be omitted or placed under About the role? The instruction: 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. It didn't forbid other headings like About the company. But examples given are limited. Safer to include only those headings that have content. We have content for About the role (intro). Responsibilities: "What You’ll Do" list. Requirements/Qualifications/Skills: the list of experience, background, etc. Benefits: "What We Offer" plus Benefits list plus Perks. Pay: compensation range. Schedule: not mentioned; we should not create Schedule section if not present. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info: include details like "Own the technical setup and integrations configuration for new and existing HR Acuity customers, ensuring all technical requirements are met during the project lifecycle." etc. We need to use

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

  for prose. Thus:

  About the role

  HR Acuity’s Professional Services group is seeking a highly skilled and experienced Integration Specialist to join our team. This role is pivotal in working with our customers during and after implementation, ensuring seamless integration setup, technical expertise, and optimizing integration performance, all of which directly impacts customer satisfaction and HR Acuity’s success. You will collaborate closely with internal teams, including Product Management and Engineering, to influence the development of new tooling and raise/resolve technical issues. Additionally, you will provide training and support to our customer-facing teams, ensuring they are well-equipped to assist clients with integration-related matters.

  Maybe also include About HR Acuity description? Could be folded into About the role? But it's separate. Could we add another

  About HR Acuity? Not in examples but maybe allowed. However instruction: "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 About HR Acuity as a heading. But to be safe, maybe we incorporate that content into About the role paragraph? But that would lose some specifics about company values. However the instruction says preserve ALL substantive information. So we need to keep that info. We could add a section

  About HR Acuity

  with paragraph. Similarly, "What We Offer" could be Benefits. But also includes mission-driven culture etc. Could be Benefits. We also have "What Does Success Look Like?" which is not a standard heading but could be considered part of Responsibilities or maybe omitted? It contains substantive info about success metrics. Might be worth including as a separate section maybe "Success Metrics"? Not in examples. Could be folded into Responsibilities? But it's more about outcomes. Safer to include as a separate heading maybe "Success Metrics". But 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 to be safe we could treat it as part of Responsibilities? However it's not duties but outcomes. Might be okay to include as a separate heading "What Does Success Look Like?" but that's not in the list. Might be considered extra heading not needed. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine success metrics into Responsibilities or maybe into a separate "Responsibilities" section? Actually responsibilities are duties; success metrics are outcomes. Could be placed under "What Does Success Look Like?" as its own heading but that adds a thin section. Might be better to incorporate into Responsibilities as a paragraph after duties? But that would change meaning. However we can keep it as a separate heading "Success Metrics" but not in examples; risk of being considered not following instruction. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, but the examples are given. Usually they'd expect only those headings. So we should stick to those. Thus we need to map content to those headings. Let's list possible headings and content: - About the role: intro + maybe About HR Acuity? Could combine. - Responsibilities: "What You’ll Do" list. - Requirements: maybe "3+ years of experience..." etc. - Qualifications: maybe education background. - Skills: maybe technical skills list. But the posting lumps many items together: "3+ years of experience working with integrations in a technical or implementation-focused role. Track record of working directly with customers... Background in API integrations... Ability to troubleshoot... Strong collaboration skills... Excellent verbal and written communication... Ability to manage multiple projects... Strong problem-solving skills... Experience in developing technical documentation and training. Familiarity with CRM, ERP, HCM/HRIS, ATS, and other enterprise software ecosystems... Experience with integration/iPaaS platforms... Bachelor's degree in a related field, or equivalent practical experience." We could split into Requirements (experience), Qualifications (education), Skills (technical and soft). But we need to avoid thin sections. Perhaps combine into one section "Requirements" that includes all. Or we could have "Requirements" and "Skills". The instruction: Prefer a few substantive sections over many thin ones. So maybe one section "Requirements" that includes experience, skills, education. But we also have separate "Benefits" and "Pay". So we will have:

  About the role

  ... intro + About HR Acuity description ...

  Responsibilities

  • Own the technical setup and integrations configuration for new and existing HR Acuity customers, ensuring all technical requirements are met during the project lifecycle.
  • Ensure a world-class customer experience by providing clear communication, technical expertise, proactive project management.
  • Facilitate and manage the migration of customer data into the HR Acuity platform.
  • Assist Sales and Customer Success teams with technical scoping calls to ensure prospects and customers are properly supported.
  • Translate customer business requirements into technical solutions and configurations.
  • Collaborate with Product Managers, providing input based on customer and technical experience to inform upcoming releases.
  • Partner with Product and Engineering teams to identify and report recurring integration challenges.
  • Provide consultative guidance using established best practices to increase customer adoption and drive positive customer outcomes.
  • Scope and document new and existing technical processes/requirements in collaboration with customers and internal teams.
  • Manage and drive special projects and initiatives as assigned by Manager.

  Requirements

  3+ years of experience working with integrations in a technical or implementation-focused role. Track record of working directly with customers, ensuring a positive and effective integration experience. Background in API integrations and enterprise system connections (e.g., REST/SOAP APIs, JSON/XML, SFTP, webhooks). Ability to troubleshoot technical issues and communicate solutions clearly to both technical and non-technical stakeholders. Strong collaboration skills with cross-functional teams, including Product, Engineering, and Sales. Excellent verbal and written communication. Ability to manage multiple projects and priorities. Strong problem-solving skills and the ability to work under pressure. Experience in developing technical documentation and training. Familiarity with CRM, ERP, HCM/HRIS, ATS, and other enterprise software ecosystems (e.g., Workday, ADP, UKG, SAP SuccessFactors, Salesforce). Experience with integration/iPaaS platforms (e.g., Workato, MuleSoft, Dell Boomi) is a plus. Bachelor's degree in a related field, or equivalent practical experience.

  Alternatively we could split into Requirements and Skills but we can keep as one.

  Benefits

  A mission‑driven culture that prioritizes people, integrity, and continuous improvement. The opportunity to help shape a growing integrations program in a high‑impact, high‑visibility role. Collaboration with Product, Engineering, Sales, and Customer Success to influence strategy and product evolution. A supportive, flexible work environment with a strong focus on work/life balance. Competitive compensation and benefits package. Professional development opportunities, including access to certifications, training resources, and cross‑functional learning.

  Then we need a separate Benefits list for health etc. Could be another
  under Benefits? But we already have a Benefits section; we could include the list as
  inside. Thus:

  Benefits

  • Stay healthy and happy with our comprehensive medical, dental and vision plans.
  • You can also choose from FSA or HSA options to suit your needs.