Procurement Specialist
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes job duties (multiple subcategories), qualifications required and preferred, physical demands, performance metrics, status, benefits, working days, hours per day, travel required, reports to.
We need to map to sections: "About the role" maybe not present; we can skip. "Responsibilities" corresponds to job duties. "Requirements" maybe qualifications required? "Qualifications" maybe both required and preferred? "Skills" maybe not explicit; we could include under qualifications. "Benefits" present: "Company benefits: Yes". That's vague but it's a statement; we can include Benefits section with that line. "Pay" not present; skip. "Schedule": we have Working Days: M-F, Hours Per Day: Approx. 8-9. That's schedule info. So we can include Schedule section.
Also we have "Status: Full Time – Exempt" maybe could be part of About the role? Not a heading. Could include under About the role? But we shouldn't create heading without content. Could embed in a paragraph under About the role? But we don't have About the role content. Maybe we can create a short paragraph with status and reporting line etc. However instructions: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide what sections to include.
We have:
- Responsibilities: job duties (multiple bullet points). We'll make Responsibilities
then - each duty.
- Qualifications: we have required and preferred. Could combine into one Qualifications section with subpoints? Could split into Required and Preferred as subheadings? But only allowed headings are the listed ones; we could still use
Qualifications
and then list required and preferred within maybe with notes. That's okay.
- Skills: not explicitly listed; we could omit.
- Benefits: we have "Company benefits: Yes". That's specific enough? It's a statement that benefits are offered. We'll include Benefits section with that line as .
- Schedule: we have Working Days: M-F, Hours Per Day: Approx. 8-9. Also Travel Required: Limited (approx. 10%). That could be part of Schedule or maybe separate but we only have Schedule heading. We'll include schedule info.
- Pay: not present, skip.
- About the role: we could include a brief paragraph summarizing role from the title? But we must not repeat job title as heading. Could we create About the role section with a paragraph describing the role? The posting didn't have a summary; but we could infer from duties? Might be considered inventing detail. Better to skip About the role if no explicit content.
- Requirements: maybe same as Qualifications; we can skip Requirements if we use Qualifications.
Thus output:
Responsibilities
- ...
...
Qualifications
- Required: ...
- Preferred: ...
maybe separate.
But we need to preserve all substantive information. Let's extract duties:
From "JOB DUTIES:" sections:
Sourcing & Supplier Strategy:
- Serve as the single purchasing channel for both Integration and Production.
- Own the company's sourcing strategy for AV, lighting, rigging, staging, networking, and installation materials, consolidating spend where it creates leverage.
- Negotiate pricing, terms, rebates, and dealer agreements with manufacturers, distributors, and vendors to maximize value and protect margin.
- Maintain alternate sources where supply risk warrants it.
- Maintain the preferred vendor list, evaluating suppliers on price, lead time, quality, and service, and build direct relationships with key manufacturer and distributor representatives.
Purchasing Process & Cost Control:
- Design and document purchasing policy, approval thresholds, and PO procedures for two distinct cadences: project-based Integration buying against a signed scope, and show-date Production buying, with a defined exception path for show-critical purchases.
- Deliver measurable cost savings without compromising quality or schedule.
- Keep purchasing activity within company policy, budget expectations, and contract terms, with organized and auditable records.
Order Fulfillment & Delivery:
- Track orders from placement through delivery, proactively resolving delays, damages, and shortages, and manage the expedited shipments and emergency purchases needed to protect live event and installation deadlines.
- Select carriers and control freight cost on purchased materials.
- Resolve shipping claims, returns, RMAs, and warranty replacements with vendors and carriers.
Supports & Coordinates:
- Partner with the CFO on purchasing budgets, flagging variances before they become overruns, and provide pricing, lead time, and total-cost input on capital equipment planning and buy-versus-rent-versus-subrent decisions.
- Coordinate delivery timing with project managers, account managers, warehouse personnel, and field crews so materials arrive when they are needed.
- Work with the warehouse team on inventory visibility, stock levels, and replenishment, and flag surplus or aging equipment for disposition.
- Support accounting on reconciliation of purchasing records, packing slips, and vendor invoices, resolving escalated discrepancies with vendors.
- Serve as the procurement point of contact for the integration, production, warehouse, and accounting teams.
- Other duties as assigned.
We need to keep all that.
Qualifications — REQUIRED:
- 2+ years of procurement, purchasing, or supply chain experience.
- Experience establishing purchasing process where little existed before, including rebuilding records from incomplete information.
- Proven negotiation skills with a track record of measurable cost savings.
- Comfort in both buying cadences this role covers: deliberate project-based purchasing and fast, deadline-driven purchasing. Depth in one with a willingness to learn the other is acceptable.
- Proficient in Excel, with working experience in ERP, inventory management, or purchasing software.
- Excellent organizational, multitasking, and communication abilities with high attention to detail, and strong decision-making where priorities shift quickly.
- Valid driver's license and reliable transportation.
QUALIFICATIONS — PREFERRED:
- Experience in the audiovisual, lighting, live production, construction, electrical, or technology industry, with working knowledge of AV manufacturers, lighting and rigging equipment, networking products, and installation materials.
- Experience controlling freight and inbound shipping costs, and financial acumen working directly with a CFO or controller on budgets and margin.
- Interest in growing into a team leadership role.
PHYSICAL DEMANDS: The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. While performing the duties of this job, the employee might be required to stand; walk; sit; reach with hands and arms; climb or balance; stoop, kneel, crouch, or crawl; talk or hear; and occasionally lift and/or move up to 100 pounds.
PERFORMANCE METRICS: Monthly, quarterly, and annual reporting.
Status: Full Time – Exempt
Company benefits: Yes
Working Days: M-F
Hours Per Day: Approx. 8-9
Travel Required: Limited (approx. 10%)
Reports to: Chief Financial Officer (no direct reports initially; Specialist as the department grows)
We need to include all substantive info. Where to put physical demands and performance metrics? Not among allowed headings. Could we put them under a generic section like "About the role"? Not ideal. Could we create a section "Details"? Not allowed. The instruction says use headings for those specific section names; but we could still include other info as paragraphs under appropriate headings, maybe under Responsibilities or Qualifications? But physical demands and performance metrics are separate; we could include them as a under a heading like "About the role" if we treat that as a summary. However we risk adding filler if we don't have content. But we do have content for physical demands and performance metrics; we could create a section "Details" but not allowed. Perhaps we can embed them under "Qualifications" or "Responsibilities"? Not appropriate.
Maybe we can create a section "Requirements" for physical demands? Not exactly.
The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we must map all content to those headings. We can create multiple sections: Responsibilities, Qualifications, Benefits, Schedule. For physical demands and performance metrics, maybe we can put them under "About the role" as a description. Or under "Requirements". But we need to decide.
Physical demands could be considered part of "Requirements" (job requirements). Performance metrics could be part of "About the role" or "Responsibilities". However "Performance metrics" is about reporting; could be under Responsibilities (tracking). But it's separate.
Better to create a section "Requirements" for physical demands and maybe also for performance metrics? But performance metrics not a requirement.
Alternatively, we could create a section "About the role" containing a brief paragraph summarizing the role, and include physical demands and performance metrics there as part of description. That might be acceptable because we have real content to put there (the physical demands and performance metrics). The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we put physical demands and performance metrics under About the role, that's specific content.
Thus we will have:
About the role
Physical demands: ...
Performance metrics: Monthly, quarterly, and annual reporting. Status: Full Time – Exempt. Reports to: Chief Financial Officer (no direct reports initially; Specialist as the department grows).
But we also have "Company benefits: Yes", "Working Days: M-F", "Hours Per Day: Approx. 8-9", "Travel Required: Limited (approx. 10%)". Those go to Benefits and Schedule.
Benefits: we have "Company benefits: Yes". Could also include other benefits? Not given. So Benefits section with that line.
Schedule: we have Working Days, Hours Per Day, Travel Required. We'll put those in Schedule section as a or
. Probably .
Now Responsibilities section with all duties.
Qualifications section with required and preferred.
We must not repeat job title as heading. Not using.
We must not include Job ID/requisition numbers.
We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present.
Now produce HTML fragment.
Let's craft.
Responsibilities: list each duty as
- . Might be long; we can group by subheadings? Not allowed to add extra headings beyond
. But we can still have - with long text containing line breaks? We'll just put each bullet as separate
- .
We need to preserve all substantive information; we can keep the subheadings as part of the
- text (e.g., "Sourcing & Supplier Strategy: Serve as the single purchasing channel...").
Let's draft.
Qualifications: we can have two
maybe one for required, one for preferred, but we can just have one with items prefixed.
Better: Qualifications
- Required: 2+ years...
... - Preferred: Experience in the audiovisual...
But we need to keep the required and preferred separate maybe as separate under same heading? Could do Qualifications
Qualifications
and then list required and preferred within- maybe with notes. That's okay.
- Skills: not explicitly listed; we could omit.
- Benefits: we have "Company benefits: Yes". That's specific enough? It's a statement that benefits are offered. We'll include Benefits section with that line as
- ... ...
- Required: ...
- Preferred: ...
- . Might be long; we can group by subheadings? Not allowed to add extra headings beyond
. But we can still have
- with long text containing line breaks? We'll just put each bullet as separate
- . We need to preserve all substantive information; we can keep the subheadings as part of the
- text (e.g., "Sourcing & Supplier Strategy: Serve as the single purchasing channel...").
Let's draft.
Qualifications: we can have two
- maybe one for required, one for preferred, but we can just have one
- Required: 2+ years... ...
- Preferred: Experience in the audiovisual...
- with items prefixed.
Better:
Qualifications
- under same heading? Could do
Qualifications
. - Schedule: we have Working Days: M-F, Hours Per Day: Approx. 8-9. Also Travel Required: Limited (approx. 10%). That could be part of Schedule or maybe separate but we only have Schedule heading. We'll include schedule info. - Pay: not present, skip. - About the role: we could include a brief paragraph summarizing role from the title? But we must not repeat job title as heading. Could we create About the role section with a paragraph describing the role? The posting didn't have a summary; but we could infer from duties? Might be considered inventing detail. Better to skip About the role if no explicit content. - Requirements: maybe same as Qualifications; we can skip Requirements if we use Qualifications. Thus output:
Responsibilities
Qualifications
under a heading like "About the role" if we treat that as a summary. However we risk adding filler if we don't have content. But we do have content for physical demands and performance metrics; we could create a section "Details" but not allowed. Perhaps we can embed them under "Qualifications" or "Responsibilities"? Not appropriate. Maybe we can create a section "Requirements" for physical demands? Not exactly. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we must map all content to those headings. We can create multiple sections: Responsibilities, Qualifications, Benefits, Schedule. For physical demands and performance metrics, maybe we can put them under "About the role" as a description. Or under "Requirements". But we need to decide.
Physical demands could be considered part of "Requirements" (job requirements). Performance metrics could be part of "About the role" or "Responsibilities". However "Performance metrics" is about reporting; could be under Responsibilities (tracking). But it's separate.
Better to create a section "Requirements" for physical demands and maybe also for performance metrics? But performance metrics not a requirement.
Alternatively, we could create a section "About the role" containing a brief paragraph summarizing the role, and include physical demands and performance metrics there as part of description. That might be acceptable because we have real content to put there (the physical demands and performance metrics). The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we put physical demands and performance metrics under About the role, that's specific content.
Thus we will have:
About the role
About the role
Physical demands: ...
Performance metrics: Monthly, quarterly, and annual reporting. Status: Full Time – Exempt. Reports to: Chief Financial Officer (no direct reports initially; Specialist as the department grows).
But we also have "Company benefits: Yes", "Working Days: M-F", "Hours Per Day: Approx. 8-9", "Travel Required: Limited (approx. 10%)". Those go to Benefits and Schedule. Benefits: we have "Company benefits: Yes". Could also include other benefits? Not given. So Benefits section with that line. Schedule: we have Working Days, Hours Per Day, Travel Required. We'll put those in Schedule section as aor
- . Probably
. Now Responsibilities section with all duties. Qualifications section with required and preferred. We must not repeat job title as heading. Not using. We must not include Job ID/requisition numbers. We must remove boilerplate like cookie/navigation/legal/EEO etc. Not present. Now produce HTML fragment. Let's craft. Responsibilities: list each duty as