Senior Post-Silicon Validation Engineer

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to parse the posting. Content: - Intro: "Come break new-ground in Post-Silicon Validation with our diverse, engineering-centric team! This is a rare opportunity to join the Chandler Post-Silicon Validation team. Our team validates and characterizes outstanding Arm SoC processors and enables customers to ramp their world changing products. As a Post-Silicon Validation Engineer, you join a hard-working group of engineers testing the limits the most sophisticated next-generation Arm processors." That's about the role. So we can have

About the role

with paragraph(s) containing that. - Responsibilities: bullet list: "Develop and enable system-level stress workloads on Linux and Bare-Metal SW environments!Collaborate with post-silicon validation team to leverage test content to characterize silicon at the system level.Debug and resolve system issues and bugsDevelop test plans and implement tests for characterizing silicon at the system level." We need to separate bullet points. The text has no punctuation between items, but we can split by capital letters? Actually they are concatenated with no spaces after exclamation? Let's parse: "Develop and enable system-level stress workloads on Linux and Bare-Metal SW environments!Collaborate with post-silicon validation team to leverage test content to characterize silicon at the system level.Debug and resolve system issues and bugsDevelop test plans and implement tests for characterizing silicon at the system level." We can separate by periods? Actually there is exclamation after environments! then "Collaborate..." then period after level. then "Debug..." then period after bugs. then "Develop test plans..." So we can treat each sentence as a bullet. - Required Skills and Experience: list of items: "Shown experience in pre-silicon and post-silicon validation.Passion for continuous improvement as you develop and apply outstanding validation practices to your workShown software engineering skills including, C/C++, ARM assembly, python, and scripting languagesSolid understanding of silicon process technology with respect to power and performanceExcel in debugging system and silicon issues using scopes, logic-analyzers, debuggers, and other advance debug technicsStrive to achieve wining solutions while you build positive relationships which are founded upon mutual trust, respect for others, open communication and sharing of information and successListen to different perspectives, evaluate, persuade, and carefully craft your work to deliver impactful resultsCandidates must hold a Bachelor’s Degree or equivalent experience, or a Master’s Degree or equivalent experience in Computer Science or Electrical Engineering." Again concatenated. We need to split into bullet points. Likely each sentence separated by period (or maybe no spaces). We'll split by period and then trim. Let's extract sentences: 1. Shown experience in pre-silicon and post-silicon validation. 2. Passion for continuous improvement as you develop and apply outstanding validation practices to your work 3. Shown software engineering skills including, C/C++, ARM assembly, python, and scripting languages 4. Solid understanding of silicon process technology with respect to power and performance 5. Excel in debugging system and silicon issues using scopes, logic-analyzers, debuggers, and other advance debug technics 6. Strive to achieve wining solutions while you build positive relationships which are founded upon mutual trust, respect for others, open communication and sharing of information and success 7. Listen to different perspectives, evaluate, persuade, and carefully craft your work to deliver impactful results 8. Candidates must hold a Bachelor’s Degree or equivalent experience, or a Master’s Degree or equivalent experience in Computer Science or Electrical Engineering. We can treat these as bullet points under Requirements or Qualifications? The heading "Required Skills and Experience" could map to Requirements or Qualifications. We have sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each. We have "Required Skills and Experience" which is basically requirements. Could put under Requirements. Also there is "Nice To Have" Skills and Experience: list. We also have "In Return:" describing culture behaviors: list of values: Partner and customer focus, Teamwork and communication, Creativity and innovation, Team and personal development, Impact and influence, Deliver on your promises. That's like Benefits? Actually it's cultural values, maybe could be Benefits? But Benefits section is for tangible benefits like salary, health, etc. The posting includes Salary Range: $161,500-$218,500 per year. Also mentions total reward package, accommodations, hybrid working, equal opportunities. Those could be Benefits or other sections. We need to include Pay section if salary is stated. Yes we have salary range. So we will have

Pay

