Portfolio Technical Program Manager - FNV3.x Cabin Climate Control and Heated Seats
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
- About the role: The initial description about TPP, vision, what you'll do? Could be "About the role". We'll put that as About the role
with paragraphs summarizing the intro (but must preserve all substantive info, not summarize away detail). However we cannot invent or summarize away detail; we need to preserve all substantive information. That means we cannot paraphrase or condense? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should keep the details, not omit them. But we can still use paragraphs to contain the text; we just shouldn't summarize or leave out details. So we can copy the relevant sentences into
elements. Thus we need to extract the substantive content and place under appropriate headings. We need sections: About the role, Responsibilities (What You'll Do), Requirements (You'll have...), Qualifications (maybe Education?), Skills (maybe technical skills?), Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. Let's map: - About the role: The first paragraphs describing TPP vision, role purpose. That's substantive. - Responsibilities: The "What You'll Do" bullet list (actually sentences). That's responsibilities. - Requirements: The "You'll have..." list (education, experience, etc.) That's qualifications/requirements. - Qualifications: Might overlap with Requirements; but we can treat "You'll have..." as Requirements, and "Even better, you may have..." as Preferred qualifications (maybe Skills). However we have separate headings: Qualifications, Skills. Could put "You'll have..." under Requirements, and "Even better..." under Skills or Preferred Qualifications. But we need to decide. Given the allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: intro. - Responsibilities: What You'll Do. - Requirements: You'll have... (mandatory). - Qualifications: Even better, you may have... (preferred). - Skills: maybe we could extract specific skills from those lists (like Jira proficiency, stakeholder management, risk identification, etc.) but those are already in Requirements/Qualifications. Could combine but we need to avoid thin sections. Perhaps we can put Skills under Requirements? But we need to follow instruction: include a section ONLY when posting has real specific content for it. If we put Skills but it's just repeating content, maybe it's okay as long as we have content. However we risk duplication. Better to assign: - Requirements: mandatory qualifications (education, years experience, etc.) - Skills: specific abilities (Jira, stakeholder management, risk identification, etc.) from the "You'll have..." list that are skill-based. But the "You'll have..." includes both experience and skills. Could split. Alternatively, we could have only About the role, Responsibilities, Requirements, Benefits, Pay. And skip Qualifications and Skills if they'd be thin. But we have content for qualifications (preferred) and skills (maybe). Let's see if we can make them substantive. We have "Even better, you may have..." list of preferred experiences: direct experience with Cabin Climate, Heated Seats, HVAC controls, etc. That's substantive. We also have "You may not check every box..." encouraging apply. Thus we could have: - About the role - Responsibilities - Requirements (mandatory) - Preferred Qualifications (but heading Qualifications is allowed) - Skills (maybe we can put the skill-based items from Requirements? Might be redundant.) Better to follow typical structure: Requirements (education/experience), Qualifications (preferred), Skills (technical skills). But we need to ensure not to create empty sections. Let's extract content: Intro (About the role): "Your Vision. Ford's Future. Technology Platform Programs (TPP). Seeking an innovative challenge? Ford's new Technology Platform Programs (TPP) team is reimagining vehicle electrical architecture and software platforms, pivoting to a streamlined, scalable, platform-first strategy, and we need your talent to drive this vision. At TPP, you'll be instrumental in simplifying software by driving Ford's minimum complexity vision, boosting quality and speed by enabling faster, higher-quality software delivery, optimizing programs to make vehicle execution significantly more efficient, and scaling solutions by leading cross-functional strategies for broad impact across our vehicle lineup. TPP is where bold ideas transform into real-world breakthroughs that define the future of Ford. Join us and drive innovation! In this position... Success in this role requires a TPM who operates with execution discipline, technical curiosity, and strong cross-functional coordination. You will support feature-level planning and governance, connect feature deliverables to vehicle and platform milestones, and use data-driven practices to identify risks early, track progress, and drive accountability. You will communicate technical and program information clearly to help teams make decisions, remove blockers, and maintain alignment. The ideal candidate has experience supporting product delivery involving hardware, embedded software, vehicle systems, validation, and release readiness, and is comfortable working across Jira-based execution tracking, technical reviews, and program milestone discussions" That's a lot; we can keep as paragraphs. Responsibilities (What You'll Do): list of bullet-like sentences each starting with a verb. We'll put each as
- .
Requirements (You'll have...): list of bullet-like sentences: Bachelor’s degree..., 5+ years..., Demonstrated experience..., Proficiency using Jira..., Experience creating..., Ability to identify risks..., Strong stakeholder management..., Experience supporting scope..., Ability to define measurable success metrics..., Working knowledge..., Ability to work through ambiguity..., Preferred: direct experience... (maybe this belongs to Qualifications). We'll separate.
Qualifications (Even better, you may have...): list of preferred experiences.
Skills: maybe we can extract from Requirements the skill-based items: Proficiency using Jira, Ability to identify risks, Strong stakeholder management, Ability to define measurable success metrics, Working knowledge of vehicle systems integration, Ability to work through ambiguity, etc. But those are already in Requirements. To avoid duplication, maybe we just not include Skills section; we can put skill items under Requirements. But the instruction says we can have few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have headings defined; we can still use them but we need to ensure each has content.
We could do:
- About the role
- Responsibilities
- Requirements (mandatory)
- Qualifications (preferred)
- Benefits
- Pay
- Schedule (maybe not present? The posting mentions hybrid with requirement to be onsite four or more days per week. That's schedule info. So we can include Schedule.)
Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to omit Job ID etc. No mention.
Now we need to format.
We'll produce:
- Own TPM execution support for Cabin Climate and Heated Seats features within the FNV3.x Platform, ensuring delivery plans, dependencies, risks, and milestone readiness are clearly tracked.
- Create and maintain feature-level roadmaps and execution plans that reflect OKRs, quality priorities, capacity constraints, and program timing commitments. ... etc for each bullet.
- Bachelor’s degree in Computer Science, Electrical Engineering, Computer Engineering, Systems Engineering, Mechanical Engineering, or a related technical field.
- 5+ years of experience in technical program management, product delivery, systems engineering, software development, embedded systems, vehicle systems, or related technical delivery roles.
- Demonstrated experience supporting cross-functional feature delivery with hardware, embedded software, vehicle systems, platform milestones, validation, release, and quality dependencies.
- Proficiency using Jira or equivalent tools to manage work, dependencies, dashboards, readiness tracking, reports, and execution transparency.
- Experience creating and maintaining feature roadmaps or execution plans aligned to objectives, milestones, capacity, quality priorities, and changing business needs.
- Ability to identify risks early, communicate them clearly, support mitigation plans, and escalate when timing, quality, or delivery outcomes are at stake.
- Strong stakeholder management skills with experience building alignment and communicating effectively across engineering and cross-functional audiences.
- Experience supporting scope management, change control, impact assessments, and tradeoffs across scope, cost, time, and quality.
- Ability to define measurable success metrics and use data-driven insights to improve execution, risk management, and feature delivery performance.
- Working knowledge of vehicle systems integration, technical interdependencies, and hardware/software delivery implications.
- Ability to work through ambiguity, prioritize effectively, and reinforce accountability, operating cadence, and customer-focused execution.
- Preferred: direct experience with Cabin Climate, Heated Seats, HVAC controls, thermal comfort features, body electronics, connected vehicle features, vehicle electrical architecture, or Ford platform delivery processes.
- Has successfully supported feature-level TPM work across vehicle systems or embedded software programs, not only single-task project coordination.
- Can translate technical complexity into clear risks, decisions, tradeoffs, and mitigation plans.
- Demonstrates strong Jira discipline, including dependency tracking, dashboards, reporting, risk visibility, and structured feature reviews.
- Shows good judgment in when to escalate, when to align stakeholders, and when to inject urgency to protect delivery outcomes.
- Balances customer experience, engineering reality, program timing, and quality priorities without losing clarity on commitments.
- Familiar with Seat Assembly product development and release.
- Able to read electrical schematics, perform DT comparison and working knowledge of Electrical Systems Integration.
- Experience with the technical implementation details of Electrical and Software vehicle program GPDS deliverables.
- Has credibility with technical teams and can contribute meaningfully to discussions involving system integration, embedded software, hardware readiness, validation, and release dependencies.
- Immediate medical, dental, vision and prescription drug coverage
- Flexible family care days, paid parental leave, new parent ramp-up programs, subsidized back-up childcare and more
- Family building benefits including adoption and surrogacy expense reimbursement, fertility treatments, and more
- Vehicle discount program for employees and family members and management leases
- Tuition assistance
- Established and active employee resource groups
- Paid time off for individual and team community service
- A generous schedule of paid holidays, including the week between Christmas and New Year’s Day
- Paid time off and the option to purchase additional vacation time
About the role
... (multiple paragraphs maybe)
Responsibilities
Requirements
Qualifications
Benefits
Pay
This position is a salary grade 8 and ranges from $99,100-$166,200. Final determination of salary grade will be based on candidate's skills and experience, and base salary will be set within the applicable range according to job scope, responsibility and competitive market value. Internal applicants: moving into this role may result in an adjustment to your current compensation based on the posted pay range for this role, taking into consideration your qualifications and other relevant factors. For more information on salary and benefits, click here: