Field Application Engineer - AMD/Xilinx
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to extract sections: Who We Are (maybe "About the company"? Not listed in allowed headings but we could use "About the role"? Actually "Who We Are" is about company, not role. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also possibly add other headings if needed? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we could use other headings if appropriate, but better to stick to those. The posting includes "Who We Are" (company overview) maybe we can treat as "About the role"? Not exactly. Could we omit? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings. But they gave examples; we could include "About the company" as maybe. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This implies those are typical sections; we can use them if content matches. For company overview, maybe we can put under "About the role"? Not ideal. Could we just not include a heading for that and embed in a
before sections? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview with job summary maybe under "About the role". Let's see.
We have sections:
- Who We Are: company description.
- Job Summary: includes visa requirement, US citizen, role description.
- Principal Responsibilities: list of duties.
- Work Experience: minimum experience.
- Education and Certification(s): Bachelors degree.
- Distinguishing Characteristics: Bachelor's Degree in EE or CS or equivalent 8+ years experience FPGA-based architecture definition, design, and support (High Speed Serial IO, Embedded Processor, or DSP knowledge a plus)
- Required Skills: list.
- Desirable Skills: list.
- Pay and Benefits: includes link to PDF and salary range.
- What We Offer: benefits list.
- Then EEO boilerplate etc to remove.
We need to produce sections: maybe "About the role" (combining Who We Are and Job Summary?), "Responsibilities", "Requirements" (maybe combine Work Experience, Education, Distinguishing Characteristics), "Skills" (Required and Desirable), "Benefits", "Pay". Schedule not present, so omit.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: salary range. Benefits are stated: link and list. So we can have separate Pay and Benefits sections, or combine? The instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one section? But they gave examples separate. However we can decide to combine if it reduces thin sections. But we need to preserve all substantive info. Combining is okay as long as we include both pay and benefits details. Let's see: The posting has "Pay and Benefits:" heading with link and salary range, then "What We Offer:" with benefits list. So we could have a single section "Compensation and Benefits" but not in allowed list. Might be safer to follow examples: have "Pay" and "Benefits" sections. That's two sections, not too many.
We also need to include "Requirements" maybe covering Work Experience, Education, Distinguishing Characteristics. Could also include "Qualifications". The examples include Requirements, Qualifications. We could use "Requirements" for experience/education, and "Qualifications" for distinguishing characteristics? Or combine. Let's think.
We need to avoid filler like "commensurate with experience". Not present.
We must remove boilerplate: EEO, accommodation, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "Position open until filled" maybe minor metadata; could fold into short p or drop. Probably drop.
We must not include job ID/requisition numbers.
We must not repeat job title as heading.
We must output only HTML fragment.
Thus final HTML:
About the role
Who We Are: At Avnet, relationships matter. We are a global, FORTUNE® 500 technology distributor and solutions company that delivers design, supply chain and logistics expertise to customers at every stage of a product’s lifecycle. Our employees have a front row seat to the latest innovations shaping the world we live in and the future we share. We’re driven to help our customers around the world succeed and we do so by earning the trust of some of the biggest names in technology. Working at Avnet means being a part of a global team. We work collaboratively and with integrity, doing business the right way. For more than a century, we have partnered together to help our customers, suppliers and teammates realize the transformative possibilities of technology. Experience what’s next at Avnet!
Job Summary: Applicants for this position must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time. MUST be U.S. Citizen. As the AMD Xilinx dedicated Field Application Engineer you will be a key member of a technical sales team acting as lead for AMD Xilinx Hardware & Software aspects of our key customers’ systems. An ideal candidate for this role will be an enthusiastic and highly motivated technical individual who wants to be marketing the cutting edge of SoC technology and proactively engaged with customers in AMD Xilinx pre- and post-sale design and technical support activities.
Responsibilities
- Drive and manage Xilinx technical related initiatives & activities for key customers in alignment with the AMD Xilinx dedicated Technical Sales Engineer (TSE)
- Provide technical leadership and guidance that focuses on AMD Xilinx design win strategies for customer opportunities
- Develop relationships with and become trusted advisor to (system) engineers & architects in your assigned key accounts
- Drive the technical part of strategy proposals for key customer programs
- Leverages understanding of known challenges to advise customer designers on the optimum use of Xilinx IP, software tools and hardware devices
- Manage technical support issues within customer base and collaborate/bring in AMD Xilinx technical specialists when required to help solve real time problems (e.g. software tool & IP issues, Design Closure, RTL and simulation assistance, system bring up and debug)
- Collaborate with field and AMD Xilinx factory resources to develop and deliver technical proposals to customer project managers, engineering managers, system architects and design engineers that align with customers’ needs
- Lead with technical solution creation to show our value proposition (e.g.: hardware, software demos, example designs)
- Work with 3rd party ecosystem partners to support mutual beneficial custom solutions into the customer base where applicable
- Attend internal and external AMD Xilinx technical training to complete and maintain certification as necessary.
- Other duties as assigned.
Requirements
- Minimum experience required is typically 8+ years with bachelor's or equivalent.
- Bachelors degree or equivalent experience from which comparable knowledge and job skills can be obtained.
Qualifications
- Bachelor's Degree in Electrical Engineering or Computer Science or equivalent
- 8+ years experience FPGA-based architecture definition, design, and support (High Speed Serial IO, Embedded Processor, or DSP knowledge a plus)
Skills
- Experience with and understanding at systems level, FPGA and ASIC design tools.
- Experience with Vivado/Vitis, ISE or Quartus required (ModelSim is a plus)
- Ability to identify a customer’s key care-abouts and thus contribute to overall sales strategy and success
- Knowledge of customers' end products including their specific market requirements.
- Strong analytical and problem-solving skills
- Strong presentations skills, and the ability to work with multiple groups
- Aptitude to communicate clearly at a high system and deep technical levels
- Organization skills with the ability to multi-task, prioritize and keep track of activities
- Team player with “can do” attitude
Desirable Skills
- Experience in designing with AMD Xilinx FPGA’s & SoCs (Versal Adaptive SOCs, Virtex, Kintex, Artix & Spartan Class FPGA’s, RFSoC, Zynq UltraScale+, & Zynq-7000)
- Knowledge of embedded system design tools such as AMD Xilinx’s Vivado & Vitis tools, IP Integrator, or Intel Altera Quartus, and Eclipse based software development environment.
- Knowledge of board design requirements for FPGA’s & SoC’s including power distribution & dissipation, high speed interface design, and debug.
- Design experience using high performance external memory interface controllers and protocols
- Design experience using FPGA based high-speed serial transceivers
- Embedded processing knowledge - Familiar with x86 and ARM architectures, performance metrics, OS (especially Linux), Yocto, BSP, drivers, and debugging tools
Pay
$195,000 - $210,000 total compensation range. Please note that this salary information serves as a general guideline. Actual compensation offered will depend on various factors, including but not limited to the scope and responsibilities of the position, geographic location, candidate's work experience, education and training, key skills, as well as market and business considerations.
Benefits
Benefits resource guide
- Generous Paid Time Off
- 401K and Pension Plan
- Paid Holidays
- Family Support (Paid Leave, Surrogacy, Adoption)
- Medical, Dental, Vision, and Life Insurance
- Long-term and Short-term Disability Insurance
- Health Savings Account / Flexible Spending Account
- Education Assistance
- Employee Development Resources
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract sections: Who We Are (maybe "About the company"? Not listed in allowed headings but we could use "About the role"? Actually "Who We Are" is about company, not role. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also possibly add other headings if needed? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we could use other headings if appropriate, but better to stick to those. The posting includes "Who We Are" (company overview) maybe we can treat as "About the role"? Not exactly. Could we omit? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings. But they gave examples; we could include "About the company" as maybe. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This implies those are typical sections; we can use them if content matches. For company overview, maybe we can put under "About the role"? Not ideal. Could we just not include a heading for that and embed in a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This implies those are typical sections; we can use them if content matches. For company overview, maybe we can put under "About the role"? Not ideal. Could we just not include a heading for that and embed in a
before sections? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview with job summary maybe under "About the role". Let's see. We have sections: - Who We Are: company description. - Job Summary: includes visa requirement, US citizen, role description. - Principal Responsibilities: list of duties. - Work Experience: minimum experience. - Education and Certification(s): Bachelors degree. - Distinguishing Characteristics: Bachelor's Degree in EE or CS or equivalent 8+ years experience FPGA-based architecture definition, design, and support (High Speed Serial IO, Embedded Processor, or DSP knowledge a plus) - Required Skills: list. - Desirable Skills: list. - Pay and Benefits: includes link to PDF and salary range. - What We Offer: benefits list. - Then EEO boilerplate etc to remove. We need to produce sections: maybe "About the role" (combining Who We Are and Job Summary?), "Responsibilities", "Requirements" (maybe combine Work Experience, Education, Distinguishing Characteristics), "Skills" (Required and Desirable), "Benefits", "Pay". Schedule not present, so omit. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: salary range. Benefits are stated: link and list. So we can have separate Pay and Benefits sections, or combine? The instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one section? But they gave examples separate. However we can decide to combine if it reduces thin sections. But we need to preserve all substantive info. Combining is okay as long as we include both pay and benefits details. Let's see: The posting has "Pay and Benefits:" heading with link and salary range, then "What We Offer:" with benefits list. So we could have a single section "Compensation and Benefits" but not in allowed list. Might be safer to follow examples: have "Pay" and "Benefits" sections. That's two sections, not too many. We also need to include "Requirements" maybe covering Work Experience, Education, Distinguishing Characteristics. Could also include "Qualifications". The examples include Requirements, Qualifications. We could use "Requirements" for experience/education, and "Qualifications" for distinguishing characteristics? Or combine. Let's think. We need to avoid filler like "commensurate with experience". Not present. We must remove boilerplate: EEO, accommodation, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "Position open until filled" maybe minor metadata; could fold into short p or drop. Probably drop. We must not include job ID/requisition numbers. We must not repeat job title as heading. We must output only HTML fragment. Thus final HTML:
About the role
Who We Are: At Avnet, relationships matter. We are a global, FORTUNE® 500 technology distributor and solutions company that delivers design, supply chain and logistics expertise to customers at every stage of a product’s lifecycle. Our employees have a front row seat to the latest innovations shaping the world we live in and the future we share. We’re driven to help our customers around the world succeed and we do so by earning the trust of some of the biggest names in technology. Working at Avnet means being a part of a global team. We work collaboratively and with integrity, doing business the right way. For more than a century, we have partnered together to help our customers, suppliers and teammates realize the transformative possibilities of technology. Experience what’s next at Avnet!
Job Summary: Applicants for this position must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time. MUST be U.S. Citizen. As the AMD Xilinx dedicated Field Application Engineer you will be a key member of a technical sales team acting as lead for AMD Xilinx Hardware & Software aspects of our key customers’ systems. An ideal candidate for this role will be an enthusiastic and highly motivated technical individual who wants to be marketing the cutting edge of SoC technology and proactively engaged with customers in AMD Xilinx pre- and post-sale design and technical support activities.
Responsibilities
- Drive and manage Xilinx technical related initiatives & activities for key customers in alignment with the AMD Xilinx dedicated Technical Sales Engineer (TSE)
- Provide technical leadership and guidance that focuses on AMD Xilinx design win strategies for customer opportunities
- Develop relationships with and become trusted advisor to (system) engineers & architects in your assigned key accounts
- Drive the technical part of strategy proposals for key customer programs
- Leverages understanding of known challenges to advise customer designers on the optimum use of Xilinx IP, software tools and hardware devices
- Manage technical support issues within customer base and collaborate/bring in AMD Xilinx technical specialists when required to help solve real time problems (e.g. software tool & IP issues, Design Closure, RTL and simulation assistance, system bring up and debug)
- Collaborate with field and AMD Xilinx factory resources to develop and deliver technical proposals to customer project managers, engineering managers, system architects and design engineers that align with customers’ needs
- Lead with technical solution creation to show our value proposition (e.g.: hardware, software demos, example designs)
- Work with 3rd party ecosystem partners to support mutual beneficial custom solutions into the customer base where applicable
- Attend internal and external AMD Xilinx technical training to complete and maintain certification as necessary.
- Other duties as assigned.
Requirements
- Minimum experience required is typically 8+ years with bachelor's or equivalent.
- Bachelors degree or equivalent experience from which comparable knowledge and job skills can be obtained.
Qualifications
- Bachelor's Degree in Electrical Engineering or Computer Science or equivalent
- 8+ years experience FPGA-based architecture definition, design, and support (High Speed Serial IO, Embedded Processor, or DSP knowledge a plus)
Skills
- Experience with and understanding at systems level, FPGA and ASIC design tools.
- Experience with Vivado/Vitis, ISE or Quartus required (ModelSim is a plus)
- Ability to identify a customer’s key care-abouts and thus contribute to overall sales strategy and success
- Knowledge of customers' end products including their specific market requirements.
- Strong analytical and problem-solving skills
- Strong presentations skills, and the ability to work with multiple groups
- Aptitude to communicate clearly at a high system and deep technical levels
- Organization skills with the ability to multi-task, prioritize and keep track of activities
- Team player with “can do” attitude
Desirable Skills
- Experience in designing with AMD Xilinx FPGA’s & SoCs (Versal Adaptive SOCs, Virtex, Kintex, Artix & Spartan Class FPGA’s, RFSoC, Zynq UltraScale+, & Zynq-7000)
- Knowledge of embedded system design tools such as AMD Xilinx’s Vivado & Vitis tools, IP Integrator, or Intel Altera Quartus, and Eclipse based software development environment.
- Knowledge of board design requirements for FPGA’s & SoC’s including power distribution & dissipation, high speed interface design, and debug.
- Design experience using high performance external memory interface controllers and protocols
- Design experience using FPGA based high-speed serial transceivers
- Embedded processing knowledge - Familiar with x86 and ARM architectures, performance metrics, OS (especially Linux), Yocto, BSP, drivers, and debugging tools
Pay
$195,000 - $210,000 total compensation range. Please note that this salary information serves as a general guideline. Actual compensation offered will depend on various factors, including but not limited to the scope and responsibilities of the position, geographic location, candidate's work experience, education and training, key skills, as well as market and business considerations.
Benefits
Benefits resource guide
- Generous Paid Time Off
- 401K and Pension Plan
- Paid Holidays
- Family Support (Paid Leave, Surrogacy, Adoption)
- Medical, Dental, Vision, and Life Insurance
- Long-term and Short-term Disability Insurance
- Health Savings Account / Flexible Spending Account
- Education Assistance
- Employee Development Resources