Lead Purchasing Agent
Kitsap Mental Health Services · Bremerton, WA · 5 days ago
On-sitePurchasing$27.16–$33.94/hrPart-time
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules.
First, I need to identify the sections:
- About the role (introductory paragraph)
- Responsibilities (Primary Responsibilities list)
- Requirements (Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite-Specific Requirements, Equipment Operated, Work Environment, Mental/Physical Requirements)
- Benefits (Benefits at a Glance)
- Pay (Hiring Range)
- Schedule (Full-Time, On-Site in Bremerton, WA)
I should not repeat the job title as a heading. The job title is "Lead Purchasing Agent" but the page already shows it, so I won't include it as a heading.
I need to use for section headings,
for section headings, - for lists,
for prose.
I must include a section ONLY when there's real, specific content. No filler.
Let me structure:
1. About the role: The introductory paragraph about KMHS seeking a Lead Purchasing Agent.
2. Responsibilities: The Primary Responsibilities list.
3. Requirements: This has multiple subsections. I could combine Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite-Specific Requirements, Equipment Operated, Work Environment, Mental/Physical Requirements under a Requirements heading, but they are distinct. The rules say use
for section headings like "Requirements". I could have one Requirements section with sub-lists, but the example headings include "Requirements" as a single heading. However, the content has multiple categories. I'll create a Requirements section with subsections using ? But the rules only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid , but to keep it simple, I'll use for each major section. However, "Requirements" is one heading, but there are subcategories. I could make separate for Minimum Qualifications, Preferred Qualifications, etc. But the example list includes "Qualifications" as a possible heading. I think it's better to have a "Requirements" heading and then use with nested lists or separate ? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It suggests those are the typical section headings. I'll create sections for each distinct category: Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But that might be too many thin sections. The rule: "Prefer a few substantive sections over many thin ones." So I should group related items.
Let me group:
- Requirements: Minimum Qualifications, Preferred Qualifications, Performance Requirements (Knowledge, Skills, Abilities)
- Worksite Requirements: Worksite-Specific Requirements
- Equipment & Environment: Equipment Operated, Work Environment
- Physical Requirements: Mental/Physical Requirements
But the rule says include a section ONLY when the posting has real, specific content. All these have content.
I'll create:
- About the role
- Responsibilities
- Requirements (with subsections)
- Benefits
- Pay
- Schedule
But the example headings include "Qualifications" and "Skills" separately. I could split Requirements into Qualifications and Skills. However, the posting has "Minimum Qualifications", "Preferred Qualifications", "Performance Requirements" which includes Knowledge, Skills, Abilities. I'll make a "Qualifications" section for education/experience, and a "Skills" section for the performance requirements? But the performance requirements include knowledge, skills, abilities. Might be better to have a "Requirements" section that includes all.
I'll do:
About the role
...
Responsibilities
...
Requirements
Minimum Qualifications
...
Preferred Qualifications
...
Performance Requirements
...
Worksite Requirements
...
Equipment Operated
...
Work Environment
...
Physical Requirements
...
But the rule says use for section headings. It doesn't say I can't use . However, to be safe, I'll use for each major section and maybe combine some. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the top-level sections. I'll use for each of those that apply. For subsections, I could use or just bold text. But the output should be semantic HTML. I think using is fine.
But the user said "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with headings.
Let me parse the content.
First, the job posting starts with "Full-Time, On-Site in Bremerton, WA Hiring Range: $27.16 – $33.94 Per Hour Benefits at a Glance ..." That's metadata: schedule, pay, benefits.
Then "Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations..." That's about the role.
Then "Primary Responsibilities:" list.
Then "Minimum Qualifications:" with EDUCATION and EXPERIENCE, plus driving requirements.
Then "Preferred Qualifications:" with EDUCATION and EXPERIENCE.
Then "Performance Requirements:" with KNOWLEDGE, SKILLS, ABILITIES.
Then "Worksite-Specific Requirements:" with checkboxes.
Then "Equipment Operated:" list.
Then "Work Environment:" description.
Then "Mental/Physical Requirements:" list.
Then EEO boilerplate at the end which should be removed.
Now, I need to create sections:
- About the role: the paragraph describing the role.
- Responsibilities: the bullet list.
- Requirements: I'll include Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But to avoid many thin sections, I'll group under Requirements with subheadings.
- Benefits: the Benefits at a Glance list.
- Pay: the hiring range.
- Schedule: Full-Time, On-Site in Bremerton, WA.
The schedule and pay are given at the top. I'll include them as sections.
Now, I must not include Job ID / requisition numbers. There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The last paragraph about recruitment processes is EEO boilerplate, so remove.
Now, write HTML.
I'll start with About the role
Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations. This position helps ensure departments have the supplies, equipment, and services needed to support daily operations across the organization. The role provides leadership for purchasing functions while maintaining efficient procurement processes and strong vendor relationships. If you're committed to supporting agency operations through effective purchasing and inventory management, we welcome your application.
Responsibilities
- Identify primary and secondary vendors and evaluate sources for materials and services.
- Maintain quality standards while supporting cost-effective purchasing practices.
- Serve as a liaison between departments and vendors.
- Maintain timely communication with departments regarding purchasing needs and order status.
- Coordinate and complete required agency and departmental trainings.
- Implement efficiencies and process improvements within the Purchasing Department.
- Assist with receiving, unpacking, and distributing inbound packages and deliveries.
- Provide receiving documentation to the Accounting Department.
- Manage inventory levels for Purchasing Department stock items, office supplies, and copy paper.
- Distribute stock items and copy paper throughout campus locations as needed.
- Assist with sourcing, negotiating, and procuring materials and services.
- Facilitate vehicle maintenance and operational status in conjunction with the Facility Department.
- Foster positive relationships with staff, vendors, and visitors through professional communication and customer service.
- Ensure purchased products meet applicable safety and regulatory requirements.
- Oversee Purchasing Department staff.
- Participate in hiring, training, scheduling, coaching, and supervision of Buyer Purchasing Agent staff.
- Collaborate with the Director of Finance in the completion of annual performance assessments.
Requirements
Minimum Qualifications
- Education: High school diploma or GED.
- Experience: Minimum five years of related experience.
- Driving Requirements: Must be at least 21 years old, have been licensed for a minimum of three years, successfully complete a motor vehicle history check, possess and maintain a current, valid driver's license in the state of Washington, and have reliable, insured transportation. This role involves driving company vehicles across multiple worksites.
Preferred Qualifications
- Education: Bachelor's degree in supply chain management, engineering, logistics, or other related field.
- Experience: Prior experience in healthcare purchasing.
Performance Requirements
- Knowledge: Ability to read and write.
- Skills: Skill in establishing and maintaining effective working relationships with other employees, clients, organizations, and the public; communicates clearly and concisely; skilled in Microsoft Office suite programs; strong organizational and time management skills.
- Abilities: Demonstrated ability to work cooperatively and collaboratively as a team member; ability to work independently.
Worksite Requirements
Position requires regular travel to all KMHS worksites (Almira Main Campus and all other KMHS campuses).
Equipment Operated
- Standard office equipment including computers, fax machines, copiers, printers, telephones, etc.
- Warehouse equipment including box cutters, hand trucks, push carts, pallet jacks, etc.
Work Environment
Office and warehouse settings.
Physical Requirements
- Sit, stand, and walk for extended periods.
- Lift, carry, push, and pull: up to 20 pounds frequently, up to 50 pounds occasionally, up to 70 pounds seldom.
- Use hands and arms for reaching, handling, and manipulation, including reaching above shoulder level.
- Visual acuity and peripheral vision sufficient to read written materials and observe surroundings.
- Hearing sufficient to communicate effectively.
Benefits
- Comprehensive Coverage: Health, Dental & Vision
- Generous PTO: Up to 19 days + 2 mental health days + 10 holidays (pro-rated for part-time)
- Fully Paid YMCA Membership for you and eligible family members
- Company-Paid Life & Disability Insurance
- Student Loan Assistance & Professional Development
- 403(b) Retirement Plan with Company
for prose. I must include a section ONLY when there's real, specific content. No filler. Let me structure: 1. About the role: The introductory paragraph about KMHS seeking a Lead Purchasing Agent. 2. Responsibilities: The Primary Responsibilities list. 3. Requirements: This has multiple subsections. I could combine Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite-Specific Requirements, Equipment Operated, Work Environment, Mental/Physical Requirements under a Requirements heading, but they are distinct. The rules say use
for section headings like "Requirements". I could have one Requirements section with sub-lists, but the example headings include "Requirements" as a single heading. However, the content has multiple categories. I'll create a Requirements section with subsections using ? But the rules only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid , but to keep it simple, I'll use for each major section. However, "Requirements" is one heading, but there are subcategories. I could make separate for Minimum Qualifications, Preferred Qualifications, etc. But the example list includes "Qualifications" as a possible heading. I think it's better to have a "Requirements" heading and then use with nested lists or separate ? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It suggests those are the typical section headings. I'll create sections for each distinct category: Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But that might be too many thin sections. The rule: "Prefer a few substantive sections over many thin ones." So I should group related items.
Let me group:
- Requirements: Minimum Qualifications, Preferred Qualifications, Performance Requirements (Knowledge, Skills, Abilities)
- Worksite Requirements: Worksite-Specific Requirements
- Equipment & Environment: Equipment Operated, Work Environment
- Physical Requirements: Mental/Physical Requirements
But the rule says include a section ONLY when the posting has real, specific content. All these have content.
I'll create:
- About the role
- Responsibilities
- Requirements (with subsections)
- Benefits
- Pay
- Schedule
But the example headings include "Qualifications" and "Skills" separately. I could split Requirements into Qualifications and Skills. However, the posting has "Minimum Qualifications", "Preferred Qualifications", "Performance Requirements" which includes Knowledge, Skills, Abilities. I'll make a "Qualifications" section for education/experience, and a "Skills" section for the performance requirements? But the performance requirements include knowledge, skills, abilities. Might be better to have a "Requirements" section that includes all.
I'll do:
About the role
...
Responsibilities
...
Requirements
Minimum Qualifications
...
Preferred Qualifications
...
Performance Requirements
...
Worksite Requirements
...
Equipment Operated
...
Work Environment
...
Physical Requirements
...
But the rule says use for section headings. It doesn't say I can't use . However, to be safe, I'll use for each major section and maybe combine some. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the top-level sections. I'll use for each of those that apply. For subsections, I could use or just bold text. But the output should be semantic HTML. I think using is fine.
But the user said "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with headings.
Let me parse the content.
First, the job posting starts with "Full-Time, On-Site in Bremerton, WA Hiring Range: $27.16 – $33.94 Per Hour Benefits at a Glance ..." That's metadata: schedule, pay, benefits.
Then "Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations..." That's about the role.
Then "Primary Responsibilities:" list.
Then "Minimum Qualifications:" with EDUCATION and EXPERIENCE, plus driving requirements.
Then "Preferred Qualifications:" with EDUCATION and EXPERIENCE.
Then "Performance Requirements:" with KNOWLEDGE, SKILLS, ABILITIES.
Then "Worksite-Specific Requirements:" with checkboxes.
Then "Equipment Operated:" list.
Then "Work Environment:" description.
Then "Mental/Physical Requirements:" list.
Then EEO boilerplate at the end which should be removed.
Now, I need to create sections:
- About the role: the paragraph describing the role.
- Responsibilities: the bullet list.
- Requirements: I'll include Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But to avoid many thin sections, I'll group under Requirements with subheadings.
- Benefits: the Benefits at a Glance list.
- Pay: the hiring range.
- Schedule: Full-Time, On-Site in Bremerton, WA.
The schedule and pay are given at the top. I'll include them as sections.
Now, I must not include Job ID / requisition numbers. There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The last paragraph about recruitment processes is EEO boilerplate, so remove.
Now, write HTML.
I'll start with About the role
Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations. This position helps ensure departments have the supplies, equipment, and services needed to support daily operations across the organization. The role provides leadership for purchasing functions while maintaining efficient procurement processes and strong vendor relationships. If you're committed to supporting agency operations through effective purchasing and inventory management, we welcome your application.
Responsibilities
- Identify primary and secondary vendors and evaluate sources for materials and services.
- Maintain quality standards while supporting cost-effective purchasing practices.
- Serve as a liaison between departments and vendors.
- Maintain timely communication with departments regarding purchasing needs and order status.
- Coordinate and complete required agency and departmental trainings.
- Implement efficiencies and process improvements within the Purchasing Department.
- Assist with receiving, unpacking, and distributing inbound packages and deliveries.
- Provide receiving documentation to the Accounting Department.
- Manage inventory levels for Purchasing Department stock items, office supplies, and copy paper.
- Distribute stock items and copy paper throughout campus locations as needed.
- Assist with sourcing, negotiating, and procuring materials and services.
- Facilitate vehicle maintenance and operational status in conjunction with the Facility Department.
- Foster positive relationships with staff, vendors, and visitors through professional communication and customer service.
- Ensure purchased products meet applicable safety and regulatory requirements.
- Oversee Purchasing Department staff.
- Participate in hiring, training, scheduling, coaching, and supervision of Buyer Purchasing Agent staff.
- Collaborate with the Director of Finance in the completion of annual performance assessments.
Requirements
Minimum Qualifications
- Education: High school diploma or GED.
- Experience: Minimum five years of related experience.
- Driving Requirements: Must be at least 21 years old, have been licensed for a minimum of three years, successfully complete a motor vehicle history check, possess and maintain a current, valid driver's license in the state of Washington, and have reliable, insured transportation. This role involves driving company vehicles across multiple worksites.
Preferred Qualifications
- Education: Bachelor's degree in supply chain management, engineering, logistics, or other related field.
- Experience: Prior experience in healthcare purchasing.
Performance Requirements
- Knowledge: Ability to read and write.
- Skills: Skill in establishing and maintaining effective working relationships with other employees, clients, organizations, and the public; communicates clearly and concisely; skilled in Microsoft Office suite programs; strong organizational and time management skills.
- Abilities: Demonstrated ability to work cooperatively and collaboratively as a team member; ability to work independently.
Worksite Requirements
Position requires regular travel to all KMHS worksites (Almira Main Campus and all other KMHS campuses).
Equipment Operated
- Standard office equipment including computers, fax machines, copiers, printers, telephones, etc.
- Warehouse equipment including box cutters, hand trucks, push carts, pallet jacks, etc.
Work Environment
Office and warehouse settings.
Physical Requirements
- Sit, stand, and walk for extended periods.
- Lift, carry, push, and pull: up to 20 pounds frequently, up to 50 pounds occasionally, up to 70 pounds seldom.
- Use hands and arms for reaching, handling, and manipulation, including reaching above shoulder level.
- Visual acuity and peripheral vision sufficient to read written materials and observe surroundings.
- Hearing sufficient to communicate effectively.
Benefits
- Comprehensive Coverage: Health, Dental & Vision
- Generous PTO: Up to 19 days + 2 mental health days + 10 holidays (pro-rated for part-time)
- Fully Paid YMCA Membership for you and eligible family members
- Company-Paid Life & Disability Insurance
- Student Loan Assistance & Professional Development
- 403(b) Retirement Plan with Company
for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid , but to keep it simple, I'll use for each major section. However, "Requirements" is one heading, but there are subcategories. I could make separate for Minimum Qualifications, Preferred Qualifications, etc. But the example list includes "Qualifications" as a possible heading. I think it's better to have a "Requirements" heading and then use with nested lists or separate ? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It suggests those are the typical section headings. I'll create sections for each distinct category: Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But that might be too many thin sections. The rule: "Prefer a few substantive sections over many thin ones." So I should group related items.
Let me group:
- Requirements: Minimum Qualifications, Preferred Qualifications, Performance Requirements (Knowledge, Skills, Abilities)
- Worksite Requirements: Worksite-Specific Requirements
- Equipment & Environment: Equipment Operated, Work Environment
- Physical Requirements: Mental/Physical Requirements
But the rule says include a section ONLY when the posting has real, specific content. All these have content.
I'll create:
- About the role
- Responsibilities
- Requirements (with subsections)
- Benefits
- Pay
- Schedule
But the example headings include "Qualifications" and "Skills" separately. I could split Requirements into Qualifications and Skills. However, the posting has "Minimum Qualifications", "Preferred Qualifications", "Performance Requirements" which includes Knowledge, Skills, Abilities. I'll make a "Qualifications" section for education/experience, and a "Skills" section for the performance requirements? But the performance requirements include knowledge, skills, abilities. Might be better to have a "Requirements" section that includes all.
I'll do:
About the role
...
Responsibilities
...
Requirements
Minimum Qualifications
...
Preferred Qualifications
...
Performance Requirements
...
Worksite Requirements
...
Equipment Operated
...
Work Environment
...
Physical Requirements
...
But the rule says use for section headings. It doesn't say I can't use . However, to be safe, I'll use for each major section and maybe combine some. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the top-level sections. I'll use for each of those that apply. For subsections, I could use or just bold text. But the output should be semantic HTML. I think using is fine.
But the user said "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with headings.
Let me parse the content.
First, the job posting starts with "Full-Time, On-Site in Bremerton, WA Hiring Range: $27.16 – $33.94 Per Hour Benefits at a Glance ..." That's metadata: schedule, pay, benefits.
Then "Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations..." That's about the role.
Then "Primary Responsibilities:" list.
Then "Minimum Qualifications:" with EDUCATION and EXPERIENCE, plus driving requirements.
Then "Preferred Qualifications:" with EDUCATION and EXPERIENCE.
Then "Performance Requirements:" with KNOWLEDGE, SKILLS, ABILITIES.
Then "Worksite-Specific Requirements:" with checkboxes.
Then "Equipment Operated:" list.
Then "Work Environment:" description.
Then "Mental/Physical Requirements:" list.
Then EEO boilerplate at the end which should be removed.
Now, I need to create sections:
- About the role: the paragraph describing the role.
- Responsibilities: the bullet list.
- Requirements: I'll include Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But to avoid many thin sections, I'll group under Requirements with subheadings.
- Benefits: the Benefits at a Glance list.
- Pay: the hiring range.
- Schedule: Full-Time, On-Site in Bremerton, WA.
The schedule and pay are given at the top. I'll include them as sections.
Now, I must not include Job ID / requisition numbers. There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The last paragraph about recruitment processes is EEO boilerplate, so remove.
Now, write HTML.
I'll start with About the role
Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations. This position helps ensure departments have the supplies, equipment, and services needed to support daily operations across the organization. The role provides leadership for purchasing functions while maintaining efficient procurement processes and strong vendor relationships. If you're committed to supporting agency operations through effective purchasing and inventory management, we welcome your application.
Responsibilities
- Identify primary and secondary vendors and evaluate sources for materials and services.
- Maintain quality standards while supporting cost-effective purchasing practices.
- Serve as a liaison between departments and vendors.
- Maintain timely communication with departments regarding purchasing needs and order status.
- Coordinate and complete required agency and departmental trainings.
- Implement efficiencies and process improvements within the Purchasing Department.
- Assist with receiving, unpacking, and distributing inbound packages and deliveries.
- Provide receiving documentation to the Accounting Department.
- Manage inventory levels for Purchasing Department stock items, office supplies, and copy paper.
- Distribute stock items and copy paper throughout campus locations as needed.
- Assist with sourcing, negotiating, and procuring materials and services.
- Facilitate vehicle maintenance and operational status in conjunction with the Facility Department.
- Foster positive relationships with staff, vendors, and visitors through professional communication and customer service.
- Ensure purchased products meet applicable safety and regulatory requirements.
- Oversee Purchasing Department staff.
- Participate in hiring, training, scheduling, coaching, and supervision of Buyer Purchasing Agent staff.
- Collaborate with the Director of Finance in the completion of annual performance assessments.
Requirements
Minimum Qualifications
- Education: High school diploma or GED.
- Experience: Minimum five years of related experience.
- Driving Requirements: Must be at least 21 years old, have been licensed for a minimum of three years, successfully complete a motor vehicle history check, possess and maintain a current, valid driver's license in the state of Washington, and have reliable, insured transportation. This role involves driving company vehicles across multiple worksites.
Preferred Qualifications
- Education: Bachelor's degree in supply chain management, engineering, logistics, or other related field.
- Experience: Prior experience in healthcare purchasing.
Performance Requirements
- Knowledge: Ability to read and write.
- Skills: Skill in establishing and maintaining effective working relationships with other employees, clients, organizations, and the public; communicates clearly and concisely; skilled in Microsoft Office suite programs; strong organizational and time management skills.
- Abilities: Demonstrated ability to work cooperatively and collaboratively as a team member; ability to work independently.
Worksite Requirements
Position requires regular travel to all KMHS worksites (Almira Main Campus and all other KMHS campuses).
Equipment Operated
- Standard office equipment including computers, fax machines, copiers, printers, telephones, etc.
- Warehouse equipment including box cutters, hand trucks, push carts, pallet jacks, etc.
Work Environment
Office and warehouse settings.
Physical Requirements
- Sit, stand, and walk for extended periods.
- Lift, carry, push, and pull: up to 20 pounds frequently, up to 50 pounds occasionally, up to 70 pounds seldom.
- Use hands and arms for reaching, handling, and manipulation, including reaching above shoulder level.
- Visual acuity and peripheral vision sufficient to read written materials and observe surroundings.
- Hearing sufficient to communicate effectively.
Benefits
- Comprehensive Coverage: Health, Dental & Vision
- Generous PTO: Up to 19 days + 2 mental health days + 10 holidays (pro-rated for part-time)
- Fully Paid YMCA Membership for you and eligible family members
- Company-Paid Life & Disability Insurance
- Student Loan Assistance & Professional Development
- 403(b) Retirement Plan with Company
, but to keep it simple, I'll use for each major section. However, "Requirements" is one heading, but there are subcategories. I could make separate for Minimum Qualifications, Preferred Qualifications, etc. But the example list includes "Qualifications" as a possible heading. I think it's better to have a "Requirements" heading and then use with nested lists or separate ? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It suggests those are the typical section headings. I'll create sections for each distinct category: Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But that might be too many thin sections. The rule: "Prefer a few substantive sections over many thin ones." So I should group related items.
Let me group:
- Requirements: Minimum Qualifications, Preferred Qualifications, Performance Requirements (Knowledge, Skills, Abilities)
- Worksite Requirements: Worksite-Specific Requirements
- Equipment & Environment: Equipment Operated, Work Environment
- Physical Requirements: Mental/Physical Requirements
But the rule says include a section ONLY when the posting has real, specific content. All these have content.
I'll create:
- About the role
- Responsibilities
- Requirements (with subsections)
- Benefits
- Pay
- Schedule
But the example headings include "Qualifications" and "Skills" separately. I could split Requirements into Qualifications and Skills. However, the posting has "Minimum Qualifications", "Preferred Qualifications", "Performance Requirements" which includes Knowledge, Skills, Abilities. I'll make a "Qualifications" section for education/experience, and a "Skills" section for the performance requirements? But the performance requirements include knowledge, skills, abilities. Might be better to have a "Requirements" section that includes all.
I'll do:
About the role
...
Responsibilities
...
Requirements
Minimum Qualifications
...
Preferred Qualifications
...
Performance Requirements
...
Worksite Requirements
...
Equipment Operated
...
Work Environment
...
Physical Requirements
...
But the rule says use for section headings. It doesn't say I can't use . However, to be safe, I'll use for each major section and maybe combine some. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the top-level sections. I'll use for each of those that apply. For subsections, I could use or just bold text. But the output should be semantic HTML. I think using is fine.
But the user said "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with headings.
Let me parse the content.
First, the job posting starts with "Full-Time, On-Site in Bremerton, WA Hiring Range: $27.16 – $33.94 Per Hour Benefits at a Glance ..." That's metadata: schedule, pay, benefits.
Then "Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations..." That's about the role.
Then "Primary Responsibilities:" list.
Then "Minimum Qualifications:" with EDUCATION and EXPERIENCE, plus driving requirements.
Then "Preferred Qualifications:" with EDUCATION and EXPERIENCE.
Then "Performance Requirements:" with KNOWLEDGE, SKILLS, ABILITIES.
Then "Worksite-Specific Requirements:" with checkboxes.
Then "Equipment Operated:" list.
Then "Work Environment:" description.
Then "Mental/Physical Requirements:" list.
Then EEO boilerplate at the end which should be removed.
Now, I need to create sections:
- About the role: the paragraph describing the role.
- Responsibilities: the bullet list.
- Requirements: I'll include Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But to avoid many thin sections, I'll group under Requirements with subheadings.
- Benefits: the Benefits at a Glance list.
- Pay: the hiring range.
- Schedule: Full-Time, On-Site in Bremerton, WA.
The schedule and pay are given at the top. I'll include them as sections.
Now, I must not include Job ID / requisition numbers. There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The last paragraph about recruitment processes is EEO boilerplate, so remove.
Now, write HTML.
I'll start with About the role
Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations. This position helps ensure departments have the supplies, equipment, and services needed to support daily operations across the organization. The role provides leadership for purchasing functions while maintaining efficient procurement processes and strong vendor relationships. If you're committed to supporting agency operations through effective purchasing and inventory management, we welcome your application.
Responsibilities
- Identify primary and secondary vendors and evaluate sources for materials and services.
- Maintain quality standards while supporting cost-effective purchasing practices.
- Serve as a liaison between departments and vendors.
- Maintain timely communication with departments regarding purchasing needs and order status.
- Coordinate and complete required agency and departmental trainings.
- Implement efficiencies and process improvements within the Purchasing Department.
- Assist with receiving, unpacking, and distributing inbound packages and deliveries.
- Provide receiving documentation to the Accounting Department.
- Manage inventory levels for Purchasing Department stock items, office supplies, and copy paper.
- Distribute stock items and copy paper throughout campus locations as needed.
- Assist with sourcing, negotiating, and procuring materials and services.
- Facilitate vehicle maintenance and operational status in conjunction with the Facility Department.
- Foster positive relationships with staff, vendors, and visitors through professional communication and customer service.
- Ensure purchased products meet applicable safety and regulatory requirements.
- Oversee Purchasing Department staff.
- Participate in hiring, training, scheduling, coaching, and supervision of Buyer Purchasing Agent staff.
- Collaborate with the Director of Finance in the completion of annual performance assessments.
Requirements
Minimum Qualifications
- Education: High school diploma or GED.
- Experience: Minimum five years of related experience.
- Driving Requirements: Must be at least 21 years old, have been licensed for a minimum of three years, successfully complete a motor vehicle history check, possess and maintain a current, valid driver's license in the state of Washington, and have reliable, insured transportation. This role involves driving company vehicles across multiple worksites.
Preferred Qualifications
- Education: Bachelor's degree in supply chain management, engineering, logistics, or other related field.
- Experience: Prior experience in healthcare purchasing.
Performance Requirements
- Knowledge: Ability to read and write.
- Skills: Skill in establishing and maintaining effective working relationships with other employees, clients, organizations, and the public; communicates clearly and concisely; skilled in Microsoft Office suite programs; strong organizational and time management skills.
- Abilities: Demonstrated ability to work cooperatively and collaboratively as a team member; ability to work independently.
Worksite Requirements
Position requires regular travel to all KMHS worksites (Almira Main Campus and all other KMHS campuses).
Equipment Operated
- Standard office equipment including computers, fax machines, copiers, printers, telephones, etc.
- Warehouse equipment including box cutters, hand trucks, push carts, pallet jacks, etc.
Work Environment
Office and warehouse settings.
Physical Requirements
- Sit, stand, and walk for extended periods.
- Lift, carry, push, and pull: up to 20 pounds frequently, up to 50 pounds occasionally, up to 70 pounds seldom.
- Use hands and arms for reaching, handling, and manipulation, including reaching above shoulder level.
- Visual acuity and peripheral vision sufficient to read written materials and observe surroundings.
- Hearing sufficient to communicate effectively.
Benefits
- Comprehensive Coverage: Health, Dental & Vision
- Generous PTO: Up to 19 days + 2 mental health days + 10 holidays (pro-rated for part-time)
- Fully Paid YMCA Membership for you and eligible family members
- Company-Paid Life & Disability Insurance
- Student Loan Assistance & Professional Development
- 403(b) Retirement Plan with Company
for Minimum Qualifications, Preferred Qualifications, etc. But the example list includes "Qualifications" as a possible heading. I think it's better to have a "Requirements" heading and then use with nested lists or separate ? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It suggests those are the typical section headings. I'll create sections for each distinct category: Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But that might be too many thin sections. The rule: "Prefer a few substantive sections over many thin ones." So I should group related items.
Let me group:
- Requirements: Minimum Qualifications, Preferred Qualifications, Performance Requirements (Knowledge, Skills, Abilities)
- Worksite Requirements: Worksite-Specific Requirements
- Equipment & Environment: Equipment Operated, Work Environment
- Physical Requirements: Mental/Physical Requirements
But the rule says include a section ONLY when the posting has real, specific content. All these have content.
I'll create:
- About the role
- Responsibilities
- Requirements (with subsections)
- Benefits
- Pay
- Schedule
But the example headings include "Qualifications" and "Skills" separately. I could split Requirements into Qualifications and Skills. However, the posting has "Minimum Qualifications", "Preferred Qualifications", "Performance Requirements" which includes Knowledge, Skills, Abilities. I'll make a "Qualifications" section for education/experience, and a "Skills" section for the performance requirements? But the performance requirements include knowledge, skills, abilities. Might be better to have a "Requirements" section that includes all.
I'll do:
About the role
...
Responsibilities
...
Requirements
Minimum Qualifications
...
Preferred Qualifications
...
Performance Requirements
...
Worksite Requirements
...
Equipment Operated
...
Work Environment
...
Physical Requirements
...
But the rule says use for section headings. It doesn't say I can't use . However, to be safe, I'll use for each major section and maybe combine some. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the top-level sections. I'll use for each of those that apply. For subsections, I could use or just bold text. But the output should be semantic HTML. I think using is fine.
But the user said "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with headings.
Let me parse the content.
First, the job posting starts with "Full-Time, On-Site in Bremerton, WA Hiring Range: $27.16 – $33.94 Per Hour Benefits at a Glance ..." That's metadata: schedule, pay, benefits.
Then "Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations..." That's about the role.
Then "Primary Responsibilities:" list.
Then "Minimum Qualifications:" with EDUCATION and EXPERIENCE, plus driving requirements.
Then "Preferred Qualifications:" with EDUCATION and EXPERIENCE.
Then "Performance Requirements:" with KNOWLEDGE, SKILLS, ABILITIES.
Then "Worksite-Specific Requirements:" with checkboxes.
Then "Equipment Operated:" list.
Then "Work Environment:" description.
Then "Mental/Physical Requirements:" list.
Then EEO boilerplate at the end which should be removed.
Now, I need to create sections:
- About the role: the paragraph describing the role.
- Responsibilities: the bullet list.
- Requirements: I'll include Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But to avoid many thin sections, I'll group under Requirements with subheadings.
- Benefits: the Benefits at a Glance list.
- Pay: the hiring range.
- Schedule: Full-Time, On-Site in Bremerton, WA.
The schedule and pay are given at the top. I'll include them as sections.
Now, I must not include Job ID / requisition numbers. There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The last paragraph about recruitment processes is EEO boilerplate, so remove.
Now, write HTML.
I'll start with About the role
Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations. This position helps ensure departments have the supplies, equipment, and services needed to support daily operations across the organization. The role provides leadership for purchasing functions while maintaining efficient procurement processes and strong vendor relationships. If you're committed to supporting agency operations through effective purchasing and inventory management, we welcome your application.
Responsibilities
- Identify primary and secondary vendors and evaluate sources for materials and services.
- Maintain quality standards while supporting cost-effective purchasing practices.
- Serve as a liaison between departments and vendors.
- Maintain timely communication with departments regarding purchasing needs and order status.
- Coordinate and complete required agency and departmental trainings.
- Implement efficiencies and process improvements within the Purchasing Department.
- Assist with receiving, unpacking, and distributing inbound packages and deliveries.
- Provide receiving documentation to the Accounting Department.
- Manage inventory levels for Purchasing Department stock items, office supplies, and copy paper.
- Distribute stock items and copy paper throughout campus locations as needed.
- Assist with sourcing, negotiating, and procuring materials and services.
- Facilitate vehicle maintenance and operational status in conjunction with the Facility Department.
- Foster positive relationships with staff, vendors, and visitors through professional communication and customer service.
- Ensure purchased products meet applicable safety and regulatory requirements.
- Oversee Purchasing Department staff.
- Participate in hiring, training, scheduling, coaching, and supervision of Buyer Purchasing Agent staff.
- Collaborate with the Director of Finance in the completion of annual performance assessments.
Requirements
Minimum Qualifications
- Education: High school diploma or GED.
- Experience: Minimum five years of related experience.
- Driving Requirements: Must be at least 21 years old, have been licensed for a minimum of three years, successfully complete a motor vehicle history check, possess and maintain a current, valid driver's license in the state of Washington, and have reliable, insured transportation. This role involves driving company vehicles across multiple worksites.
Preferred Qualifications
- Education: Bachelor's degree in supply chain management, engineering, logistics, or other related field.
- Experience: Prior experience in healthcare purchasing.
Performance Requirements
- Knowledge: Ability to read and write.
- Skills: Skill in establishing and maintaining effective working relationships with other employees, clients, organizations, and the public; communicates clearly and concisely; skilled in Microsoft Office suite programs; strong organizational and time management skills.
- Abilities: Demonstrated ability to work cooperatively and collaboratively as a team member; ability to work independently.
Worksite Requirements
Position requires regular travel to all KMHS worksites (Almira Main Campus and all other KMHS campuses).
Equipment Operated
- Standard office equipment including computers, fax machines, copiers, printers, telephones, etc.
- Warehouse equipment including box cutters, hand trucks, push carts, pallet jacks, etc.
Work Environment
Office and warehouse settings.
Physical Requirements
- Sit, stand, and walk for extended periods.
- Lift, carry, push, and pull: up to 20 pounds frequently, up to 50 pounds occasionally, up to 70 pounds seldom.
- Use hands and arms for reaching, handling, and manipulation, including reaching above shoulder level.
- Visual acuity and peripheral vision sufficient to read written materials and observe surroundings.
- Hearing sufficient to communicate effectively.
Benefits
- Comprehensive Coverage: Health, Dental & Vision
- Generous PTO: Up to 19 days + 2 mental health days + 10 holidays (pro-rated for part-time)
- Fully Paid YMCA Membership for you and eligible family members
- Company-Paid Life & Disability Insurance
- Student Loan Assistance & Professional Development
- 403(b) Retirement Plan with Company
? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It suggests those are the typical section headings. I'll create sections for each distinct category: Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But that might be too many thin sections. The rule: "Prefer a few substantive sections over many thin ones." So I should group related items.
Let me group:
- Requirements: Minimum Qualifications, Preferred Qualifications, Performance Requirements (Knowledge, Skills, Abilities)
- Worksite Requirements: Worksite-Specific Requirements
- Equipment & Environment: Equipment Operated, Work Environment
- Physical Requirements: Mental/Physical Requirements
But the rule says include a section ONLY when the posting has real, specific content. All these have content.
I'll create:
- About the role
- Responsibilities
- Requirements (with subsections)
- Benefits
- Pay
- Schedule
But the example headings include "Qualifications" and "Skills" separately. I could split Requirements into Qualifications and Skills. However, the posting has "Minimum Qualifications", "Preferred Qualifications", "Performance Requirements" which includes Knowledge, Skills, Abilities. I'll make a "Qualifications" section for education/experience, and a "Skills" section for the performance requirements? But the performance requirements include knowledge, skills, abilities. Might be better to have a "Requirements" section that includes all.
I'll do:
About the role
About the role
...
Responsibilities
- ...
Requirements
Minimum Qualifications
- ...
Preferred Qualifications
- ...
Performance Requirements
- ...
Worksite Requirements
...
Equipment Operated
- ...
Work Environment
...
Physical Requirements
- ...
for section headings. It doesn't say I can't use . However, to be safe, I'll use for each major section and maybe combine some. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the top-level sections. I'll use for each of those that apply. For subsections, I could use or just bold text. But the output should be semantic HTML. I think using is fine.
But the user said "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with headings.
Let me parse the content.
First, the job posting starts with "Full-Time, On-Site in Bremerton, WA Hiring Range: $27.16 – $33.94 Per Hour Benefits at a Glance ..." That's metadata: schedule, pay, benefits.
Then "Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations..." That's about the role.
Then "Primary Responsibilities:" list.
Then "Minimum Qualifications:" with EDUCATION and EXPERIENCE, plus driving requirements.
Then "Preferred Qualifications:" with EDUCATION and EXPERIENCE.
Then "Performance Requirements:" with KNOWLEDGE, SKILLS, ABILITIES.
Then "Worksite-Specific Requirements:" with checkboxes.
Then "Equipment Operated:" list.
Then "Work Environment:" description.
Then "Mental/Physical Requirements:" list.
Then EEO boilerplate at the end which should be removed.
Now, I need to create sections:
- About the role: the paragraph describing the role.
- Responsibilities: the bullet list.
- Requirements: I'll include Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But to avoid many thin sections, I'll group under Requirements with subheadings.
- Benefits: the Benefits at a Glance list.
- Pay: the hiring range.
- Schedule: Full-Time, On-Site in Bremerton, WA.
The schedule and pay are given at the top. I'll include them as sections.
Now, I must not include Job ID / requisition numbers. There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The last paragraph about recruitment processes is EEO boilerplate, so remove.
Now, write HTML.
I'll start with About the role
for each major section and maybe combine some. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the top-level sections. I'll use for each of those that apply. For subsections, I could use or just bold text. But the output should be semantic HTML. I think using is fine.
But the user said "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with headings.
Let me parse the content.
First, the job posting starts with "Full-Time, On-Site in Bremerton, WA Hiring Range: $27.16 – $33.94 Per Hour Benefits at a Glance ..." That's metadata: schedule, pay, benefits.
Then "Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations..." That's about the role.
Then "Primary Responsibilities:" list.
Then "Minimum Qualifications:" with EDUCATION and EXPERIENCE, plus driving requirements.
Then "Preferred Qualifications:" with EDUCATION and EXPERIENCE.
Then "Performance Requirements:" with KNOWLEDGE, SKILLS, ABILITIES.
Then "Worksite-Specific Requirements:" with checkboxes.
Then "Equipment Operated:" list.
Then "Work Environment:" description.
Then "Mental/Physical Requirements:" list.
Then EEO boilerplate at the end which should be removed.
Now, I need to create sections:
- About the role: the paragraph describing the role.
- Responsibilities: the bullet list.
- Requirements: I'll include Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But to avoid many thin sections, I'll group under Requirements with subheadings.
- Benefits: the Benefits at a Glance list.
- Pay: the hiring range.
- Schedule: Full-Time, On-Site in Bremerton, WA.
The schedule and pay are given at the top. I'll include them as sections.
Now, I must not include Job ID / requisition numbers. There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The last paragraph about recruitment processes is EEO boilerplate, so remove.
Now, write HTML.
I'll start with About the role
for each of those that apply. For subsections, I could use or just bold text. But the output should be semantic HTML. I think using is fine.
But the user said "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with headings.
Let me parse the content.
First, the job posting starts with "Full-Time, On-Site in Bremerton, WA Hiring Range: $27.16 – $33.94 Per Hour Benefits at a Glance ..." That's metadata: schedule, pay, benefits.
Then "Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations..." That's about the role.
Then "Primary Responsibilities:" list.
Then "Minimum Qualifications:" with EDUCATION and EXPERIENCE, plus driving requirements.
Then "Preferred Qualifications:" with EDUCATION and EXPERIENCE.
Then "Performance Requirements:" with KNOWLEDGE, SKILLS, ABILITIES.
Then "Worksite-Specific Requirements:" with checkboxes.
Then "Equipment Operated:" list.
Then "Work Environment:" description.
Then "Mental/Physical Requirements:" list.
Then EEO boilerplate at the end which should be removed.
Now, I need to create sections:
- About the role: the paragraph describing the role.
- Responsibilities: the bullet list.
- Requirements: I'll include Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But to avoid many thin sections, I'll group under Requirements with subheadings.
- Benefits: the Benefits at a Glance list.
- Pay: the hiring range.
- Schedule: Full-Time, On-Site in Bremerton, WA.
The schedule and pay are given at the top. I'll include them as sections.
Now, I must not include Job ID / requisition numbers. There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The last paragraph about recruitment processes is EEO boilerplate, so remove.
Now, write HTML.
I'll start with About the role
is fine.
But the user said "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output HTML with headings.
Let me parse the content.
First, the job posting starts with "Full-Time, On-Site in Bremerton, WA Hiring Range: $27.16 – $33.94 Per Hour Benefits at a Glance ..." That's metadata: schedule, pay, benefits.
Then "Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations..." That's about the role.
Then "Primary Responsibilities:" list.
Then "Minimum Qualifications:" with EDUCATION and EXPERIENCE, plus driving requirements.
Then "Preferred Qualifications:" with EDUCATION and EXPERIENCE.
Then "Performance Requirements:" with KNOWLEDGE, SKILLS, ABILITIES.
Then "Worksite-Specific Requirements:" with checkboxes.
Then "Equipment Operated:" list.
Then "Work Environment:" description.
Then "Mental/Physical Requirements:" list.
Then EEO boilerplate at the end which should be removed.
Now, I need to create sections:
- About the role: the paragraph describing the role.
- Responsibilities: the bullet list.
- Requirements: I'll include Minimum Qualifications, Preferred Qualifications, Performance Requirements, Worksite Requirements, Equipment, Work Environment, Physical Requirements. But to avoid many thin sections, I'll group under Requirements with subheadings.
- Benefits: the Benefits at a Glance list.
- Pay: the hiring range.
- Schedule: Full-Time, On-Site in Bremerton, WA.
The schedule and pay are given at the top. I'll include them as sections.
Now, I must not include Job ID / requisition numbers. There's none.
Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The last paragraph about recruitment processes is EEO boilerplate, so remove.
Now, write HTML.
I'll start with About the role
Kitsap Mental Health Services (KMHS) is seeking a Lead Purchasing Agent to oversee the agency's Purchasing Department operations. This position helps ensure departments have the supplies, equipment, and services needed to support daily operations across the organization. The role provides leadership for purchasing functions while maintaining efficient procurement processes and strong vendor relationships. If you're committed to supporting agency operations through effective purchasing and inventory management, we welcome your application.
Responsibilities
- Identify primary and secondary vendors and evaluate sources for materials and services.
- Maintain quality standards while supporting cost-effective purchasing practices.
- Serve as a liaison between departments and vendors.
- Maintain timely communication with departments regarding purchasing needs and order status.
- Coordinate and complete required agency and departmental trainings.
- Implement efficiencies and process improvements within the Purchasing Department.
- Assist with receiving, unpacking, and distributing inbound packages and deliveries.
- Provide receiving documentation to the Accounting Department.
- Manage inventory levels for Purchasing Department stock items, office supplies, and copy paper.
- Distribute stock items and copy paper throughout campus locations as needed.
- Assist with sourcing, negotiating, and procuring materials and services.
- Facilitate vehicle maintenance and operational status in conjunction with the Facility Department.
- Foster positive relationships with staff, vendors, and visitors through professional communication and customer service.
- Ensure purchased products meet applicable safety and regulatory requirements.
- Oversee Purchasing Department staff.
- Participate in hiring, training, scheduling, coaching, and supervision of Buyer Purchasing Agent staff.
- Collaborate with the Director of Finance in the completion of annual performance assessments.
Requirements
Minimum Qualifications
- Education: High school diploma or GED.
- Experience: Minimum five years of related experience.
- Driving Requirements: Must be at least 21 years old, have been licensed for a minimum of three years, successfully complete a motor vehicle history check, possess and maintain a current, valid driver's license in the state of Washington, and have reliable, insured transportation. This role involves driving company vehicles across multiple worksites.
Preferred Qualifications
- Education: Bachelor's degree in supply chain management, engineering, logistics, or other related field.
- Experience: Prior experience in healthcare purchasing.
Performance Requirements
- Knowledge: Ability to read and write.
- Skills: Skill in establishing and maintaining effective working relationships with other employees, clients, organizations, and the public; communicates clearly and concisely; skilled in Microsoft Office suite programs; strong organizational and time management skills.
- Abilities: Demonstrated ability to work cooperatively and collaboratively as a team member; ability to work independently.
Worksite Requirements
Position requires regular travel to all KMHS worksites (Almira Main Campus and all other KMHS campuses).
Equipment Operated
- Standard office equipment including computers, fax machines, copiers, printers, telephones, etc.
- Warehouse equipment including box cutters, hand trucks, push carts, pallet jacks, etc.
Work Environment
Office and warehouse settings.
Physical Requirements
- Sit, stand, and walk for extended periods.
- Lift, carry, push, and pull: up to 20 pounds frequently, up to 50 pounds occasionally, up to 70 pounds seldom.
- Use hands and arms for reaching, handling, and manipulation, including reaching above shoulder level.
- Visual acuity and peripheral vision sufficient to read written materials and observe surroundings.
- Hearing sufficient to communicate effectively.
Benefits
- Comprehensive Coverage: Health, Dental & Vision
- Generous PTO: Up to 19 days + 2 mental health days + 10 holidays (pro-rated for part-time)
- Fully Paid YMCA Membership for you and eligible family members
- Company-Paid Life & Disability Insurance
- Student Loan Assistance & Professional Development
- 403(b) Retirement Plan with Company