Mid-level Physical Design Engineer CPU

We need to output HTML fragment with sections: About the role, Responsibilities (What You’ll Do), Behavioral Traits maybe as Skills? Actually behavioral traits could be under Skills or Qualifications? The instructions: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. We have content: - About The Role: paragraph. - What You’ll Do: list of responsibilities (bulleted). Should be under Responsibilities heading. - Behavioral Traits That We Are Looking For: list of traits. Could be under Skills or maybe Qualifications? Probably Skills. - Why Join Us: could be under Benefits? Actually it's more about reasons to join; but we have Benefits section later. The "Why Join Us" includes statements about work on cutting-edge etc. Could be considered as Benefits? But we also have explicit Benefits section later: "Benefits We offer a total compensation package..." plus salary range. So we should put Benefits heading with that content (including salary range). Also Pay heading maybe separate? The instructions: include Pay section only if posting actually states them. The posting includes Annual Salary Range. So we can have Pay section with that salary range. Also Benefits section with description of benefits (health, retirement, vacation). The posting also says "Work Model for this Role This role will require an on-site presence." That's Schedule? Actually work model could be Schedule? The heading Schedule is for schedule info like full-time, part-time, shift. We have Shift 1 (United States of America) and Work Model on-site. Could be under Schedule heading. But we need to decide if we include Schedule. The posting includes "Shift Shift 1 (United States of America)" and "Work Model for this Role This role will require an on-site presence." That's schedule info. So we can include Schedule heading with that. We also have Qualifications section: Minimum Qualifications and Preferred Qualifications. So we need Qualifications heading with both. We also have Requirements? Not separate; qualifications cover. We also have Skills? Could be under Skills heading for behavioral traits? Or we could put behavioral traits under Skills. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Skills heading for behavioral traits. We need to avoid repeating job title as heading. No Job ID etc. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About The Role paragraph: "Join a team developing next-generation CPU cores that power client, server, IoT, and AI platforms. As a Mid-level Physical Design Engineer CPU, you will contribute to delivering high-performance, power-efficient silicon using advanced process technologies. In this role, you will take on increasing ownership within the RTL-to-GDS flow, working on block-level implementation while collaborating closely with cross-functional teams. This position offers strong growth opportunities as you build depth in physical design and SoC development." Responsibilities (What You’ll Do): list items: - Execute physical design implementation for CPU core blocks or subsystems - Perform synthesis, floor planning, place and route (PnR), and design closure activities - Conduct static timing analysis (STA), power analysis, and physical verification - Identify and debug timing, power, and design rule violations - Contribute to achieving timing, power, and area (PPA) targets - Develop and maintain scripts for design automation (e.g., TCL, Python) - Collaborate with RTL design, verification, clocking, and full-chip teams - Support improvements to design flows, methodologies, and best practices - Document technical work and share knowledge within the team Behavioral Traits That We Are Looking For list: - Strong analytical and problem-solving skills - Takes ownership of assigned tasks and delivers with accountability - Works effectively in collaborative, cross-functional environments - Communicates technical information clearly and concisely - Shows adaptability in a fast-paced, evolving engineering environment - Demonstrates continuous learning and skill development Why Join Us paragraph: "Work on cutting-edge CPU core designs that power client, server, IoT, and AI platforms used worldwideBe part of a team driving innovation at advanced semiconductor process nodesContribute across the full RTL-to-GDS flow, gaining exposure to complex, high-impact silicon designCollaborate with experienced engineers across architecture, design, and full-chip integrationGrow your technical expertise through challenging problems, modern tools, and continuous learning opportunitiesJoin a culture that values inclusion, collaboration, and diverse perspectives while delivering industry-leading technologyIntel invests in our people and offers a complete and competitive package of benefits employees and their families through every stage of life.See Intel Benefits for more details." But note there are missing spaces; but we keep as is. Qualifications: Minimum Qualifications And Experience: "Bachelors in Computer / Electrical Engineering or related field with 5+ years of relevant work experience. Or a Masters in the same field with 3+ years of relevant work experience. Your Experience Described Above Must Be In The Following Experience with integrated circuit design tools (ex: Synopsys/Cadence), including logic synthesis, place and route, static timing analysis and design closurePV convergence (including static timing and power analysis)Chip physical design verification including formal equivalence, timing, electrical rules, DRC/LVS, Noise and electro-migration checks.Scripting in an interpreted language, minimum TCL in addition to at least one other (e.g. Perl, Python, Ruby)Experience with one or more of the following areas: Synthesis of a digital logic block, which was integrated into a large SoC or IP" Preferred Qualifications And Experience: "Industry experience/exposure with CPU Micro-ArchitecturePhysical design best known practices concerning floor-planning, routing techniques, clock distributionStatic Timing Analysis, Noise analysis, and reliability verification techniquesRTL to GDS methodologies and formal equivalenceSynopsys tool suite (Fusion compiler, ICC2, PrimeTime) or Cadence (genus/innovus)" 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." Pay: "Annual Salary Range for jobs which could be performed in the US: $122,440.00 - 232,190.00 USD The range displayed on this job posting reflects the minimum and maximum target compensation for the position across all US locations. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training. Your recruiter can share more about the specific compensation range for your preferred location during the hiring process." Schedule/Work Model: "Job Type Experienced Hire Shift Shift 1 (United States of America) Primary Location: US, Oregon, Hillsboro Additional Locations: ... Work Model for this Role This role will require an on-site presence." We need to include Schedule heading with shift and work model. Possibly also location? But location is not schedule. The instructions: Use heading Schedule for schedule info. We'll include shift and work model. We should not include location as heading; maybe we can include location in a paragraph under About the role? But we already have About the role; location could be placed in a short p under About the role? However instructions: do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata; we could include it in a paragraph under About the role or maybe under a separate "Details" but not required. Safer to include location in a short p under About the role or maybe under a separate "Details" but we don't have a heading for that. We could add a paragraph after About the role: "