with paragraph containing the salary range and maybe note about total reward. We have Schedule? Not explicitly stated; hybrid working described but not schedule. Could we put hybrid working under Benefits? Or maybe Schedule section if we have schedule info. The posting mentions hybrid working approach but not specific schedule. Since we should not create Schedule unless posting actually states them. It does mention hybrid working but not specific schedule like "full-time", "part-time". Might be considered schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Hybrid working is a work arrangement, could be considered Benefits? Might be better to put under Benefits as a description of flexible work arrangements. However Benefits section is for benefits like health, retirement etc. But we can still include hybrid working under Benefits as a benefit. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Benefits and maybe other info into one Benefits section. We have also "Accommodations at Arm", "Hybrid Working at Arm", "Equal Opportunities at Arm". Those could be part of Benefits or maybe a separate section like "Additional Info". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add custom headings. So we need to fit these into existing headings. We could put Accommodations, Hybrid Working, Equal Opportunities under Benefits (as they are benefits/perks). Or we could put them under About the role? Probably Benefits is appropriate. Skills: we have "Nice To Have" Skills and Experience. That could go under Skills section. Requirements: we have Required Skills and Experience (the list). Could go under Requirements. Qualifications: maybe we could put degree requirement under Qualifications. But we already have degree in Required list. Could split: Requirements for experience, Qualifications for education. But we have degree in the Required list; we could still put it under Qualifications. However we must not duplicate content. We need to preserve all substantive information. So we need to include degree requirement somewhere. If we put it under Requirements, we still satisfy. Qualifications could be omitted if no specific content besides degree? But we could still put degree under Qualifications and keep Requirements for experience/skills. However the degree is also in Required list; we could split the list: experience/skills under Requirements, degree under Qualifications. That would avoid duplication. Let's parse Required list again and separate into experience/skills vs education. Experience/skills items (1-7) are about experience, skills, passion, etc. Item 8 is degree requirement. Thus: - Requirements (

Requirements

) bullet list: items 1-7. - Qualifications (

Qualifications

) bullet list: item 8 (Bachelor’s or Master’s degree in CS or EE). Now Skills section: Nice To Have list. Let's extract Nice To Have items: "Commanding knowledge with process, voltage, and temperature validationExperience with PCIe, CLX, UCIe, and DDR interfacesUnderstanding of system level test and correlation with manufacture testStrong skills related to debug and root-cause of silicon issuesShown time-management skills to prioritize and accomplish your work and will demonstrate excellent verbal and written communication" Again concatenated. Split by capital letters? Let's split by periods? There are no periods. We'll need to infer separate items based on capital letters after no space. Let's manually separate: 1. Commanding knowledge with process, voltage, and temperature validation 2. Experience with PCIe, CLX, UCIe, and DDR interfaces 3. Understanding of system level test and correlation with manufacture test 4. Strong skills related to debug and root-cause of silicon issues 5. Shown time-management skills to prioritize and accomplish your work and will demonstrate excellent verbal and written communication We can treat each as bullet. Now Benefits section: we have "In Return:" list of cultural behaviors, plus Accommodations, Hybrid Working, Equal Opportunities. Also mention total reward package, accommodations email, hybrid working details, equal opportunity statement. We need to include all substantive info. We'll create a Benefits section with paragraphs and maybe a list for the cultural behaviors. We should not include boilerplate like EEO/equal-opportunity? The instruction says remove EEO/equal-opportunity boilerplate. However the Equal Opportunities at Arm paragraph is likely boilerplate. We should remove it. But we need to preserve substantive information; equal opportunity statement is boilerplate, so we can remove it. Similarly accommodation request details might be considered boilerplate? It's specific to Arm's accommodation process; maybe we keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the Equal Opportunities at Arm paragraph. Also the accommodation request details might be considered part of application instructions? It's about accommodations during recruitment; could be considered application instructions? It's not exactly applying but it's about accommodation request. Might be considered part of application instructions? Safer to remove? However the instruction says remove application instructions. The accommodation request is not exactly how to apply, but it's about requesting accommodation. Might be considered part of application process. I'd lean to remove it to be safe. However we might lose substantive info about accommodations. But the instruction says remove application instructions; accommodation request is a type of instruction for candidates needing accommodation. So remove. Hybrid Working description: not exactly application instructions; it's about work arrangement. Could keep. Salary range: we keep. Total reward package: mention that total reward package will be shared during recruitment; that's substantive. Thus Benefits section could include: - Paragraph: "In Return: We are proud to have a set of behaviors that reflect our culture and guide our decisions, defining how we work together to defy ordinary and shape outstanding!" followed by list of behaviors. - Paragraph about hybrid working: description. - Paragraph about total reward package. We should not include the accommodation paragraph. Now Pay section: salary range. Schedule section: not present; we omit. Now About the role: we have intro paragraph. Now Responsibilities: bullet list. Now Requirements: bullet list (experience/skills). Now Qualifications: bullet list (degree). Now Skills: bullet list (nice-to-have). Now Benefits: as described. Now Pay: salary. Now output only HTML fragment. We must use

for headings,

• for lists,

  for prose. We must not repeat job title as heading. We must not include Job ID etc. Now craft HTML. Let's write:

  About the role

  Come break new-ground in Post-Silicon Validation with our diverse, engineering-centric team! This is a rare opportunity to join the Chandler Post-Silicon Validation team. Our team validates and characterizes outstanding Arm SoC processors and enables customers to ramp their world changing products. As a Post-Silicon Validation Engineer, you join a hard-working group of engineers testing the limits the most sophisticated next-generation Arm processors.

  Responsibilities

  • Develop and enable system-level stress workloads on Linux and Bare-Metal SW environments.
  • Collaborate with post-silicon validation team to leverage test content to characterize silicon at the system level.
  • Debug and resolve system issues and bugs