Senior Principal Digital IC Design Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description of role and maybe company overview. The posting includes "Your Team, Your Impact" and description of role. So we can put that under About the role.
- Responsibilities: bullet list of duties: "Design, develop, implement, verify, and document micro-architecture and RTL for complex power management integrated circuits. Work closely with system and chip architects to design industrial quality implementations. Participate in the full design development cycle, end-to-end, from writing micro-architecture docs, RTL coding, specifications of timing, closely work with design verification teams to review test plans and execution of test, ability to bring up block tests on silicon during lab testing, and maintenance of designed blocks and reusable IPs. Produce comprehensive block uArchitecture and register Specs. Schedule detailed reviews with cross-functional teams Evaluate and participate in improving design and verification methodologies. Supervise or mentor other digital design engineers."
We need to split into list items.
- Requirements: maybe education and experience: "Bachelor’s degree in Computer Science, Electrical Engineering or related fields and 12+ years of related professional experience. Master’s degree in Electrical Engineering or related fields with 10+ years of experience. or PhD in EE or ECE or related fields with 5+ years of experience."
- Qualifications: maybe domain expertise: "Extensive experience in Verilog/SystemVerilog, Synthesis, STA, low power design, Spyglass and Quality checks of the implemented RTL for LINT, CDC. Hands on experience in scripting language such as Perl/Python. Proven track record of delivering production-quality designs on aggressive development schedules. Domain expertise in 802.3 standards and Serdes design is a plus. Background in Digital Signal Processing, Error Correction codes and physical layer protocols through hands on prior experience is a plus."
- Skills: maybe combine with qualifications? But we can separate: Skills could be "Verilog/SystemVerilog, Synthesis, STA, low power design, Spyglass, CDC checks, Perl/Python scripting". However we already have those in qualifications. Might be okay to have Skills section listing technical skills.
- Benefits: The posting mentions "Marvell is committed to providing exceptional, comprehensive benefits..." and details: employee stock purchase plan with 2-year look back, family support programs, robust mental health resources, recognition and service awards. Also mentions bonus and equity plans, new hire equity grant, annual equity refreshers. So we can include Benefits section with those items.
- Pay: "Expected Base Pay Range (USD) 182,360 - 273,200, $ per annum". Also mention that starting base pay determined based on skills etc. So we can include Pay section with that range.
- Schedule: Not mentioned. No schedule info. So we should NOT include Schedule section.
We must not include boilerplate like EEO, export control, interview integrity, etc. Remove those.
We must not repeat job title as heading. Not needed.
We must not include Job ID/requisition numbers.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "employee stock purchase plan with a 2-year look back", "family support programs to help balance work and home life", "robust mental health resources to prioritize emotional well-being", "recognition and service awards to celebrate contributions and milestones". Also mention bonus and equity plans, new hire equity grant, annual equity refreshers.
We also need to keep the line about "The successful candidate’s starting base pay will be determined based on job-related skills, experience, qualifications, work location and market conditions. The expected base pay range for this role may be modified based on market conditions." That's substantive.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML fragment with headings and appropriate - or
.
We need to decide which content goes into which section.
Let's outline:
About the role
In this role you’ll be a member of the Data Center Engineering business group. Our group owns the digital design of high performance mixed signal ICs used in high speed interconnects in hyperscaler data centers. These chips implement advanced digital signal processing algorithms and protocol processing to meet demanding performance, speed, power and latency requirements of the interconnects that power the communication in AI clusters.
Your Team, Your Impact ... maybe combine with above? Actually "Your Team, Your Impact" is a heading in original but we can't use headings other than those listed. We can incorporate that text into About the role paragraph.
We could also include description of Marvell company overview? Might be considered "About the role"? The instruction says use headings e.g. About the role, Responsibilities... So we can put company overview under About the role as well.
Thus About the role paragraph(s) could include both Marvell description and role description.
Now Responsibilities: list items.
We need to break the responsibilities into separate bullet points.
Original responsibilities paragraph: "Design, develop, implement, verify, and document micro-architecture and RTL for complex power management integrated circuits. Work closely with system and chip architects to design industrial quality implementations. Participate in the full design development cycle, end-to-end, from writing micro-architecture docs, RTL coding, specifications of timing, closely work with design verification teams to review test plans and execution of test, ability to bring up block tests on silicon during lab testing, and maintenance of designed blocks and reusable IPs. Produce comprehensive block uArchitecture and register Specs. Schedule detailed reviews with cross-functional teams Evaluate and participate in improving design and verification methodologies. Supervise or mentor other digital design engineers."
We can split into logical bullets:
- Design, develop, implement, verify, and document micro-architecture and RTL for complex power management integrated circuits.
- Work closely with system and chip architects to design industrial quality implementations.
- Participate in the full design development cycle, end-to-end, from writing micro-architecture docs, RTL coding, specifications of timing, closely work with design verification teams to review test plans and execution of test, ability to bring up block tests on silicon during lab testing, and maintenance of designed blocks and reusable IPs.
- Produce comprehensive block uArchitecture and register specifications.
- Schedule detailed reviews with cross-functional teams.
- Evaluate and participate in improving design and verification methodologies.
- Supervise or mentor other digital design engineers.
Now Requirements: education/experience.
We can list as bullet points:
- Bachelor’s degree in Computer Science, Electrical Engineering or related fields and 12+ years of related professional experience.
- Master’s degree in Electrical Engineering or related fields with 10+ years of experience.
- PhD in EE or ECE or related fields with 5+ years of experience.
Now Qualifications: maybe list the extensive experience items.
We could list:
- Extensive experience in Verilog/SystemVerilog, Synthesis, STA, low power design, Spyglass and Quality checks of the implemented RTL for LINT, CDC.
- Hands‑on experience in scripting language such as Perl/Python.
- Proven track record of delivering production‑quality designs on aggressive development schedules.
- Domain expertise in 802.3 standards and Serdes design is a plus.
- Background in Digital Signal Processing, Error Correction codes and physical layer protocols through hands‑on prior experience is a plus.
Now Skills: maybe we could separate technical skills but we already listed many. Could combine Qualifications and Skills but we need to follow instruction: use sections only when posting has real specific content. We have content for both Qualifications and Skills; we can split: Qualifications could be education/experience? Actually we already used Requirements for education/experience. Qualifications could be the experience/skill requirements. Skills could be specific technical skills. But we might duplicate. Better to treat Requirements as education/experience, Qualifications as experience/skill requirements, Skills as maybe soft skills? Not given. Could omit Skills if no distinct content. But we have technical skills listed; we could put them under Skills and keep Qualifications for experience like "Proven track record..." etc. However the posting says "What We're Looking For" includes both education/experience and technical skills. So we could map:
- Requirements: education/experience.
- Qualifications: extensive experience in Verilog..., hands-on scripting, proven track record.
- Skills: domain expertise in 802.3, Serdes, DSP, error correction, physical layer protocols (these are plus). But they are also qualifications.
Given the instruction to prefer few substantive sections over many thin ones, maybe we combine Qualifications and Skills into one section called "Qualifications" (or "Requirements") but we already have Requirements for education/experience. Could have Requirements (education/experience) and Qualifications (technical experience). That seems reasonable.
Thus we will have:
Requirements
education/experience bullets
Qualifications
technical experience bullets
We can omit Skills section.
Now Benefits: list items.
Benefits paragraph: "Marvell is committed to providing exceptional, comprehensive benefits that support our employees at every stage - from internship to retirement and through life’s most important moments. Our offerings are built around four key pillars: financial well-being, family support, mental and physical health, and recognition. Highlights include an employee stock purchase plan with a 2-year look back, family support programs to help balance work and home life, robust mental health resources to prioritize emotional well-being, and a recognition and service awards to celebrate contributions and milestones. We look forward to sharing more with you during the interview process."
Also earlier: "This role is eligible to participate in Marvell's bonus and equity plans, including a new hire equity grant and annual equity refreshers, ensuring you are rewarded for your contributions and remain invested in the company's long-term success."
Thus Benefits bullets:
- Employee stock purchase plan with a 2‑year look back.
- Family support programs to help balance work and home life.
- Robust mental health resources to prioritize emotional well‑being.
- Recognition and service awards to celebrate contributions and milestones.
- Eligibility to participate in Marvell's bonus and equity plans, including a new hire equity grant and annual equity refreshers.
Now Pay: include range and note about determination.
Pay paragraph: "Expected Base Pay Range (USD) 182,360 - 273,200, $ per annum. The successful candidate’s starting base pay will be determined based on job-related skills, experience, qualifications, work location and market conditions. The expected base pay range for this role may be modified based on market conditions."
We can put that in a .
Now we must not include Schedule section.
Now ensure we removed boilerplate: EEO, export control, interview integrity, etc.
Now produce HTML.
Check for any repeated content: we must preserve all substantive info. Did we miss any? Let's review original text for any other substantive info not covered:
- About Marvell paragraph: we included in About the role.
- "Your Team, Your Impact In this role you’ll be a member of the Data Center Engineering business group..." we included.
- Responsibilities: we covered.
- What We're Looking For: we split into Requirements (education/experience) and Qualifications (technical experience). Did we capture "Extensive experience in Verilog/SystemVerilog, Synthesis, STA, low power design, Spyglass and Quality checks of the implemented RTL for LINT, CDC." yes.
- "Hands on experience in scripting language
- or
. We need to decide which content goes into which section. Let's outline:
About the role
In this role you’ll be a member of the Data Center Engineering business group. Our group owns the digital design of high performance mixed signal ICs used in high speed interconnects in hyperscaler data centers. These chips implement advanced digital signal processing algorithms and protocol processing to meet demanding performance, speed, power and latency requirements of the interconnects that power the communication in AI clusters.
Your Team, Your Impact ... maybe combine with above? Actually "Your Team, Your Impact" is a heading in original but we can't use headings other than those listed. We can incorporate that text into About the role paragraph. We could also include description of Marvell company overview? Might be considered "About the role"? The instruction says use headings e.g. About the role, Responsibilities... So we can put company overview under About the role as well. Thus About the role paragraph(s) could include both Marvell description and role description. Now Responsibilities: list items. We need to break the responsibilities into separate bullet points. Original responsibilities paragraph: "Design, develop, implement, verify, and document micro-architecture and RTL for complex power management integrated circuits. Work closely with system and chip architects to design industrial quality implementations. Participate in the full design development cycle, end-to-end, from writing micro-architecture docs, RTL coding, specifications of timing, closely work with design verification teams to review test plans and execution of test, ability to bring up block tests on silicon during lab testing, and maintenance of designed blocks and reusable IPs. Produce comprehensive block uArchitecture and register Specs. Schedule detailed reviews with cross-functional teams Evaluate and participate in improving design and verification methodologies. Supervise or mentor other digital design engineers." We can split into logical bullets: - Design, develop, implement, verify, and document micro-architecture and RTL for complex power management integrated circuits. - Work closely with system and chip architects to design industrial quality implementations. - Participate in the full design development cycle, end-to-end, from writing micro-architecture docs, RTL coding, specifications of timing, closely work with design verification teams to review test plans and execution of test, ability to bring up block tests on silicon during lab testing, and maintenance of designed blocks and reusable IPs. - Produce comprehensive block uArchitecture and register specifications. - Schedule detailed reviews with cross-functional teams. - Evaluate and participate in improving design and verification methodologies. - Supervise or mentor other digital design engineers. Now Requirements: education/experience. We can list as bullet points: - Bachelor’s degree in Computer Science, Electrical Engineering or related fields and 12+ years of related professional experience. - Master’s degree in Electrical Engineering or related fields with 10+ years of experience. - PhD in EE or ECE or related fields with 5+ years of experience. Now Qualifications: maybe list the extensive experience items. We could list: - Extensive experience in Verilog/SystemVerilog, Synthesis, STA, low power design, Spyglass and Quality checks of the implemented RTL for LINT, CDC. - Hands‑on experience in scripting language such as Perl/Python. - Proven track record of delivering production‑quality designs on aggressive development schedules. - Domain expertise in 802.3 standards and Serdes design is a plus. - Background in Digital Signal Processing, Error Correction codes and physical layer protocols through hands‑on prior experience is a plus. Now Skills: maybe we could separate technical skills but we already listed many. Could combine Qualifications and Skills but we need to follow instruction: use sections only when posting has real specific content. We have content for both Qualifications and Skills; we can split: Qualifications could be education/experience? Actually we already used Requirements for education/experience. Qualifications could be the experience/skill requirements. Skills could be specific technical skills. But we might duplicate. Better to treat Requirements as education/experience, Qualifications as experience/skill requirements, Skills as maybe soft skills? Not given. Could omit Skills if no distinct content. But we have technical skills listed; we could put them under Skills and keep Qualifications for experience like "Proven track record..." etc. However the posting says "What We're Looking For" includes both education/experience and technical skills. So we could map: - Requirements: education/experience. - Qualifications: extensive experience in Verilog..., hands-on scripting, proven track record. - Skills: domain expertise in 802.3, Serdes, DSP, error correction, physical layer protocols (these are plus). But they are also qualifications. Given the instruction to prefer few substantive sections over many thin ones, maybe we combine Qualifications and Skills into one section called "Qualifications" (or "Requirements") but we already have Requirements for education/experience. Could have Requirements (education/experience) and Qualifications (technical experience). That seems reasonable. Thus we will have:
Requirements
- education/experience bullets
Qualifications
- technical experience bullets
. Now we must not include Schedule section. Now ensure we removed boilerplate: EEO, export control, interview integrity, etc. Now produce HTML. Check for any repeated content: we must preserve all substantive info. Did we miss any? Let's review original text for any other substantive info not covered: - About Marvell paragraph: we included in About the role. - "Your Team, Your Impact In this role you’ll be a member of the Data Center Engineering business group..." we included. - Responsibilities: we covered. - What We're Looking For: we split into Requirements (education/experience) and Qualifications (technical experience). Did we capture "Extensive experience in Verilog/SystemVerilog, Synthesis, STA, low power design, Spyglass and Quality checks of the implemented RTL for LINT, CDC." yes. - "Hands on experience in scripting language