Compensation HR Analyst
Altium Packaging · Atlanta, GA · 1 mo ago
Human ResourcesFull-time
We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse content.
Location address line: "Location Address: 2500 Windy Ridge Parkway, Atlanta, Georgia 30339 Work Shift Salary Exempt (United States of America)" This includes location and maybe shift? Not needed as heading.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should drop EEO statement, etc.
We need to preserve all substantive info.
Let's extract sections:
- About the role: The first paragraph after location: "The Compensation HR Analyst is a key contributor to the design, governance, and execution of the company’s compensation programs and reports to the Director, HR Programs. This role supports Altium’s annual compensation cycles, provides expert guidance on pay decisions, and ensures market competitiveness through robust pricing and job architecture practices. The position also serves as a Workday compensation and data governance expert, maintaining accurate job and pay structures while strengthening controls and compliance. Partnering closely with HR Business Partners and business leaders, the Compensation HR Analyst delivers data driven insights, mitigates risk, and supports equitable, consistent compensation practices across the organization."
That's about the role.
- Responsibilities: There's a "Key Responsibilities" heading with subpoints: Compensation Program Management, Workday Compensation & Data Governance, Market Pricing & Job Architecture, Stakeholder Support & Consultation. Each has bullet-like sentences. We need to convert to
- . Probably each bullet is a sentence or group. We need to preserve all details. Let's list responsibilities: Compensation Program Management: - Lead and execute annual compensation cycles (Merit and MIP), including eligibility, validations, audits, testing, and post‑cycle support. - Provide compensation guidance to HR Business Partners and leaders, including recommendations for offers, promotions, adjustments, re‑leveling, and risk mitigation - Assist with the development of compensation policies, governance practices, and decision-making frameworks to ensure consistency and compliance Workday Compensation & Data Governance: - Maintain and update Workday compensation dashboards, audit tools, job profile data, and compensation codes. - Ensure the accuracy of job profiles, compensation grades, and job architecture alignment across the system. - Strengthen compensation data governance, including access controls, role‑based visibility, and compliance with need‑to‑know protocols. Market Pricing & Job Architecture: - Lead market pricing initiatives using survey tools (e.g., Radford and Culpepper) and manage annual survey submissions. - Partner with HRBPs to ensure appropriate leveling and market alignment across roles. - Support job description and job profile standardization efforts, ensuring consistency in structure and compensation alignment Stakeholder Support & Consultation: - Serve as a subject‑matter expert for compensation inquiries, providing timely and accurate guidance to HR and business leaders. - Manage and respond to Compensation ServiceDesk requests and ad‑hoc analyzes. We'll put each bullet as
- .
- Requirements: The posting has "Required Qualifications" list. Also "Preferred Qualifications". We need to decide sections: Requirements vs Qualifications vs Skills. The instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content.
We have Required Qualifications and Preferred Qualifications. Could map Required Qualifications to "Requirements" section. Preferred Qualifications could go under "Qualifications" or "Skills"? Possibly "Qualifications" for both required and preferred? But we have separate headings: Requirements and Qualifications. Might treat Requirements as mandatory, Qualifications as preferred? Or we could combine both into Qualifications and leave Requirements empty? But we must not emit empty sections. So we need to decide which content goes where.
We have "Required Qualifications" list: 2 to 4 years progressive experience..., Strong Workday experience..., Demonstrated ability..., High level..., Advanced analytical skills..., Excellent communication...
These are qualifications/requirements. Could put under "Requirements". Then "Preferred Qualifications": Experience in multisite manufacturing..., Familiarity with compensation governance..., Expertise with survey providers..., Reasonable mandatory overtime may be required... That's more like preferred qualifications and also a note about overtime.
We could put Preferred Qualifications under "Qualifications" section. Also maybe "Skills" could be derived from required qualifications (analytical skills, communication). But we already have those in Required Qualifications. Could also create a Skills section for things like "Advanced analytical skills", "Excellent communication and stakeholder management skills". But that would duplicate. Better to follow instruction: Use headings as given; we can decide to put Required Qualifications under Requirements, Preferred Qualifications under Qualifications, and maybe Skills could be omitted if not distinct. However we might still include Skills if we can extract skill-specific items not covered elsewhere. The Required Qualifications already includes skills: Advanced analytical skills, Excellent communication and stakeholder management skills. Could put those under Skills. But then Requirements would be experience and Workday etc. Let's see.
We could split:
Requirements: 2 to 4 years of progressive experience in compensation, including market pricing, job architecture, and administration of annual compensation programs. Strong Workday experience, including compensation dashboards, job profile maintenance, audits, and data governance. Demonstrated ability to manage complex compensation cycles with precision and attention to detail. High level of organization and ability to manage multiple priorities in a fast‑paced environment.
Qualifications: Preferred qualifications: Experience in a multisite manufacturing or corporate HR environment. Familiarity with compensation governance frameworks and risk mitigation practices. Expertise with survey providers such as Radford and Culpepper. Reasonable mandatory overtime may be required due to business needs.
Skills: Advanced analytical skills with the ability to interpret data, identify trends, and translate insights into recommendations. Excellent communication and stakeholder management skills.
That seems reasonable and avoids duplication.
Now Benefits: The posting includes a paragraph about benefits: "We Believe in Rewarding our Most Important Resource – Our People! We show our commitment to Total Rewards by providing a competitive, comprehensive benefits package. In addition to medical, dental and vision plans, company holidays and vacation days, tuition reimbursement, learning and training opportunities, bonus potential, and a 401(k) plan with company contributions, Altium Packaging locations offer rewards and recognition programs and opportunities to make a difference in the community."
We need to include Benefits section with that content. Should we list as
- ? Could be prose
. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. Benefits is a list of items; we could make a
- . However the paragraph is prose listing items separated by commas. Could convert to list items: medical, dental and vision plans; company holidays and vacation days; tuition reimbursement; learning and training opportunities; bonus potential; 401(k) plan with company contributions; rewards and recognition programs; opportunities to make a difference in the community. That seems appropriate.
Pay and Schedule: The posting includes "Work Shift Salary Exempt (United States of America)" at top. That indicates salary exempt (i.e., exempt status) but no actual pay amount. Also "Work Shift" maybe indicates shift? Not specific. There's no explicit pay amount or schedule details. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Work Shift Salary Exempt". That's not a specific pay figure, but it's about salary exempt status. Might be considered Pay info? It says "Salary Exempt". That's a classification, not a number. The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Salary Exempt" is not a placeholder like "not specified"? It's a statement about exempt status. Could be considered Pay info? Might be okay to include Pay section with that statement? However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Work Shift Salary Exempt". So we could include Pay section with that line. But we need to avoid filler like "not specified". This is specific: "Work Shift Salary Exempt". Might be acceptable.
Schedule: Not mentioned besides maybe "Work Shift". Could infer shift? Not specific. Probably we should not create Schedule section because no specific schedule info (like full-time, part-time, shift times). The phrase "Work Shift" is vague. Better to omit Schedule.
Thus we will include Pay section with the statement: "Work Shift Salary Exempt (United States of America)". Could be placed in
- for lists. Use
for prose. We need to ensure we don't repeat job title as heading. Not needed. We need to remove boilerplate: EEO statement, etc. Also remove "Take your career to the next level at Altium Packaging!" maybe considered boilerplate? It's a call to action; could be considered application instruction? Might be considered boilerplate; we should remove. Also remove "Altium Packaging, Our Culture Differentiates Us! ..."? That's culture description; could be considered substantive? It's about guiding principles. Might be considered part of About the role? Not directly about role. Could be considered extra but maybe we keep as part of About the role? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The culture description is substantive about company. Could be included maybe under About the role? But we already have About the role paragraph. Could add another paragraph about culture. However the instruction about sections: we could include About the role section with multiple paragraphs. That's fine. We need to decide whether to include culture description. It's not directly about the role but about company. It's substantive. I'd include it as part of About the role after the initial paragraph. Thus About the role will have two paragraphs: first about role, second about culture and guiding principles. Now we need to ensure we don't include duplicated lines. Check for duplicates: none. Now produce HTML. Structure:
About the role
...
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ...
- ...
Benefits
- ... ...
Pay
Work Shift Salary Exempt (United States of America)
No Schedule. Check that we didn't include any placeholder like "commensurate with experience". Not present. Now let's craft the content precisely. About the role paragraph 1: "The Compensation HR Analyst is a key contributor to the design, governance, and execution of the company’s compensation programs and reports to the Director, HR Programs. This role supports Altium’s annual compensation cycles, provides expert guidance on pay decisions, and ensures market competitiveness through robust pricing and job architecture practices. The position also serves as a Workday compensation and data governance expert, maintaining accurate job and pay structures while strengthening controls and compliance. Partnering closely with HR Business Partners and business leaders, the Compensation HR Analyst delivers data driven insights, mitigates risk, and supports equitable, consistent compensation practices across the organization." Paragraph 2 (culture): "Altium Packaging, Our Culture Differentiates Us! We incorporate our Guiding
. Now we need to output HTML fragment only, no /. Use
for section headings. Use
- for lists. Use
- for any list of duties/requirements/benefits, and
- ? Could be prose