Jobs · OTHR · Kansas

Solid Waste Scale Lead #26-9-2

Leavenworth USD453 · Leavenworth, KS · 1 mo ago
OTHR$23.5/hrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Title, Working Title, Department, Pay Level, Exempt/Non-exempt, Supervisor, Supervises N/A, Location, Schedule (Tuesday-Friday 7:45 am to 4:15pm Saturday 7am to 3pm). Salary range: $23.50-$24.45. Also residency policy, scope, percentage of time/accountabilities, knowledge and skills, human relations. We need to map to sections. We should not repeat job title as heading. So we can have sections: About the role (maybe scope), Responsibilities (percentage of time/accountabilities, human relations?), Requirements (knowledge and skills?), Qualifications (maybe knowledge and skills?), Skills (maybe same as knowledge and skills?), Benefits (none given), Pay (salary range), Schedule (hours). Also maybe Location? Not a heading category; we could put location in About the role paragraph. We must not create sections with filler like "not specified". So only include sections where we have content. We have Pay: salary range given. So Pay section. Schedule: given hours. Benefits: none mentioned, so omit. About the role: we have scope description: "Serves as the lead customer service personnel who manages the daily scale operations and fee collections..." etc. Also location and maybe working title. Responsibilities: we have percentage of time/accountabilities list, also human relations tasks. Requirements: maybe knowledge and skills (required prior to employment). Qualifications: maybe same? But we should avoid duplication. Could combine knowledge and skills into Requirements or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple of those if content exists. We have knowledge and skills list (required prior to employment). That could go under Requirements or Qualifications or Skills. Since we have separate Skills heading, we could put the skill items under Skills. Requirements could be maybe "Must possess a high level of organization and communication skills. Ability to deal with disgruntled customers." etc. But those are also in scope. Better: Use Requirements for mandatory prerequisites (knowledge and skills). Use Skills for maybe the skill list? But they overlap. To avoid thin sections, we could combine into one section like Requirements and put both knowledge and skills there, and omit Skills heading. Or we could have Requirements (knowledge) and Skills (skill items). Let's see content: Knowledge and skills (*Required prior to employment) list includes both knowledge and skill items. So we could treat that as Requirements (knowledge) and Skills (skill). But the list includes both knowledge and skill items; splitting may be artificial but okay. We also have Human Relations list (tasks/duties). Could go under Responsibilities. Percentage of time/accountabilities also responsibilities. Thus: - About the role: brief paragraph summarizing role, location, working title, department, supervisor. - Responsibilities: combine percentage of time/accountabilities and human relations tasks (maybe as bullet list). Also scope tasks. - Requirements: knowledge items (maybe the knowledge bullet points). Could be bullet list. - Skills: skill items (the skilled bullet points). Could be bullet list. - Pay: salary range. - Schedule: hours. We must not include boilerplate like residency policy, etc. That's not in headings; we could include residency policy in About the role? It's not directly about role but could be considered extra info. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Residency policy is not boilerplate? It's a policy but not about the job? It's substantive? Might be considered relevant to eligibility. However, we have no heading for it; we could embed in About the role paragraph as a note. But it's lengthy. Might be considered substantive; we should preserve it. Could put in a

under About the role. But we must not create sections with filler. So we can include residency policy as a paragraph. Also note about "County Employees Only: May apply at..." etc is application instruction; we should remove that. Also "This position closes when filled" is boilerplate; remove. Also "NOTE: Scavenging of solid waste is strictly prohibited..." that's a policy note; could be included under Responsibilities or About the role. We need to preserve all substantive information, but we can remove application instructions and boilerplate. The residency policy is substantive; we keep. Let's extract details: Job posting text includes duplicate sections: Title, Working Title, Department, Pay Level, Exempt/NON-EXEMPT, Supervisor, Supervises N/A, Location, Schedule. We have: - Position: Solid Waste Scale Lead - Working Title: Scale/Office Manager - Department: Solid Waste - Pay Level: Level C (also Step 11 to 13) - Exempt/Non-Exempt: N (Non-exempt) - Supervisor: Director/SW Lead Manager - Supervises: N/A - Location: Leavenworth County Transfer Station, 24967 136th St., Lansing, KS 66043 - Schedule: Tuesday-Friday 7:45 am to 4:15pm Saturday 7am to 3pm - Salary: $23.50-$24.45 Also Pay Level: Level C Step 11 to 13. We also have "County Employees Only: May apply at the Human Resources Department..." remove. Residency policy paragraph. Scope paragraph. Percentage of time/accountabilities list. Knowledge and skills list (with *Required prior to employment). Human relations list. Note about scavenging. We need to output HTML fragment only. Let's craft:

About the role

The Solid Waste Scale Lead (Working Title: Scale/Office Manager) serves as the lead customer service personnel managing daily scale operations and fee collections at the Leavenworth County Transfer Station (24967 136th St., Lansing, KS 66043). The role reports to the Director/SW Lead Manager, is non‑exempt, and falls under Pay Level C (Step 11‑13). Responsibilities include overseeing scale operations, training and accountability for scales, handling customer inquiries by phone and in person, directing customers to recycling, bays, and dumping zones, maintaining accurate monetary records, preparing daily deposits and balance receipts, posting fees to commercial accounts, handling billing and collections on late accounts, managing purchase orders, working with Accounts Payable, keeping the Transfer Station webpage current, and ensuring compliance with policies prohibiting scavenging. The position also requires adherence to the county residency policy, which defines residency as the primary residence and includes adjacent counties (Wyandotte, Johnson, Douglas, Jefferson, Atchison in Kansas and Platte County, Missouri), with possible department‑specific exceptions requiring BOCC approval.

