Chief Product Engineer - Audio Technology

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - Intro paragraph about Bose: "At Bose Corporation, we believe sound is the most powerful force on earth — and for over 60 years, we have been a company built on innovation, excellence, and independence. Privately owned, fiercely customer-focused, and driven by our values, we continue to lead industries and transform lives through sound. Today, Bose Corporation is entering an exciting new era. Across multiple global Business Units and Global Functions, we are shaping the future of audio technology, automotive, luxury, and premium experiences. We invite you to join us in this transformation." That's about the company, could be "About the role"? Actually "About the role" is typical heading for description of role. But we have a "Job Description" heading then description: "The Chief Product Engineer serves as the top technical leader responsible for aligning product engineering with product, intellectual property (IP) and licensing strategies. This role bridges core research and development (R&D) with external commercialization, ensuring that engineered systems are modular, documented, and legally robust for third-party adoption or joint ventures. As the principal technical architect responsible for the creation, protection, and commercial transfer of our proprietary consumer audio and hearables technology. You will ensure that our patented algorithms, hardware / software architectures, and software stacks (e.g., ANC, spatial audio, voice pickup, wireless connectivity) are packaged into robust, modular, and easily integrable Reference Designs or Intellectual Property (IP) blocks for third-party consumer electronics brands and ODMs." That's prose about role. Then "Key Responsibilities" heading then list of responsibilities bullet points (but they are separated by periods? Actually they are separated by periods but each line starts with capitalized phrase and ends with period. We'll treat as list items. List: - Licensing Architecture Strategy: Define and design the technical boundaries of our licensing portfolio (IP blocks, SDKs, reference hardware). Ensure audio technologies are modular and seamlessly integrate into diverse host chipsets (Qualcomm, Bestechnic, MediaTek, etc.). - DSP Platform Integration: Oversee the optimization and integration of audio code libraries across leading wireless audio SoC and DSP platforms (e.g. Cadence Tensilica HiFi DSPs etc.). - Technical Package Delivery: Oversee the development of comprehensive Technical Data Packages (TDPs). This includes golden reference designs, tuning tools and software, comprehensive SDKs, APIs and bit-exact reference models, acoustic design guidelines, DSP code libraries, and documentation for licensee onboarding. - Tuning & Tooling Development: Champion the creation of developer-facing software tools and GUI-based tuning utilities that empower licensees to calibrate ANC, EQ, and spatial audio parameters to their specific acoustic hardware. - Partner Evaluation & Integration Support: Act as the primary technical authority during licensing evaluations. Provide deep-dive technical support, reference tuning, and architectural reviews for tier-1 consumer electronics licensees and manufacturing partners (ODMs). - IP Protection & Compliance: Partner with the Legal and IP teams to identify patentable innovations in hardware, firmware, and acoustic architectures. Develop technical validation methodologies and tools to audit and verify licensee compliance. - Cross-Functional Leadership: Mentor a highly specialized team of audio, DSP, firmware, and hardware engineers, steering their R&D output toward scalable, high-margin licensing platforms rather than single bespoke products. Then "Required Skills & Qualifications" heading then list: - Experience: 12+ years in consumer audio, acoustics, or hearables product development (e.g., TWS earbuds, smart headphones, spatial audio systems), with a heavy emphasis on embedded software and DSP algorithm development. At least 4 years managing software IP delivery, technical transfers, or external licensing integrations. - Algorithm & DSP Mastery: Deep expertise in developing and optimizing real-time audio processing software. This includes fixed-point math optimization, assembly-level vectorization (e.g., NEON, Tensilica instruction extensions), and low-latency scheduling. - Domain Expertise: Domain mastery over core hearable software pillars: Active Noise Cancellation (ANC/biquad design), Spatial Audio/HRTF, Echo Cancellation (AEC), Wind Noise Reduction, and Machine Learning-based Voice Pickup (VPU). Deep understanding of Bluetooth LE Audio/Auracast, microphone arrays (beamforming), and audio codecs (LC3, LDAC, aptX). - Systems & Standards: Strong fluency in C/C++, Python (for modeling), real-time operating systems (RTOS), Bluetooth LE Audio pipelines, Auracast, and standard audio codecs (LC3, AAC, LDAC). - Hardware & Acoustic Context: Solid understanding of how software interacts with physical acoustic constraints, including microphone array geometries, transducer frequency responses, and ADC/DAC latency paths. - Communication & Negotiation Support: Exceptional ability to present highly complex acoustic and software concepts to non-technical business stakeholders, IP attorneys, and external executive teams. - Education: Bachelor’s, Master’s, or Ph.D. in Electrical Engineering, Computer Science, Acoustical Engineering, or a related technical discipline. Then after that: "At Bose, you're inspired to be and do your best and are rewarded for your unique talents! Our compensation is thoughtfully tailored to your skills, experience, education, and location, and goes beyond base salary. The hiring range for this position in the primary work location of Remote, California is: $205,800-$282,900. The hiring range for other Bose work locations may vary. In addition to competitive base pay we offer rewards including bonus programs, comprehensive health and welfare benefits, a 401(k) plan, plus exclusive perks designed to support your wellbeing, and a generous employee discount where you can immerse yourself in our products and experiences." Then more fluff: "We are a proudly independent company—driven by purpose, guided by our values, and united by a belief in the power of sound. As the world leader in audio experiences, we’re creating what’s next—pushing boundaries and delivering transformative sound experiences for people everywhere. Join us and make your next career move a mic-drop. Let’s Make Waves." We need to remove boilerplate: navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. There's no explicit application instructions but the last paragraph is fluff; we might keep some of it if it's substantive? It's more marketing fluff; but we need to preserve ALL substantive information; do NOT invent or summarize away detail. The fluff about being proud independent company etc. is not substantive? It's generic marketing; but maybe we can keep as part of "About the role" or "About the company"? The instruction: "Prefer a few substantive sections over many thin ones." We could combine company overview and role description into an "About the role" section (or maybe "About the company"). We need sections: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have: - About the role / company overview: we have introductory paragraph about Bose and the role description. Could be "About the role". We'll include that. - Responsibilities: we have list under Key Responsibilities. - Requirements / Qualifications: we have "Required Skills & Qualifications". Could split into Requirements and Qualifications? The instruction says we can use headings like Requirements, Qualifications, Skills. We have both experience and skills. Could combine into "Requirements" or "Qualifications". Since they ask to prefer few substantive sections, we could have one section "Requirements" that includes experience, skills, education. Or we could have "Skills" and "Qualifications". But we need to avoid thin sections. Probably better to have one "Requirements" section containing all the bullet points under Required Skills & Qualifications. - Benefits: we have mention of bonus programs, comprehensive health and welfare benefits, a 401(k) plan, exclusive perks, employee discount. That's benefits. So we can include a Benefits section. - Pay: we have hiring range $205,800-$282,900 for Remote, California. Also note that hiring range for other Bose work locations may vary. That's specific pay info. So we should include a Pay section. - Schedule: not mentioned. No schedule info. So we should NOT create a Schedule section. - Skills: we could separate but we already have Requirements covering skills. Might be redundant. We'll keep only Requirements. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to output HTML fragment only, no /, no markdown fences. We need to use

  for each section heading. Then under each heading, we need to put content: either

  for prose, or

  • for lists. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. Let's extract each piece. About the role: Should include the introductory paragraph about Bose and the role description (the Job Description paragraph). Also maybe the sentence "At Bose, you're inspired to be and do your best and are rewarded for your unique talents!"? That's more about culture; but it's before compensation. Might be considered part of About the role or maybe we could include in Benefits? It's about being rewarded; but we have compensation details later. The phrase "At Bose, you're inspired to be and do your best and are rewarded for your unique talents!" is fluffy but still substantive? It's a statement about culture. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. However, we need to avoid filler/placeholder text like "commensurate with experience", "not specified", etc. This is not placeholder. So we can include it. But we need to decide where to put it. Could be part of About the role paragraph. Thus About the role content: Paragraph 1: "At Bose Corporation, we believe sound is the most powerful force on earth — and for over 60 years, we have been a company built on innovation, excellence, and independence. Privately owned, fiercely customer-focused, and driven by our values, we continue to lead industries and transform lives through sound. Today, Bose Corporation is entering an exciting new era. Across multiple global Business Units and Global Functions, we are shaping the future of audio technology, automotive, luxury, and premium experiences. We invite you to join us in this transformation." Paragraph 2: "The Chief Product Engineer serves as the top technical leader responsible for aligning product engineering with product, intellectual property (IP) and licensing strategies. This role bridges core research and development (R&D) with external commercialization, ensuring that engineered systems are modular, documented, and legally robust for third-party adoption or joint ventures. As the principal technical architect responsible for the creation, protection, and commercial transfer of our proprietary consumer audio and hearables technology. You will ensure that our patented algorithms, hardware / software architectures, and software stacks (e.g., ANC, spatial audio, voice pickup, wireless connectivity) are packaged into robust, modular, and easily integrable Reference Designs or Intellectual Property (IP) blocks for third-party consumer