Primary Location: US, Oregon, Hillsboro. Additional Locations: [list if any].

" But the posting says "Additional Locations:" but no specifics given. So we can just mention primary location. We must preserve ALL substantive information; location is substantive. So we need to include it somewhere. We'll add a paragraph after About the role: "

Primary Location: US, Oregon, Hillsboro.

" (Additional Locations not specified, so we omit). Now schedule: shift and work model. We'll put under Schedule heading: "

Shift: Shift 1 (United States of America). Work Model: On-site presence required.

" Now Benefits heading: we have benefits description. Pay heading: salary range. Now we need to ensure we don't include boilerplate like EEO, legal, etc. Remove those. Now produce HTML fragment:

About the role

Join a team developing next-generation CPU cores that power client, server, IoT, and AI platforms. As a Mid-level Physical Design Engineer CPU, you will contribute to delivering high-performance, power-efficient silicon using advanced process technologies. In this role, you will take on increasing ownership within the RTL-to-GDS flow, working on block-level implementation while collaborating closely with cross-functional teams. This position offers strong growth opportunities as you build depth in physical design and SoC development.

Primary Location: US, Oregon, Hillsboro.

Responsibilities

• Execute physical design implementation for CPU core blocks or subsystems
• Perform synthesis, floor planning, place and route (PnR), and design closure activities
• Conduct static timing analysis (STA), power analysis, and physical verification
• Identify and debug timing, power, and design rule violations
• Contribute to achieving timing, power, and area (PPA) targets
• Develop and maintain scripts for design automation (e.g., TCL, Python)
• Collaborate with RTL design, verification, clocking, and full-chip teams
• Support improvements to design flows, methodologies, and best practices
• Document technical work and share knowledge within the team

Skills

• Strong analytical and problem-solving skills
• Takes ownership of assigned tasks and delivers with accountability
• Works effectively in collaborative, cross-functional environments
• Communicates technical information clearly and concisely
• Shows adaptability in a fast-paced, evolving engineering environment
• Demonstrates continuous learning and skill development

Qualifications

Minimum Qualifications

• Bachelors in Computer / Electrical Engineering or related field with 5+ years of relevant work experience. Or a Masters in the same field with 3+ years of relevant work experience.
• Experience with integrated circuit design tools (ex: Synopsys/Cadence), including logic synthesis, place and route, static timing analysis and design closure.
• PV convergence (including static timing and power analysis).
• Chip physical design verification including formal equivalence, timing, electrical rules, DRC/LVS, Noise and electro-migration checks.
• Scripting in an interpreted language, minimum TCL in addition to at least one other (e.g. Perl, Python, Ruby).
• Experience with one or more of the following areas: Synthesis of a digital logic block, which was integrated into a large SoC or IP.

Preferred Qualifications

• Industry experience/exposure with CPU Micro-Architecture.
• Physical design best known practices concerning floor-planning, routing techniques, clock distribution.
• Static Timing Analysis, Noise analysis, and reliability verification techniques.
• RTL to GDS methodologies and formal equivalence.
• Synopsys tool suite (F