That covers scope, location, supervisor, pay level, residency policy, note about scavenging. Now Responsibilities: we can use bullet list from percentage of time/accountabilities and human relations. Let's combine:
  • Managing the solid waste office supply inventory (5% of time)
  • Handling customer service calls and in‑person inquiries (55%)
  • Managing monetary funds, preparing deposit receipts, and posting account fees (30%)
  • Preparing department level transaction records and profitability reports (5%)
  • Maintaining an organized, clean, safe work environment (5%)
  • Working closely with director, facility lead, scale operator, solid waste heavy equipment operators, and customers during scheduled shifts
  • Communicating clearly and concisely in person, on the phone, and over the radio
  • Discussing customer accounts, reading financial reports, and checking customer fee assessments
  • Communicating daily with (text cut off) – but we have incomplete sentence: "Communicate daily with". The original text ends abruptly: "Communicate daily with". Probably it's incomplete; we should not invent. We have to preserve exactly as given? The text: "4\. Communicate daily with". It's incomplete; we should keep as is? It's a fragment; we should not invent completion. We'll include as "Communicate daily with". Might be weird but it's what's given. We'll keep it as a bullet.
But we need to avoid incomplete bullet? It's part of the posting; we should keep it. Now Requirements: knowledge items (the ones with *Required prior to employment). Let's list them as bullet list. Knowledge items: 1. Knowledge of industry terminology, solid waste principles, practices, and procedures. 2. Knowledge of book keeping and monetary transaction receipts and account ledgers.* 3. Knowledge of scale software and accounting software. 4. Knowledge to follow solid waste management policies and protocols for permitting and compliance. 5. Knowledge to follow safety procedures, and requirements associated with the duties as assigned. 6. Knowledge to use a two-way radio. We'll output as
  • ...
. Now Skills: skilled items: 7. Skilled in oral and written communication to customers and operations manager.* 8. Skilled in quickly and accurately providing monetary mathematical computations.* 9. Skilled in preparing departmental profitability reports. We'll output as bullet list. Now Pay:

Pay

$23.50‑$24.45 per hour (Level C, Step 11‑13)

Schedule:

Schedule

Tuesday‑Friday: 7:45 am – 4:15 pm; Saturday: 7:00 am – 3:00 pm

We should not include Benefits section. We must not repeat job title as heading; we didn't. We must not put Job ID/requisition numbers as headings; we didn't. We must not include application instructions; we removed. We must not include duplicated lines; we avoided. Now output only HTML fragment. Check for any missing substantive info: we omitted "EXEMPT/NON-EXEMPT: N" but we mentioned non-exempt in About the role. Good. We omitted "SUPERVISES: N/A" - not needed. We omitted "WORKING TITLE: Scale/Office Manager" included. We omitted "DEPARTMENT: Solid Waste" included. We omitted "PAY LEVEL: Level C" included. We omitted "LOCATION: ..." included. We omitted "RESIDENCY POLICY" included. We omitted "SCOPE" included. We omitted "PERCENTAGE OF TIME /ACCOUNTABILITIES" included. We omitted "KNOWLEDGE AND SKILLS" split. We omitted "HUMAN RELATIONS" included. We omitted "NOTE: Scavenging of solid waste is strictly prohibited and is against Department policy." included in About the role. We omitted "This position closes when filled" removed. We omitted "County Employees Only: May apply at..." removed. We omitted "General Public: May apply at the Leavenworth Workforce Center..." removed. We omitted "EMAIL applications to hr@leavenworthcounty.gov or fax the application to (913) 684-10" removed. We omitted "Application may be found on the Leavenworth County website at www.leavenworthcounty.gov" removed. We omitted duplicate lines. All good. Now ensure proper HTML escaping for special characters like &, <, >. We have ampersand in "Scale/Office Manager"? No. We have "$23.50‑$24.45" includes an en dash; we can keep as is. Use plain hyphen? We'll keep as "-". Use regular

Similar jobs

Warehouse Lead (357)

ABC Supply Co. Inc.Chesapeake, VA· 2 wk ago
Manufacturing$24–$27/hrapply on abcsupply.wd1.myworkdayjobs.com

Warehouse Lead

BrameCharlotte, NC· 3 wk ago
Management$19–$21/hrapply on workforcenow.adp.com

Warehouse Lead

CJ Logistics AmericaBethlehem, PA· 1 mo ago
Management$24.96/hrapply on jobs.jobvite.com

Warehouse Lead

Williams-Sonoma, Inc.Braselton, GA· 1 mo ago
Manufacturingapply on wssupplychain.applicantstack.com

Warehouse Lead

Heartland Coca-ColaConcordia, KS· 1 mo ago
Management$22.5/hrapply on conaservices.jobs2web.com

Warehouse Lead

Kenco GroupZeeland, MI· 1 mo ago
Managementapply on kencogroup.wd12.myworkdayjobs.com