Pre-si Power and Performance System Validation Engineer

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes "Life at Intel" maybe not needed. We need to include sections only when there is real content. The job description includes a paragraph about Intel shaping future etc. That could be "About the role" or maybe "About Intel". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content. We have: - Intro paragraph: "Intel is shaping the future..." That's about the company, could be "About the role" or maybe "About Intel". We'll use "About the role". - "Life at Intel" maybe not needed; but we could treat as part of About the role? Probably not needed. - "The Role and Impact" description: could be part of About the role or Responsibilities? It describes role and impact. Could be part of About the role. - "Business Group": could be part of About the role. - "Key Responsibilities": list -> Responsibilities section. - "Well Qualified Candidates Should Possess The Following Behavioral Traits": list? It's bullet-like sentences. Could be part of Requirements or Qualifications? It's behavioral traits; could be under Requirements. - Then "Qualifications": heading with subparts: Education, Experience, Technical Skills, How To Stand Out (Preferred Qualifications). So we need Qualifications section with subcontent? We can put subheadings? Not required; just use

and

• . We'll include Education, Experience, Technical Skills, Preferred Qualifications as lists. - Benefits: there is a Benefits section with description and link. Also later "Benefits" repeated with total compensation package. So we have Benefits content. - Pay: there is Annual Salary Range. - Schedule: there is Shift 1 (United States of America) and Work Model: on-site presence. So we have Schedule/Shift info. We must not include boilerplate like EEO, application instructions, etc. We must not repeat job title as heading. We must not include Job ID etc. We must not include sections with filler like "commensurate with experience". Not present. We need to preserve all substantive information. Let's extract content. Intro paragraph: "Intel is shaping the future of technology to help create a better future for the entire world. Our work in pushing forward fields like AI, analytics, and cloud-to-edge technology is at the heart of countless innovations. With a career at Intel, you'll have the opportunity to use technology to power major breakthroughs and create enhancements that improve our everyday quality of life. Join us and help make the future more wonderful for everyone. Want to learn more? Visit our YouTube Channel or the link below." We keep that. Life at Intel maybe not needed; but could be considered part of About the role? It says "Life at Intel". Not substantive beyond heading. We'll skip. "The Role and Impact As a SoC Power Thermal Performance Validation and Optimization Engineer, you will play an essential role in ensuring Intel's products achieve optimal power, thermal, and performance benchmarks at the system-on-chip (SoC) level. In this position, you will develop and execute validation methodologies, optimize hardware/software solutions, and perform SoC-level debugging to address power, thermal, and performance challenges. Your contribution will directly impact Intel's ability to deliver competitive, high-performing products to market." We can include that under About the role or maybe as part of Responsibilities? It's more role description. We'll put under About the role. "Business Group This role is part of Intel's Data Center Group (DCG), which focuses on designing innovative solutions to power the next generation of computing platforms for data centers. As a member of the PTP PreSi Correlation Solution team, you will contribute to shaping the development and validation processes for cutting-edge technologies, ensuring Intel meets and exceeds industry standards for performance and efficiency." Could be About the role as well. Now Responsibilities: list bullet points. Let's extract each: - Develop and execute SoC-level power, thermal, and performance validation and optimization plans across Intel products. - Collaborate with architecture, design, firmware, and software teams to ensure power, thermal, and performance meet competitive targets and specifications. - Establish and execute methodologies for validating hardware/software optimizations and ensure alignment with business KPIs. - Perform SoC-level debug to identify root causes and resolve functional and triage failures related to power, thermal, and performance. - Configure and set up data loggers to collect and analyze thermal data. - Develop and maintain validation infrastructure, including performance monitors, behavioral checkers, and testing environments. - Produce comprehensive validation reports summarizing activities and results, and communicate findings effectively to relevant teams. - Drive continuous improvements to validation strategies, methodologies, and processes. Now Behavioral Traits (Well Qualified Candidates Should Possess The Following Behavioral Traits): - Strong analytical and problem-solving aptitude. - Effective communication and documentation skills for cross-functional collaboration. - Ability to work across team in multi-faceted groups (architecture, design, verification, firmware, software, and platform teams.) Now Qualifications section: Education: "Bachelors in electrical, Computer Engineering, or related field. A master's degree is preferred." Experience: list: - 3+ years of experience in SoC power and performance validation. - 3+ years of experience in Pre-Si simulation and emulation. - 3+ years of experience developing and / or optimization of power/performance KPI's. Technical Skills (2+ Years of experience in each): - Debugging experience for SoC-level power, thermal, and performance failures. - Knowledge of hardware/software optimizations for power and performance. - Experience of silicon verification, test program development and test plan execution. - Knowledge of RTL language, in-circuit emulation and FPGA fast prototyping is an advantage. - Experience with Python Programming language. How To Stand Out (Preferred Qualifications): - Graduate degree (Masters or PhD). - Knowledge of DSP, ETHERNET, and 3G/4G/5G. - 2+ years' experience in SoC FPGA/Emulation function. - 2+ years' experience with System (SoC) level debug using JTAG debuggers. - 1+ year experience in Pre-Si functional design, validation, and/or HW/FW/SW integration. - 1+ year experience on major Pre-Si platforms: logic simulation, virtual platform, FPGA, and/or emulation. - Expertise in system-level power management of real-time processors and systems. - Understand MIPI MPHY, JTAG, DDR, PCIe/USB/PCI-E/ETHERNET/SPMI bus protocol. - Familiarity with validation tools such as data loggers, behavioral checkers, and state space coverage techniques. - Familiar with system board design/debugging and usage of lab equipment like Oscilloscope and Logic analyzer. - Knowledge of AI accelerators systems including GFX, NPU, NPP design and architecture. - Experience with performance modeling, benchmarking, and validation infrastructure setup. - Debugging experience for SoC-level power, thermal, and performance failures. (duplicate) - Familiarity with validation tools such as data loggers, behavioral checkers, and state space coverage techniques. (duplicate) - Knowledge of hardware/software optimizations for power and performance. (duplicate) We can deduplicate but must preserve all substantive info; duplicates can be removed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicates are not new info; we could keep them but it's okay to deduplicate? Might be considered summarizing away detail? Safer to keep them as they appear, but we can combine duplicates into single bullet to avoid redundancy while preserving info. The instruction says do not summarize away detail; merging duplicates could be considered summarizing. However duplicates are identical; merging them doesn't lose info. I'd keep one instance. Now Benefits: there are two benefits sections. First: "Benefits At Intel Our total rewards package goes above and beyond just a paycheck. Whether you're looking to build your career, improve your health, or protect your wealth, we offer generous benefits to help you achieve your goals. Go to Intel Benefits | Intel Careers for details of benefits available to you. Intel reserves the right to modify, change or discontinue benefit plans at any time in its sole discretion." Second: "Benefits We offer a total compensation package that ranks among the best in the industry. It consists of competitive pay, stock bonuses, and benefit programs which include health, retirement, and vacation. Find out more about the benefits of working at Intel." We can combine into a Benefits section with both paragraphs. Pay: Annual Salary Range: "$122,440.00 - 232,190.00 USD". Also note that individual pay determined by location etc. We'll include that. Schedule/Shift: "Job Type Experienced Hire Shift Shift 1 (United States of America)" and "Work Model for this Role This role will require an on-site presence." Also note "* Job posting details (such as work model, location or time type) are subject to change." That's maybe metadata but we can include as part of Schedule. We should not include "Posting Statement" EEO etc. Now construct HTML. We'll have sections:

  About the role

  Intro paragraph + Role and Impact + Business Group (maybe combine into one paragraph or multiple). We'll keep as

  with sentences.

  Responsibilities

  • ...

  Requirements

  maybe for Behavioral Traits? Or we could put Behavioral Traits under Requirements. Let's use

  Requirements

  for behavioral traits.

  Qualifications

  with subheadings? Not required but we can use

  for each subsection and

  • for lists. We could also have

    Education

    inside Qualifications but that would be extra heading not in allowed list? Allowed list includes Qualifications, Skills, Benefits, Pay, Schedule. Education could be part of Qualifications. We'll just put paragraphs. We'll include:

    Education: Bachelors in electrical, Computer Engineering, or related field. A master's degree is preferred.

    Experience:

    • 3+ years of experience in SoC power and performance validation.
    • 3+ years of experience in Pre-Si simulation and emulation.
    • 3+ years of experience developing and / or optimization of power/performance KPI's.

    Technical Skills (2+ Years of experience in each):

    • Debugging experience for SoC-level power, thermal, and performance failures.
    • Knowledge of hardware/software optimizations for power and performance.
    • Experience of silicon verification, test program development and test plan execution.
    • Knowledge of RTL language, in-circuit emulation and FPGA fast prototyping is an advantage.
    • Experience with Python Programming language.

    Preferred Qualifications:

    • Graduate degree (Masters or PhD).
    • Knowledge of DSP, ETHERNET, and 3G/4G/5G.
    • 2+ years' experience in SoC FPGA/Emulation function.
    • 2+ years' experience with System (SoC) level debug using JTAG debuggers.
    • 1+ year experience in Pre-Si functional design, validation, and/or HW/FW/SW integration.
    • 1+ year experience on major Pre-Si platforms: logic simulation, virtual platform, FPGA, and/or emulation.
    • Expertise in system-level power management of real-time processors and systems.
    • Understand MIPI MPHY, JTAG, DDR, PCIe/USB/PCI-E/ETHERNET/SPMI bus protocol.
    • F