Procurement Specialist
for each heading. Use - for lists,
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Must preserve all substantive info. Include sections only if posting has real specific content. Avoid filler like "commensurate with experience". So we need to parse the posting.
Let's extract sections:
- About Standard Bots (company description) maybe not needed as a heading? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include About the role (maybe from "About The Role" paragraph). Then Responsibilities (list of duties). Then Requirements/Qualifications/Skills maybe combined? The posting has "What You'll Bring" which includes requirements, qualifications, skills. We can split into Requirements (experience), Qualifications (education), Skills (technical). But we can also combine into one section if content thin? The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including experience, education, skills), Benefits, Pay. Schedule: location mentions on-site 5 days/week, that's schedule info. So we can include Schedule section.
We must not include filler like "commensurate with experience". The posting says: "We are open to a variety of seniority levels for this role and will build compensation packages that are commensurate with seniority and skill level." That's filler; we should avoid including that sentence if it's just filler. But we need to preserve substantive info: salary range $68,000 to $73,000. Also benefits listed. So we can include Pay section with salary range. Benefits section with list of benefits. Schedule section with on-site 5 days/week location.
We need to avoid repeating job title. Not include "About Standard Bots" maybe not needed as heading; but could be included as a brief intro paragraph? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that. Probably we should include About the role heading and then the paragraph about the role. The "About Standard Bots" is company overview; could be placed before About the role as a
without heading? It's substantive info about company. Might be okay to include as a
before any heading. The instruction: do NOT repeat the job title as a heading (the page already shows it) and 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 about Standard Bots as intro.
Now let's craft HTML.
Structure:
About Standard Bots: Standard Bots builds AI-native industrial robot arms deployed at manufacturing facilities across the U.S. In June 2026 we closed a $200M Series C at a $1B valuation, led by RoboStrategy with continued backing from General Catalyst and new participation from the Amazon Industrial Innovation Fund and Samsung Next.
About the role
As Procurement Specialist, you'll own purchase orders from first quote to final delivery, and you'll be the person Production, Hardware, Sales, and Finance count on to keep builds moving. If you like the idea of your negotiating skills directly determining whether a robot ships on schedule, this is your kind of job.
📍 Location: This is an on-site role (5 days/week) based at Standard Bots' Glen Cove, NY facility.
But location maybe belongs to Schedule section. We'll keep location in Schedule.
Better: About the role paragraph only (the description). Then later Schedule section includes location and on-site 5 days/week.
Now Responsibilities: list from "What You'll Do". We'll create - each bullet.
Responsibilities list:
- Source and evaluate suppliers — electronic component distributors and contract manufacturers alike — on quality, cost, and reliability
- Request and negotiate quotes for custom and off-the-shelf parts, from PCBs and ICs to connectors and other electronic components
- Onboard new vendors and track their performance on quality, on-time delivery, and responsiveness
- Create, manage, and track purchase orders from issuance all the way through delivery
- Manage domestic and international shipments, coordinating with forwarders, carriers, and customs brokers to keep things on schedule
- Reconcile invoices against purchase orders and receipts, catching pricing or quantity discrepancies before they become problems
- Work closely with Production, Hardware, Sales, and Finance to keep purchasing aligned with build schedules and inventory levels
- Keep vendor communication sharp and professional over email and phone
- Support engineering with make-versus-buy calls and alternate sourcing for custom or long-lead components
- Hunt for ways to shorten lead times, cut cost, and streamline how purchasing actually works
- Maintain a quote log and cost database that leadership can actually use for spend analysis and budgeting
Now Requirements/Qualifications/Skills: from "What You'll Bring". We'll need to decide sections. Could combine into one section "Requirements" with sub-bullets. But instruction: prefer few substantive sections over many thin ones. So we can have one section "Requirements" that includes experience, education, skills. However they also have separate headings like Qualifications, Skills in the list of possible headings. But we can choose to include only those with real content. The posting includes all those categories; we could split into Requirements (experience), Qualifications (education), Skills (technical). That's three sections but each substantive. Might be okay. But instruction: prefer a few substantive sections over many thin ones. Three is still few. Let's do three: Requirements (experience), Qualifications (education), Skills (technical). Or we could combine experience and skills into Requirements and have Qualifications for education. Let's see.
What You'll Bring bullet list:
- 2–5 years of hands-on procurement, purchasing, or supply chain experience in a manufacturing or hardware environment
- Demonstrated experience purchasing electronic components — PCBs, ICs, connectors, passives, or similar — for a hardware or electronics manufacturing environment (required)
- Experience purchasing CNC-machined parts, welded assemblies, or other mechanical and electrical components
- Experience working from engineering BOMs or technical part lists to build out purchasing requirements
- Familiarity with international logistics — lead times, customs, freight tracking
- Confidence negotiating with suppliers to land favorable pricing, terms, and delivery
- A bachelor's degree or equivalent experience
- Proficiency with ERP or procurement platforms like NetSuite, QuickBooks, or Fishbowl — and comfort picking up new systems fast
- Strong Excel or Google Sheets skills for BOM tracking, spend analysis, and inventory management
- Ability to read engineering drawings and interpret BOM structures, including assemblies and sub-assemblies
- Familiarity with freight documentation — bills of lading, packing slips, certificates of conformance, customs forms
- Comfort processing invoices and handling basic accounts payable
- Sharp organizational instincts — you keep records accurate, flag discrepancies early, and follow through on open items
- A self-directed streak — you spot shortages and process gaps before they turn into fires
- Clear, proactive communication with Production, Hardware, Sales, and Finance, with context when you escalate
- Comfort with the pace and shape-shifting nature of a growing hardware startup
- A genuine commitment to ethics, integrity, and confidentiality
- Nice to have: Experience in robotics, automation, or advanced manufacturing supply chains
- Nice to have: A trusted network of vetted electronic component distributors or contract manufacturers
- Nice to have: Familiarity with Incoterms and international freight/customs processes
- Nice to have: Experience with lean inventory practices, Kanban systems, or demand-driven replenishment
- Nice to have: Prior experience supporting the implementation or refinement of an ERP/MRP platform
We need to separate required vs nice-to-have? Not required but we can keep all.
We could create Requirements section for experience bullets (first 6 maybe). Qualifications for education (bachelor's degree). Skills for technical proficiencies (ERP, Excel, etc.) plus other abilities.
But many bullets overlap. Let's think: The instruction: Use
- for any list of duties/requirements/benefits. So we can have multiple lists.
We'll create:
Requirements
- 2–5 years of hands-on procurement, purchasing, or supply chain experience in a manufacturing or hardware environment
- Demonstrated experience purchasing electronic components — PCBs, ICs, connectors, passives, or similar — for a hardware or electronics manufacturing environment (required)
- Experience purchasing CNC-machined parts, welded assemblies, or other mechanical and electrical components
- Experience working from engineering BOMs or technical part lists to build out purchasing requirements
- Familiarity with international logistics — lead times, customs, freight tracking
- Confidence negotiating with suppliers to land favorable pricing, terms, and delivery
Qualifications
- A bachelor's degree or equivalent experience
Skills
- Proficiency with ERP or procurement platforms like NetSuite, QuickBooks, or Fishbowl — and comfort picking up new systems fast
- Strong Excel or Google Sheets skills for BOM tracking, spend analysis, and inventory management
- Ability to read engineering drawings and interpret BOM structures, including assemblies and sub-assemblies
- Familiarity with freight documentation — bills of lading, packing slips, certificates of conformance, customs forms
- Comfort processing invoices and handling basic accounts payable
- Sharp organizational instincts — you keep records accurate, flag discrepancies early, and follow through on open items
- A self-directed streak — you spot shortages and process gaps before they turn into fires
- Clear, proactive communication with Production, Hardware, Sales, and Finance, with context when you escalate
- Comfort with the pace and shape-shifting nature of a growing hardware startup
- A genuine commitment to ethics, integrity, and confidentiality
Nice-to-have items could be included in Skills as well, but we could add a separate "Nice to have" subsection but that might be thin. However they are substantive. Could add another Nice to have
with list. But instruction: prefer few sections; but we already have many sections. Might be okay to include Nice to have as part of Skills? Could add a note within Skills list: "Nice to have: ..." but that mixes. Better to keep separate but maybe we can combine all into Skills and note nice-to-have in parentheses. However we need to preserve all substantive info; we can include them as separate bullet points with "(Nice to have)" prefix.
Let's incorporate them into Skills list with prefix.
Now Benefits section: list of benefits: paid time off, medical/dental/vision insurance, life insurance, disability insurance, 401(k) to regular full-time employees. Also Employee Stock Options for all Full-Time Employees. Also base salary range? That's Pay.
We'll create Benefits section:
Benefits
- Employee Stock Options (eligible for all Full-Time Employees)
- Paid time off
- Medical, dental, and vision insurance
- Life insurance
- Disability insurance
- 401(k) plan (regular full-time employees)
Pay section: salary range $68,000 to $73,000. Also note
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Must preserve all substantive info. Include sections only if posting has real specific content. Avoid filler like "commensurate with experience". So we need to parse the posting. Let's extract sections: - About Standard Bots (company description) maybe not needed as a heading? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include About the role (maybe from "About The Role" paragraph). Then Responsibilities (list of duties). Then Requirements/Qualifications/Skills maybe combined? The posting has "What You'll Bring" which includes requirements, qualifications, skills. We can split into Requirements (experience), Qualifications (education), Skills (technical). But we can also combine into one section if content thin? The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including experience, education, skills), Benefits, Pay. Schedule: location mentions on-site 5 days/week, that's schedule info. So we can include Schedule section. We must not include filler like "commensurate with experience". The posting says: "We are open to a variety of seniority levels for this role and will build compensation packages that are commensurate with seniority and skill level." That's filler; we should avoid including that sentence if it's just filler. But we need to preserve substantive info: salary range $68,000 to $73,000. Also benefits listed. So we can include Pay section with salary range. Benefits section with list of benefits. Schedule section with on-site 5 days/week location. We need to avoid repeating job title. Not include "About Standard Bots" maybe not needed as heading; but could be included as a brief intro paragraph? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that. Probably we should include About the role heading and then the paragraph about the role. The "About Standard Bots" is company overview; could be placed before About the role as a
without heading? It's substantive info about company. Might be okay to include as a
before any heading. The instruction: do NOT repeat the job title as a heading (the page already shows it) and 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 about Standard Bots as intro. Now let's craft HTML. Structure:
About Standard Bots: Standard Bots builds AI-native industrial robot arms deployed at manufacturing facilities across the U.S. In June 2026 we closed a $200M Series C at a $1B valuation, led by RoboStrategy with continued backing from General Catalyst and new participation from the Amazon Industrial Innovation Fund and Samsung Next.
About the role
As Procurement Specialist, you'll own purchase orders from first quote to final delivery, and you'll be the person Production, Hardware, Sales, and Finance count on to keep builds moving. If you like the idea of your negotiating skills directly determining whether a robot ships on schedule, this is your kind of job.
📍 Location: This is an on-site role (5 days/week) based at Standard Bots' Glen Cove, NY facility.
But location maybe belongs to Schedule section. We'll keep location in Schedule. Better: About the role paragraph only (the description). Then later Schedule section includes location and on-site 5 days/week. Now Responsibilities: list from "What You'll Do". We'll create- each bullet.
Responsibilities list:
- Source and evaluate suppliers — electronic component distributors and contract manufacturers alike — on quality, cost, and reliability
- Request and negotiate quotes for custom and off-the-shelf parts, from PCBs and ICs to connectors and other electronic components
- Onboard new vendors and track their performance on quality, on-time delivery, and responsiveness
- Create, manage, and track purchase orders from issuance all the way through delivery
- Manage domestic and international shipments, coordinating with forwarders, carriers, and customs brokers to keep things on schedule
- Reconcile invoices against purchase orders and receipts, catching pricing or quantity discrepancies before they become problems
- Work closely with Production, Hardware, Sales, and Finance to keep purchasing aligned with build schedules and inventory levels
- Keep vendor communication sharp and professional over email and phone
- Support engineering with make-versus-buy calls and alternate sourcing for custom or long-lead components
- Hunt for ways to shorten lead times, cut cost, and streamline how purchasing actually works
- Maintain a quote log and cost database that leadership can actually use for spend analysis and budgeting
Now Requirements/Qualifications/Skills: from "What You'll Bring". We'll need to decide sections. Could combine into one section "Requirements" with sub-bullets. But instruction: prefer few substantive sections over many thin ones. So we can have one section "Requirements" that includes experience, education, skills. However they also have separate headings like Qualifications, Skills in the list of possible headings. But we can choose to include only those with real content. The posting includes all those categories; we could split into Requirements (experience), Qualifications (education), Skills (technical). That's three sections but each substantive. Might be okay. But instruction: prefer a few substantive sections over many thin ones. Three is still few. Let's do three: Requirements (experience), Qualifications (education), Skills (technical). Or we could combine experience and skills into Requirements and have Qualifications for education. Let's see.
What You'll Bring bullet list:
- 2–5 years of hands-on procurement, purchasing, or supply chain experience in a manufacturing or hardware environment
- Demonstrated experience purchasing electronic components — PCBs, ICs, connectors, passives, or similar — for a hardware or electronics manufacturing environment (required)
- Experience purchasing CNC-machined parts, welded assemblies, or other mechanical and electrical components
- Experience working from engineering BOMs or technical part lists to build out purchasing requirements
- Familiarity with international logistics — lead times, customs, freight tracking
- Confidence negotiating with suppliers to land favorable pricing, terms, and delivery
- A bachelor's degree or equivalent experience
- Proficiency with ERP or procurement platforms like NetSuite, QuickBooks, or Fishbowl — and comfort picking up new systems fast
- Strong Excel or Google Sheets skills for BOM tracking, spend analysis, and inventory management
- Ability to read engineering drawings and interpret BOM structures, including assemblies and sub-assemblies
- Familiarity with freight documentation — bills of lading, packing slips, certificates of conformance, customs forms
- Comfort processing invoices and handling basic accounts payable
- Sharp organizational instincts — you keep records accurate, flag discrepancies early, and follow through on open items
- A self-directed streak — you spot shortages and process gaps before they turn into fires
- Clear, proactive communication with Production, Hardware, Sales, and Finance, with context when you escalate
- Comfort with the pace and shape-shifting nature of a growing hardware startup
- A genuine commitment to ethics, integrity, and confidentiality
- Nice to have: Experience in robotics, automation, or advanced manufacturing supply chains
- Nice to have: A trusted network of vetted electronic component distributors or contract manufacturers
- Nice to have: Familiarity with Incoterms and international freight/customs processes
- Nice to have: Experience with lean inventory practices, Kanban systems, or demand-driven replenishment
- Nice to have: Prior experience supporting the implementation or refinement of an ERP/MRP platform
We need to separate required vs nice-to-have? Not required but we can keep all.
We could create Requirements section for experience bullets (first 6 maybe). Qualifications for education (bachelor's degree). Skills for technical proficiencies (ERP, Excel, etc.) plus other abilities.
But many bullets overlap. Let's think: The instruction: Use
- for any list of duties/requirements/benefits. So we can have multiple lists.
We'll create:
Requirements
- 2–5 years of hands-on procurement, purchasing, or supply chain experience in a manufacturing or hardware environment
- Demonstrated experience purchasing electronic components — PCBs, ICs, connectors, passives, or similar — for a hardware or electronics manufacturing environment (required)
- Experience purchasing CNC-machined parts, welded assemblies, or other mechanical and electrical components
- Experience working from engineering BOMs or technical part lists to build out purchasing requirements
- Familiarity with international logistics — lead times, customs, freight tracking
- Confidence negotiating with suppliers to land favorable pricing, terms, and delivery
Qualifications
- A bachelor's degree or equivalent experience
Skills
- Proficiency with ERP or procurement platforms like NetSuite, QuickBooks, or Fishbowl — and comfort picking up new systems fast
- Strong Excel or Google Sheets skills for BOM tracking, spend analysis, and inventory management
- Ability to read engineering drawings and interpret BOM structures, including assemblies and sub-assemblies
- Familiarity with freight documentation — bills of lading, packing slips, certificates of conformance, customs forms
- Comfort processing invoices and handling basic accounts payable
- Sharp organizational instincts — you keep records accurate, flag discrepancies early, and follow through on open items
- A self-directed streak — you spot shortages and process gaps before they turn into fires
- Clear, proactive communication with Production, Hardware, Sales, and Finance, with context when you escalate
- Comfort with the pace and shape-shifting nature of a growing hardware startup
- A genuine commitment to ethics, integrity, and confidentiality
Nice to have
with list. But instruction: prefer few sections; but we already have many sections. Might be okay to include Nice to have as part of Skills? Could add a note within Skills list: "Nice to have: ..." but that mixes. Better to keep separate but maybe we can combine all into Skills and note nice-to-have in parentheses. However we need to preserve all substantive info; we can include them as separate bullet points with "(Nice to have)" prefix. Let's incorporate them into Skills list with prefix. Now Benefits section: list of benefits: paid time off, medical/dental/vision insurance, life insurance, disability insurance, 401(k) to regular full-time employees. Also Employee Stock Options for all Full-Time Employees. Also base salary range? That's Pay. We'll create Benefits section:Benefits
- Employee Stock Options (eligible for all Full-Time Employees)
- Paid time off
- Medical, dental, and vision insurance
- Life insurance
- Disability insurance
- 401(k) plan (regular full-time employees)
- for any list of duties/requirements/benefits. So we can have multiple lists.
We'll create: