Receptionist/Corporate Support Specialist
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Summary (maybe About the role), Essential Duties And Responsibilities (Responsibilities), Qualifications (Education and/or Experience), Skills And Abilities (Skills). No explicit Benefits, Pay, Schedule. So we should not create those sections. Also we should not repeat job title as heading. Also we should not include metadata like Job ID, FLSA Status, Revised date? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short
for metadata like "Revised: 09/2026 FLSA Status: Non-Exempt". Probably we can include that as a paragraph after the heading? The page already shows job title; we can include a short paragraph for metadata. Also we need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO etc. There's none. We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide sections: About the role (maybe from Summary). Responsibilities (Essential Duties And Responsibilities). Requirements (Education And/or Experience). Qualifications maybe same as Requirements? Actually they have Qualifications heading then subheadings Education And/or Experience and Skills And Abilities. We could combine: Requirements (Education/Experience) and Skills (Skills And Abilities). The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have About the role, Responsibilities, Requirements, Qualifications, Skills. But Qualifications and Requirements may overlap. The posting has "Qualifications" heading with subparts Education And/or Experience and Skills And Abilities. So we could map: Requirements = Education And/or Experience, Qualifications = maybe same? But better to follow the posting: we could have Requirements (Education/Experience) and Skills (Skills And Abilities). The Qualifications heading could be omitted if we treat it as same as Requirements? But we need to include sections only when posting has real specific content. The posting has a "Qualifications" section with subparts. So we should include a Qualifications section. Inside that we could have subheadings? Not allowed; only use
for section headings. We could put the content under Qualifications as prose and lists. But we also have Skills And Abilities as a subheading under Qualifications. Could we treat Skills as separate section? The instruction says use headings for sections like ... Skills. So we could have a Skills section. Then Qualifications could contain Education And/or Experience. That seems reasonable.
Thus sections:
- About the role (from Summary)
- Responsibilities (Essential Duties And Responsibilities)
- Requirements (Education And/or Experience)
- Skills (Skills And Abilities)
We could also include Qualifications as a section containing Education And/or Experience, but then Skills separate. However that would duplicate. Let's read: The posting has "Qualifications" heading then under it "Education And/or Experience Required" and "Skills And Abilities". So we could treat Qualifications as the parent section, with two sub-sections: Education And/or Experience and Skills And Abilities. But we cannot create subheadings other than . So we could either make Qualifications section and inside it have two subheadings? That would be nested headings, but still . Might be okay but could be considered extra headings. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are top-level sections. So we should map each of those to a heading if content exists. So we will have headings: About the role, Responsibilities, Requirements, Qualifications, Skills. But we need to avoid duplication: Requirements and Qualifications both exist. The posting has Education And/or Experience under Qualifications. So we could put Education/Experience under Requirements, and Skills under Skills. Then Qualifications could be empty? Better to not have empty Qualifications. So maybe we treat Requirements as Education/Experience, Skills as Skills, and omit Qualifications heading. But the instruction says include a section ONLY when the posting has real, specific content for it. The posting does have a Qualifications section with content (Education And/or Experience and Skills And Abilities). So we need to include Qualifications. But we could split its content into two sub-sections: Requirements (Education/Experience) and Skills (Skills And Abilities) under Qualifications? That would be weird.
Alternative: Use Qualifications heading and inside it have two subheadings: Requirements and Skills. But then we would have headings: About the role, Responsibilities, Qualifications (with subheadings Requirements and Skills). That seems okay: we still have Qualifications as a heading, and inside we have more specific headings. The instruction didn't forbid nested headings, just said use for section headings (list). It didn't say only one level. So we can do:
About the role
...
Responsibilities
...
Qualifications
Requirements
...
Skills
...
But that would have two consecutive without content between them; maybe okay. However the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the headings we should use. So we should use exactly those headings, not add extra ones like Requirements under Qualifications. So we need to map content to those headings directly.
Thus we need to decide which content goes under each heading.
- About the role: Summary paragraph.
- Responsibilities: Essential Duties And Responsibilities.
- Requirements: Education And/or Experience Required.
- Qualifications: maybe we could put Skills And Abilities under Qualifications? But Skills is also a heading. Could combine Skills under Qualifications? But then we would not have a Skills heading. However the instruction says we can include a section ONLY when posting has real specific content for it. It does not require us to include all possible headings; we can omit Skills if we put its content under Qualifications. But then we lose the Skills heading. The instruction list includes Skills as an example heading, but not mandatory. So we could omit Skills heading and put skills under Qualifications. However the posting has a distinct "Skills And Abilities" subsection; it might be better to reflect that as a Skills heading. But then we would have both Qualifications and Skills headings, with Qualifications maybe empty or just containing Education/Experience. Could we put Education/Experience under Qualifications and Skills under Skills? That would leave Qualifications with only Education/Experience content, which is fine. Then we have both headings with content. That seems acceptable: Qualifications heading contains Education/Experience; Skills heading contains Skills And Abilities. The posting's Qualifications heading includes both, but we split them. Is that allowed? We are not inventing content; we are just dividing the existing content into two headings. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Splitting is okay as long as we preserve all info. It does not forbid splitting a section into multiple headings. So we can do that.
Thus final HTML:
About the role
Supports the Accounting Department, Sales Auditing team, and Corporate Office Operations; by auditing daily sales audit packets, validating retail transaction data, greeting corporate visitors, managing the central lobby, and completing other administrative and analytical duties as assigned. This position reports to the Sales Audit Manager.
Responsibilities
- Serves as the primary face of the corporate office, maintaining a welcoming lobby environment and greeting arriving clients, visitors, executives, and vendors.
- Manages central corporate communications, routing incoming telephone calls promptly and professionally to the correct internal departments.
- Handles logistics for corporate mail operations, sorting and distributing inbound mail, packages, and coordinating outbound courier deliveries.
- Provides general administrative and clerical backing to the corporate operations team, including data entry, archiving records, ordering office supplies, and managing conference room schedules.
- Audits daily sales from retail store networks to ensure transactional accuracy, verify documentation, and ensure company policies and compliance standards are being met.
- Identifies, researches, and reconciles data discrepancies, missing store documentation, and cash/sales variances by partnering directly with store managers and the auditing team.
- Maintains organized physical and digital files of audited store packets, audit tracking logs, and compliance spreadsheets.
- Perform other duties and special assignments as directed, including assignments that may be outside the primary area of employment.
Requirements
High school diploma required. An Associate’s degree in administration, accounting, finance, or a related field is preferred but not required. One to three (1–3) years of progressive professional experience in a receptionist, administrative support, data entry, or bookkeeping role. Prior experience supporting a finance or auditing unit is highly preferred. Experience in retail cashiering procedures, transaction reconciliation, or basic financial auditing is helpful.
Skills
- Mathematical Skills: 10-key data entry experience is required. Ability to calculate figures and amounts such as discounts, proportions, percentages, and apply concepts of basic algebra.
- Technical Skills: Proficient in personal computing skills and electronic communications, with specific intermediate proficiency in the Microsoft Office Suite (Word, Excel, Outlook).
- Reasoning Ability: Ability to solve practical problems and deal with a variety of concrete variables in situations where only limited standardization exists. Ability to interpret a variety of instructions furnished in written, oral, diagram, or schedule form.
- Communication Skills: Strong written and verbal communication skills, with the ability to deal effectively with all levels of management and corporate personnel.
- Interpersonal Dynamics: Experience working with a diverse workforce. Ability to work with individuals possessing developmental disabilities, dealing effectively with respect, sensitivity, and a customer-service mindset toward all employees and guests.
- Self-Management: Highly organized, detail-oriented, self-directed, and possesses the energy required to take on fast-paced, multi-tasking corporate work.
We should also maybe include Physical Demands? Not a heading in list; we could omit as not requested. The instruction only mentions those headings; we can omit Physical Demands. However we must preserve ALL substantive information. If we omit Physical Demands, we lose info. But the instruction says we should include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It didn't say we must include all possible headings; we can choose to include Physical Demands under a heading like "Requirements" or "About the role"? But it's not a standard 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 an exhaustive list; we could add other headings if needed, but they gave examples. It might be okay to add a Physical Demands section with Physical Demands
. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g
for prose. We need to decide sections: About the role (maybe from Summary). Responsibilities (Essential Duties And Responsibilities). Requirements (Education And/or Experience). Qualifications maybe same as Requirements? Actually they have Qualifications heading then subheadings Education And/or Experience and Skills And Abilities. We could combine: Requirements (Education/Experience) and Skills (Skills And Abilities). The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have About the role, Responsibilities, Requirements, Qualifications, Skills. But Qualifications and Requirements may overlap. The posting has "Qualifications" heading with subparts Education And/or Experience and Skills And Abilities. So we could map: Requirements = Education And/or Experience, Qualifications = maybe same? But better to follow the posting: we could have Requirements (Education/Experience) and Skills (Skills And Abilities). The Qualifications heading could be omitted if we treat it as same as Requirements? But we need to include sections only when posting has real specific content. The posting has a "Qualifications" section with subparts. So we should include a Qualifications section. Inside that we could have subheadings? Not allowed; only use
for section headings. We could put the content under Qualifications as prose and lists. But we also have Skills And Abilities as a subheading under Qualifications. Could we treat Skills as separate section? The instruction says use headings for sections like ... Skills. So we could have a Skills section. Then Qualifications could contain Education And/or Experience. That seems reasonable.
Thus sections:
- About the role (from Summary)
- Responsibilities (Essential Duties And Responsibilities)
- Requirements (Education And/or Experience)
- Skills (Skills And Abilities)
We could also include Qualifications as a section containing Education And/or Experience, but then Skills separate. However that would duplicate. Let's read: The posting has "Qualifications" heading then under it "Education And/or Experience Required" and "Skills And Abilities". So we could treat Qualifications as the parent section, with two sub-sections: Education And/or Experience and Skills And Abilities. But we cannot create subheadings other than . So we could either make Qualifications section and inside it have two subheadings? That would be nested headings, but still . Might be okay but could be considered extra headings. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are top-level sections. So we should map each of those to a heading if content exists. So we will have headings: About the role, Responsibilities, Requirements, Qualifications, Skills. But we need to avoid duplication: Requirements and Qualifications both exist. The posting has Education And/or Experience under Qualifications. So we could put Education/Experience under Requirements, and Skills under Skills. Then Qualifications could be empty? Better to not have empty Qualifications. So maybe we treat Requirements as Education/Experience, Skills as Skills, and omit Qualifications heading. But the instruction says include a section ONLY when the posting has real, specific content for it. The posting does have a Qualifications section with content (Education And/or Experience and Skills And Abilities). So we need to include Qualifications. But we could split its content into two sub-sections: Requirements (Education/Experience) and Skills (Skills And Abilities) under Qualifications? That would be weird.
Alternative: Use Qualifications heading and inside it have two subheadings: Requirements and Skills. But then we would have headings: About the role, Responsibilities, Qualifications (with subheadings Requirements and Skills). That seems okay: we still have Qualifications as a heading, and inside we have more specific headings. The instruction didn't forbid nested headings, just said use for section headings (list). It didn't say only one level. So we can do:
About the role
subheadings? That would be nested headings, but still . Might be okay but could be considered extra headings. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are top-level sections. So we should map each of those to a heading if content exists. So we will have headings: About the role, Responsibilities, Requirements, Qualifications, Skills. But we need to avoid duplication: Requirements and Qualifications both exist. The posting has Education And/or Experience under Qualifications. So we could put Education/Experience under Requirements, and Skills under Skills. Then Qualifications could be empty? Better to not have empty Qualifications. So maybe we treat Requirements as Education/Experience, Skills as Skills, and omit Qualifications heading. But the instruction says include a section ONLY when the posting has real, specific content for it. The posting does have a Qualifications section with content (Education And/or Experience and Skills And Abilities). So we need to include Qualifications. But we could split its content into two sub-sections: Requirements (Education/Experience) and Skills (Skills And Abilities) under Qualifications? That would be weird.
Alternative: Use Qualifications heading and inside it have two subheadings: Requirements and Skills. But then we would have headings: About the role, Responsibilities, Qualifications (with subheadings Requirements and Skills). That seems okay: we still have Qualifications as a heading, and inside we have more specific headings. The instruction didn't forbid nested headings, just said use for section headings (list). It didn't say only one level. So we can do:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are top-level sections. So we should map each of those to a heading if content exists. So we will have headings: About the role, Responsibilities, Requirements, Qualifications, Skills. But we need to avoid duplication: Requirements and Qualifications both exist. The posting has Education And/or Experience under Qualifications. So we could put Education/Experience under Requirements, and Skills under Skills. Then Qualifications could be empty? Better to not have empty Qualifications. So maybe we treat Requirements as Education/Experience, Skills as Skills, and omit Qualifications heading. But the instruction says include a section ONLY when the posting has real, specific content for it. The posting does have a Qualifications section with content (Education And/or Experience and Skills And Abilities). So we need to include Qualifications. But we could split its content into two sub-sections: Requirements (Education/Experience) and Skills (Skills And Abilities) under Qualifications? That would be weird.
Alternative: Use Qualifications heading and inside it have two subheadings: Requirements and Skills. But then we would have headings: About the role, Responsibilities, Qualifications (with subheadings Requirements and Skills). That seems okay: we still have Qualifications as a heading, and inside we have more specific headings. The instruction didn't forbid nested headings, just said use for section headings (list). It didn't say only one level. So we can do:
About the role
for section headings (list). It didn't say only one level. So we can do:
About the role
...
Responsibilities
- ...
Qualifications
Requirements
...
Skills
- ...
without content between them; maybe okay. However the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the headings we should use. So we should use exactly those headings, not add extra ones like Requirements under Qualifications. So we need to map content to those headings directly.
Thus we need to decide which content goes under each heading.
- About the role: Summary paragraph.
- Responsibilities: Essential Duties And Responsibilities.
- Requirements: Education And/or Experience Required.
- Qualifications: maybe we could put Skills And Abilities under Qualifications? But Skills is also a heading. Could combine Skills under Qualifications? But then we would not have a Skills heading. However the instruction says we can include a section ONLY when posting has real specific content for it. It does not require us to include all possible headings; we can omit Skills if we put its content under Qualifications. But then we lose the Skills heading. The instruction list includes Skills as an example heading, but not mandatory. So we could omit Skills heading and put skills under Qualifications. However the posting has a distinct "Skills And Abilities" subsection; it might be better to reflect that as a Skills heading. But then we would have both Qualifications and Skills headings, with Qualifications maybe empty or just containing Education/Experience. Could we put Education/Experience under Qualifications and Skills under Skills? That would leave Qualifications with only Education/Experience content, which is fine. Then we have both headings with content. That seems acceptable: Qualifications heading contains Education/Experience; Skills heading contains Skills And Abilities. The posting's Qualifications heading includes both, but we split them. Is that allowed? We are not inventing content; we are just dividing the existing content into two headings. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Splitting is okay as long as we preserve all info. It does not forbid splitting a section into multiple headings. So we can do that.
Thus final HTML:
About the role
About the role
Supports the Accounting Department, Sales Auditing team, and Corporate Office Operations; by auditing daily sales audit packets, validating retail transaction data, greeting corporate visitors, managing the central lobby, and completing other administrative and analytical duties as assigned. This position reports to the Sales Audit Manager.
Responsibilities
- Serves as the primary face of the corporate office, maintaining a welcoming lobby environment and greeting arriving clients, visitors, executives, and vendors.
- Manages central corporate communications, routing incoming telephone calls promptly and professionally to the correct internal departments.
- Handles logistics for corporate mail operations, sorting and distributing inbound mail, packages, and coordinating outbound courier deliveries.
- Provides general administrative and clerical backing to the corporate operations team, including data entry, archiving records, ordering office supplies, and managing conference room schedules.
- Audits daily sales from retail store networks to ensure transactional accuracy, verify documentation, and ensure company policies and compliance standards are being met.
- Identifies, researches, and reconciles data discrepancies, missing store documentation, and cash/sales variances by partnering directly with store managers and the auditing team.
- Maintains organized physical and digital files of audited store packets, audit tracking logs, and compliance spreadsheets.
- Perform other duties and special assignments as directed, including assignments that may be outside the primary area of employment.
Requirements
High school diploma required. An Associate’s degree in administration, accounting, finance, or a related field is preferred but not required. One to three (1–3) years of progressive professional experience in a receptionist, administrative support, data entry, or bookkeeping role. Prior experience supporting a finance or auditing unit is highly preferred. Experience in retail cashiering procedures, transaction reconciliation, or basic financial auditing is helpful.
Skills
- Mathematical Skills: 10-key data entry experience is required. Ability to calculate figures and amounts such as discounts, proportions, percentages, and apply concepts of basic algebra.
- Technical Skills: Proficient in personal computing skills and electronic communications, with specific intermediate proficiency in the Microsoft Office Suite (Word, Excel, Outlook).
- Reasoning Ability: Ability to solve practical problems and deal with a variety of concrete variables in situations where only limited standardization exists. Ability to interpret a variety of instructions furnished in written, oral, diagram, or schedule form.
- Communication Skills: Strong written and verbal communication skills, with the ability to deal effectively with all levels of management and corporate personnel.
- Interpersonal Dynamics: Experience working with a diverse workforce. Ability to work with individuals possessing developmental disabilities, dealing effectively with respect, sensitivity, and a customer-service mindset toward all employees and guests.
- Self-Management: Highly organized, detail-oriented, self-directed, and possesses the energy required to take on fast-paced, multi-tasking corporate work.