Senior Design Engineer

We need to output HTML fragment with sections: About the role? The posting includes introductory paragraph: "Are you ready for a new and exciting challenge? If you are a self-motivated design engineer..." That's like about the role. Then "Responsibilities" section with bullet list. Then "Required Skills and Experience:" with bullet list. Then "Nice to Have:" maybe part of Requirements? Could be separate but we can include under Requirements or Skills. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real, specific content. So we need sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe combine Required Skills and Experience and Nice to Have?). Could also have Skills section. But we can combine Required Skills and Experience as Requirements. Nice to Have could be under Requirements as a sublist? But we should not create thin sections. Probably better: About the role, Responsibilities, Requirements (includes both required and nice-to-have). Benefits (they mention competitive base salary, annual bonus, RSUs, 401k matching, excellent PTO allowance, family bonding time, competitive benefits, quarterly days of care). Also they mention Salary Range: $161,500-$218,500 per year. So we need Pay section (salary range). Also they mention Hybrid Working at Arm (maybe Schedule? Not exactly schedule but hybrid working details). Could be Schedule? The instruction says Schedule section only if posting actually states them. They have hybrid working details, not a specific schedule. Might be considered Schedule? Probably not; better to omit Schedule if not explicit. Benefits section: we have many benefits. Also they mention "In Return We Are Proud To Have a Set Of Behaviors That Reflect Our Culture..." That's like company values, not benefits. Could be omitted as boilerplate? It's not exactly boilerplate but it's cultural behaviors. Might be considered part of About the role? Might be optional. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The cultural behaviors might be considered not boilerplate but not required. Could include as part of About the role? Might be better to include as a separate section like "Culture and Values"? Not in allowed headings list. So we should not create new headings. Could fold into About the role paragraph. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to preserve all substantive information. Let's extract. About the role: The introductory paragraph plus maybe the sentence about "Are you ready for a new and exciting challenge? If you are a self-motivated design engineer with expertise in micro-architecture, logic design and ARM IP’s, system protocols and looking to make a difference in an innovative and inclusive team, you’ve come to the right place!" Also maybe the sentence about "As a creative design engineer with a knowledge of I/O subsystems, SoCs you will be part of a team integrating PCIe, DDR and other IP's for SoCs." Actually that is part of Responsibilities. So keep intro separate. Responsibilities: list items: - Collaborate with the project team to understand and review the architecture and develop the build specifications. - Writing micro-architecture specifications, developing the RTL, fixing bugs, and running various design checks. - Collaborate with the verification team to review test plans and help debug build issues. - Partner with the performance analysis team to evaluate and improve system performance. - Work with backend implementation team to help with floor planning, writing constraints, and timing closure. - Contribute to developing and enhancing the design methodologies used by the team. - Guide and support other members of the team as needed to enable the successful completion of project activities. - Balance other opportunities such as working with Project Management on activities, plans, and schedules. We need to ensure each as

. Required Skills and Experience: list: - Bachelors or Master’s degree in Computer Science or Electrical/Computer Engineering or a similar related field - 7+ years experience working in design of complex compute subsystems or SoCs - Strong knowledge of digital hardware design and Verilog HDL. - Thorough understanding and experience of the current design techniques for complex SoC development. - Experience developing and integrating subsystems for PCIe, DDR/LPDDR, HBM, UCIe, Ethernet - Experience creating design specifications and developing RTL for SoC projects and compute platforms - Experience in Static design checks, including CDC, RDC, X-Propagation, Linting - Experience with Perl, Python or other scripting language Nice to Have: list: - Experience with ARM-based designs and/or ARM System Architectures - Experience with SystemVerilog and verification methodologies – UVM/OVM/e - Experience leading small teams or projects - Experience or knowledge in the following areas - Synthesis and timing analysis - Power management techniques - DFT and physical implementation We could combine Nice to Have as part of Requirements but maybe better to keep as part of Requirements with a note? The instruction: Use sections only when posting has real, specific content. We could have a single Requirements section that includes both required and nice-to-have, maybe with subheadings? But we cannot add extra headings besides the allowed ones. Could we embed Nice to Have as a

inside Requirements? Probably okay: we can have a

stating "Nice to have:" then a

