Senior Procurement Specialist
Qcells EPC · United States · 4 wk ago
RemoteRemotePurchasing$30/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 if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate like EEO, etc. Must not include sections with filler like "commensurate with experience". Must only include sections where there is real content.
We need to parse the posting.
Key info:
Title: Senior Procurement Specialist (but we don't repeat as heading). Department: SCM – EPC Procurement. Location: Houston, TX. Supervisor: Senior Procurement Manager. FLSA Status: Exempt. Position Status: Permanent, Full-time. Work Status: Remote.
Summary: description of responsibilities.
Essential Job Function & Responsibilities: list of duties.
Required Qualifications: bullet list.
Examples of Physical Demands: maybe not needed; but we could include under Requirements? Probably not needed; but we can include as part of Requirements? The instruction: Use
- for any list of duties/requirements/benefits. So we can have sections: About the role (maybe summary), Responsibilities (list), Requirements (maybe education/experience), Qualifications (maybe preferred?), Skills (maybe skills list), Benefits (if any), Pay (if any), Schedule (if any).
We need to see if posting includes Benefits, Pay, Schedule specifics.
Benefits: Not explicitly listed. There's mention: "An additional discretionary bonus structure or incentives may be offered as part of the overall compensation package, in addition to the full range of medical, dental, and/or other benefits, dependent on the level and position offered." That's vague but mentions benefits exist but not specific. The instruction: never create Benefits section unless posting actually states them. It does mention benefits in general but not specific. Is that enough? It says "full range of medical, dental, and/or other benefits". That is somewhat specific but still generic. Might be considered stating benefits exist. However, they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state that there are benefits (medical, dental, etc.) albeit not detailed. I'd argue we can include a Benefits section with that statement. But we must not invent details; we can include the exact sentence.
Pay: The posting mentions salary range required by California Pay Transparency Act, but says the salary range shared is for Irvine, CA and may differ. It does not give actual numbers. It says "The above-listed salary range is required by the California Pay Transparency Act and may differ depending on the location...". However, there is no actual salary range listed in the text we have. So we cannot include Pay section because no specific numbers. The instruction: never create Pay section unless posting actually states them. Since no numbers, we should not include Pay.
Schedule: The posting says: "working hours are Monday through Friday, from 8:00am to 5:00pm or 9:00am to 6:00pm local time." That's a schedule. So we can include Schedule section with that.
Also there is travel up to 15% mentioned.
Now we need to decide sections.
About the role: Could use the summary paragraph (the paragraph after "Summary"). That is substantive.
Responsibilities: The "Essential Job Function & Responsibilities" list.
Requirements: Could include the "Required Qualifications" (education, experience). Also maybe "Preferred experience in Solar or Renewable Energy" etc. But we have separate Qualifications and Skills sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have:
- About the role: summary paragraph.
- Responsibilities: list of duties.
- Requirements: maybe the mandatory qualifications (Bachelor's Degree required, Minimum 4-6 years experience in Contract Management and/or Procurement, Minimum 4 years experience in solar and/or construction field project at project size over $30M, etc.). Also maybe "Applicants must be authorized to work for any employer in the United States. We are unable to sponsor or take over sponsorship of an employment visa at this time." That's a requirement.
- Qualifications: maybe the preferred qualifications: "Preferred experience in Solar or Renewable Energy", "Knowledge in contract management", "Change order management experience", "Ability to work autonomously...", etc. But many of those are skills. Actually the list after Required Qualifications includes many items that could be considered skills or qualifications. We need to split.
We could treat:
Requirements: mandatory (education, years experience, work authorization, etc.)
Qualifications: preferred qualifications (Solar/Renewable Energy experience, knowledge in contract management, change order management, ability to work autonomously, prioritize tasks, organizational skills, communication skills, confidence communicator, experience conducting supplier reviews, computer literacy with MS Office, understanding of construction management software systems, SAP Experience preferred). That seems like qualifications/skills.
Skills: maybe we could separate out technical skills: MS Office, construction management software (Procore, E-Builder, CMiC), SAP. But we already have many.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine Qualifications and Skills into one section? But headings are predefined; we can choose to include only those with real content. We could include Requirements and Responsibilities and About the role and Schedule and Benefits. Possibly also Qualifications (if we have content). Skills maybe not needed if we put those under Qualifications.
Let's see what content we have for each:
About the role: summary paragraph (2-3 sentences). Good.
Responsibilities: list of duties (many). Good.
Requirements: mandatory: Bachelor's Degree required; Minimum 4-6 years experience in Contract Management and/or Procurement; Minimum 4 years experience in solar and/or construction field project at project size over $30M; Applicants must be authorized to work for any employer in the United States; Unable to sponsor visa. Also maybe "Preferred experience in Solar or Renewable Energy" is not mandatory, it's preferred. So we keep that out.
Qualifications: Preferred experience in Solar or Renewable Energy; Knowledge in contract management; Change order management experience; Ability to work autonomously in a fast pace, professional, team environment with minimal supervision; Ability to prioritize tasks appropriately and in support of project schedules and other deadlines; Excellent organizational skills and attention to detail; Strong verbal and written communication skills; Confidence communicator and ability to interact with people at all levels of the organization; Experience in conducting supplier reviews and evaluation, and maintaining good business relationships; Computer literacy with an advance knowledge on Microsoft office including, but not limited to, Excel, Word, Outlook, etc.; Strong understanding of construction management software systems (Procore, E-Builder, CMiC, etc.); SAP Experience preferred.
That's a lot; could be considered qualifications.
Skills: maybe we could separate out technical skills: MS Office, construction management software, SAP. But we already have them in qualifications. To avoid thin sections, we could omit Skills section and put those under Qualifications.
Benefits: we have statement about benefits: "An additional discretionary bonus structure or incentives may be offered as part of the overall compensation package, in addition to the full range of medical, dental, and/or other benefits, dependent on the level and position offered." Also maybe mention of "full range of medical, dental, and/or other benefits". We'll include that.
Schedule: "working hours are Monday through Friday, from 8:00am to 5:00pm or 9:00am to 6:00pm local time." Also travel up to 15% maybe could be under Schedule or Responsibilities. We'll include schedule with working hours and travel.
Pay: No specific numbers, so omit.
Now we need to output HTML fragment with sections.
We must not include any markdown code fences. Just raw HTML.
We need to use
for section headings. Use
- for any list of duties/requirements/benefits.
Use
for prose. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to ensure we don't include the EEO statement etc. We also need to exclude the "EXAMPLES OF PHYSICAL DEMANDS" and "EXAMPLES OF WORK ENVIRONMENT" maybe? Those are not required headings but could be considered part of Requirements? They are not explicitly requested; but we might include them under Requirements? However they are not about qualifications; they are about physical demands and work environment. The instruction says to preserve ALL substantive information; do not invent or summarize away detail. So we should include that information somewhere. Where? Could be under Requirements or maybe a separate section like "Working Conditions". But we only have predefined headings; we could put them under Requirements as part of the list? But they are not requirements per se. However we could include them under Requirements as a list. The instruction: Use
- for any list of duties/requirements/benefits. So we could treat physical demands and work environment as part of Requirements (or maybe a separate section but we don't have a heading for that). Since we must preserve all substantive info, we need to include them somewhere. We could add a section "Requirements" and include both the mandatory qualifications and physical demands/work environment as list items. That would preserve them.
But we must not create sections with filler text. The physical demands and work environment are substantive.
Thus, under Requirements we can have a
- with list items: Bachelor's Degree required; Minimum 4-6 years experience in Contract Management and/or Procurement; Minimum 4 years experience in solar and/or construction field project at project size over $30M; Applicants must be authorized to work for any employer in the United States; Unable to sponsor visa; Physical demands: (list items from EXAMPLES OF PHYSICAL DEMANDS); Work environment: (list items from EXAMPLES OF WORK ENVIRONMENT). However we need to be careful not to invent or summarize away detail. We should preserve the exact phrasing? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the details as they are, maybe as separate list items.
We could keep the physical demands as a sublist? But we only have
- . We could just include each sentence as a list item. Similarly for work environment. Now for Responsibilities we need to list each duty from "Essential Job Function & Responsibilities". That is a long paragraph with semicolons separating duties. We need to split into list items preserving each duty. We must not invent or summarize away detail. So we need to break at each semicolon (and maybe "and" before last). We'll produce list items. Let's extract duties: "Collaborate with internal and external stakeholders to optimize the procurement of materials and/or services;" "Manage key procurement processes in alignment with Companies overall strategic goals;" "Administers the RFP process including, but not limited to the following:Prepare RFPs to qualified suppliers including working with other functional groups to gather all required documents and data;" "Determine and maintain bid schedules in accordance with project schedules;" "Coordinate responses to RFIs from bidders;" "Review, compare and evaluate supplier proposals with historical and market pricing to determine cost-competitive pricing and identify opportunities for cost savings;" "Support commercial negotiations for Equipment Supply Agreements, project specific orders, change orders, etc. with key suppliers in accordance with company policies and guidelines;" "Administer change order process for suppliers and other related contract management processes;" "Ensure prime contract flow downs are incorporated into subcontract documents as needed or applicable to scope of work/supply;"
- for any list of duties/requirements/benefits. So we could treat physical demands and work environment as part of Requirements (or maybe a separate section but we don't have a heading for that). Since we must preserve all substantive info, we need to include them somewhere. We could add a section "Requirements" and include both the mandatory qualifications and physical demands/work environment as list items. That would preserve them.
But we must not create sections with filler text. The physical demands and work environment are substantive.
Thus, under Requirements we can have a
- for any list of duties/requirements/benefits.
Use