Payroll Analyst
John Hancock · Boston, MA · 3 wk ago
Hybrid$62k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We must parse the posting.
Key content:
- Intro: "We are seeking a highly skilled Payroll Analyst..." This is about the role. Could be About the role.
- Position Responsibilities: list of responsibilities.
- Required Qualifications: list.
- Preferred Qualifications: list.
- When You Join Our Team: benefits? Actually includes empowerment, flexible environment, etc. Also later: "Manulife/John Hancock offers eligible employees a wide array of customizable benefits..." That's benefits.
- Salary range: "Salary range is expected to be between $61,875.00 USD - $103,125.00 USD". Also mention incentive compensation.
- Working Arrangement: Hybrid.
- Schedule? Not explicitly given. Might not include schedule if not specified.
- Pay: we have salary range.
- Benefits: we have description of benefits.
- Skills: maybe from qualifications: analytical, troubleshooting, problem solving, Excel, etc. Could be a Skills section.
We must not repeat job title as heading. Use for each section heading.
We need to preserve all substantive info, not invent.
We must remove boilerplate: EEO, legal, accommodation request, etc. Also remove "Know Your Rights ..." lines. Remove "Company: John Hancock..." maybe not needed but could be considered metadata; we can drop.
We must not include Job ID/requisition numbers.
We must not include duplicated lines.
We need to decide sections:
- About the role: include intro paragraph(s) describing role, team size, purpose.
- Responsibilities: list from "Position Responsibilities" bullet points.
- Requirements: could combine Required Qualifications and maybe Preferred Qualifications? But we have separate sections: Requirements (maybe Required Qualifications) and Skills (maybe preferred?). However instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They list both Requirements and Qualifications as possible headings. We need to decide which to use. Probably we can have Requirements (for required qualifications) and Qualifications (for preferred). Or we could combine. But they said "Prefer a few substantive sections over many thin ones." So maybe combine Required and Preferred into Qualifications? But they gave both as possible headings. We could have Requirements (required) and Qualifications (preferred). That's two sections.
Skills: could be extracted from qualifications (Excel, analytical, etc.) but might be redundant. Could omit Skills if not distinct.
Benefits: include description.
Pay: include salary range and incentive.
Schedule: not specified; we should not include Schedule section if no real content.
Hybrid: that's working arrangement; could be part of About the role or maybe a separate Schedule? But schedule not given. Hybrid is work arrangement, not schedule. Could include in About the role.
We must not include placeholder text like "commensurate with experience". Not present.
Now craft HTML.
We need to wrap content in appropriate tags:
for section headings; we could keep as a single list, but that loses the subheadings. However we can keep them as list items with the subheading text as part of the item. That's okay.
Required Qualifications:
- 5+ years of progressive payroll experience with increasing levels of responsibility.
- Strong analytical, troubleshooting, and problem-solving skills, including the ability to independently research and resolve complex payroll, tax, and benefits issues.
- Experience with payroll audits, reconciliations, quarterly and year-end activities, taxable benefit reporting, and employee year-end reporting.
- Experience supporting payroll system or process changes, including documenting requirements and decisions, managing scope, developing test scenarios, and executing positive and negative testing.
- Experience with ADP GlobalView, SAP, or similar enterprise payroll systems.
- Expert-level knowledge of gross-to-net payroll processing, including earnings, deductions, taxable benefits, statutory remittances, employer liabilities, general ledger impacts, payroll funding, and accounting reconciliations.
- Advanced Excel and data analysis skills.
- Ability to manage multiple priorities, work independently with minimal direction, and collaborate effectively within a team environment.
Preferred Qualifications:
- CPP, FPC, or similar payroll certification.
- Experience supporting international payroll operations, including expatriate payroll, mobile employees, cross-border taxation, and related compliance requirements across jurisdictions such as Canada, the United Kingdom, and Hong Kong.
- Benefits administration or operations experience, particularly where benefits programs affect payroll taxation, disability payments, paid leave, taxable wages, or year-end reporting.
- Experience serving as a lead tester, project contributor, subject matter expert, mentor, or escalation point.
When You Join Our Team: "We’ll empower you to learn and grow the career you want. We’ll recognize and support you in a flexible environment where well being and inclusion are more than just words. As part of our global team, we’ll support you in shaping the future you want to see." Could be part of Benefits or About the role? Might be a separate section but we have Benefits heading; we could put this under Benefits? But it's more about culture. Could be part of About the role. However we already have About the role; we could add a paragraph there.
Benefits: "Manulife/John Hancock offers eligible employees a wide array of customizable benefits, including health, dental, mental health, vision, short- and long-term disability, life and AD&D insurance coverage, adoption/surrogacy and wellness benefits, and employee/family assistance plans. We also offer eligible employees various retirement savings plans (including pension/401(k) savings plans and a global share ownership plan with employer matching contributions) and financial education and counseling resources. Our generous paid time off program in the U.S. includes up to 11 paid holidays, 3 personal days, 150 hours of vacation, and 40 hours of sick time (or more where required by law) each year, and we offer the full range of statutory leaves of absence."
Pay: "Salary range is expected to be between $61,875.00 USD - $103,125.00 USD Employees also have the opportunity to participate in incentive programs and earn incentive compensation tied to business and individual performance. The actual salary will vary depending on local market conditions, geography and relevant job-related factors such as knowledge, skills, qualifications, experience, and education/training. If you are applying for this role outside of the primary location, please contact hr@manulife.com for the salary range for your location."
We should not include the instruction to contact hr for location; that's maybe boilerplate? It's still substantive but maybe we can keep. However it's a directive; could be considered application instruction? It's about salary range location. Might be okay to keep but it's somewhat instructional. The instruction says remove application instructions. This is not exactly application instruction but about salary range. Might be okay to keep but we could drop the sentence about contacting hr. Safer to keep only the salary range and incentive.
Schedule: Not specified; we should not include Schedule section.
Hybrid: mention in About the role maybe.
Now craft HTML.
We'll have sections:
for each section heading.
We need to preserve all substantive info, not invent.
We must remove boilerplate: EEO, legal, accommodation request, etc. Also remove "Know Your Rights ..." lines. Remove "Company: John Hancock..." maybe not needed but could be considered metadata; we can drop.
We must not include Job ID/requisition numbers.
We must not include duplicated lines.
We need to decide sections:
- About the role: include intro paragraph(s) describing role, team size, purpose.
- Responsibilities: list from "Position Responsibilities" bullet points.
- Requirements: could combine Required Qualifications and maybe Preferred Qualifications? But we have separate sections: Requirements (maybe Required Qualifications) and Skills (maybe preferred?). However instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They list both Requirements and Qualifications as possible headings. We need to decide which to use. Probably we can have Requirements (for required qualifications) and Qualifications (for preferred). Or we could combine. But they said "Prefer a few substantive sections over many thin ones." So maybe combine Required and Preferred into Qualifications? But they gave both as possible headings. We could have Requirements (required) and Qualifications (preferred). That's two sections.
Skills: could be extracted from qualifications (Excel, analytical, etc.) but might be redundant. Could omit Skills if not distinct.
Benefits: include description.
Pay: include salary range and incentive.
Schedule: not specified; we should not include Schedule section if no real content.
Hybrid: that's working arrangement; could be part of About the role or maybe a separate Schedule? But schedule not given. Hybrid is work arrangement, not schedule. Could include in About the role.
We must not include placeholder text like "commensurate with experience". Not present.
Now craft HTML.
We need to wrap content in appropriate tags: About the role
then
...
. For lists:- ...
for section headings; we could keep as a single list, but that loses the subheadings. However we can keep them as list items with the subheading text as part of the item. That's okay.
Required Qualifications:
- 5+ years of progressive payroll experience with increasing levels of responsibility.
- Strong analytical, troubleshooting, and problem-solving skills, including the ability to independently research and resolve complex payroll, tax, and benefits issues.
- Experience with payroll audits, reconciliations, quarterly and year-end activities, taxable benefit reporting, and employee year-end reporting.
- Experience supporting payroll system or process changes, including documenting requirements and decisions, managing scope, developing test scenarios, and executing positive and negative testing.
- Experience with ADP GlobalView, SAP, or similar enterprise payroll systems.
- Expert-level knowledge of gross-to-net payroll processing, including earnings, deductions, taxable benefits, statutory remittances, employer liabilities, general ledger impacts, payroll funding, and accounting reconciliations.
- Advanced Excel and data analysis skills.
- Ability to manage multiple priorities, work independently with minimal direction, and collaborate effectively within a team environment.
Preferred Qualifications:
- CPP, FPC, or similar payroll certification.
- Experience supporting international payroll operations, including expatriate payroll, mobile employees, cross-border taxation, and related compliance requirements across jurisdictions such as Canada, the United Kingdom, and Hong Kong.
- Benefits administration or operations experience, particularly where benefits programs affect payroll taxation, disability payments, paid leave, taxable wages, or year-end reporting.
- Experience serving as a lead tester, project contributor, subject matter expert, mentor, or escalation point.
When You Join Our Team: "We’ll empower you to learn and grow the career you want. We’ll recognize and support you in a flexible environment where well being and inclusion are more than just words. As part of our global team, we’ll support you in shaping the future you want to see." Could be part of Benefits or About the role? Might be a separate section but we have Benefits heading; we could put this under Benefits? But it's more about culture. Could be part of About the role. However we already have About the role; we could add a paragraph there.
Benefits: "Manulife/John Hancock offers eligible employees a wide array of customizable benefits, including health, dental, mental health, vision, short- and long-term disability, life and AD&D insurance coverage, adoption/surrogacy and wellness benefits, and employee/family assistance plans. We also offer eligible employees various retirement savings plans (including pension/401(k) savings plans and a global share ownership plan with employer matching contributions) and financial education and counseling resources. Our generous paid time off program in the U.S. includes up to 11 paid holidays, 3 personal days, 150 hours of vacation, and 40 hours of sick time (or more where required by law) each year, and we offer the full range of statutory leaves of absence."
Pay: "Salary range is expected to be between $61,875.00 USD - $103,125.00 USD Employees also have the opportunity to participate in incentive programs and earn incentive compensation tied to business and individual performance. The actual salary will vary depending on local market conditions, geography and relevant job-related factors such as knowledge, skills, qualifications, experience, and education/training. If you are applying for this role outside of the primary location, please contact hr@manulife.com for the salary range for your location."
We should not include the instruction to contact hr for location; that's maybe boilerplate? It's still substantive but maybe we can keep. However it's a directive; could be considered application instruction? It's about salary range location. Might be okay to keep but it's somewhat instructional. The instruction says remove application instructions. This is not exactly application instruction but about salary range. Might be okay to keep but we could drop the sentence about contacting hr. Safer to keep only the salary range and incentive.
Schedule: Not specified; we should not include Schedule section.
Hybrid: mention in About the role maybe.
Now craft HTML.
We'll have sections:
About the role
... (including hybrid mention)
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
...
Pay
...
We must not include empty sections. Check for any duplicated lines: ensure we didn't repeat. Now produce HTML fragment. Be careful to escape any HTML special characters