Benefits Concierge Specialist
NorthPoint Development · Kansas City, MO · 3 wk ago
On-siteInformation TechnologyFull-time
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. Remove boilerplate like EEO, legal, etc. Also remove application instructions (none). Keep all substantive info.
We need to parse the posting.
Content:
- Intro: "This is an in-person role in Kansas City Curious about a career with NorthPoint? NorthPoint is a real estate developer that has grown through combining an entrepreneurial spirit and empowerment of its team members. We are looking for a Benefits Concierge Specialist to join our Human Resources team in Kansas City! NorthPoint provides an inclusive environment that cultivates collaboration and mentorship. Our core values set the foundation of our culture and guide us in every business decision. “We truly believe, and I’m convinced, we have some pretty incredible assets. But those assets have all come from our people.” - Nathaniel Hagedorn | CEO. How We Put You First At NorthPoint Development we ask a lot of our employees, which is why we give so much in return. In addition to your competitive salary, we offer market-leading benefits and perks: ..."
So we have an "About the role" or "About the company" section. Could be "About the role" or "About NorthPoint". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- About the role/company: description of NorthPoint, inclusive environment, core values, quote, How We Put You First (benefits). Actually benefits are listed later.
- Responsibilities: "What You'll Do" bullet list.
- Requirements/Qualifications/Skills: "Who You Are" includes warm empathetic, 5+ years experience, working knowledge, experienced with benefits billing, skilled at translating, detail-oriented, proficient in HRIS and MS Office, discreet. Also "Preferred Experience" includes familiarity with self-funded medical plans, prior experience supporting benefits compliance, clinical/patient advocacy/medical claims background.
We need to separate into Requirements, Qualifications, Skills perhaps. But we can combine if content is thin. However we should only include sections that have real specific content. We can have:
- About the role (company overview, mission, values, How We Put You First maybe part of Benefits? Actually benefits listed there: "In addition to your competitive salary, we offer market-leading benefits and perks:" then list benefits. That's benefits content. So we could put that under Benefits section.
- Responsibilities: from "What You'll Do".
- Requirements: maybe "5+ years of experience in employee benefits..." etc.
- Qualifications: maybe "Working knowledge of group health and welfare plans..." etc.
- Skills: maybe "Skilled at translating complex benefits concepts..." etc.
But we need to avoid duplication. Let's extract each piece.
First, About the role/company:
"This is an in-person role in Kansas City Curious about a career with NorthPoint? NorthPoint is a real estate developer that has grown through combining an entrepreneurial spirit and empowerment of its team members. We are looking for a Benefits Concierge Specialist to join our Human Resources team in Kansas City! NorthPoint provides an inclusive environment that cultivates collaboration and mentorship. Our core values set the foundation of our culture and guide us in every business decision. “We truly believe, and I’m convinced, we have some pretty incredible assets. But those assets have all come from our people.” - Nathaniel Hagedorn | CEO."
That's about the company and role.
Then "How We Put You First At NorthPoint Development we ask a lot of our employees, which is why we give so much in return. In addition to your competitive salary, we offer market-leading benefits and perks:" then list benefits.
Thus Benefits section content: list of benefits.
Responsibilities: bullet list under "What You'll Do".
Requirements/Qualifications/Skills: from "Who You Are" and "Preferred Experience".
Let's extract "Who You Are":
- A warm, empathetic people person who's just as comfortable heads-down in a spreadsheet as across the table from a teammate
- 5+ years of experience in employee benefits, benefits administration, HR, or a related field (HR, insurance/brokerage, or healthcare/medical backgrounds all welcome)
- Working knowledge of group health and welfare plans and applicable regulations (ERISA, ACA, HIPAA, COBRA, FMLA, Section 125)
- Experienced with benefits billing reconciliation and vendor management
- Skilled at translating complex benefits concepts into plain language employees can actually use
- Detail-oriented and comfortable juggling multiple deadlines
- Proficient in HRIS platforms and Microsoft Office
- Discreet with confidential and sensitive employee information
Preferred Experience:
- Familiarity with self-funded medical plans
- Prior experience supporting benefits compliance and required notice distribution
- A clinical, patient advocacy, or medical claims background
We could map:
- Requirements: maybe the mandatory items: 5+ years experience, working knowledge, experienced with benefits billing, skilled at translating, detail-oriented, proficient in HRIS/MS Office, discreet.
- Qualifications: maybe the warm empathetic people person? Or we could treat that as Skills? Actually "warm, empathetic people person" is a trait/skill.
- Skills: maybe the same as above? Might be overlapping.
Given instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section maybe "Requirements & Qualifications". But headings are prescribed; we can still use them but if content is thin we should avoid. However we have enough content for each.
Let's assign:
- About the role: company description.
- Responsibilities: What You'll Do list.
- Requirements: 5+ years experience, working knowledge, experienced with benefits billing, skilled at translating, detail-oriented, proficient in HRIS/MS Office, discreet.
- Qualifications: warm empathetic people person? Actually that's more of a skill/trait. Could be under Skills.
- Skills: maybe the same as above? Hmm.
Better: Use Requirements for experience and knowledge, Qualifications for education/training? Not given. Could skip Qualifications if not specific. But we have "Preferred Experience" which could be under Qualifications? Or we could make a "Preferred Qualifications" section but not in list. The instruction only allows those headings; we could still use Qualifications for preferred experience.
Skills: maybe the soft skills like warm empathetic people person, detail-oriented, comfortable juggling multiple deadlines, discreet.
But we already used detail-oriented etc in Requirements. Might duplicate.
Let's think: We can structure as:
- About the role (company overview)
- Responsibilities
- Requirements (mandatory experience/knowledge)
- Qualifications (preferred experience)
- Skills (soft skills and technical proficiency)
- Benefits
- Pay (not mentioned besides "competitive salary" but no specifics; we should not create Pay section unless posting actually states them. It says "In addition to your competitive salary" but no amount or range. That's not specific; we should not create Pay section.
- Schedule: not mentioned (in-person role in Kansas City but no schedule details). So skip.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
Now we need to format:
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. Remove boilerplate like EEO, legal, etc. Also remove application instructions (none). Keep all substantive info.
We need to parse the posting.
Content:
- Intro: "This is an in-person role in Kansas City Curious about a career with NorthPoint? NorthPoint is a real estate developer that has grown through combining an entrepreneurial spirit and empowerment of its team members. We are looking for a Benefits Concierge Specialist to join our Human Resources team in Kansas City! NorthPoint provides an inclusive environment that cultivates collaboration and mentorship. Our core values set the foundation of our culture and guide us in every business decision. “We truly believe, and I’m convinced, we have some pretty incredible assets. But those assets have all come from our people.” - Nathaniel Hagedorn | CEO. How We Put You First At NorthPoint Development we ask a lot of our employees, which is why we give so much in return. In addition to your competitive salary, we offer market-leading benefits and perks: ..."
So we have an "About the role" or "About the company" section. Could be "About the role" or "About NorthPoint". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- About the role/company: description of NorthPoint, inclusive environment, core values, quote, How We Put You First (benefits). Actually benefits are listed later.
- Responsibilities: "What You'll Do" bullet list.
- Requirements/Qualifications/Skills: "Who You Are" includes warm empathetic, 5+ years experience, working knowledge, experienced with benefits billing, skilled at translating, detail-oriented, proficient in HRIS and MS Office, discreet. Also "Preferred Experience" includes familiarity with self-funded medical plans, prior experience supporting benefits compliance, clinical/patient advocacy/medical claims background.
We need to separate into Requirements, Qualifications, Skills perhaps. But we can combine if content is thin. However we should only include sections that have real specific content. We can have:
- About the role (company overview, mission, values, How We Put You First maybe part of Benefits? Actually benefits listed there: "In addition to your competitive salary, we offer market-leading benefits and perks:" then list benefits. That's benefits content. So we could put that under Benefits section.
- Responsibilities: from "What You'll Do".
- Requirements: maybe "5+ years of experience in employee benefits..." etc.
- Qualifications: maybe "Working knowledge of group health and welfare plans..." etc.
- Skills: maybe "Skilled at translating complex benefits concepts..." etc.
But we need to avoid duplication. Let's extract each piece.
First, About the role/company:
"This is an in-person role in Kansas City Curious about a career with NorthPoint? NorthPoint is a real estate developer that has grown through combining an entrepreneurial spirit and empowerment of its team members. We are looking for a Benefits Concierge Specialist to join our Human Resources team in Kansas City! NorthPoint provides an inclusive environment that cultivates collaboration and mentorship. Our core values set the foundation of our culture and guide us in every business decision. “We truly believe, and I’m convinced, we have some pretty incredible assets. But those assets have all come from our people.” - Nathaniel Hagedorn | CEO."
That's about the company and role.
Then "How We Put You First At NorthPoint Development we ask a lot of our employees, which is why we give so much in return. In addition to your competitive salary, we offer market-leading benefits and perks:" then list benefits.
Thus Benefits section content: list of benefits.
Responsibilities: bullet list under "What You'll Do".
Requirements/Qualifications/Skills: from "Who You Are" and "Preferred Experience".
Let's extract "Who You Are":
- A warm, empathetic people person who's just as comfortable heads-down in a spreadsheet as across the table from a teammate
- 5+ years of experience in employee benefits, benefits administration, HR, or a related field (HR, insurance/brokerage, or healthcare/medical backgrounds all welcome)
- Working knowledge of group health and welfare plans and applicable regulations (ERISA, ACA, HIPAA, COBRA, FMLA, Section 125)
- Experienced with benefits billing reconciliation and vendor management
- Skilled at translating complex benefits concepts into plain language employees can actually use
- Detail-oriented and comfortable juggling multiple deadlines
- Proficient in HRIS platforms and Microsoft Office
- Discreet with confidential and sensitive employee information
Preferred Experience:
- Familiarity with self-funded medical plans
- Prior experience supporting benefits compliance and required notice distribution
- A clinical, patient advocacy, or medical claims background
We could map:
- Requirements: maybe the mandatory items: 5+ years experience, working knowledge, experienced with benefits billing, skilled at translating, detail-oriented, proficient in HRIS/MS Office, discreet.
- Qualifications: maybe the warm empathetic people person? Or we could treat that as Skills? Actually "warm, empathetic people person" is a trait/skill.
- Skills: maybe the same as above? Might be overlapping.
Given instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section maybe "Requirements & Qualifications". But headings are prescribed; we can still use them but if content is thin we should avoid. However we have enough content for each.
Let's assign:
- About the role: company description.
- Responsibilities: What You'll Do list.
- Requirements: 5+ years experience, working knowledge, experienced with benefits billing, skilled at translating, detail-oriented, proficient in HRIS/MS Office, discreet.
- Qualifications: warm empathetic people person? Actually that's more of a skill/trait. Could be under Skills.
- Skills: maybe the same as above? Hmm.
Better: Use Requirements for experience and knowledge, Qualifications for education/training? Not given. Could skip Qualifications if not specific. But we have "Preferred Experience" which could be under Qualifications? Or we could make a "Preferred Qualifications" section but not in list. The instruction only allows those headings; we could still use Qualifications for preferred experience.
Skills: maybe the soft skills like warm empathetic people person, detail-oriented, comfortable juggling multiple deadlines, discreet.
But we already used detail-oriented etc in Requirements. Might duplicate.
Let's think: We can structure as:
- About the role (company overview)
- Responsibilities
- Requirements (mandatory experience/knowledge)
- Qualifications (preferred experience)
- Skills (soft skills and technical proficiency)
- Benefits
- Pay (not mentioned besides "competitive salary" but no specifics; we should not create Pay section unless posting actually states them. It says "In addition to your competitive salary" but no amount or range. That's not specific; we should not create Pay section.
- Schedule: not mentioned (in-person role in Kansas City but no schedule details). So skip.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
Now we need to format:
About the role
... (prose)
ThenResponsibilities
- ... each duty
- ...)
Benefits
- ... each benefit