. That's fine. Benefits: list: - competitive base salary - annual bonus - RSUs - 401k matching - excellent PTO allowance - family bonding time - competitive benefits - quarterly days of care Also mention "work life balance with quarterly days of care!" Already captured. Pay: Salary Range: $161,500-$218,500 per year. Also mention "In addition, you will also be rewarded with a competitive base salary, an annual bonus, RSUs, 401k matching, an excellent PTO allowance as well as family bonding time and competitive benefits." That's benefits. We also have "We also pride ourselves on our work life balance with quarterly days of care!" Already. We also have "Hybrid Working at Arm" details. Could be considered Schedule? Not exactly schedule but maybe we could put under Benefits? It's about working arrangement. Could be considered as part of Benefits? Might be okay to include as a

under Benefits? But the instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Hybrid Working is specific content. But we don't have a heading for hybrid working in allowed list. Could we put under Benefits? Might be a stretch. Could we create a Schedule section? The posting does not specify schedule like "full-time" etc. Hybrid working is about flexibility, not schedule. Might be better to omit Schedule section. We also have "Accommodations at Arm" etc. That's like EEO/accommodation boilerplate; should be removed. Also "Equal Opportunities at Arm" boilerplate; remove. Thus final HTML:

About the role

Are you ready for a new and exciting challenge? If you are a self-motivated design engineer with expertise in micro-architecture, logic design and ARM IP’s, system protocols and looking to make a difference in an innovative and inclusive team, you’ve come to the right place!

Responsibilities

• Collaborate with the project team to understand and review the architecture and develop the build specifications.
• Writing micro-architecture specifications, developing the RTL, fixing bugs, and running various design checks.
• Collaborate with the verification team to review test plans and help debug build issues.
• Partner with the performance analysis team to evaluate and improve system performance.
• Work with backend implementation team to help with floor planning, writing constraints, and timing closure.
• Contribute to developing and enhancing the design methodologies used by the team.
• Guide and support other members of the team as needed to enable the successful completion of project activities.
• Balance other opportunities such as working with Project Management on activities, plans, and schedules.

Requirements

• Bachelors or Master’s degree in Computer Science or Electrical/Computer Engineering or a similar related field
• 7+ years experience working in design of complex compute subsystems or SoCs
• Strong knowledge of digital hardware design and Verilog HDL.
• Thorough understanding and experience of the current design techniques for complex SoC development.
• Experience developing and integrating subsystems for PCIe, DDR/LPDDR, HBM, UCIe, Ethernet
• Experience creating design specifications and developing RTL for SoC projects and compute platforms
• Experience in Static design checks, including CDC, RDC, X-Propagation, Linting
• Experience with Perl, Python or other scripting language

Nice to have:

• Experience with ARM-based designs and/or ARM System Architectures
• Experience with SystemVerilog and verification methodologies – UVM/OVM/e
• Experience leading small teams or projects
• Experience or knowledge in the following areas:
• Synthesis and timing analysis
• Power management techniques
• DFT and physical implementation
But note we have nested
inside

then

. Might be okay but better to keep as
with sub-items using
• and nested
  . The "Nice to have:" could be a

  then a

  . That's fine. Now Benefits:

  Benefits

  • competitive base salary
  • annual bonus
  • RSUs
  • 401k matching
  • excellent PTO allowance
  • family bonding time
  • competitive benefits
  • quarterly days of care
  Pay:

  Pay

  Salary Range: $161,500-$218,500 per year

  Make sure no extra sections. Output only HTML fragment. Check for any duplicated lines: we removed boilerplate. Check that we didn't repeat job title as heading. Good. Check that we didn't include Job ID etc. Check that we preserved all substantive info: we included intro, responsibilities, required skills, nice to have, benefits, pay. We omitted hybrid working, accommodations, equal opportunity, etc. That's per instruction to remove boilerplate. Hybrid working might be considered not boilerplate but it's not in allowed headings; we could maybe include under Benefits as a bullet? But it's not a benefit per se; it's work arrangement. Could we add a bullet under Benefits: "Hybrid working flexibility"? Might be okay but not explicitly stated as benefit. The posting says "Hybrid Working at Arm" with details. Could be considered a benefit. But to be safe, maybe we can add a

  under Benefits describing hybrid working? However instruction: Prefer a few substantive sections over many thin ones. Adding a paragraph under Benefits is okay. But we must not invent content. We can include hybrid working details as a

  under Benefits? That would be adding content not originally under Benefits but we are just placing it there; still preserving info. That's acceptable. Let's add after benefits list a

  with hybrid working details. Hybrid Working at Arm: "Arm’s approach to hybrid working is designed to create a working environment that supports both high performance and personal wellbeing. We believe in bringing people together face to face to enable us to work at pace, whilst recognizing the value of flexibility. Within that framework, we empower groups/teams to determine their