Technical Sales Engineer - AMD/Xilinx

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements (What We're Looking For), Background & Qualifications maybe as Qualifications, Benefits (Compensation & Benefits), maybe Pay (they gave salary range). Also maybe Schedule? Not present. Should not include sections without content. Must not repeat job title. Must not include boilerplate like EEO, etc. Must preserve all substantive info. We need to parse content. Sections present: - Who We Are (intro) maybe not needed as heading? It's not one of the allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is not in list; we could maybe treat as part of About the role? But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only output those headings if content exists. "Who We Are" is not allowed heading; we could incorporate into a

maybe as intro? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. They didn't forbid other headings not in list? They gave examples; likely they expect only those headings. Safer to not output a heading for Who We Are; we could include its content in a

before first heading? But they said output ONLY the HTML fragment; we can include a

with that intro. However they might consider that as boilerplate? It's substantive about company. Probably keep as a

before sections. Then "About the Role" heading ->

About the role

then paragraph(s) from that section. Then "What You'll Do" -> Responsibilities. Then "What We're Looking For" -> Requirements (or maybe Skills?). They said Requirements heading for list of duties/requirements/benefits. So we can put Requirements. Then "Background & Qualifications" -> Qualifications. Then "Compensation & Benefits" -> Benefits heading (maybe also Pay). They gave salary range and benefits description. So we need Benefits and Pay sections. They said include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. They gave salary range $130,000 - 165,000 total compensation range and note that specific compensation is commensurate with experience and territory. That's specific enough for Pay. Benefits: they list medical, dental, vision, 401(k), paid time off, professional development support, plus later list many benefits. So we have Benefits. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include Schedule. We must use

• for any list of duties/requirements/benefits. So for responsibilities we need to convert bullet points into
  • . The responsibilities section has many bullet-like sentences each starting with a verb. We'll make each as
  • . Similarly for Requirements (What We're Looking For) bullet points. For Benefits we need list of benefits. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from each bullet. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must drop the EEO paragraph at end, also the "Position open until filled", "What We Offer:" maybe duplicate of benefits? Actually "What We Offer:" includes benefits list again; we need to avoid duplication. We should combine benefits info but not duplicate. The posting includes "Compensation & Benefits" section with some benefits, then later "What We Offer:" with a list of benefits. We need to preserve all substantive info but not duplicate lines. So we need to merge unique benefits from both sections, avoiding duplication. Let's extract. From Compensation & Benefits: - "competitive base salary with a variable component tied to design-win and revenue performance" - "Avnet offers a comprehensive benefits package including medical, dental, and vision coverage, a 401(k) plan, paid time off, and professional development support." - "$130,000 - 165,000 total compensation range" - "Specific compensation is commensurate with experience and territory." From What We Offer: - "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" - "Employee Wellness, Leadership Development and Mentorship Programs" - "Benefits listed above may vary depending on the nature of your employment with Avnet." We need to avoid duplication: medical, dental, vision appear both; 401(k) appears both; paid time off appears both; professional development support maybe similar to Employee Development Resources; we can keep both but avoid exact duplicate lines. We'll combine unique items. We'll produce a
    • list for Benefits. Now for Pay: we need to include base salary variable component and range. We'll put in

      . Now for About the role: we need to keep the paragraph(s) from that section. The section includes multiple paragraphs: first paragraph about owning customer-AMD relationship, building senior relationships, etc. Second paragraph about paired coverage model with FAE. Third paragraph about AMD's FPGA etc. Fourth paragraph about people who thrive. We'll combine into maybe multiple

      elements. Now Responsibilities (What You'll Do): list of bullet points each starting with a bold phrase? Actually they are sentences each starting with a capitalized verb phrase. We'll make each as

    • . Need to keep all details. Now Requirements (What We're Looking For): bullet points each starting with bold phrase. We'll make
    • . Now Qualifications (Background & Qualifications): includes Experience, Track record, Technical baseline, Location, etc. We'll make
    • for each bullet? It's not a list but we can treat each paragraph as
    • under a
      . Or we could use

      for prose. The instruction: Use

      • for any list of duties/requirements/benefits. For qualifications, it's a list of items (Experience, Track record, Technical baseline, Location, etc.) So we can use
        • . Now we must not include minor metadata like Job ID etc. There's none. We must not include application instructions like "Please note that this salary information serves as a general guideline." That's part of compensation; we keep it? It's substantive about compensation. It's not boilerplate. We'll keep. We must not include duplicated lines. We'll avoid duplication. Now produce HTML. Let's craft. First, maybe an introductory

          for 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! Territory covers upstate New York and Connecticut 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. Candidate must be a U.S. citizen or permanent resident." But note that "Territory covers upstate New York and Connecticut" and the authorization lines are metadata; they said fold minor metadata into a short

          or drop it. This is minor metadata about location and work authorization. We could include as a short

          after intro. But we could also drop it? They said preserve ALL substantive information; is location substantive? It's about territory coverage and work auth; maybe it's substantive for the role. However they said "fold minor metadata into a short

          or drop it." So we can include a short

          with that info. Thus after intro we can have a

          containing: "Territory covers upstate New York and Connecticut. Applicants must be authorized to work for any employer in the U.S.; visa sponsorship is not available. Candidate must be a U.S. citizen or permanent resident." Now then sections. Let's draft. HTML:

          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!

          Territory covers upstate New York and Connecticut. Applicants must be authorized to work for any employer in the U.S.; visa sponsorship is not available. Candidate must be a U.S. citizen or permanent resident.

          About the role

          The AMD Dedicated Technical Sales Engineer (TSE) owns the customer–AMD relationship in the Boston territory. That means building and holding senior relationships across systems architects, engineering leaders, and executive stakeholders — managing a disciplined pipeline, driving deal velocity, and being personally accountable for outcomes from design registration through production ramp. The TSE operates in a paired coverage model with an AMD Dedicated Field Applications Engineer (FAE), who owns the technical relationship and engineering engagement. This is a field sales role with an engineering audience. AMD's FPGA, Embedded SoC, and Embedded x86 device families serve customers across aerospace and defense, industrial automation, communications infrastructure, automotive electronics, and medical — markets where buying decisions are made by engineers and engineering managers, not procurement alone. The people who thrive here combine the drive to own a number and close with the relationship depth to build lasting customer trust at the executive level — and enough technical credibility to be taken seriously by the engineers who influence those decisions.

          Responsibilities

          • Own AMD embedded revenue across the territory. Design registrations, design wins, and production ramp — you are accountable for the full commercial lifecycle from first engagement through volume production. Revenue is the measure of this role.
          • Build and sustain executive relationships. Engage systems architects, engineering managers, and executive stakeholders across the account base, and build the kind of trust that makes you the first call when a customer has a new program to place or a commercial decision to make.
          • Drive pipeline and demand creation. Actively identify new design opportunities before they appear in a CRM — engaging customers on upcoming programs, roadmap discussions, and technology transitions that create pull for AMD solutions. Don't wait for inbound; go find the next opportunity.
          • Manage the commercial motion end to end. Own pricing, supply chain alignment, deal structure, and competitive positioning across all active opportunities. Guide customers through AMD roadmap decisions and product selection in a way that locks in AMD for the next design cycle and the one after it.