Customer Operations Support Manager
for headings, - for lists,
for prose.
We need to parse the posting.
Content:
- Intro paragraph: "ADVANCE YOUR CAREER. ADVANCE THE WORLD. At AMD, we believe technology has the power to solve the world’s most important challenges. From advancing healthcare and scientific discovery to powering AI and the technologies people rely on every day, innovation at AMD is shaping the future. Whether you’re designing next-gen processors, enabling AI breakthroughs, or bringing leading edge products to market, every role at AMD contributes to something bigger — technology that moves the world forward. Join us and, together, we’ll advance your career."
That's about the company, could be "About the role"? Actually "About the role" maybe includes description of role. But we have "The Role Customer Operations Account Manager is responsible for operations between AMD and its customers. They build strong and sustainable relationships at operational and managerial levels within both the Customer’s and AMD’s organization. The Customer Operations Account Manager leverages these relationships to manage expectations, improve operations, and resolve order, supply, delivery, forecast and other operational issues. They work to achieve organizational goals."
That's description of role. Could be placed under "About the role" heading.
Then "Key Responsibilities" list: bullet points (some with parentheses). We'll extract each bullet.
List:
- Executes timely/ongoing review of customer backlogs and collaborates with stakeholders to resolve (e.g., factory, finance, sales, and customers)
- Manages business through all stages of the product lifecycle (NPI, EOL)
- Manages inventory and DOI (Days of Inventory) to prevent incurring inventory cost to AMD
- Manages Demand vs Supply profiles for AMD direct customers or distribution channels
- Monitors the consumption rate and ordering patterns to perform standard demand/supply analysis
- From forecast understanding and maintenance, effectively manages on-time revenue forecasting as assigned
- Identify and manage key internal and external strategic relationships at multiple levels of management to ensure business continuitng (typo: continuitng? Should be continuity)
- Drive projects and processes of identified importance within the organization and provide consultative advice to management, including business partners
- Work collaboratively within the team to share best practices and remove obstacles for all
- Develop self, adopt new tools and processes to achieve goals, create new ways to enhance the organization’s capability
- Enable effective and efficient service through operational excellence and customer collaboration
- Provide leadership and collect feedback in the implementation of new processes in support of the strategy
- Engage with customers through quarterly business reviews and operational meetings
- Provide guidance and support on operational issue resolution
- Support customer operations through a high-level understanding of business processes and procedures
We need to preserve all substantive info; we can keep as is.
Then "Preferred Experience" list:
- Possess understanding of business strategy and the ability to identify areas for process improvement
- Strong problem-solving skills and the ability to implement solution
- Ability to write executive communications
- Strong oral and presentation skills, and can discuss operational concepts with customer, management and team
- Demonstrated use of AI Tools
- Ability to manage conflict internally and externally
- Experience in developing and strengthening customer relationships
- Strong analytical skills required, with the ability to manage cross functional dependencies
- Ability to deal with uncertainty
- Strong Excel, PowerPoint and Power BI skills
- Strong Supply Chain knowledge
- Project management experience
Then "Academic Credentials": Bachelor's degree and/or equivalent industry-related experience
Location: "LOCATION: Austin, Texas This role is not eligible for visa sponsorship."
Benefits: "Benefits offered are described: AMD benefits at a glance."
That's a reference but not details. According to rule: do NOT create Benefits section unless posting actually states them. It says "Benefits offered are described: AMD benefits at a glance." That's not specific benefit details, just a reference. Likely we should not create Benefits section because no specific benefits listed. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states benefits are described elsewhere, but not actual benefits. So we should not include Benefits section.
Pay: none.
Schedule: none.
Thus we may have sections: About the role, Responsibilities, Requirements (maybe Preferred Experience?), Qualifications (Academic Credentials), Skills (maybe combine Preferred Experience and Skills?). The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include based on content.
We have:
- About the role: description paragraph.
- Responsibilities: list.
- Requirements: maybe Preferred Experience? Or we could split into Requirements (mandatory) and Qualifications (education). The posting doesn't separate mandatory vs preferred; it's "Preferred Experience". Could treat as Requirements. Or we could have "Qualifications" for Academic Credentials. And "Skills" for the list of skills (Excel, PowerPoint, etc). But the Preferred Experience includes many skill-like items. Might be better to have "Requirements" for Preferred Experience, and "Qualifications" for Academic Credentials. Or we could combine.
We need to avoid thin sections. Let's see:
- About the role: substantive paragraph.
- Responsibilities: list of many items.
- Preferred Experience: list of items (skills, experience). Could be "Requirements".
- Academic Credentials: Bachelor's degree etc. Could be "Qualifications".
- Location: maybe we could include as a short paragraph under About the role or separate? Not a heading; we can embed in About the role or as a
after.
We should not create sections for Benefits, Pay, Schedule.
Thus output:
About the role
... (company intro + role description)
Responsibilities
- ... each bullet
Requirements
- ... preferred experience bullets
Qualifications
Bachelor's degree and/or equivalent industry-related experience
Optionally include location as a after Qualifications.
We must not repeat job title as heading. Good.
We must not include boilerplate like EEO, legal, etc. Remove.
Check for duplicated lines: none.
Now craft HTML.
We need to preserve all substantive info: ensure we include everything from intro, role description, responsibilities, preferred experience, academic credentials, location, visa sponsorship note? The line "This role is not eligible for visa sponsorship." is substantive; we should keep it. Where to place? Could be after location as a
. It's not a heading.
Also "Benefits offered are described: AMD benefits at a glance." This is not specific benefits; we might still include as a short note? The rule says do NOT create Benefits section unless posting actually states them. It does state that benefits are described elsewhere, but not actual benefits. I'd say we can include a brief note under About the role or as a
but not a Benefits heading. Since it's not a list of benefits, we can include as a short paragraph maybe under About the role or after Qualifications. However, the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The benefits line is not boilerplate; it's a statement about benefits. Might be okay to keep as a
. But we must not create a Benefits heading. So we can add a
after Qualifications: "Benefits offered are described: AMD benefits at a glance."
Similarly, the line about unsolicited resumes from headhunters etc is boilerplate? It's a recruitment policy; could be considered boilerplate? It's not EEO but it's a policy. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those categories, but it's a recruitment agency policy. Might be considered boilerplate? Safer to remove? It's not essential to the role description. I'd remove it.
EEO paragraph definitely remove.
AI screening line: "AMD may use Artificial Intelligence to help screen, assess or select applicants for this position. AMD’s “Responsible AI Policy” is available here." That's maybe boilerplate? It's about process; could be considered boilerplate? Might be removed. The instruction says remove legal/EEO etc. Not explicitly AI policy. But it's still a generic statement. I'd remove to keep focus.
"This posting is for an existing vacancy." Could be removed as boilerplate.
Thus keep: company intro, role description, responsibilities, preferred experience, academic credentials, location, visa sponsorship note, benefits reference.
Now format.
We need to ensure proper HTML:
About the role
...
Responsibilities
- ...
etc.
Make sure to escape any HTML special characters? The text includes parentheses, commas, etc. No need.
Now craft the content.
Company intro paragraph: Combine the first two sentences? Actually we have:
"ADVANCE YOUR CAREER. ADVANCE THE WORLD. At AMD, we believe technology has the power to solve the world’s most important challenges. From advancing healthcare and scientific discovery to powering AI and the technologies people rely on every day, innovation at AMD is shaping the future. Whether you’re designing next-gen processors, enabling AI breakthroughs, or bringing leading edge products to market, every role at AMD contributes to something bigger — technology that moves the world forward. Join us and, together, we’ll advance your career."
Then role description: "The Role Customer Operations Account Manager is responsible for operations between AMD and its customers. They build strong and sustainable relationships at operational and managerial levels within both the Customer’s and AMD’s organization. The Customer Operations Account Manager leverages these relationships to manage expectations, improve operations, and resolve order, supply, delivery, forecast and other operational issues. They work to achieve organizational goals."
We can combine into one about the role.
Now responsibilities list: each bullet as
- .
We need to keep the exact phrasing. Let's list them:
1. Executes timely/ongoing review of customer backlogs and collaborates with stakeholders to resolve (e.g., factory, finance, sales, and customers)
2. Manages business through all stages of the product lifecycle (NPI, EOL)
3. Manages inventory and DOI (Days of Inventory) to prevent incurring inventory cost to AMD
4. Manages Demand vs Supply profiles for AMD direct customers or distribution channels
5. Monitors the consumption rate and ordering patterns to perform standard demand/supply analysis
6. From forecast understanding and maintenance, effectively manages on-time revenue forecasting as assigned
7. Identify and manage key internal and external strategic relationships at multiple levels of management to ensure business continuitng
8. Drive projects and processes of identified importance within the organization and provide consultative advice to management, including business partners
9. Work collaboratively within the team to share best practices and remove obstacles for all
10. Develop self, adopt new tools and processes to achieve goals, create new ways to enhance the organization’s capability
11. Enable effective and efficient service through operational excellence and customer collaboration
12. Provide leadership and collect feedback in the implementation of new processes in support of the strategy
13. Engage with customers through quarterly business reviews and operational meetings
14. Provide guidance and support on operational issue resolution
15. Support customer operations through a high-level understanding of business processes and procedures
Note bullet 7 has typo "continuitng". Keep as is.
Now Preferred Experience list:
- Possess understanding of business strategy and the ability to identify areas for process improvement
- Strong problem-solving skills
for prose. We need to parse the posting. Content: - Intro paragraph: "ADVANCE YOUR CAREER. ADVANCE THE WORLD. At AMD, we believe technology has the power to solve the world’s most important challenges. From advancing healthcare and scientific discovery to powering AI and the technologies people rely on every day, innovation at AMD is shaping the future. Whether you’re designing next-gen processors, enabling AI breakthroughs, or bringing leading edge products to market, every role at AMD contributes to something bigger — technology that moves the world forward. Join us and, together, we’ll advance your career." That's about the company, could be "About the role"? Actually "About the role" maybe includes description of role. But we have "The Role Customer Operations Account Manager is responsible for operations between AMD and its customers. They build strong and sustainable relationships at operational and managerial levels within both the Customer’s and AMD’s organization. The Customer Operations Account Manager leverages these relationships to manage expectations, improve operations, and resolve order, supply, delivery, forecast and other operational issues. They work to achieve organizational goals." That's description of role. Could be placed under "About the role" heading. Then "Key Responsibilities" list: bullet points (some with parentheses). We'll extract each bullet. List: - Executes timely/ongoing review of customer backlogs and collaborates with stakeholders to resolve (e.g., factory, finance, sales, and customers) - Manages business through all stages of the product lifecycle (NPI, EOL) - Manages inventory and DOI (Days of Inventory) to prevent incurring inventory cost to AMD - Manages Demand vs Supply profiles for AMD direct customers or distribution channels - Monitors the consumption rate and ordering patterns to perform standard demand/supply analysis - From forecast understanding and maintenance, effectively manages on-time revenue forecasting as assigned - Identify and manage key internal and external strategic relationships at multiple levels of management to ensure business continuitng (typo: continuitng? Should be continuity) - Drive projects and processes of identified importance within the organization and provide consultative advice to management, including business partners - Work collaboratively within the team to share best practices and remove obstacles for all - Develop self, adopt new tools and processes to achieve goals, create new ways to enhance the organization’s capability - Enable effective and efficient service through operational excellence and customer collaboration - Provide leadership and collect feedback in the implementation of new processes in support of the strategy - Engage with customers through quarterly business reviews and operational meetings - Provide guidance and support on operational issue resolution - Support customer operations through a high-level understanding of business processes and procedures We need to preserve all substantive info; we can keep as is. Then "Preferred Experience" list: - Possess understanding of business strategy and the ability to identify areas for process improvement - Strong problem-solving skills and the ability to implement solution - Ability to write executive communications - Strong oral and presentation skills, and can discuss operational concepts with customer, management and team - Demonstrated use of AI Tools - Ability to manage conflict internally and externally - Experience in developing and strengthening customer relationships - Strong analytical skills required, with the ability to manage cross functional dependencies - Ability to deal with uncertainty - Strong Excel, PowerPoint and Power BI skills - Strong Supply Chain knowledge - Project management experience Then "Academic Credentials": Bachelor's degree and/or equivalent industry-related experience Location: "LOCATION: Austin, Texas This role is not eligible for visa sponsorship." Benefits: "Benefits offered are described: AMD benefits at a glance." That's a reference but not details. According to rule: do NOT create Benefits section unless posting actually states them. It says "Benefits offered are described: AMD benefits at a glance." That's not specific benefit details, just a reference. Likely we should not create Benefits section because no specific benefits listed. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states benefits are described elsewhere, but not actual benefits. So we should not include Benefits section. Pay: none. Schedule: none. Thus we may have sections: About the role, Responsibilities, Requirements (maybe Preferred Experience?), Qualifications (Academic Credentials), Skills (maybe combine Preferred Experience and Skills?). The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections to include based on content. We have: - About the role: description paragraph. - Responsibilities: list. - Requirements: maybe Preferred Experience? Or we could split into Requirements (mandatory) and Qualifications (education). The posting doesn't separate mandatory vs preferred; it's "Preferred Experience". Could treat as Requirements. Or we could have "Qualifications" for Academic Credentials. And "Skills" for the list of skills (Excel, PowerPoint, etc). But the Preferred Experience includes many skill-like items. Might be better to have "Requirements" for Preferred Experience, and "Qualifications" for Academic Credentials. Or we could combine. We need to avoid thin sections. Let's see: - About the role: substantive paragraph. - Responsibilities: list of many items. - Preferred Experience: list of items (skills, experience). Could be "Requirements". - Academic Credentials: Bachelor's degree etc. Could be "Qualifications". - Location: maybe we could include as a short paragraph under About the role or separate? Not a heading; we can embed in About the role or as a
after. We should not create sections for Benefits, Pay, Schedule. Thus output:
About the role
... (company intro + role description)
Responsibilities
- ... each bullet
Requirements
- ... preferred experience bullets
Qualifications
Bachelor's degree and/or equivalent industry-related experience
Optionally include location as aafter Qualifications. We must not repeat job title as heading. Good. We must not include boilerplate like EEO, legal, etc. Remove. Check for duplicated lines: none. Now craft HTML. We need to preserve all substantive info: ensure we include everything from intro, role description, responsibilities, preferred experience, academic credentials, location, visa sponsorship note? The line "This role is not eligible for visa sponsorship." is substantive; we should keep it. Where to place? Could be after location as a
. It's not a heading. Also "Benefits offered are described: AMD benefits at a glance." This is not specific benefits; we might still include as a short note? The rule says do NOT create Benefits section unless posting actually states them. It does state that benefits are described elsewhere, but not actual benefits. I'd say we can include a brief note under About the role or as a
but not a Benefits heading. Since it's not a list of benefits, we can include as a short paragraph maybe under About the role or after Qualifications. However, the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The benefits line is not boilerplate; it's a statement about benefits. Might be okay to keep as a
. But we must not create a Benefits heading. So we can add a
after Qualifications: "Benefits offered are described: AMD benefits at a glance." Similarly, the line about unsolicited resumes from headhunters etc is boilerplate? It's a recruitment policy; could be considered boilerplate? It's not EEO but it's a policy. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those categories, but it's a recruitment agency policy. Might be considered boilerplate? Safer to remove? It's not essential to the role description. I'd remove it. EEO paragraph definitely remove. AI screening line: "AMD may use Artificial Intelligence to help screen, assess or select applicants for this position. AMD’s “Responsible AI Policy” is available here." That's maybe boilerplate? It's about process; could be considered boilerplate? Might be removed. The instruction says remove legal/EEO etc. Not explicitly AI policy. But it's still a generic statement. I'd remove to keep focus. "This posting is for an existing vacancy." Could be removed as boilerplate. Thus keep: company intro, role description, responsibilities, preferred experience, academic credentials, location, visa sponsorship note, benefits reference. Now format. We need to ensure proper HTML:
About the role
...
Responsibilities
- ...
about the role. Now responsibilities list: each bullet as