STORE MANAGER - 21 and older only - BATTLE MOUNTAIN, NV
Dollar General · Battle Mountain, NV · 1 mo ago
On-siteBusiness DevelopmentFull-time
We need to output HTML fragment with sections for headings where there is content. The posting includes: Company Overview (maybe not needed as heading? It's a section). Job Details includes GENERAL SUMMARY, DUTIES and ESSENTIAL JOB FUNCTIONS, Qualifications (with subparts KNOWLEDGE and SKILLS, WORK EXPERIENCE and/or EDUCATION, COMPETENCIES), WORKING CONDITIONS and PHYSICAL REQUIREMENTS. Also there is an equal opportunity employer line which we should remove (boilerplate). Also there is "#CC#" maybe ignore.
We need to use for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can use other headings if they match content? The instruction says use
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can use other headings if they match content? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those specific headings, but we can also use other headings if they match? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those headings when applicable. However the posting has sections like "Company Overview", "Job Details", "GENERAL SUMMARY", "DUTIES and ESSENTIAL JOB FUNCTIONS", "Qualifications", "WORKING CONDITIONS and PHYSICAL REQUIREMENTS". We need to map to allowed headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use for section headings (e.g., those). Probably we should use those headings where appropriate. For example, "About the role" could correspond to GENERAL SUMMARY. "Responsibilities" corresponds to DUTIES. "Requirements" could correspond to Qualifications (knowledge/skills, experience). "Skills" could be part of Qualifications. "Benefits", "Pay", "Schedule" not present, so we should not include those sections.
We also need to include a section ONLY when the posting has real, specific content for it. So we will include About the role (GENERAL SUMMARY), Responsibilities (DUTIES), Requirements (Qualifications), maybe Skills (but we can incorporate into Requirements). Since they said prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Requirements section. But they said use headings like Qualifications, Skills. Might be okay to have both if content distinct. However we have knowledge and skills, work experience, competencies. Could split into Requirements (knowledge/skills + experience) and Skills (competencies). But better to follow instruction: Use headings for those categories if content exists. Let's see:
- About the role: GENERAL SUMMARY.
- Responsibilities: DUTIES and ESSENTIAL JOB FUNCTIONS.
- Requirements: KNOWLEDGE and SKILLS + WORK EXPERIENCE and/or EDUCATION.
- Skills: COMPETENCIES (maybe).
- Benefits, Pay, Schedule: not present, omit.
Also we might include Company Overview? Not in the list of headings, but could be considered "About the role"? Actually Company Overview is about the company, not the role. The instruction didn't list company overview as a heading, but we could still include it as a section? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could include Company Overview as a as well, but it's not in the examples. However they said "Prefer a few substantive sections over many thin ones." Including Company Overview may be okay. But the instruction about headings may be just examples, not exclusive. I'd include Company Overview as a heading.
We must not repeat the job title as a heading (the page already shows it). No job title given in snippet, but we won't add.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: equal opportunity employer line, maybe also the "#CC#". Also remove navigation/cookie etc. Not present.
We must preserve ALL substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
Company Overview
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to use those headings when applicable. However the posting has sections like "Company Overview", "Job Details", "GENERAL SUMMARY", "DUTIES and ESSENTIAL JOB FUNCTIONS", "Qualifications", "WORKING CONDITIONS and PHYSICAL REQUIREMENTS". We need to map to allowed headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use for section headings (e.g., those). Probably we should use those headings where appropriate. For example, "About the role" could correspond to GENERAL SUMMARY. "Responsibilities" corresponds to DUTIES. "Requirements" could correspond to Qualifications (knowledge/skills, experience). "Skills" could be part of Qualifications. "Benefits", "Pay", "Schedule" not present, so we should not include those sections.
We also need to include a section ONLY when the posting has real, specific content for it. So we will include About the role (GENERAL SUMMARY), Responsibilities (DUTIES), Requirements (Qualifications), maybe Skills (but we can incorporate into Requirements). Since they said prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Requirements section. But they said use headings like Qualifications, Skills. Might be okay to have both if content distinct. However we have knowledge and skills, work experience, competencies. Could split into Requirements (knowledge/skills + experience) and Skills (competencies). But better to follow instruction: Use headings for those categories if content exists. Let's see:
- About the role: GENERAL SUMMARY.
- Responsibilities: DUTIES and ESSENTIAL JOB FUNCTIONS.
- Requirements: KNOWLEDGE and SKILLS + WORK EXPERIENCE and/or EDUCATION.
- Skills: COMPETENCIES (maybe).
- Benefits, Pay, Schedule: not present, omit.
Also we might include Company Overview? Not in the list of headings, but could be considered "About the role"? Actually Company Overview is about the company, not the role. The instruction didn't list company overview as a heading, but we could still include it as a section? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could include Company Overview as a as well, but it's not in the examples. However they said "Prefer a few substantive sections over many thin ones." Including Company Overview may be okay. But the instruction about headings may be just examples, not exclusive. I'd include Company Overview as a heading.
We must not repeat the job title as a heading (the page already shows it). No job title given in snippet, but we won't add.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: equal opportunity employer line, maybe also the "#CC#". Also remove navigation/cookie etc. Not present.
We must preserve ALL substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
Company Overview
for section headings (e.g., those). Probably we should use those headings where appropriate. For example, "About the role" could correspond to GENERAL SUMMARY. "Responsibilities" corresponds to DUTIES. "Requirements" could correspond to Qualifications (knowledge/skills, experience). "Skills" could be part of Qualifications. "Benefits", "Pay", "Schedule" not present, so we should not include those sections.
We also need to include a section ONLY when the posting has real, specific content for it. So we will include About the role (GENERAL SUMMARY), Responsibilities (DUTIES), Requirements (Qualifications), maybe Skills (but we can incorporate into Requirements). Since they said prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Requirements section. But they said use headings like Qualifications, Skills. Might be okay to have both if content distinct. However we have knowledge and skills, work experience, competencies. Could split into Requirements (knowledge/skills + experience) and Skills (competencies). But better to follow instruction: Use headings for those categories if content exists. Let's see:
- About the role: GENERAL SUMMARY.
- Responsibilities: DUTIES and ESSENTIAL JOB FUNCTIONS.
- Requirements: KNOWLEDGE and SKILLS + WORK EXPERIENCE and/or EDUCATION.
- Skills: COMPETENCIES (maybe).
- Benefits, Pay, Schedule: not present, omit.
Also we might include Company Overview? Not in the list of headings, but could be considered "About the role"? Actually Company Overview is about the company, not the role. The instruction didn't list company overview as a heading, but we could still include it as a section? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could include Company Overview as a as well, but it's not in the examples. However they said "Prefer a few substantive sections over many thin ones." Including Company Overview may be okay. But the instruction about headings may be just examples, not exclusive. I'd include Company Overview as a heading.
We must not repeat the job title as a heading (the page already shows it). No job title given in snippet, but we won't add.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: equal opportunity employer line, maybe also the "#CC#". Also remove navigation/cookie etc. Not present.
We must preserve ALL substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
Company Overview
as well, but it's not in the examples. However they said "Prefer a few substantive sections over many thin ones." Including Company Overview may be okay. But the instruction about headings may be just examples, not exclusive. I'd include Company Overview as a heading.
We must not repeat the job title as a heading (the page already shows it). No job title given in snippet, but we won't add.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: equal opportunity employer line, maybe also the "#CC#". Also remove navigation/cookie etc. Not present.
We must preserve ALL substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
Company Overview
... content ...
About the role
... GENERAL SUMMARY ...
Responsibilities
- ... each duty ...
Requirements
Maybe split into two subsections? Could usefor prose and
- for lists.
We have KNOWLEDGE and SKILLS (list of abilities), WORK EXPERIENCE and/or EDUCATION (list), COMPETENCIES (list). Could combine into Requirements with subheadings? But we cannot add extra headings besides
- ... each bullet ...
- ...
- ...
- items? The instruction: Use
- for any list of duties/requirements/benefits. So we can treat each duty as a list item. The original text uses semicolons to separate multiple actions within a duty; we could keep them as part of the item. Simpler: each line before a semicolon that starts a new duty? But there are multiple sentences. Safer: treat each sentence that ends with a period as a duty. However some sentences have multiple actions separated by semicolons but still one duty. We'll keep each sentence as an item. Let's split by periods that end a sentence (but watch abbreviations like "etc." not present). We'll approximate. Sentences: 1. Recruit, select and retain qualified employees according to federal and state labor laws and company policies; ensure store is properly staffed. 2. Provide proper training for employees; conduct performance evaluations; identify gaps for appropriate solutions and/or counseling, up to and including termination. 3. Make recommendations regarding employee pay rate and advancement. 4. Communicate performance, conduct and safety expectations regularly; coordinate meetings and events to encourage safety, security and policies. 5. Ensure that the store is appropriately staffed and effectively opened and closed each day. Personally open the store a minimum of two times per week; personally close the store a minimum of two times per week. 6. Evaluate operating statements to identify business trends (including sales, profitability, and turn), expense control opportunities, potential shrink, and errors. 7. Order to ensure the meeting or exceeding of in-stock targets; review ordering plan, seasonal direction and inventory management issues on a weekly basis; follow up on Basic Stock Replenishment (BSR)/cycle counts. 8. Facilitate the efficient staging, stocking and storage of merchandise by following defined company work processes. 9. Ensure that all merchandise is presented according to established practices; utilize merchandise fixtures properly including presentation, product pricing and signage. 10. Maintain accurate inventory levels by controlling damages, markdowns, scanning, paperwork, and facility controls. 11. Ensure the financial integrity of the store through strict cashier accountability, key control, and adherence to stated company security practices and cash control procedures. 12. Provide superior customer service leadership. 13. Maintain a clean, well-organized store; facilitate a safe and secure working and shopping environment. 14. Ensure that store is adequately equipped with tools necessary to perform required tasks. 15. Follow company policies and procedures as outlined in the Standard Operating Procedures manual, Employee Handbook, and company communications; ensure employee compliance. 16. Complete all paperwork and documentation according to guidelines and deadlines. Note sentence 5 has two sentences: "Ensure that the store is appropriately staffed and effectively opened and closed each day." and "Personally open the store a minimum of two times per week; personally close the store a minimum of two times per week." We'll split into two items. Thus items: 5a. Ensure that the store is appropriately staffed and effectively opened and closed each day. 5b. Personally open the store a minimum of two times per week; personally close the store a minimum
? We could use but not allowed? Not specified. Safer to just use
and
- within Requirements.
We'll list knowledge and skills as
Requirements
Knowledge and Skills:
- ...
Work Experience and/or Education:
- ...
Skills
Competencies:
- ...