Technical Consultant II (ADP WFN)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, accommodations, etc. Must preserve all substantive info. We need to parse the posting. Content: Position Summary: Technical Consultant II (title). Then description: "We are seeking a highly motivated and driven individual..." etc. That's about the role. Then "CANDIDATES MUST HAVE EXPERT KNOWLEDGE OF IMPLEMENTING ADP WFN SOFTWARE. ADDITIONAL KNOWLEDGE IMPLEMENTING PAYCOR A PLUS**" That's a requirement. Then "Candidate Profile" with many bullet-like sentences describing traits. Could be considered Skills or Qualifications? Might be "Skills" or "Qualifications". We'll decide. Then "Essential Duties And Responsibilities" list. Then "Minimum Qualifications (Knowledge, Skills, And Abilities)" list. Then "Compensation & Benefits" with pay range and benefits description. Then "#SPG Department Business Operations Required Experience: 2-5 years of relevant experience Required Travel: No Travel Required Required Education: High school or equivalent" This is metadata; we should fold minor metadata into short

or drop it. Probably we can include in a short paragraph under "About the role" or "Qualifications". But we should not create headings for these unless they have content. They are not separate sections. We must not include EEO etc. We need to produce sections: About the role (summary), Responsibilities (Essential Duties...), Requirements (maybe Minimum Qualifications?), Qualifications (maybe Candidate Profile?), Skills (maybe from Candidate Profile?), Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. Let's see what we have: - About the role: we have position summary paragraph(s). Yes. - Responsibilities: we have Essential Duties And Responsibilities list. Yes. - Requirements: we have Minimum Qualifications list. Yes. - Qualifications: maybe we could combine with Requirements? But we have also "CANDIDATES MUST HAVE EXPERT KNOWLEDGE..." which is a requirement. Could be part of Requirements. The "Candidate Profile" is more about soft skills/attributes; could be Skills or Qualifications. We'll decide to put "Skills" for Candidate Profile (soft skills). Or "Qualifications" for the hard requirements (experience, ADP WFN knowledge). But we already have Requirements for Minimum Qualifications. Might be overlapping. The instruction: Prefer a few substantive sections over many thin ones. So we could combine similar content. We have: - About the role: summary paragraph. - Responsibilities: list of duties. - Requirements/Skills/Qualifications: we have Minimum Qualifications (experience, ADP WFN knowledge, multi-entity, etc.) plus the "CANDIDATES MUST HAVE EXPERT KNOWLEDGE..." plus maybe the Candidate Profile traits. We could make a section "Requirements" that includes both hard and soft requirements. Or we could split into "Qualifications" (hard) and "Skills" (soft). But to avoid many thin sections, maybe just one "Requirements" covering all. Then Benefits: we have description of benefits. Pay: we have pay range. Schedule: we have Required Travel: No Travel Required, but schedule not mentioned. No explicit schedule (like full-time, part-time). So we should not create Schedule section because no specific content. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to use

for each section heading. Inside each section, use

for prose,

