Senior Buyer Planner

We need to output HTML fragment with sections: About the role? Actually the posting includes "About IonQ" description, location, travel, job ID, then "The Role:" description, responsibilities, requirements, preferred qualifications, compensation, benefits, etc. We must not repeat job title as heading. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content. We have: - About IonQ: description of company. Could be "About the role"? Actually "About IonQ" is about company, not role. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading for the description of the role (the paragraph after "The Role:"). We also have location and travel info; maybe we can include as a short paragraph under "About the role" or separate? Not required to have a heading for location; we can embed in a

. Responsibilities: we have a list of duties. Use

• . Requirements: we have bullet list (though not formatted as bullet but sentences). We'll convert to
  • . Preferred Qualifications: could be under "Qualifications" or "Skills". The instruction includes Qualifications and Skills as possible headings. We could combine preferred qualifications under "Qualifications". Or we could have "Qualifications" for required and "Preferred Qualifications" maybe as a subsection? But we should avoid thin sections. Perhaps combine required and preferred under "Qualifications" with two sub-lists? But we must not invent headings not listed. We could have "Qualifications" heading and include both required and preferred as separate
    maybe with a note. Or we could have "Skills" for preferred qualifications. Let's decide: Use "Requirements" for required qualifications, and "Preferred Qualifications" maybe as a separate heading? The instruction list includes Qualifications and Skills but not "Preferred Qualifications". However we can still use "Qualifications" heading for both required and preferred, but we need to differentiate? Could just list all under one
    but that would mix required and preferred; might be okay but we risk losing distinction. Better to have "Requirements" for required, and "Qualifications" for preferred (or Skills). The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "Qualifications" for preferred qualifications. Or "Skills" for skills like Excel, etc. But we have many skill-like items in requirements (Excel, BOMs, etc). Could treat those as Skills. However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one "Requirements" section that includes both required and preferred, but we can note "Preferred" within items. That might be acceptable. We also have compensation: Wage Transparency range $100,800—$126,000 USD, plus note about bonus, equity, benefits. So we have Pay section. Benefits: list of benefits: comprehensive medical, dental, vision, matching 401(k), unlimited PTO and paid holidays, parental/adoption leave, legal insurance, home technology stipend. So Benefits section. Schedule: not mentioned besides location and travel up to 5%; no explicit schedule (full-time?). Not given, so we should not create Schedule section. Pay: we have compensation range. So we create Pay section. We also need to include location and travel info maybe as a short paragraph under About the role or separate? Could be under About the role. We must not include boilerplate like EEO, legal, application instructions, etc. Remove those. We must preserve all substantive information: company description, location, travel, role description, responsibilities, requirements, preferred qualifications, compensation, benefits. We must not repeat job title as heading. The job title is "Buyer Planner". Not to be used as heading. We must not put Job ID/requisition numbers as headings; we can drop them or fold into short p. We'll drop. We must not include cookie/navigation/legal/EEO etc. Now craft HTML. Structure:

    About the role

    ... role description paragraph(s) ... maybe also include location and travel.

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Pay

    Wage transparency: $100,800—$126,000 USD base compensation. Total compensation includes base, bonus, equity, and a range of benefit options.

    Benefits

    • Comprehensive medical, dental, and vision plans
    • Matching 401(k)
    • Unlimited PTO and paid holidays
    • Parental/adoption leave
    • Legal insurance
    • Home technology stipend
    We might also include a short paragraph about location and travel inside About the role. Let's extract role description: After "The Role:" we have: "We are looking for a Buyer Planner to join our Supply Chain team. As a Buyer Planner, you'll be part of a cross-functional team whose mission is to lead IonQ on its journey to build the world's best quantum computers to solve the world's most complex problems. In this role, you will own the buy side of the material plan — converting demand into purchase orders, holding vendors to committed dates, and keeping the supply picture in the ERP accurate enough that the rest of the organization can plan against it. You are the connection point between what the factory needs and what the supply base has actually agreed to deliver. This is a high-volume, high-judgment execution role. Lead times are long, demand shifts, and a large share of what you buy is custom or single-source. The ideal candidate is someone who works a queue with discipline, chases commitments rather than replies, and understands that a date is only real once it is recorded in the system." We can include that. Location and travel: "Location: This role will work onsite at our office located in Bothell, WA. Travel: Up to 5%, domestic or international." We can add after role description. Now responsibilities list: Let's extract each bullet from the responsibilities paragraph. The responsibilities paragraph is long with many sentences separated by line breaks? Let's parse: "Purchasing Execution Review the buyer workbench daily for new demand, pull-ins, quantity changes, and cancellations before releasing anything, so that every release is a deliberate decisionRelease compressed lead time purchase requests first, prioritizing items past the Suggested Order Date, then batch standard within-lead-time releasesCreate Transfer Orders to connect supply and demand across locations and subsidiaries, checking other locations' on-hand before releasing a new POWork the purchase request intake queue end to end: requests assigned to you, items needing a vendor or vendor part number, quote requests, returned or rejected requests, and approved requests with no PO created yetReturn a status note to the requester on anything aging in the queue Delivery & Supplier Management Chase purchase order acknowledgments where a vendor has not confirmed price, quantity, and date Confirm delivery dates and update the PO with each new committed dateDrive expedite and pull-in requests for material creating a shortage or a compressed date; Data Integrity & Financial Accuracy Resolve three-way match discrepancies — price variance, quantity variance, or missing receipts — correcting whichever record is actually wrong rather than forcing the invoice throughEstablish and maintain lead times in NetSuite for items missing themIdentify and load preferred vendors and vendor part numbers for items missing them" We need to split into sensible items. Could break at each capitalized section heading? But we can just create list items for each major responsibility: - Review the buyer workbench daily for new demand, pull-ins, quantity changes, and cancellations before releasing anything, so that every release is a deliberate decision. - Release compressed lead time purchase requests first, prioritizing items past the Suggested Order Date, then batch standard within-lead-time releases. - Create Transfer Orders to connect supply and demand across locations and subsidiaries, checking other locations' on-hand before releasing a new PO. - Work the purchase request intake queue end to end: requests assigned to you, items needing a vendor or vendor part number, quote requests, returned or rejected requests, and approved requests with no PO created yet. - Return a status note to the requester on anything aging in the queue. - Chase purchase order acknowledgments where a vendor has not confirmed price, quantity, and date. - Confirm delivery dates and update the PO with each new committed date. - Drive expedite and pull-in requests for material creating a shortage or a compressed date. - Resolve three-way match discrepancies — price variance, quantity variance, or missing receipts — correcting whichever record is actually wrong rather than forcing the invoice through. - Establish and maintain lead times in NetSuite for items missing them. - Identify and load preferred vendors and vendor part numbers for items missing them. That seems good. Now requirements list: The requirements paragraph: "[2]+ years of purchasing, buying, or materials planning experience in a manufacturing environment, or an equivalent combination of education and experienceBachelor's degree in Supply Chain, Operations, Business, or a related field, or equivalent practical experienceWorking knowledge of MRP/ERP purchasing mechanics — planned orders, suggested order dates, lead time logic, exception messagesDirect experience managing vendor relationships and holding suppliers to committed delivery datesStrong Excel skills — pivot tables, lookups, and the ability to build a working analysis without waiting on a report requestAbility to read and interpret BOMs and engineering drawings well enough to buy the right partOrganized and persistent; able to work a large daily queue to completion and communicate status clearly" We need to split into items: - 2+ years of purchasing, buying, or materials planning experience in a manufacturing environment, or an equivalent combination of education and experience. - Bachelor's degree in Supply Chain, Operations, Business, or a related field, or equivalent practical experience. - Working knowledge of MRP/ERP purchasing mechanics — planned orders, suggested order dates, lead time logic, exception messages. - Direct experience managing vendor relationships and holding suppliers to committed delivery dates. - Strong Excel skills — pivot tables, lookups, and the ability to build a working analysis without waiting on a report request. - Ability to read and interpret BOMs and engineering drawings well enough to buy the right part. - Organized and persistent; able to work a large daily queue to completion and communicate status clearly. Now preferred qualifications list: "Experience with NetSuite or a comparable Tier 1/Tier 2 ERPExperience with an intake or procure-to-pay tool such as Zip, Coupa, or AribaBackground in high-mix / low-volume, prototype-to-production, or new product introduction environmentsAPICS/ASCM certification (CPIM, CPSM, CSCP) or active pursuitExperience buying custom fabrication, machined parts, electronics, or long-lead capital equipmentFamiliarity with three-way match, receiving, and AP resolution workflowsWorking knowledge of business analytics reporting tools" Split: - Experience with NetSuite or a comparable Tier 1/Tier 2 ERP. - Experience with an intake or procure-to-pay tool such as Zip, Coupa, or Ariba. - Background in high-mix / low-volume, prototype-to-production, or new product introduction environments. - APICS/ASCM certification (CPIM, CPSM, CSCP) or active pursuit. - Experience buying custom fabrication, machined parts, electronics, or long-lead capital equipment. - Familiarity with three-way match, receiving, and AP resolution workflows. - Working knowledge of business analytics reporting tools. Now Pay section: We have compensation range and note about bonus, equity, benefits. We'll write:

    The