Technical Project Manager

for prose. We need to decide sections. Potential sections: - About the role: could be a paragraph describing the role overview (the "The Role" paragraph). Use

About the role

... . - Responsibilities: list of duties from "What You'll Do" sections: Lead Complex Technical Programs, Drive Project Governance & Execution Excellence, Manage Financial & Resource Performance, Proactively Manage Risk & Change, Lead Supplier & External Partner Execution, Influence Across a Global Organization. Could break into bullet points. - Qualifications: Required qualifications list (Bachelor's degree, 8+ years, etc.) and Preferred qualifications list. - Skills: maybe not needed if we combine with qualifications; but we could have Skills section for technical skills like Jira, Confluence, etc. However the posting includes "Experience with tools such as Jira, Confluence, Microsoft Project, Power BI, Excel, or equivalent platforms." and certifications. Could be Skills. - Benefits: list of benefits: bonus programs, comprehensive health and welfare benefits, a 401(k) plan, exclusive perks, generous employee discount. - Pay: the hiring range: $109,700-$150,875 for Troy, Michigan. Also note that hiring range for other locations may vary. We'll include that. - Schedule: not present, so omit. We must not create sections with filler like "commensurate with experience". We have actual content. We must not repeat job title as heading. We must not include navigation/legal/EEO etc. The posting includes "Living the Bose Essence & Values" etc. That's values description; could be part of About the role or maybe a separate section? But we only have predefined headings; we could include it under About the role as prose. We must preserve all substantive information; not invent or summarize away detail. So we need to include details from the "Living the Bose Essence & Values" section (Tenacity, Ingenuity, Interconnected, Empowered). That's substantive. We could include that as part of About the role or maybe a separate section like "Values". But we only allowed headings from list; we could put it under About the role as prose. We need to ensure we don't miss any substantive info: The role location: Michigan – Bloomfield Hills or Troy. Should be included. Also mention "primary work location of Troy, Michigan". We'll include location in About the role. Also mention "At Bose Corporation, we believe sound is the most powerful force on earth..." That's introductory fluff; maybe we can include as part of About the role? It's substantive but maybe considered boilerplate? It's about company mission; could be included but not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The introductory paragraph about Bose's belief is not boilerplate; it's company description. Might be okay to keep. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that intro as part of About the role. Now produce HTML. Structure:

About the role

...

Responsibilities

• Lead complex automotive engineering programs from ideation and concept exploration through development, driving execution in alignment with defined product development lifecycle phases, technical milestones, and gate requirements.
• Develop and manage integrated project plans encompassing scope, schedule, technical deliverables, resources, budget, risks, dependencies, and milestones.
• Partner closely with Engineering teams to understand technical architecture, requirements, dependencies, validation strategies, and implementation risks.
• Drive execution across software, hardware, systems, validation, product, purchasing, finance, and other cross-functional organizations.
• Establish clear ownership and accountability for project deliverables.
• Drive timely resolution of technical and program-level issues affecting project commitments.
• Establish effective project governance, operating cadence, decision-making processes, and escalation mechanisms.
• Define and monitor meaningful project KPIs and provide objective visibility into project health.
• Lead program reviews, milestone reviews, risk reviews, and executive-level discussions.
• Identify execution gaps and bottlenecks and establish actionable recovery plans.
• Drive consistent project management standards and best practices across programs.
• Champion continuous improvement by identifying opportunities to simplify processes, improve transparency, and increase engineering execution efficiency.
• Manage project financial performance including budget, forecast, actuals, resource demand, external engineering spend, and financial risks.
• Partner with Finance and Engineering leadership to maintain accurate forecasts and clear visibility into financial performance.
• Monitor resource demand versus availability and identify capacity constraints that could impact project commitments.
• Support annual operating planning, quarterly business reviews and ongoing forecast activities.
• Drive financial discipline around project changes, external engineering expenditures, purchase orders, and supplier commitments.
• Understand the connection between technical decisions, project execution, and financial outcomes.
• Proactively manage risk & change: establish disciplined management of project risks, issues, actions, decisions, and dependencies.
• Identify risks early and ensure appropriate mitigation plans, owners, and timelines are established.
• Escalate critical issues with a clear understanding of technical impact, business impact, options, and recommended actions.
• Lead cross-functional resolution of issues affecting cost, schedule, quality, technical performance, or customer commitments.
• Ensure changes in project scope or requirements are evaluated for their downstream technical, resource, schedule, and financial impacts.
• Coordinate execution with engineering suppliers and external service providers supporting software and hardware development.
• Partner with Engineering and Purchasing to establish clear Statements of Work, deliverables, milestones, acceptance criteria, and supplier commitments.
• Monitor supplier performance against technical, schedule, quality, and cost expectations.
• Identify supplier-related risks and drive appropriate recovery and escalation plans.
• Support effective management of external engineering investments.
• Build strong partnerships across geographically distributed engineering teams and business functions.
• Create alignment around priorities, commitments, dependencies, and decisions.
• Influence outcomes without relying solely on organizational authority.
• Translate complex technical and project information into concise, actionable insights.
• Prepare and communicate project health, risks, financial performance, and critical decisions to senior leadership.
• Foster a culture of transparency, accountability, collaboration, and continuous improvement.

Qualifications

lists with headings inside? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? It says use

for section headings (list). Likely they expect only those headings as top-level sections. Inside we can use

and

• . So we can include Required and Preferred as paragraphs. Thus:

  Qualifications

  Required:

  • Bachelor's degree in Engineering, Computer Science, Information Technology, or another related technical discipline.
  • 8+ years of professional experience, including significant experience leading complex engineering or technical programs.
  • Demonstrated experience leading cross-functional engineering programs with multiple teams, stakeholders, and dependencies.
  • Strong understanding of project/program management including scope, schedule, budget, resources, risk, change management, and governance.
  • Experience partnering directly with engineering teams in a product development environment.
  • Demonstrated ability to identify project risks and drive cross-functional resolution.
  • Strong analytical and problem-solving capabilities.
  • Excellent written, verbal, and executive-level communication skills.
  • Ability to manage multiple priorities and drive results within a dynamic global organization.

  Preferred:

  • Experience within automotive, embedded systems, audio, or another complex technology/product development environment.
  • Experience managing programs involving embedded software, hardware, systems engineering, or integrated product development.
  • Experience working with automotive customers and automotive product development processes.
  • Experience managing engineering suppliers, external service providers, and Statements of Work.
  • Experience with engineering budgets, forecasting, resource planning, and external development costs.
  • Experience with tools such as Jira, Confluence, Microsoft Project, Power BI, Excel, or equivalent platforms.
  • PMP, PgMP, Agile/Scrum, SAFe, ASPICE or equivalent certification is a plus.
  • Experience operating within globally distributed engineering organizations.
  Skills: maybe we could separate tools and certifications as Skills. But we already included them in Preferred. Could still have a Skills section for technical skills like Jira, Confluence, etc. However to avoid duplication, maybe we keep them under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Skills into Qualifications. But we have a separate Skills heading allowed; we could omit Skills if we think it's thin. However we have details about tools and certifications; they could be considered Skills. But we already placed them under Preferred. Might be okay. Benefits: list.

  Benefits

  • Bonus programs
  • Comprehensive health and welfare benefits
  • 401(k) plan
  • Exclusive perks designed to support wellbeing
  • Generous employee discount where you can immerse yourself in Bose products and experiences
  Pay:

  Pay

  The hiring range for this position in the primary work location of Troy, Michigan is: $109,700‑$150,875. The hiring range for other Bose work locations may vary.

  We also need to include location maybe in About the role. About the role paragraph: include company intro, role location, description. Let's craft:

  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.