• for lists. We must preserve all substantive information; do not invent or summarize away detail. Let's extract exact text. About the role: The position summary includes multiple sentences. We'll combine into a paragraph. Original: "Position Summary: Technical Consultant II We are seeking a highly motivated and driven individual to join our team in the role of Technical Consultant II. As an employer, we value individuals who possess a strong sense of ownership, are self-driven, and demonstrate genuine enthusiasm for the work they do. This position requires an individual that has strong client relationship skills, is system driven, has meticulous attention to detail, and strives to deliver an excellent client experience." We should not repeat the job title as heading, but we can keep the summary text. The phrase "Position Summary: Technical Consultant II" includes title; we can drop that prefix? The instruction: Do NOT repeat the job title as a heading (the page already shows it). It doesn't say we cannot include it in the paragraph. But better to remove the redundant "Position Summary: Technical Consultant II" maybe keep as part of prose? It's okay to keep but it's repeating title. Safer to remove that line and start with "We are seeking a highly motivated..." We'll keep the substantive content. Thus About the role paragraph: "We are seeking a highly motivated and driven individual to join our team in the role of Technical Consultant II. As an employer, we value individuals who possess a strong sense of ownership, are self-driven, and demonstrate genuine enthusiasm for the work they do. This position requires an individual that has strong client relationship skills, is system driven, has meticulous attention to detail, and strives to deliver an excellent client experience." Now Responsibilities: list from "Essential Duties And Responsibilities". The text: "Leads all aspects of the implementation project as a “client-side” resource Manage day-to-day project tasks for a client’s successful payroll transition Configure workflows to optimize system buildout Possess and maintain a high level of HCM specific technology knowledge Ability to create custom reports and showcase templated reports Ability to provide custom system training for clients" We need to preserve each line as
• . Now Requirements: combine: - "CANDIDATES MUST HAVE EXPERT KNOWLEDGE OF IMPLEMENTING ADP WFN SOFTWARE. ADDITIONAL KNOWLEDGE IMPLEMENTING PAYCOR A PLUS**" - Minimum Qualifications list: "3-5 years’ experience in a high-volume, client-facing, implementation role with vendor or consulting organization Expert knowledge of at least the payroll and time and attendance modules within ADP WFN, including extensive payroll knowledge and implementation experience Experience with multi-entity, complex implementations Prior experience owning and leading multiple projects Experienced in Time & Attendance Strong communication and interpersonal skills Demonstrated organizational and time management skills" Also Candidate Profile traits (soft skills). We'll include them as part of Requirements maybe as bullet list? But they are prose sentences. Could be a

  describing. We'll keep them as a paragraph. Candidate Profile text: "We are looking for a candidate who is customer obsessed. Your mission is to earn and maintain the loyalty of your customers by proactively understanding and satisfying their needs. You are the owner of this client relationship, responsible for the client’s longevity with HCM Unlocked and treat their business as if it were your own.Excellent communication skills are vital for this role. You must articulate your ideas effectively, both verbally and in writing. Prompt responsiveness and communication with your clients and peers are critical to the success of this role.You take ownership of your work, approach it with a sense of responsibility, urgency, and accountability. You are someone who thrives on taking initiative, setting goals, and driving projects to successful completion.You are self-motivated and possess a strong work ethic with a rigorous attention to detail.You are capable of working independently, managing your time effectively with multiple clients, and delivering high-quality results even in the face of challenges. Your ability to prioritize tasks and meet deadlines will be critical to your success in this role.We believe that enthusiasm is contagious and can drive positive change. We are looking for a candidate who genuinely enjoys delivering an exceptional customer experience, has a passion for implementation, and brings energy and excitement to their team and to their customers.You must be an analytical thinker with a passion for numbers.You approach challenges with a positive mindset, proactively seek solutions, and adapt quickly to changing circumstances." We'll keep as a paragraph. Now Benefits: from "Compensation & Benefits" paragraph: "The expected pay range for this position is $36.06 - $43.27/hr and will be impacted by factors such as the successful candidate’s skills, experience and working location, as well as the specific position’s business line, scope and level. HUB International is proud to offer comprehensive benefit and total compensation packages which could include health/dental/vision/life/disability insurance, FSA, HSA and 401(k) accounts, paid-time-off benefits, and eligible bonuses, equity and commissions for some positions." We need to separate Pay and Benefits sections. The instruction: create Pay and Benefits sections only if posting actually states them. It does state pay range and benefits. So we should split: Pay section includes the pay range sentence. Benefits section includes the benefits description. Thus Pay: "

  The expected pay range for this position is $36.06 - $43.27/hr and will be impacted by factors such as the successful candidate’s skills, experience and working location, as well as the specific position’s business line, scope and level.

  " Benefits: "

  HUB International is proud to offer comprehensive benefit and total compensation packages which could include health/dental/vision/life/disability insurance, FSA, HSA and 401(k) accounts, paid-time-off benefits, and eligible bonuses, equity and commissions for some positions.

  " Now we need to ensure we didn't include boilerplate like "#SPG Department Business Operations Required Experience: 2-5 years of relevant experience Required Travel: No Travel Required Required Education: High school or equivalent". This is metadata; we should fold minor metadata into a short

  or drop it. Could include a short paragraph under About the role or Requirements? But it's minor. Probably we can drop it as it's not substantive? It includes required experience (2-5 years) which overlaps with Minimum Qualifications (3-5 years). But we already have that. Required Travel: No Travel Required is not schedule; we could mention in a short line but not required. Since we are not making a Schedule section, we could include a short note in About the role or Requirements? But the instruction: fold minor metadata into a short

  or drop it. We could add a short paragraph under About the role after the summary: "Required experience: 2-5 years; no travel required; high school or equivalent education." But we already have experience in Requirements. Might be redundant. Safer to drop it. Now ensure we don't include EEO etc. Now produce HTML fragment:

  About the role

  We are seeking a highly motivated and driven individual to join our team in the role of Technical Consultant II. As an employer, we value individuals who possess a strong sense of ownership, are self-driven, and demonstrate genuine enthusiasm for the work they do. This position requires an individual that has strong client relationship skills, is system driven, has meticulous attention to detail, and strives to deliver an excellent client experience.

  Responsibilities

  • Leads all aspects of the implementation project as a “client-side” resource
  • Manage day-to-day project tasks for a client’s successful payroll transition
  • Configure workflows to optimize system buildout
  • Possess and maintain a high level of HCM specific technology knowledge
  • Ability to create custom reports and showcase templated reports
  • Ability to provide custom system training for clients

  Requirements

  CANDIDATES MUST HAVE EXPERT KNOWLEDGE OF IMPLEMENTING ADP WFN SOFTWARE. ADDITIONAL KNOWLEDGE IMPLEMENTING PAYCOR A PLUS