Senior Parts Storekeeper - Hetch Hetchy Water & Power (Moccasin) - SFPUC (1931) Exempt

We need to output HTML fragment with sections only if real content. Remove boilerplate. Keep substantive info: About the role? The posting includes "WHO ARE WE?" description of SFPUC. That's about organization, could be "About the role"? Actually "About the role" is not present; we have "WHO ARE WE?" describing organization. Could treat as "About the organization" but headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to appropriate headings. We have: - Role Description: Reporting Location, Project, Position Description, Essential Duties And Responsibilities (list). That's responsibilities. - Supplemental Information: physical demands, hazards, equipment, shifts, training. - How To Qualify: Experience, License, Verification etc. That's qualifications/requirements. - Benefits? Not mentioned. Pay? Not mentioned. Schedule? Not mentioned (though mentions rotating shifts, weekends, holidays). That's schedule info: "May be required to work rotating shifts, weekends and holidays." That's schedule detail. So we can include Schedule section. - Benefits: Not mentioned. So omit. - Pay: Not mentioned. Omit. - Skills: Not explicit; maybe we can infer but better not invent. So omit Skills. - About the role: Could use "About the role" heading for the WHO ARE WE? and Role Description? Actually "About the role" could include description of role and organization. But we already have Responsibilities separate. Could put organization description under "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (organization overview), Responsibilities (duties), Requirements (maybe experience/license), Qualifications (maybe same as Requirements? Might be redundant). Actually they list both Requirements and Qualifications as possible headings. We need to decide what to put where. The posting has "How To Qualify" with Experience and License. That's qualifications. Also "Verification Of Education And Experience" etc. That's also qualifications. Could treat as Qualifications. Requirements could be things like "Must have valid California driver license" etc. But we can combine. Better: Use sections: - About the role: includes WHO ARE WE? description of SFPUC and maybe role location/project. - Responsibilities: Essential Duties And Responsibilities (list). - Requirements: maybe the supplemental info? Actually requirements often are experience, license. But we have Qualifications separate. Let's assign: - Requirements: Experience (3 years) and License (valid CA driver license). Could also include ability to lift 60 lbs, operate equipment, work rotating shifts etc. Those are more like job demands. - Qualifications: maybe verification process etc. But that's not a qualification per se. Could skip Qualifications if not distinct. Given instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section called "Requirements" (or "Qualifications"). But we need to pick headings from list; we can use both if we have content. We have content for: - About the role (organization description, reporting location, project) - Responsibilities (list of duties) - Requirements (experience, license, physical demands, shift work, training) - Schedule (rotating shifts, weekends, holidays) - but that's already in requirements; maybe we can put schedule separate. But to avoid thin sections, we could put schedule info within Requirements. However schedule is a distinct heading allowed; but if we put schedule separate, we need to ensure it has real content. It does: "May be required to work rotating shifts, weekends and holidays." That's schedule. So we can have Schedule section. Benefits: none. Pay: none. Skills: none. Thus sections: About the role, Responsibilities, Requirements, Schedule. Now we need to format lists with

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc as headings; fold minor metadata into short

  or drop it. So we can drop Application Opening date, Filing Deadline, Recruitment ID, APPOINTMENT TYPE etc? Those are minor metadata; we can fold into a short

  maybe under About the role? But 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 paragraph with that info, maybe after About the role. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip all the "How To Apply", "Job Analyst Information", EEO statement, etc. We must keep substantive info: organization description, reporting location, project, essential duties, supplemental info, experience, license, verification notes? The verification notes are procedural; maybe considered boilerplate? It's about application process; but it's not exactly boilerplate; it's about verification of education and experience. Might be considered part of "How To Qualify". The instruction says remove application instructions. The verification notes are part of qualification process; but they are more about how to verify. Might be considered application instructions. Safer to drop them? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop the verification notes and "How To Qualify" procedural text, but keep the actual qualifications (experience, license). The "How To Qualify" heading itself is procedural; we can drop that heading but keep the bullet points of experience and license. Similarly, "Supplemental Information" is substantive (physical demands, hazards, equipment, shifts, training). Keep that. Now craft HTML. We'll start with a short paragraph for metadata: maybe include Application Opening, Filing Deadline, Recruitment ID, Appointment Type. Could be one

  . Then

  About the role

  with paragraphs: WHO ARE WE? description, plus Reporting Location and Project. We need to preserve all substantive info: So include the SFPUC description: headquartered, employees, customers, mission, vision, award-winning, infrastructure, workforce, links? We should keep the links? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The links are part of the description; we should keep them as plain text? Probably keep them as plain text URLs. Not as links? The output is HTML fragment; we could keep them as plain text or as tags? The instruction didn't forbid links; but we should preserve the URLs. Safer to keep as plain text. Thus include: "Headquartered in San Francisco, we have 2,300 employees operating across eight counties serving more than 2.7 million customers in the San Francisco Bay Area – 24 hours per day, 365 days per year. Our Mission: To provide our customers with high quality, efficient, and reliable water, power, and wastewater services in a manner that values environmental and community interests and sustains the resources entrusted to our care. Our Vision: We are an innovative utility leader, recognized for excellent results in service, safety, stewardship, and inclusiveness. We are an award-winning and industry-leading utilities organization committed to our customers, community interests, and the environment. To learn more about our organization, please visit our website at https://www.sfpuc.gov . We are proud of our infrastructure and programs, but most importantly, we value our highly qualified and dedicated workforce which ensures that this vision becomes a reality. To learn more about working at the SFPUC, visit our career site at https://www.sfpuc.gov/about-us/careers-sfpuc" Then Reporting Location and Project: "Reporting Location: Moccasin is located 140 miles east of the San Francisco Bay Area and requires a 5-hour round trip commute by car in fair weather. Project: Health and Safety Program Procurement Project" We can combine into paragraphs. Next

  Responsibilities

  with
  • list of essential duties. Need to capture all duties from the list. Let's extract them: - Plans, assigns, supervises, reviews and evaluates the work of subordinate personnel engaged in ordering, receiving, inspecting, rotating, storing, inventorying, and issuing of automotive and/or transit parts and related materials. - Coordinates storeroom operations with inventory control staff of a materials management system, purchasing and user departmental personnel and vendors to maintain established levels of inventories; plans and coordinates the storage and issuance of inventories and insures proper rotation of stock. - Initiates orders to replenish inventories or to acquire as needed non-inventoried parts and related materials; contacts vendors regarding specifications, prices, and delivery particulars, and places orders as authorized; arranges for the disposal of obsolete or surplus inventories. - Oversees the receipt and inspection of automotive, transit, electrical, waterworks parts, and/or related materials from vendors; ensures conformance with ordered specifications and receiving documents; coordinates with vendors, freight carriers, technicians, and purchasing and inventory control personnel to resolve discrepancies; coordinates the return of defective or repairable inventories to vendors or other facilities. - Assists inventory control staff in the periodic and as-required inventorying of storeroom stocks and in the validating of stock location records. - Ensures the safety, orderliness, and security of storeroom inventories, facilities and equipment. - Oversees the maintenance of required files in the storeroom and the proper distribution of stores documents such as requisitions, purchase and delivery orders, packing slips, bills of lading, freight bills, shipping and issue documents, and materials safety data sheets. - Trains storeroom personnel in general storeroom practices, automotive, transit, electrical, waterworks parts and/or related materials, support operations, facilities and equipment safety, and hazardous materials handling. - Supervises and trains storeroom personnel in the use of an automated materials management system. - Operates light vehicles and related materials handling equipment in the performance of assigned responsibilities. We must keep all that. Next

    Requirements

    with list: Experience (3 years as automotive/transit parts storekeeper in storeroom/warehouse with duties receipt, inspection, rotation, storage, inventory, ordering, issuing of large quantities of wide variety of automotive/transit parts and related equipment and materials). License: Possession of a valid California driver license. Also supplemental info: May require lifting of heavy equipment, parts, and materials up to sixty (60) pounds. May involve possible exposure to hazardous materials such as diesel fumes, cleaning solvents, dust, adhesives, herbicides, and aerosols. Requires the operation of hand tools and power equipment used in materials handling, such as pallet jacks, crow bars, and forklifts. May be required to work rotating shifts, weekends and holidays. All appointees to the position will be required to participate in the National Safety Council Forklift Truck Operators training course, conducted by the department. We could split schedule info into Schedule section, but we already have schedule info here. To avoid duplication, we could put schedule info in Schedule section and keep other physical demands in Requirements. Thus Requirements: Experience, License, lifting, exposure to hazardous materials, operation of hand tools/power equipment. Schedule: May be required to work rotating shifts, weekends and holidays. All appointees will be required to participate in the National Safety Council Forklift Truck Operators training course. But the training course is not schedule; it's a requirement. Could keep in Requirements. Better: Keep schedule separate: "May be required to work rotating shifts, weekends and holidays." That's schedule. Training course maybe also a requirement; we can keep in Requirements. Thus: Requirements list: - Experience: Three (3) years of experience as an automotive/transit parts storekeeper in a storeroom or warehouse, in which the duties consisted of receipt, inspection, rotation, storage, inventory