Jobs · Engineering · California

Principal Application Engineer

Marvell Technology · Santa Clara, CA · 4 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Marvell (company description), Your Team, Your Impact, What You Can Expect, Required (What We're Looking For), Expected Base Pay Range, Additional Compensation And Benefit Elements, Interview Integrity, Export control etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove Interview Integrity? That's not boilerplate but maybe considered policy; but it's not a standard section like Benefits, Pay, Schedule. The instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. We have content for: About Marvell (company description) maybe not a section heading but could be "About the role"? Actually "About Marvell" is company overview, not role. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We have: - About the role: could be "What You Can Expect" describing responsibilities. Also "Your Team, Your Impact" maybe part of role description. - Responsibilities: from "What You Can Expect" bullet points. - Requirements/Qualifications/Skills: from "Required What We're Looking For" list. - Benefits: from "Additional Compensation And Benefit Elements". - Pay: from "Expected Base Pay Range (USD)". - Schedule: not present, so omit. We should not repeat job title as heading. No Job ID. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO statement, Interview Integrity, Export control, etc. Also remove "All qualified applicants will receive consideration..." etc. Also remove "Interview Integrity" and export control paragraphs. Also remove "Any applicant who requires a reasonable accommodation..." etc. Also remove "Marvell may be required to obtain export licensing..." etc. Also remove "Except for U.S. citizens..." etc. Also remove "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 part of Pay section but maybe we keep the range and note that it's based on factors? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence as part of Pay section? It's not boilerplate; it's about pay determination. It's substantive. So include. Similarly, "Additional Compensation And Benefit Elements" includes description of benefits; we keep. We need to format using

for section headings. Use
  • for any list of duties/requirements/benefits, and

    for prose. We need to decide which sections to include: About the role (maybe a brief paragraph summarizing role?), Responsibilities (list), Requirements (list), Qualifications (maybe combine with Requirements?), Skills (maybe separate?), Benefits, Pay. We have content: "What You Can Expect" includes responsibilities list. Also "Your Team, Your Impact" includes some description of team and impact; could be part of About the role. "About Marvell" is company overview; maybe not needed as a section per instruction but could be included as "About the role"? But it's about company not role. The instruction says use headings e.g. About the role, Responsibilities, etc. So we should include About the role heading with a paragraph summarizing the role (maybe combine Your Team, Your Impact and What You Can Expect?). But we must not invent or summarize away detail; we can paraphrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not paraphrase or summarize; we should keep the original sentences. However we can keep them as prose under heading. So we can put the paragraphs under About the role heading as is (maybe combine multiple paragraphs). That would preserve detail. Responsibilities: we can extract the bullet points from "What You Can Expect". Those are: - Serve as the primary technical interface for key customers integrating Marvell’s Optical DSP solutions into next-generation AI and datacenter platforms - Drive end-to-end system success, from early design-in through bring-up, validation, and production deployment - Lead complex issue resolution with urgency and precision—problems you solve will have immediate business and customer impact - Shape the future of our products by translating real-world customer challenges into actionable feedback for design and product teams - Operate at the forefront of scale-out architectures, enabling the high-bandwidth, low-latency connectivity required for modern AI workloads - Work hands-on in the lab with high-speed systems, pushing the limits of performance across optical, electrical, and system domains These are duties. Requirements/Qualifications/Skills: from "Required What We're Looking For". The list includes: - Deep understanding of DSP fundamentals, analog/mixed-signal circuits, and high-speed SerDes systems - Strong system-level hardware knowledge, with the ability to debug across multiple domains - Hands-on lab experience with TX/RX validation, high-speed measurement equipment (oscilloscopes, BERTs, VNAs, etc.) - Proven track record of owning and resolving complex technical issues end-to-end - Experience in applications engineering or customer-facing roles supporting advanced semiconductor or system products - Familiarity with optical transceiver architectures and PAM4-based DSP systems - Strong communication skills and ability to influence both customers and internal stakeholders - Knowledge in C and/or Python is a plus - BS in Electrical Engineering with 8–12 years of experience, or MS/PhD with 5+ years We could split into Requirements (experience/education) and Qualifications/Skills (technical skills). But instruction says we can use those headings; we can decide to combine into one section "Requirements" with list. Or we could have separate sections: Requirements, Qualifications, Skills. But we should not create thin sections with little content. Better to have a single "Requirements" section containing all those bullet points. Benefits: from "Additional Compensation And Benefit Elements". The paragraph describes benefits pillars and highlights: employee stock purchase plan with 2-year look back, family support programs, robust mental health resources, recognition and service awards. We should keep that as list? It's prose; we can make a list of highlights. Pay: from "Expected Base Pay Range (USD)". Include the range and the sentence about determination. We should omit sections like Schedule (none). Also omit Interview Integrity, Export control, EEO, accommodation request, etc. Now produce HTML fragment:

    About the role

    Marvell’s semiconductor solutions are the essential building blocks of the data infrastructure that connects our world. Across enterprise, cloud and AI, and carrier architectures, our innovative technology is enabling new possibilities. At Marvell, you can affect the arc of individual lives, lift the trajectory of entire industries, and fuel the transformative potential of tomorrow. For those looking to make their mark on purposeful and enduring innovation, above and beyond fleeting trends, Marvell is a place to thrive, learn, and lead. Your Team, Your Impact Marvell is at the center of the data infrastructure revolution—powering the backbone of cloud, AI, and high-performance computing. Our Optical DSP (ODSP) Applications Engineering team sits at the intersection of silicon, systems, and customers—turning breakthrough technology into real-world deployments at massive scale. You’ll join a team that directly enables next-generation hyperscale data centers, working alongside world-class silicon designers, system architects, and leading cloud customers. This is where cutting-edge PAM4 DSP, advanced process nodes, and high-speed optical interconnects converge to solve some of the hardest problems in scaling AI infrastructure.

    But note we duplicated some sentences; we need to preserve all substantive information, not remove any. The paragraphs above are from About Marvell and Your Team, Your Impact. We should keep them exactly as they appear (maybe with line breaks). We must not omit any detail. So we need to include the full text of those two sections. Let's extract exact text: About Marvell paragraph: "About Marvell Marvell’s semiconductor solutions are the essential building blocks of the data infrastructure that connects our world. Across enterprise, cloud and AI, and carrier architectures, our innovative technology is enabling new possibilities. At Marvell, you can affect the arc of individual lives, lift the trajectory of entire industries, and fuel the transformative potential of tomorrow. For those looking to make their mark on purposeful and enduring innovation, above and beyond fleeting trends, Marvell is a place to thrive, learn, and lead." Your Team, Your Impact paragraph: "Your Team, Your Impact Marvell is at the center of the data infrastructure revolution—powering the backbone of cloud, AI, and high-performance computing. Our Optical DSP (ODSP) Applications Engineering team sits at the intersection of silicon, systems, and customers—turning breakthrough technology into real-world deployments at massive scale. You’ll join a team that directly enables next-generation hyperscale data centers, working alongside world-class silicon designers, system architects, and leading cloud customers. This is where cutting-edge PAM4 DSP, advanced process nodes, and high-speed optical interconnects converge to solve some of the hardest problems in scaling AI infrastructure." We need to keep them as is, but note there is no space between "About Marvell" and the first sentence; it's "About Marvell Marvell’s". That's weird but we keep. Similarly "Your Team, Your Impact Marvell is". We'll keep. Now responsibilities list: we need to put each as
  • . Now requirements list: we need to put each as
  • . Now benefits: we need to list highlights maybe as
    • . The 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 can keep that as prose under Benefits heading, or make list of highlights. The instruction: Use
      • for any list of duties/requirements/benefits, and

        for prose. So benefits is a list; we can make a list of the four pillars and highlights. But we need to preserve all substantive information; we can convert the sentences into list items but must not lose info. Could do:

        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.
        That preserves. Pay section: we need to include the range and the sentence about determination. We have: "Expected Base Pay Range (USD) 154,680 - 231,700, $ 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 as

        Expected Base Pay Range (USD) 154,680 - 231,700, $ per annum. The successful candidate’s starting base pay will be determined based on job-related skills, experience, qualifications, work location

Similar jobs

Principal Application Engineer

Banner Life family of companies | life insuranceFrederick, MD· 3 mo ago
Engineering$145k–$199k/yrapply on careers-bannerlife.icims.com