Field Applications Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Content: - About Supermicro (company description) maybe corresponds to "About the role"? Actually "About Supermicro" is company description. Could be "About the role" but we have "Job Summary". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. We have: - Job Summary: description of role. - Essential Duties And Responsibilities: list of duties. - Qualifications: list of qualifications. - Salary Range: $140,000 - $155,000. - No explicit Benefits, Schedule. - Skills: maybe part of qualifications? Could extract skills from qualifications: communication, business sense, hardware architecture, etc. But we should not invent sections unless there is real specific content. The posting includes "Excellent communication skills and business sense required", "Strong technical communication and leadership skills". That could be Skills section. We need to decide which sections to include: About the role (Job Summary), Responsibilities (Essential Duties), Requirements (maybe Qualifications?), Qualifications (maybe education/experience), Skills (maybe communication/technical skills), Pay (Salary Range). Benefits and Schedule not present, so omit. We must not repeat job title as heading. Not include Job ID etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details from each section. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus: - About the role:

  About the role

  then

  with job summary prose. - Responsibilities:

  Responsibilities

  then
  • each duty. - Requirements: maybe combine qualifications? But we have Qualifications section separate. Could treat "Requirements" as education/experience required. However we also have "Qualifications" as separate heading. The instruction list includes both Requirements and Qualifications as possible headings. We need to decide based on content. The posting has "Qualifications" heading with bullet-like list. It also has "Essential Duties And Responsibilities". There's no separate "Requirements". So we could map the qualifications list to either Requirements or Qualifications. Since both are allowed, we need to avoid duplication. Perhaps we put education/experience under "Requirements" and skills under "Skills". But the qualifications list includes both education/experience and skills. Might be better to have a single "Qualifications" section containing all qualification statements. Then we could omit Requirements. The instruction says prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Qualifications, Pay. That's four sections. But we also have skills mentioned: "Excellent communication skills and business sense required", "Strong technical communication and leadership skills". Those are part of qualifications. So we can keep them inside Qualifications. Thus sections: - About the role (Job Summary) - Responsibilities (Essential Duties And Responsibilities) - Qualifications (includes education, experience, skills) - Pay (Salary Range) We must not include Benefits or Schedule. Now we need to extract the content precisely. Job Summary paragraph: "The Field Application Engineer (FAE) will be part of a growing, dynamic, highly-focused team responsible for developing new or existing opportunities in the global IT market. The FAE will be required to work with customers from ground to executive-level, manage projects hand in hand with internal and external teams, and help grow the business whenever possible. Customer and solution focus, are two key factors for this position, as well as business continuity and support. The FAE must work with multiple departments to ensure new projects and existing projects are initiated or maintained towards customer requirements." We need to preserve all substantive information. Keep as is. Responsibilities list: The list after "Essential Duties And Responsibilities Includes the following essential duties and responsibilities (other duties may also be assigned):" then bullet points (each line starts with a capital letter). We need to convert each to
  • . Let's extract them: - Support revenue growth at all assigned accounts - Solution architect and presentation skills to help expand Fortune1000 account penetration and loyalty - Works closely with the sales and extended teams to map end-user customer business, partner requirements and provide most optimized technical solutions - Provides technical leadership in Pre-Sales and oversee implementation of such solutions - Effectively engage with C-level technical customers, gain and maintain trust - Highly technical problem solver who understands system architecture, hardware and software interaction - Should possess basic hardware architecture understanding and debug skills - Manage and leads teams during investigation and resolution of problems in the field - Has a good understanding of firmware, drivers, OS, Applications and their interaction that can cause system issues - Develop and review systems solutions, technical bid responses and presentations - Work cross-department to ensure customer satisfaction and timely resolution of issues - Ability to build and demonstrate proof-of-concept that meets or exceeds customer business needs - Ability to present the corporate brand, product messaging and solutions to customers - Visit on-site facilities and operations to enable solution integration and issue resolution - Some travel required (up to 25%) We need to keep each as separate
  • . Ensure we preserve punctuation. Now Qualifications section: The list after "Qualifications". It includes: - Bachelors' or Masters' degree in engineering discipline; computer engineering, electrical engineering, or computer science preferred - Hands on Data Center and Liquid Cooling experience is a definite plus - Excellent communication skills and business sense required - Minimum 5 years of related experience with Compute/Storage Server or Data Center or IT Infrastructure experience desired - Strong background and experience with x86-based server architecture - Solid hardware system understanding and diagnostics skills - Familiarity with Firmware, Linux, Windows, virtualization, storage, GPUs, AI/ML, Liquid Cooling and data center operations is a plus - Strong technical communication and leadership skills to drive investigations with engineers of multiple disciplines - Individual must be able to work effectively and independently in high pressure environments We need to keep each as
  • under Qualifications. Pay section: Salary Range $140,000 - $155,000. We'll put

    Pay

    then

    Salary Range: $140,000 - $155,000

    maybe. We must not include boilerplate like EEO, Job Segment, Apply now, Date, Location, Company, Job Req ID. Also remove "About Supermicro" company description? That is substantive? It's about the company, not the role. The instruction says preserve ALL substantive information; but we might consider company description as substantive? However they said to use headings for sections like About the role, Responsibilities, etc. The company description could be considered part of "About the role"? But it's about the company. The instruction says "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." The company description is not minor metadata; it's about the company. Should we keep it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the company description somewhere. Where to put? Could be a short

    before sections, maybe as a general description. Since we don't have a heading for "About the company", we could just include it as a

    before the first heading. That seems acceptable. Thus output:

    Supermicro® is a Top Tier provider of advanced server, storage, and networking solutions for Data Center, Cloud Computing, Enterprise IT, Hadoop/ Big Data, Hyperscale, HPC and IoT/Embedded customers worldwide. We are the #5 fastest growing company among the Silicon Valley Top 50 technology firms. Our unprecedented global expansion has provided us with the opportunity to offer a large number of new positions to the technology community. We seek talented, passionate, and committed engineers, technologists, and business leaders to join us.

    Then headings. Make sure not to include any extra text like "Apply now". Also remove "Date:", "Location:", "Company:", "Job Req ID:", "EEO Statement", "Job Segment:", etc. Now produce HTML fragment. Check that we didn't miss any substantive info: The "Some travel required (up to 25%)" is included in responsibilities list. Good. Check that we didn't include any boilerplate like "EEO Statement". Good. Now format. We'll output:

    Supermicro® is a Top Tier provider of advanced server, storage, and networking solutions for Data Center, Cloud Computing, Enterprise IT, Hadoop/ Big Data, Hyperscale, HPC and IoT/Embedded customers worldwide. We are the #5 fastest growing company among the Silicon Valley Top 50 technology firms. Our unprecedented global expansion has provided us with the opportunity to offer a large number of new positions to the technology community. We seek talented, passionate, and committed engineers, technologists, and business leaders to join us.

    About the role

    The Field Application Engineer (FAE) will be part of a growing, dynamic, highly-focused team responsible for developing new or existing opportunities in the global IT market. The FAE will be required to work with customers from ground to executive-level, manage projects hand in hand with internal and external teams, and help grow the business whenever possible. Customer and solution focus, are two key factors for this position, as well as business continuity and support. The FAE must work with multiple departments to ensure new projects and existing projects are initiated or maintained towards customer requirements.

    Responsibilities

    • Support revenue growth at all assigned accounts
    • Solution architect and presentation skills to help expand Fortune1000 account penetration and loyalty
    • Works closely with the sales and extended teams to map end-user customer business, partner requirements and provide most optimized technical solutions
    • Provides technical leadership in Pre-Sales and oversee implementation of such solutions
    • Effectively engage with C-level technical customers, gain and maintain trust
    • Highly technical problem solver who understands system architecture, hardware and software interaction
    • Should possess basic hardware architecture understanding and debug skills
    • Manage and leads teams during investigation and resolution of problems in the field
    • Has a good understanding of firmware, drivers, OS, Applications and their interaction that can cause system issues
    • Develop and review systems solutions, technical bid responses and presentations
    • Work cross-department to ensure customer satisfaction and timely resolution of issues
    • Ability to build and demonstrate proof-of-concept that meets or exceeds customer business needs
    • Ability to present the corporate brand, product messaging and solutions to customers
    • Visit on-site facilities and operations to enable solution integration and issue resolution
    • Some travel required (up to 25%)

    Qualifications

    • Bachelors' or Masters' degree in engineering discipline; computer engineering, electrical engineering, or computer science preferred
    • Hands on Data Center and Liquid Cooling experience is a definite plus
    • Excellent communication skills and business sense required
    • Minimum 5 years of related experience with Compute/Storage Server or Data Center or IT Infrastructure experience desired
    • Strong background and experience with x86-based server architecture
    • Solid hardware system understanding and diagnostics skills
    • Familiarity with Firmware, Linux, Windows, virtualization, storage, GPUs, AI/ML, Liquid Cool