Order Management Specialist II
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for any list of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
- About Us: Company description
- How We Work: Core values (BRAVE)
- The Role: Description of the Order Management role
- Core Responsibilities: List of duties
- Core Capabilities: List of skills/abilities
- Experience & Qualifications: List of requirements
- Why Proofpoint?: Benefits/compensation info
- Our Culture: Culture description
- How To Apply: Application instructions (should be removed)
- Pay transparency info: Base pay ranges by location
I need to structure this into appropriate sections. The user wants sections like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But only include sections that have real content.
Let me map:
- "About the role" could combine "The Role" description
- "Responsibilities" from "Core Responsibilities"
- "Requirements" or "Qualifications" from "Experience & Qualifications"
- "Skills" from "Core Capabilities"
- "Benefits" from "Why Proofpoint?" (but note: it lists benefits like competitive compensation, comprehensive benefits, flexible work environment, etc.)
- "Pay" from the pay transparency section (base pay ranges)
- "Schedule" not explicitly mentioned, but "flexible work environment" and "three-week Work from Anywhere option" might be schedule-related.
But the rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state pay ranges and benefits. So I should include Pay and Benefits sections.
Also, "How We Work" and "Our Culture" are company info, maybe not needed as separate sections? The user said "About the role" etc. But we can include a "Company Overview" or similar? The rules say use
for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't forbid other headings, but prefer those. However, the posting has "About Us" and "How We Work" which are company description. The user said "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the text, but presumably "Order Management" role. The page already shows it, so we shouldn't include a heading for the job title.
We need to output only the HTML fragment. Let's decide on sections:
1. About the role (from "The Role" paragraph)
2. Responsibilities (from "Core Responsibilities" list)
3. Skills (from "Core Capabilities" list)
4. Qualifications (from "Experience & Qualifications" list)
5. Benefits (from "Why Proofpoint?" list)
6. Pay (from pay transparency section)
We might also include a brief company description? The rules say "Preserve ALL substantive information". The "About Us" and "How We Work" are substantive about the company. But the user said "Prefer a few substantive sections over many thin ones." Could include a "Company Overview" section with that info. However, the example headings given are specific to the role. The user didn't say we cannot have other headings, but they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests those are the typical sections. But we can add others if needed. However, the company info might be considered boilerplate? It's not cookie/navigation/legal/EEO, it's company description. I think we should include it as a "Company Overview" or "About Us" section. But the user said "Do NOT repeat the job title as a heading". The job title is not in the text. The page already shows it. So we can start with "About the role".
Let's structure:
- About the role
-
...The Role paragraph...
- Responsibilities
- - ... each bullet from Core Responsibilities ...
- Skills
- - ... each bullet from Core Capabilities ...
- Qualifications
- - ... each bullet from Experience & Qualifications ...
- Benefits
- - ... each bullet from Why Proofpoint? ...
- Pay
- ... pay transparency info ...
but the pay info is structured with ranges. Could present as a list or prose. The rule: use - for any list of duties/requirements/benefits, and
for prose. The pay ranges are a list of locations and ranges. Could be a list. But it's not duties/requirements/benefits. It's pay data. Could be a
with each region and range. Or a with line breaks? Better to use
for clarity.
Also, the "Why Proofpoint?" includes "Competitive compensation" which is also in Pay. But we can keep Benefits separate.
The "How To Apply" should be removed.
The "Our Culture" paragraph: "Our culture is rooted in values that inspire belonging, empower purpose and drive success-every day, for everyone. We encourage applications from individuals of all backgrounds, experiences, and perspectives. If you need accommodation during the application or interview process, please reach out to accessibility@proofpoint.com." This is EEO/accommodation boilerplate? It's a culture statement and accommodation notice. The rule says remove EEO/equal-opportunity boilerplate. The accommodation line is EEO-related. The culture statement is generic. Might be considered boilerplate. But it's part of "Our Culture". Could include in a "Culture" section? But the user didn't list Culture as a typical heading. Might be thin. I'll omit it, as it's generic and includes EEO boilerplate.
The "How We Work" with BRAVE values: could be included in "About the role" or a separate "Company Values" section. But again, might be thin. The user said "Preserve ALL substantive information". The values are substantive about the company. However, the job posting is for a role, and the company info is often considered part of the posting. I think we should include a brief "Company Overview" section with About Us and How We Work. But the user didn't specify that heading. They gave examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". They didn't say we cannot add others. But they said "Prefer a few substantive sections over many thin ones." So maybe we can combine company info into a "Company Overview" section. However, the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the headings we should use. It doesn't explicitly forbid others, but the example list is indicative. I'll stick to those headings.
But "About the role" is about the role, not the company. The company info could be omitted? The rule: "Preserve ALL substantive information". If we omit company info, we lose that. But the user might consider that the page already shows company info elsewhere. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". Similarly, maybe company info is already shown elsewhere. However, the user gave the entire posting text, and expects us to reformat it. I think we should include the company description as a section, maybe "About Us". But the example headings don't include "About Us". The user said "e.g." meaning for example. So we can use other headings.
Let's look at the posting: It has "About Us", "How We Work", "The Role", "Core Responsibilities", "Core Capabilities", "Experience & Qualifications", "Why Proofpoint?", "Our Culture", "How To Apply", "Pay transparency". We need to map to semantic sections.
I'll create:
- About the role
(combining The Role description)
- Responsibilities
- Skills
- Qualifications
- Benefits
- Pay
And maybe a Company Overview
for About Us and How We Work. But that adds a section. The user said "Prefer a few substantive sections over many thin ones." Company Overview is substantive. I'll include it.
But the user said "Output ONLY the HTML fragment". So I'll output the HTML.
Let's write the HTML.
First, Company Overview:
Company Overview
Proofpoint is a global leader in human- and agent-centric cybersecurity. We protect how people, data, and AI agents connect across email, cloud, and collaboration tools. Over 80 of the Fortune 100, 10,000 large enterprises, and millions of smaller organizations trust Proofpoint to stop threats, prevent data loss, and build resilience across their people and AI workflows. Our mission is simple: safeguard the digital world and empower people to work securely and confidently.
At Proofpoint you'll be part of a global team that breaks barriers to redefine cybersecurity guided by our BRAVE core values:
- Bold in how we dream and innovate
- Responsive to feedback, challenges and opportunities
- Accountable for results and best in class outcomes
- Visionary in future focused problem-solving
- Exceptional in execution and impact
Then About the role:
About the role
The Order Management role independently manages complex, high-impact orders across the Quote-to-Cash (Q2C) lifecycle. This role is a trusted resource for resolving escalations, ensuring order quality and compliance, and driving continuous process improvement. The individual operates with minimal supervision, partners cross-functionally, and contributes to improving accuracy, efficiency, and scalability of order operations.
Responsibilities:
Responsibilities
- Own and manage complex customer orders end-to-end, ensuring timely and accurate processing
- Interpret contracts, purchase orders (POs), and deal structures to ensure alignment with policies and systems
- Resolve order-related issues and escalations with a focus on
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - About Us: Company description - How We Work: Core values (BRAVE) - The Role: Description of the Order Management role - Core Responsibilities: List of duties - Core Capabilities: List of skills/abilities - Experience & Qualifications: List of requirements - Why Proofpoint?: Benefits/compensation info - Our Culture: Culture description - How To Apply: Application instructions (should be removed) - Pay transparency info: Base pay ranges by location I need to structure this into appropriate sections. The user wants sections like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But only include sections that have real content. Let me map: - "About the role" could combine "The Role" description - "Responsibilities" from "Core Responsibilities" - "Requirements" or "Qualifications" from "Experience & Qualifications" - "Skills" from "Core Capabilities" - "Benefits" from "Why Proofpoint?" (but note: it lists benefits like competitive compensation, comprehensive benefits, flexible work environment, etc.) - "Pay" from the pay transparency section (base pay ranges) - "Schedule" not explicitly mentioned, but "flexible work environment" and "three-week Work from Anywhere option" might be schedule-related. But the rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state pay ranges and benefits. So I should include Pay and Benefits sections. Also, "How We Work" and "Our Culture" are company info, maybe not needed as separate sections? The user said "About the role" etc. But we can include a "Company Overview" or similar? The rules say use
for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It doesn't forbid other headings, but prefer those. However, the posting has "About Us" and "How We Work" which are company description. The user said "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the text, but presumably "Order Management" role. The page already shows it, so we shouldn't include a heading for the job title.
We need to output only the HTML fragment. Let's decide on sections:
1. About the role (from "The Role" paragraph)
2. Responsibilities (from "Core Responsibilities" list)
3. Skills (from "Core Capabilities" list)
4. Qualifications (from "Experience & Qualifications" list)
5. Benefits (from "Why Proofpoint?" list)
6. Pay (from pay transparency section)
We might also include a brief company description? The rules say "Preserve ALL substantive information". The "About Us" and "How We Work" are substantive about the company. But the user said "Prefer a few substantive sections over many thin ones." Could include a "Company Overview" section with that info. However, the example headings given are specific to the role. The user didn't say we cannot have other headings, but they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests those are the typical sections. But we can add others if needed. However, the company info might be considered boilerplate? It's not cookie/navigation/legal/EEO, it's company description. I think we should include it as a "Company Overview" or "About Us" section. But the user said "Do NOT repeat the job title as a heading". The job title is not in the text. The page already shows it. So we can start with "About the role".
Let's structure:
- About the role
-
About the role
-...The Role paragraph...
-Responsibilities
-- ... each bullet from Core Responsibilities ...
Skills
-- ... each bullet from Core Capabilities ...
Qualifications
-- ... each bullet from Experience & Qualifications ...
Benefits
-- ... each bullet from Why Proofpoint? ...
Pay
-... pay transparency info ...
but the pay info is structured with ranges. Could present as a list or prose. The rule: use- for any list of duties/requirements/benefits, and
for prose. The pay ranges are a list of locations and ranges. Could be a list. But it's not duties/requirements/benefits. It's pay data. Could be a
- with each region and range. Or a
- Bold in how we dream and innovate
- Responsive to feedback, challenges and opportunities
- Accountable for results and best in class outcomes
- Visionary in future focused problem-solving
- Exceptional in execution and impact
- Own and manage complex customer orders end-to-end, ensuring timely and accurate processing
- Interpret contracts, purchase orders (POs), and deal structures to ensure alignment with policies and systems
- Resolve order-related issues and escalations with a focus on
with line breaks? Better to use
- for clarity.
Also, the "Why Proofpoint?" includes "Competitive compensation" which is also in Pay. But we can keep Benefits separate.
The "How To Apply" should be removed.
The "Our Culture" paragraph: "Our culture is rooted in values that inspire belonging, empower purpose and drive success-every day, for everyone. We encourage applications from individuals of all backgrounds, experiences, and perspectives. If you need accommodation during the application or interview process, please reach out to accessibility@proofpoint.com." This is EEO/accommodation boilerplate? It's a culture statement and accommodation notice. The rule says remove EEO/equal-opportunity boilerplate. The accommodation line is EEO-related. The culture statement is generic. Might be considered boilerplate. But it's part of "Our Culture". Could include in a "Culture" section? But the user didn't list Culture as a typical heading. Might be thin. I'll omit it, as it's generic and includes EEO boilerplate.
The "How We Work" with BRAVE values: could be included in "About the role" or a separate "Company Values" section. But again, might be thin. The user said "Preserve ALL substantive information". The values are substantive about the company. However, the job posting is for a role, and the company info is often considered part of the posting. I think we should include a brief "Company Overview" section with About Us and How We Work. But the user didn't specify that heading. They gave examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". They didn't say we cannot add others. But they said "Prefer a few substantive sections over many thin ones." So maybe we can combine company info into a "Company Overview" section. However, the instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the headings we should use. It doesn't explicitly forbid others, but the example list is indicative. I'll stick to those headings. But "About the role" is about the role, not the company. The company info could be omitted? The rule: "Preserve ALL substantive information". If we omit company info, we lose that. But the user might consider that the page already shows company info elsewhere. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". Similarly, maybe company info is already shown elsewhere. However, the user gave the entire posting text, and expects us to reformat it. I think we should include the company description as a section, maybe "About Us". But the example headings don't include "About Us". The user said "e.g." meaning for example. So we can use other headings. Let's look at the posting: It has "About Us", "How We Work", "The Role", "Core Responsibilities", "Core Capabilities", "Experience & Qualifications", "Why Proofpoint?", "Our Culture", "How To Apply", "Pay transparency". We need to map to semantic sections. I'll create: -
About the role
(combining The Role description) -Responsibilities
-Skills
-Qualifications
-Benefits
-Pay
And maybe aCompany Overview
for About Us and How We Work. But that adds a section. The user said "Prefer a few substantive sections over many thin ones." Company Overview is substantive. I'll include it. But the user said "Output ONLY the HTML fragment". So I'll output the HTML. Let's write the HTML. First, Company Overview:Company Overview
Proofpoint is a global leader in human- and agent-centric cybersecurity. We protect how people, data, and AI agents connect across email, cloud, and collaboration tools. Over 80 of the Fortune 100, 10,000 large enterprises, and millions of smaller organizations trust Proofpoint to stop threats, prevent data loss, and build resilience across their people and AI workflows. Our mission is simple: safeguard the digital world and empower people to work securely and confidently.
At Proofpoint you'll be part of a global team that breaks barriers to redefine cybersecurity guided by our BRAVE core values:
About the role
The Order Management role independently manages complex, high-impact orders across the Quote-to-Cash (Q2C) lifecycle. This role is a trusted resource for resolving escalations, ensuring order quality and compliance, and driving continuous process improvement. The individual operates with minimal supervision, partners cross-functionally, and contributes to improving accuracy, efficiency, and scalability of order operations.
Responsibilities:Responsibilities