Field Application Engineer - Midwest
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it—never emit heading with filler placeholder like "commensurate with experience", "not specified", etc. Never create Pay/Schedule/Benefits sections unless posting actually states them. The posting mentions "Benefits offered are described: AMD benefits at a glance." That's a mention of benefits but not specific details. Should we include Benefits section? The rule: never create Benefits sections unless posting actually states them. It states "Benefits offered are described: AMD benefits at a glance." That's a statement that benefits exist but not specifics. Is that enough? It says "Benefits offered are described: AMD benefits at a glance." That is a reference to benefits but not actual benefit details. Likely we should not create a Benefits section because no specific benefit details given. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states benefits are described elsewhere, but not actual benefits. I'd interpret that as not enough to create a Benefits section. So we omit Benefits, Pay, Schedule.
We need sections: About the role (maybe from first paragraph?), Responsibilities, Requirements, Qualifications, Skills. The posting includes sections: "The Role", "The Person", "Key Responsibilities", "Preferred Experience", "In Addition, We're Looking For", "Academic Credentials", "LOCATION". Also there is some intro paragraph about AMD mission.
We need to map to headings: About the role (maybe combine intro and The Role). Responsibilities (Key Responsibilities). Requirements (maybe Preferred Experience + In Addition). Qualifications (Academic Credentials). Skills (maybe from The Person bullet list). Also location maybe as a short p.
We must not repeat job title as heading. No job title given explicitly? The posting didn't include a job title; we just have content.
We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details like responsibilities list, etc.
We need to use
- for any list of duties/requirements/benefits. So for responsibilities list, we need
- . For requirements list (Preferred Experience, In Addition) also list. For skills list (The Person) also list. For qualifications (Academic Credentials) maybe just a
(single line). Location maybe
.
We must not include boilerplate like EEO, AI screening, etc. Remove those lines.
Let's extract substantive 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 substantive; we can put under About the role as
.
"The Role" paragraph: "We are looking for our next team member to help AMD drive a new era of computing for AMD commercial solutions, with specialized support for both commercial client and datacenter, working within large enterprise markets. Working with end customers to demonstrate how AMD technology can be used to address the needs of their business. Responsible for providing technical support for the targeted end customer accounts with a special focus on pre-sales and development support activity as opportunities transition from opportunity to deployment. Post-sales technical support is also required as the account encounters technical issues. Responsible for engaging the commercial ecosystem and partnering with the regional OEM leads, as well as OEM/hardware/software partners as needed."
That's role description; could be part of About the role or separate. We'll put under About the role maybe after intro.
"The Person" bullet list: It's a paragraph with many adjectives separated by line breaks? Actually it's a block: "Proficient in managing, optimizing, and troubleshooting common client applications and datacenter workloads on AMD hardware with priority end customersExcellent organizational and communication skills with a good balance of hardware, architecture and software expertiseAbility to work independently as well as part of a team Good time management and prioritization skillsStrong internal (Sales, Marketing, Engineering) and external (customer/partner/OEM) relationships Proven success in developing and maintaining technical relationshipsA standout colleague with excellent collaborative skills and outstanding written and oral communication skillsProven problem-solving skills and the ability to lead complex problems involving multi-disciplined, cross-functional teams"
We need to split into list items. Each seems like a skill. We'll create
- for each distinct skill.
"Key Responsibilities" list: many sentences each starting with verb. We'll create
- for each.
"Preferred Experience" paragraph: "If you have a broad technical understanding of Server / Client CPUs, GPUs and APUs, platform architecture and the development process needed to successfully win client opportunities with end customers and experience working with large enterprise customers we'd love to talk."
That's a requirement.
"In Addition, We're Looking For" list: bullet points after that: "Proven experience working with large enterprise customers Experience in datacenter solutions, with specialized knowledge of client software environments including Operating systems (Windows, Linux), drivers, benchmarks, and targeted applications that may be used to validate server and workstation platforms.Knowledge in one or more of the following areas: CPU and Server system architecture, benchmarks, GPU computing, and Server platform enablementA firm understanding of platform development process from concept to productionGood hands-on and solid knowledge of server hardware ecosystem at the node, rack and datacenter levelHands on experience in the setup and configuration of client systems including software, networking and storage infrastructure"
We need to parse into list items. It's a bit messy but we can split by periods maybe.
"Academic Credentials" line: "Bachelor’s degree in a technical field (e.g. Engineering or Computer Science)"
"LOCATION: Midwest US – Chicago, IL area"
Also note: "This role is not eligible for visa sponsorship." That's substantive? Might be considered metadata but not boilerplate; we could include as a short p under maybe About the role or separate. It's not a heading; we can include as a
.
We must not include duplicated lines. Ensure we don't repeat.
Now produce HTML fragment with sections:
About the role
Intro paragraph + The Role paragraph + maybe visa note.
Responsibilities
- ...
...
Requirements
- ...
...
(combining Preferred Experience and In Addition)
Qualifications
Bachelor’s degree in a technical field (e.g. Engineering or Computer Science)
Skills
- ...
...
(from The Person)
Optionally location as after sections.
We must not add Pay/Benefits/Schedule.
Now craft the content precisely, preserving all info.
Let's extract each piece exactly as in text, but we may need to split into list items.
Intro: "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."
The Role paragraph: "We are looking for our next team member to help AMD drive a new era of computing for AMD commercial solutions, with specialized support for both commercial client and datacenter, working within large enterprise markets. Working with end customers to demonstrate how AMD technology can be used to address the needs of their business. Responsible for providing technical support for the targeted end customer accounts with a special focus on pre-sales and development support activity as opportunities transition from opportunity to deployment. Post-sales technical support is also required as the account encounters technical issues. Responsible for engaging the commercial ecosystem and partnering with the regional OEM leads, as well as OEM/hardware/software partners as needed."
Combine them maybe.
Now Responsibilities list: Let's copy each sentence from "Key Responsibilities" block:
- Develop technical relationships with target end customer accounts and OEM partners
- Win new commercial opportunities by working with our partners by establishing technical solutions based on AMD technology
- Work with AMD internal teams across AMD Business Units to build technical presentations and documentation to be delivered in the field
- Improve AMD’s ability to support large enterprise end customers by driving feedback into AMD BU and engineering teams
- Provide technical assistance to sales personnel and the end customer in the evaluation, design and development of AMD based Server and Client solutions
- Partner with sales in determining possible application of AMD based products and solutions to meet customer requirements
- Perform technical presentations, training and updates for OEM, partners and prospects
- Translate large enterprise customer business issues and requirements into technical solution opportunities/engagements that best demonstrate AMD based product offerings
- Influence and evaluate technical specifications and requirements for our partners with their RFPs
- Possess a solid understanding of the competitive landscape and clearly articulate the technical differentiation and value proposition associated with AMD versus its competitors
- Proficient in security requirements, certifications, and the AMD-based security solutions for large enterprise customers across the ecosystem including AMD hardware, OS, and OEM platforms
- Assist with the solution development/architectural design to meet specific customer needs
- Analyze OEM product solutions and evaluate product performance based on customer needs
- Keep up-to-date on relevant competitive solutions and work with internal teams to provide competitive responses where needed
- Install and test solutions in-house, as required, to ensure successful deployments and evaluations
- Lead technical design sessions; architect and detail technical solutions that are aligned with customer objectives
- Lead technical scopes, requirements and customer expectations
- Provide hands-on, expert-level technical assistance to end customer development and software teams
- Be a credible subject matter authority to customers on direct and indirect product capabilities.
Check that we didn't miss any.
Now Requirements: Preferred Experience sentence: "If you have a broad technical understanding of Server / Client CPUs, GPUs and APUs, platform architecture and the development process needed to successfully win client opportunities with end customers and experience working with large enterprise customers we'd love to talk."
In Addition list: Let's parse:
- Proven experience working with large enterprise customers
- Experience in datacenter solutions, with specialized knowledge of client software environments including Operating systems (Windows, Linux), drivers, benchmarks, and targeted applications that may be used to validate server and workstation platforms.
- Knowledge in one or more of the following areas: CPU and Server system architecture, benchmarks, GPU computing, and Server platform enablement
- A firm understanding of platform development process from concept to production
- Good hands-on and solid knowledge of server hardware ecosystem at the node, rack and datacenter level
- Hands on experience in the setup and configuration of client systems including software, networking and storage infrastructure
Note there may be missing punctuation; we keep as is.
Now Skills from The Person: Need to split into sensible items. The block:
"Proficient in managing, optimizing, and troubleshooting common client applications and datacenter workloads on AMD hardware with priority end customersExcellent organizational and communication skills with a good balance of hardware, architecture and software expertiseAbility to work
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it—never emit heading with filler placeholder like "commensurate with experience", "not specified", etc. Never create Pay/Schedule/Benefits sections unless posting actually states them. The posting mentions "Benefits offered are described: AMD benefits at a glance." That's a mention of benefits but not specific details. Should we include Benefits section? The rule: never create Benefits sections unless posting actually states them. It states "Benefits offered are described: AMD benefits at a glance." That's a statement that benefits exist but not specifics. Is that enough? It says "Benefits offered are described: AMD benefits at a glance." That is a reference to benefits but not actual benefit details. Likely we should not create a Benefits section because no specific benefit details given. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states benefits are described elsewhere, but not actual benefits. I'd interpret that as not enough to create a Benefits section. So we omit Benefits, Pay, Schedule. We need sections: About the role (maybe from first paragraph?), Responsibilities, Requirements, Qualifications, Skills. The posting includes sections: "The Role", "The Person", "Key Responsibilities", "Preferred Experience", "In Addition, We're Looking For", "Academic Credentials", "LOCATION". Also there is some intro paragraph about AMD mission. We need to map to headings: About the role (maybe combine intro and The Role). Responsibilities (Key Responsibilities). Requirements (maybe Preferred Experience + In Addition). Qualifications (Academic Credentials). Skills (maybe from The Person bullet list). Also location maybe as a short p. We must not repeat job title as heading. No job title given explicitly? The posting didn't include a job title; we just have content. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details like responsibilities list, etc. We need to use
- for any list of duties/requirements/benefits. So for responsibilities list, we need
- . For requirements list (Preferred Experience, In Addition) also list. For skills list (The Person) also list. For qualifications (Academic Credentials) maybe just a
(single line). Location maybe
. We must not include boilerplate like EEO, AI screening, etc. Remove those lines. Let's extract substantive 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 substantive; we can put under About the role as
. "The Role" paragraph: "We are looking for our next team member to help AMD drive a new era of computing for AMD commercial solutions, with specialized support for both commercial client and datacenter, working within large enterprise markets. Working with end customers to demonstrate how AMD technology can be used to address the needs of their business. Responsible for providing technical support for the targeted end customer accounts with a special focus on pre-sales and development support activity as opportunities transition from opportunity to deployment. Post-sales technical support is also required as the account encounters technical issues. Responsible for engaging the commercial ecosystem and partnering with the regional OEM leads, as well as OEM/hardware/software partners as needed." That's role description; could be part of About the role or separate. We'll put under About the role maybe after intro. "The Person" bullet list: It's a paragraph with many adjectives separated by line breaks? Actually it's a block: "Proficient in managing, optimizing, and troubleshooting common client applications and datacenter workloads on AMD hardware with priority end customersExcellent organizational and communication skills with a good balance of hardware, architecture and software expertiseAbility to work independently as well as part of a team Good time management and prioritization skillsStrong internal (Sales, Marketing, Engineering) and external (customer/partner/OEM) relationships Proven success in developing and maintaining technical relationshipsA standout colleague with excellent collaborative skills and outstanding written and oral communication skillsProven problem-solving skills and the ability to lead complex problems involving multi-disciplined, cross-functional teams" We need to split into list items. Each seems like a skill. We'll create
- for each distinct skill.
"Key Responsibilities" list: many sentences each starting with verb. We'll create
- for each.
"Preferred Experience" paragraph: "If you have a broad technical understanding of Server / Client CPUs, GPUs and APUs, platform architecture and the development process needed to successfully win client opportunities with end customers and experience working with large enterprise customers we'd love to talk."
That's a requirement.
"In Addition, We're Looking For" list: bullet points after that: "Proven experience working with large enterprise customers Experience in datacenter solutions, with specialized knowledge of client software environments including Operating systems (Windows, Linux), drivers, benchmarks, and targeted applications that may be used to validate server and workstation platforms.Knowledge in one or more of the following areas: CPU and Server system architecture, benchmarks, GPU computing, and Server platform enablementA firm understanding of platform development process from concept to productionGood hands-on and solid knowledge of server hardware ecosystem at the node, rack and datacenter levelHands on experience in the setup and configuration of client systems including software, networking and storage infrastructure"
We need to parse into list items. It's a bit messy but we can split by periods maybe.
"Academic Credentials" line: "Bachelor’s degree in a technical field (e.g. Engineering or Computer Science)"
"LOCATION: Midwest US – Chicago, IL area"
Also note: "This role is not eligible for visa sponsorship." That's substantive? Might be considered metadata but not boilerplate; we could include as a short p under maybe About the role or separate. It's not a heading; we can include as a
. We must not include duplicated lines. Ensure we don't repeat. Now produce HTML fragment with sections:
About the role
Intro paragraph + The Role paragraph + maybe visa note.
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
Bachelor’s degree in a technical field (e.g. Engineering or Computer Science)
Skills
- ... ...
after sections. We must not add Pay/Benefits/Schedule. Now craft the content precisely, preserving all info. Let's extract each piece exactly as in text, but we may need to split into list items. Intro: "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." The Role paragraph: "We are looking for our next team member to help AMD drive a new era of computing for AMD commercial solutions, with specialized support for both commercial client and datacenter, working within large enterprise markets. Working with end customers to demonstrate how AMD technology can be used to address the needs of their business. Responsible for providing technical support for the targeted end customer accounts with a special focus on pre-sales and development support activity as opportunities transition from opportunity to deployment. Post-sales technical support is also required as the account encounters technical issues. Responsible for engaging the commercial ecosystem and partnering with the regional OEM leads, as well as OEM/hardware/software partners as needed." Combine them maybe. Now Responsibilities list: Let's copy each sentence from "Key Responsibilities" block: - Develop technical relationships with target end customer accounts and OEM partners - Win new commercial opportunities by working with our partners by establishing technical solutions based on AMD technology - Work with AMD internal teams across AMD Business Units to build technical presentations and documentation to be delivered in the field - Improve AMD’s ability to support large enterprise end customers by driving feedback into AMD BU and engineering teams - Provide technical assistance to sales personnel and the end customer in the evaluation, design and development of AMD based Server and Client solutions - Partner with sales in determining possible application of AMD based products and solutions to meet customer requirements - Perform technical presentations, training and updates for OEM, partners and prospects - Translate large enterprise customer business issues and requirements into technical solution opportunities/engagements that best demonstrate AMD based product offerings - Influence and evaluate technical specifications and requirements for our partners with their RFPs - Possess a solid understanding of the competitive landscape and clearly articulate the technical differentiation and value proposition associated with AMD versus its competitors - Proficient in security requirements, certifications, and the AMD-based security solutions for large enterprise customers across the ecosystem including AMD hardware, OS, and OEM platforms - Assist with the solution development/architectural design to meet specific customer needs - Analyze OEM product solutions and evaluate product performance based on customer needs - Keep up-to-date on relevant competitive solutions and work with internal teams to provide competitive responses where needed - Install and test solutions in-house, as required, to ensure successful deployments and evaluations - Lead technical design sessions; architect and detail technical solutions that are aligned with customer objectives - Lead technical scopes, requirements and customer expectations - Provide hands-on, expert-level technical assistance to end customer development and software teams - Be a credible subject matter authority to customers on direct and indirect product capabilities. Check that we didn't miss any. Now Requirements: Preferred Experience sentence: "If you have a broad technical understanding of Server / Client CPUs, GPUs and APUs, platform architecture and the development process needed to successfully win client opportunities with end customers and experience working with large enterprise customers we'd love to talk." In Addition list: Let's parse: - Proven experience working with large enterprise customers - Experience in datacenter solutions, with specialized knowledge of client software environments including Operating systems (Windows, Linux), drivers, benchmarks, and targeted applications that may be used to validate server and workstation platforms. - Knowledge in one or more of the following areas: CPU and Server system architecture, benchmarks, GPU computing, and Server platform enablement - A firm understanding of platform development process from concept to production - Good hands-on and solid knowledge of server hardware ecosystem at the node, rack and datacenter level - Hands on experience in the setup and configuration of client systems including software, networking and storage infrastructure Note there may be missing punctuation; we keep as is. Now Skills from The Person: Need to split into sensible items. The block: "Proficient in managing, optimizing, and troubleshooting common client applications and datacenter workloads on AMD hardware with priority end customersExcellent organizational and communication skills with a good balance of hardware, architecture and software expertiseAbility to work
- for each.
"Preferred Experience" paragraph: "If you have a broad technical understanding of Server / Client CPUs, GPUs and APUs, platform architecture and the development process needed to successfully win client opportunities with end customers and experience working with large enterprise customers we'd love to talk."
That's a requirement.
"In Addition, We're Looking For" list: bullet points after that: "Proven experience working with large enterprise customers Experience in datacenter solutions, with specialized knowledge of client software environments including Operating systems (Windows, Linux), drivers, benchmarks, and targeted applications that may be used to validate server and workstation platforms.Knowledge in one or more of the following areas: CPU and Server system architecture, benchmarks, GPU computing, and Server platform enablementA firm understanding of platform development process from concept to productionGood hands-on and solid knowledge of server hardware ecosystem at the node, rack and datacenter levelHands on experience in the setup and configuration of client systems including software, networking and storage infrastructure"
We need to parse into list items. It's a bit messy but we can split by periods maybe.
"Academic Credentials" line: "Bachelor’s degree in a technical field (e.g. Engineering or Computer Science)"
"LOCATION: Midwest US – Chicago, IL area"
Also note: "This role is not eligible for visa sponsorship." That's substantive? Might be considered metadata but not boilerplate; we could include as a short p under maybe About the role or separate. It's not a heading; we can include as a
- for each distinct skill.
"Key Responsibilities" list: many sentences each starting with verb. We'll create
- . For requirements list (Preferred Experience, In Addition) also list. For skills list (The Person) also list. For qualifications (Academic Credentials) maybe just a